Bug 706621

This looks like the same problem I'm having (I'll attach an image of the panic shortly).

Upgraded machine to Fedora 15 (final) from DVD image.

Problem occurred with the original kernel version (2.6.38.6-26.rc1.fc15.i686.PAE) and after performing a yum update from a text console (2.6.38.6-27.fc15.i686.PAE).

Problem occurs randomly while using X (with Gnome Shell). Doesn't seem to take long, but isn't entirely consistent.

Adding nomodeset to the kernel command line seems to fix the problem (but I haven't used it for long, so it might just not have happened yet) at the cost of disabling Gnome Shell.

Created attachment 500777 [details]
Screen-photo of panic

Apologies for the photo attachment. Seemed like a more reliable option than trying to type it up manually.

Yes, putting nomodeset in the kernel cmdline does prevent the kernel from panicing but then I can't start up "X" (no /dev/fb0 error). My panics occur only in "X" and always involve the DRM module for the i915 driver. And I need "X". I might add that both fc 13 and 14 are installed and neither have a problem with "X".

My system has now been running with nomodeset for some time, and seems stable. Obviously, I would prefer not to have to use this workaround (I quite like a graphical boot and the new Gnome Shell, neither of which work with this applied, though, unlike floyd's system, X still works for me).

Here's the details of the graphics hardware being used (lspci -vv output).

00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04) (prog-if 00 [VGA controller])
	Subsystem: Hewlett-Packard Company Device 3007
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at cfd00000 (32-bit, non-prefetchable) [size=512K]
	Region 1: I/O ports at 1800 [size=8]
	Region 2: Memory at e0000000 (32-bit, prefetchable) [size=256M]
	Region 3: Memory at cfd80000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: i915

If there's any other information that could be useful, please let me know.

Created attachment 501168 [details]
two lspic outputs for i915 graphics panic

The first lspci output is for a Dell Dimension 310E - both fc 13 and 14 work (with NO special param passed) but not fc 15 - setting the nomodeset param causes a missing /dev/fb0 error even though the device is present).

The second lspci output in the attachment is for a very old asrock 777I65G which works for both "X" and gnome in fc 13 (but ONLY when nomodeset is used or if the kernel is compiled without the DRM module) and in fc 14 without modifying of the kernel params (I haven't installed fc 15 on it yet).
And beginning with fc 14, if the nomodeset param is present, then "X" won't start.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
on 08-28-11 downloaded:       
kernel-2.6.40.3-0.fc15.x86_64.rpm
This fixes the Intel915 DRM bugzilla 706621 panic in fc 15 while in GUI.
The last downloaded kernel was:
vmlinuz-2.6.38.8-32.fc15.x86_64
which had the panic problem.
 
Floyd,

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log)
* output of the dmesg command (best would be after crash and before reboot, if any life remains in your system yet), and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Of course, testing should be done WITHOUT nomodeset.

F15 beta?  Really?

Please reopen if you can still reproduce this with F15 updates.

there have been no problems (panics or otherwise) since kernel-2.6.40.3-0.fc15.x86_64.rpm.
pristine fc16 as well as all updates thus far (last update was on 020112) works also.