Bug #8103

Crash on boot with two monitors (Xorg 1.14)

Added by Alexander Pyhalov about 1 year ago. Updated 11 months ago.

Status:NewStart date:2017-04-25
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Difficulty:Medium Tags:needs-triage

Description

I've just got crash while booting system (likely, on Xorg startup), when 1 external monitor was attached to notebook.

> $C
ffffff0004c95a50 drm_gem_handle_create+0xb4(ffffff01931e0940, ffffff0190b87ac0, ffffff0004c95b48)
ffffff0004c95a80 intel_user_framebuffer_create_handle+0x26(ffffff018e92e3e8, ffffff01931e0940, ffffff0004c95b48)
ffffff0004c95ae0 drm_mode_getfb+0xa4(6c00000000, ffffff018769e080, ffffff0004c95b30, ffffff01931e0940, 202083, ffffff018e0d23b0)
ffffff0004c95c20 drm_ioctl+0x15d(6c00000000, ffffff01931e0940, c01c64ad, fffffd7fffdffc60, 202083, ffffff018e0d23b0)
ffffff0004c95cc0 drm_sun_ioctl+0xf7(6c00000000, c01c64ad, fffffd7fffdffc60, 202083, ffffff018e0d23b0, ffffff0004c95ea8)
ffffff0004c95d00 cdev_ioctl+0x39(6c00000000, c01c64ad, fffffd7fffdffc60, 202083, ffffff018e0d23b0, ffffff0004c95ea8)
ffffff0004c95d50 spec_ioctl+0x60(ffffff0198ca9400, c01c64ad, fffffd7fffdffc60, 202083, ffffff018e0d23b0, ffffff0004c95ea8, 0)
ffffff0004c95de0 fop_ioctl+0x55(ffffff0198ca9400, c01c64ad, fffffd7fffdffc60, 202083, ffffff018e0d23b0, ffffff0004c95ea8, 0)
ffffff0004c95f00 ioctl+0x9b(b, c01c64ad, fffffd7fffdffc60)
ffffff0004c95f10 sys_syscall+0x17a()

Notebook has driver/graphics/ (from 23 April).

History

#1 Updated by Gordon Ross 11 months ago

Is this still reproducible? If not, let's close it.

#2 Updated by Alexander Pyhalov 11 months ago

We bumped Xorg, with xorg 1.18.4 it is not reproducible.

#3 Updated by Gordon Ross 11 months ago

OK. What version of Xorg (etc.) was running when it crashed?

#4 Updated by Alexander Pyhalov 11 months ago

Xorg 1.14.7.

#5 Updated by Alexander Pyhalov 11 months ago

As it's no longer reproducible, perhaps, really just close it?

#6 Updated by Gordon Ross 11 months ago

Well, if a user program can make this driver crash, that's arguably a "real" bug.
Just not sure when we'll get to looking at it...

Also available in: Atom