kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

*** This bug is a duplicate of bug 566379 ***
    https://bugs.launchpad.net/bugs/566379

** Summary changed:

- [i855] (Needs i915.modeset=1) Kernel lockup at boot in 2.6.32-21 and 2.6.32-22
+ 8086:3582 [i855] (Needs i915.modeset=1) Kernel lockup at boot in 2.6.32-21 and 2.6.32-22

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/577444

Title:
  8086:3582 [i855] (Needs i915.modeset=1) Kernel lockup at boot in
  2.6.32-21 and 2.6.32-22

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  On a Dell Latitude D400 laptop, kernel 2.6.32-20 worked fine but the two most recent kernel releases cause a hard lockup on boot.
  2.6.32-21 and 2.6.32-22 both tested and confirmed to lockup on boot every time at the same point.

  I then tried the following two mainline kernels and they work fine.

  2.6.33-020633-generic
  2.6.34-020634rc6-generic

  checkout the /var/log/messages attached to this bug report.
  The easiest way to find the points it hangs on is to search for "imklog" which starts every reboot.

  An example is as follows (which shows the log file stopping abruptly
  due to a hard reset

  
  May  8 08:25:34 simon-laptop kernel: [    0.000000]  modified: 0000000000100000 - 000000001feaa000 (usable)
  May  8 08:25:34 simon-laptop kernel: [    0.000000]  modified: 000000001feaa000 - 0000000020000000 (reserved)
  May  8 08:25:34 simon-laptop kernel: [    0.000000]  modified: 00000000fecMay  8 08:36:48 simon-laptop kernel: imklog 4.2.0, log source = /proc/kmsg started.
  May  8 08:36:48 simon-laptop rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="464" x-info="http://www.rsyslog.com";] (re)start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/577444/+subscriptions