[Bug 553675] [NEW] Yorkfield/Eaglelake system hang during boot (and no splashscreen)

Bryce Harrington bryce at bryceharrington.org
Thu Apr 1 23:01:58 UTC 2010 

Public bug reported:

[Problem]
With the -16, -18, and -19 kernels, system appears to freeze during boot (becomes completely unresponsive to input) without displaying any boot graphics.  Some errors are shown regarding plymouth failing to start, but the screen clears before I can capture what they say.

I have an old -14 kernel installed, which boots fine.

[Discussion]
This is an unreleased developer box from Intel with the Yorkfield/Eaglelake chipset.  I've been using it during Lucid as a development box, updating it every week or two, but it's been a few weeks since I rebooted.  I updated to the -18 kernel and rebooted, and found that it was not booting except with the -14 kernel.  I updated again to the -19 kernel, but same problem.

The boot process shows it going into KMS (the text on the console gets
small anyway), and the screen refreshes a few times.  I see listings of
error messages printed out (DNS unavailable... NFS mount points couldn't
be mounted... mountall freaking out... something about plymouth
exiting...) and then the system does nothing further.  If I'm quick I
can do vt switches (they're all blank with one cursor blinking), or can
do a ctrl-alt-del to reboot, but if I'm not quick it seems to lock up
hard after a minute or so.  It seems sometimes (every other boot maybe?)
it locks up right away after printing the nfs mountall error messages
and I can only cycle the power to recover.

Booting into recovery mode shows identical behavior (same error messages
too).

Booting with the -14 kernel always works.  (At least, X and gdm comes
up, I've not seen the bootscreen stuff)

The system is connected to a KVM.  I thought perhaps it could be
filtering out the monitor's EDID, however while booted to the -14
kernel, running xrandr --verbose shows the EDID blob there, and
appropriate resolutions listed and so on.

Since one of the big changes in -16 was the introduction of the 2.6.33 drm, I am wondering if it is a drm issue?
--- 
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  bryce     11038 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe7f0000 irq 22'
   Mixer name	: 'Intel G45 DEVELK'
   Components	: 'HDA:10ec0885,10ec0885,00100103 HDA:80862803,80860101,00100000'
   Controls      : 46
   Simple ctrls  : 24
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=6014ea95-bee9-4b30-b6f4-e5bb0891951b
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
IwConfig:
 lo        no wireless extensions.
 
 eth0      no wireless extensions.
MachineType: System Manufacturer To Be Filled By O.E.M. Product Name To Be Filled By O.E.M.
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=cc52aa3c-96d7-4e1e-b2d7-83b10e23c0d7 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:
 
Tags: lucid  regression-potential needs-upstream-testing
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: CGELIA47.86P
dmi.board.asset.tag: BB Asset To Be Filled By O.E.M.
dmi.board.name: BB Name To be filled by O.E.M.
dmi.board.vendor: BB Manufacturer To be filled by O.E.M.
dmi.board.version: BB Version To be filled by O.E.M.
dmi.chassis.asset.tag: Chasis Asset Tag To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Chasis Manufacturer To Be Filled By O.E.M.
dmi.chassis.version: Chasis Version To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCGELIA47.86P:bd05/30/2008:svnSystemManufacturerToBeFilledByO.E.M.:pnProductNameToBeFilledByO.E.M.:pvrSystemVersionToBeFilledByO.E.M.:rvnBBManufacturerTobefilledbyO.E.M.:rnBBNameTobefilledbyO.E.M.:rvrBBVersionTobefilledbyO.E.M.:cvnChasisManufacturerToBeFilledByO.E.M.:ct3:cvrChasisVersionToBeFilledByO.E.M.:
dmi.product.name: Product Name To Be Filled By O.E.M.
dmi.product.version: System Version To Be Filled By O.E.M.
dmi.sys.vendor: System Manufacturer To Be Filled By O.E.M.

** Affects: linux (Ubuntu)
     Importance: High
         Status: New


** Tags: apport-collected

** Summary changed:

- Yorkfield Eaglelake
+ Yorkfield/Eaglelake system hang during boot (and no splashscreen)

** Tags added: apport-collected

** Description changed:

  [Problem]
  With the -16, -18, and -19 kernels, system appears to freeze during boot (becomes completely unresponsive to input) without displaying any boot graphics.  Some errors are shown regarding plymouth failing to start, but the screen clears before I can capture what they say.
  
  I have an old -14 kernel installed, which boots fine.
  
  [Discussion]
  This is an unreleased developer box from Intel with the Yorkfield/Eaglelake chipset.  I've been using it during Lucid as a development box, updating it every week or two, but it's been a few weeks since I rebooted.  I updated to the -18 kernel and rebooted, and found that it was not booting except with the -14 kernel.  I updated again to the -19 kernel, but same problem.
  
  The boot process shows it going into KMS (the text on the console gets
  small anyway), and the screen refreshes a few times.  I see listings of
  error messages printed out (DNS unavailable... NFS mount points couldn't
  be mounted... mountall freaking out... something about plymouth
  exiting...) and then the system does nothing further.  If I'm quick I
  can do vt switches (they're all blank with one cursor blinking), or can
  do a ctrl-alt-del to reboot, but if I'm not quick it seems to lock up
  hard after a minute or so.  It seems sometimes (every other boot maybe?)
  it locks up right away after printing the nfs mountall error messages
  and I can only cycle the power to recover.
  
  Booting into recovery mode shows identical behavior (same error messages
  too).
  
  Booting with the -14 kernel always works.  (At least, X and gdm comes
  up, I've not seen the bootscreen stuff)
  
  The system is connected to a KVM.  I thought perhaps it could be
  filtering out the monitor's EDID, however while booted to the -14
  kernel, running xrandr --verbose shows the EDID blob there, and
  appropriate resolutions listed and so on.
  
- Since one of the big changes in -16 was the introduction of the 2.6.33
- drm, I am wondering if it is a drm issue?
+ Since one of the big changes in -16 was the introduction of the 2.6.33 drm, I am wondering if it is a drm issue?
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
+ Architecture: i386
+ AudioDevicesInUse:
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC0:  bryce     11038 F.... pulseaudio
+ CRDA: Error: [Errno 2] No such file or directory
+ Card0.Amixer.info:
+  Card hw:0 'Intel'/'HDA Intel at 0xfe7f0000 irq 22'
+    Mixer name	: 'Intel G45 DEVELK'
+    Components	: 'HDA:10ec0885,10ec0885,00100103 HDA:80862803,80860101,00100000'
+    Controls      : 46
+    Simple ctrls  : 24
+ DistroRelease: Ubuntu 10.04
+ HibernationDevice: RESUME=UUID=6014ea95-bee9-4b30-b6f4-e5bb0891951b
+ InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
+ IwConfig:
+  lo        no wireless extensions.
+  
+  eth0      no wireless extensions.
+ MachineType: System Manufacturer To Be Filled By O.E.M. Product Name To Be Filled By O.E.M.
+ Package: linux (not installed)
+ ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=cc52aa3c-96d7-4e1e-b2d7-83b10e23c0d7 ro quiet splash
+ ProcEnviron:
+  PATH=(custom, user)
+  LANG=C
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
+ Regression: Yes
+ RelatedPackageVersions: linux-firmware 1.33
+ Reproducible: Yes
+ RfKill:
+  
+ Tags: lucid  regression-potential needs-upstream-testing
+ Uname: Linux 2.6.32-14-generic i686
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
+ dmi.bios.date: 05/30/2008
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: CGELIA47.86P
+ dmi.board.asset.tag: BB Asset To Be Filled By O.E.M.
+ dmi.board.name: BB Name To be filled by O.E.M.
+ dmi.board.vendor: BB Manufacturer To be filled by O.E.M.
+ dmi.board.version: BB Version To be filled by O.E.M.
+ dmi.chassis.asset.tag: Chasis Asset Tag To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chasis Manufacturer To Be Filled By O.E.M.
+ dmi.chassis.version: Chasis Version To Be Filled By O.E.M.
+ dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCGELIA47.86P:bd05/30/2008:svnSystemManufacturerToBeFilledByO.E.M.:pnProductNameToBeFilledByO.E.M.:pvrSystemVersionToBeFilledByO.E.M.:rvnBBManufacturerTobefilledbyO.E.M.:rnBBNameTobefilledbyO.E.M.:rvrBBVersionTobefilledbyO.E.M.:cvnChasisManufacturerToBeFilledByO.E.M.:ct3:cvrChasisVersionToBeFilledByO.E.M.:
+ dmi.product.name: Product Name To Be Filled By O.E.M.
+ dmi.product.version: System Version To Be Filled By O.E.M.
+ dmi.sys.vendor: System Manufacturer To Be Filled By O.E.M.

-- 
Yorkfield/Eaglelake system hang during boot (and no splashscreen)
https://bugs.launchpad.net/bugs/553675
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.

More information about the kernel-bugs mailing list