Bug 688714 - openSUSE 11.4 often crashing during boot (i915 driver, probably) (nomodeset works)
Summary: openSUSE 11.4 often crashing during boot (i915 driver, probably) (nomodeset w...
Status: RESOLVED WONTFIX
: 676330 (view as bug list)
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i686 openSUSE 11.4
: P5 - None : Major with 2 votes (vote)
Target Milestone: ---
Assignee: Egbert Eich
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-20 09:08 UTC by Roger Whittaker
Modified: 2012-08-02 15:54 UTC (History)
6 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
full hwinfo output (416.01 KB, application/octet-stream)
2011-04-20 09:11 UTC, Roger Whittaker
Details
photo 1 of crash (728.36 KB, image/jpeg)
2011-04-20 10:37 UTC, Roger Whittaker
Details
photo 2 of crash (729.16 KB, image/jpeg)
2011-04-20 10:38 UTC, Roger Whittaker
Details
photo 3 of crash (730.52 KB, image/jpeg)
2011-04-20 10:38 UTC, Roger Whittaker
Details
photo 4 of crash (731.11 KB, image/jpeg)
2011-04-20 10:39 UTC, Roger Whittaker
Details
photo 5 of crash (728.39 KB, image/jpeg)
2011-04-20 10:39 UTC, Roger Whittaker
Details
photo 6 of crash (728.24 KB, image/jpeg)
2011-04-20 10:40 UTC, Roger Whittaker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Whittaker 2011-04-20 09:08:08 UTC
On Samsung N-310 netbook, 11.4 often (but not always) crashes when booting.

This looks similar to what I reported with m6 in 
https://bugzilla.novell.com/show_bug.cgi?id=669556

I suspect i915 because:

 - with m6 it always happened just as that driver was loaded and at the point in the boot where the console text size is about to change as a result of mode setting

 - it does not happen if I pass the kernel parameter nomodeset.

# uname -a
Linux dinah.disruptive.org.uk 2.6.37.1-1.2-default #1 SMP 2011-02-21 10:34:10 +0100 i686 i686 i386 GNU/Linux

# hwinfo --gfxcard
09: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.318]
  Unique ID: _Znp.m6RtaS4MHK5
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel 945 GME"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x27ae "945 GME"
  SubVendor: pci 0x144d "Samsung Electronics Co Ltd"
  SubDevice: pci 0xc052 
  Revision: 0x03
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xf0000000-0xf007ffff (rw,non-prefetchable)
  I/O Ports: 0x1800-0x1807 (rw)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  Memory Range: 0xf0300000-0xf033ffff (rw,non-prefetchable)
  IRQ: 16 (9671 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d000027AEsv0000144Dsd0000C052bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: intel
  Driver Info #1:
    XFree86 v4 Server Module: intel
    3D Support: yes
    Extensions: dri
  Config Status: cfg=no, avail=yes, need=no, active=unknown

10: PCI 02.1: 0380 Display controller
  [Created at pci.318]
  Unique ID: ruGf.eqIm9AJgpU7
  SysFS ID: /devices/pci0000:00/0000:00:02.1
  SysFS BusID: 0000:00:02.1
  Hardware Class: graphics card
  Model: "Intel Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x27a6 "Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller"
  SubVendor: pci 0x144d "Samsung Electronics Co Ltd"
  SubDevice: pci 0xc052 
  Revision: 0x03
  Memory Range: 0xf0080000-0xf00fffff (rw,non-prefetchable)
  Module Alias: "pci:v00008086d000027A6sv0000144Dsd0000C052bc03sc80i00"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Primary display adapter: #9
Comment 1 Roger Whittaker 2011-04-20 09:11:50 UTC
Created attachment 425823 [details]
full hwinfo output

Full hwinfo output attached.
Comment 2 Roger Whittaker 2011-04-20 10:37:19 UTC
Created attachment 425847 [details]
photo 1 of crash

Adding some photos of the crash
Comment 3 Roger Whittaker 2011-04-20 10:38:00 UTC
Created attachment 425848 [details]
photo 2 of crash
Comment 4 Roger Whittaker 2011-04-20 10:38:39 UTC
Created attachment 425849 [details]
photo 3 of crash
Comment 5 Roger Whittaker 2011-04-20 10:39:22 UTC
Created attachment 425850 [details]
photo 4 of crash
Comment 6 Roger Whittaker 2011-04-20 10:39:57 UTC
Created attachment 425851 [details]
photo 5 of crash
Comment 7 Roger Whittaker 2011-04-20 10:40:47 UTC
Created attachment 425852 [details]
photo 6 of crash
Comment 8 Christoph Obexer 2011-05-08 08:17:59 UTC
I can confirm that same crash on one of my systems back to 11.3, booting the default kernel deadlocks right away, booting -desktop worked but the system would randomly freeze or crash later.

with the desktop kernel i always got these at boot time:
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
[drm] set up 7M of stolen space
[drm:i915_gem_init_ringbuffer] *ERROR* Ring head not reset to zero ctl ffffffff head ffffffff tail ffffffff start ffffffff
[drm:i915_gem_init_ringbuffer] *ERROR* Ring head forced to zero ctl ffffffff head ffffffff tail ffffffff start ffffffff
[drm:i915_gem_init_ringbuffer] *ERROR* Ring initialization failed ctl ffffffff head ffffffff tail ffffffff start ffffffff
[drm:i915_driver_load] *ERROR* failed to init modeset
i915 0000:00:02.0: PCI INT A disabled
i915: probe of 0000:00:02.0 failed with error -5


10: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_8086_2772
  Unique ID: _Znp.jVvabPUZnPB
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel 945G"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x2772 "945G"
  SubVendor: pci 0x105b "Foxconn International, Inc."
  SubDevice: pci 0x0d4d
  Revision: 0x02
  Memory Range: 0xffe80000-0xffefffff (rw,non-prefetchable)
  I/O Ports: 0xec00-0xec07 (rw)
  Memory Range: 0xd0000000-0xdfffffff (rw,prefetchable)
  Memory Range: 0xffe40000-0xffe7ffff (rw,non-prefetchable)
  IRQ: 16 (11004 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00002772sv0000105Bsd00000D4Dbc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: intel
  Driver Info #1:
    XFree86 v4 Server Module: intel
    3D Support: yes
    Extensions: dri
  Config Status: cfg=no, avail=yes, need=no, active=unknown
(I could attach some of the seemingly random oopses if you whish)
Comment 9 Rafael Wysocki 2011-05-09 19:40:55 UTC
*** Bug 676330 has been marked as a duplicate of this bug. ***
Comment 10 Holger Sickenberg 2011-05-10 08:30:23 UTC
No idea why the older bug is a duplicate of the newer bug, but anyway:

Also here the information:
No, it does not help to boot with "vga=0" - same problems with this option.
Comment 11 Ferdinand Thiessen 2011-05-18 16:27:14 UTC
Could it be, that this bug is the same like this: https://bugzilla.novell.com/show_bug.cgi?id=686451
?
Comment 12 Roger Whittaker 2011-05-18 21:34:20 UTC
Looks like it, yes.
Comment 13 Brian Martin 2011-05-18 23:14:02 UTC
Same problem.  Nomodeset appears to prevent the problem, as does nosmp, which appears to be why the failsafe option works.  I'm working on a dual process, hyperthreaded Atom 330 1.66 GHz processor with I915.
Comment 14 Ferdinand Thiessen 2011-05-19 11:13:28 UTC
(In reply to comment #13)
> Same problem.  Nomodeset appears to prevent the problem, as does nosmp, which
> appears to be why the failsafe option works.  I'm working on a dual process,
> hyperthreaded Atom 330 1.66 GHz processor with I915.

only a hint:. to work around you can use the desktop kernel for the moment untill they fix the problem.
See workaround in Bug 686451.
Comment 15 Paul van Noort 2011-06-04 15:56:40 UTC
i confirm the bug with 11.4 on a hp laptop 
hp compaq 6710b with mentioned chipset
Comment 16 Jeff Mahoney 2012-08-02 15:54:35 UTC
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users.  We're working hard to make openSUSE 12.2 the best openSUSE release yet!