Lenovo X60s freezes during boot sequence

Bug #267541 reported by DSHR
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.27-2-generic

System freezes during bootup sequence during "loading hardware drivers"

Booting without splash gives a hint where the freeze occurs ...

Below is a "correct" dmesg output. When freezing the system stops somewhere after iwl3945, before HDA ...

[ 25.174581] sdhci-pci 0000:15:00.2: SDHCI controller found [1180:0822] (rev 18)
[ 25.174681] sdhci-pci 0000:15:00.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 25.177879] mmc0: SDHCI controller on PCI [0000:15:00.2] using PIO
[ 25.259326] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 25.259597] usbcore: registered new interface driver btusb
[ 25.732917] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[ 25.733017] iwl3945: Copyright(c) 2003-2008 Intel Corporation
[ 25.734237] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 25.734314] iwl3945 0000:03:00.0: setting latency timer to 64
[ 25.734346] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[ 25.829057] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 25.852217] phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 26.058867] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 26.080892] input: TPPS/2 IBM TrackPoint as /class/input/input8
[ 26.089204] cs: IO port probe 0x100-0x3af: clean.
[ 26.091475] cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
[ 26.092601] cs: IO port probe 0x820-0x8ff: clean.
[ 26.093488] cs: IO port probe 0xc00-0xcf7: clean.
[ 26.094659] cs: IO port probe 0xa00-0xaff: clean.
[ 26.182089] iwl3945 0000:03:00.0: PCI INT A disabled
[ 26.298804] HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 26.298892] hda_intel: probe_mask set to 0x1 for device 17aa:2010
[ 26.298982] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 27.431588] Adding 4803392k swap on /dev/sda5. Priority:-1 extents:1 across:4803392k
[ 27.489062] EXT3 FS on sda1, internal journal

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: linux-image-2.6.27-2-generic 2.6.27-2.3 [modified: lib/modules/2.6.27-2-generic/modules.pcimap lib/modules/2.6.27-2-generic/modules.dep lib/modules/2.6.27-2-generic/modules.ieee1394map lib/modules/2.6.27-2-generic/modules.usbmap lib/modules/2.6.27-2-generic/modules.isapnpmap lib/modules/2.6.27-2-generic/modules.inputmap lib/modules/2.6.27-2-generic/modules.seriomap lib/modules/2.6.27-2-generic/modules.alias lib/modules/2.6.27-2-generic/modules.symbols]
ProcCmdLine: root=UUID=78188840-c926-4cc1-adf0-77158e7cd374 ro locale=de_DE
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.27-2.3-generic
SourcePackage: linux

Revision history for this message
DSHR (s-heuer) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi DSHR,

I'm curious if you'd take a look at bug 267002 and bug 263059 . I'm wondering if this might be a possible duplicate of those as I see you also are using the iwl3945 driver. Each comment about some possible workarounds that you may want to try. Please let us know your results. Thanks.

Revision history for this message
DSHR (s-heuer) wrote :

I checked the other bugs and I'm now quiet sure it is not related to the ultrabase. I still experience the problem - even if booting without being docked. I boot without splash so I see the freeze is very near the lines

[ 25.734346] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[ 25.829057] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels

The exact loading of modules seems to be different from boot to boot.

Currently the is a chance of 50% that the system is not going to lockup during boot. I'm going to disable wifi at boot time and see if that helps.
I'll check the new firmware too ...

Revision history for this message
DSHR (s-heuer) wrote :

After upgrading the firmware it took me 3 boots to start the system successfully. After checking the dmesg output below I think that loading the firmware takes place 20 seconds after the lockups. I'll be booting with radio off and see if that helps ...

$ dmesg|grep iwl
[ 34.902570] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[ 34.902658] iwl3945: Copyright(c) 2003-2008 Intel Corporation
[ 34.903591] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 34.903669] iwl3945 0000:03:00.0: setting latency timer to 64
[ 34.903699] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[ 35.018365] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 35.032761] phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 35.304402] iwl3945 0000:03:00.0: PCI INT A disabled
[ 57.900359] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 57.900536] iwl3945 0000:03:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
[ 57.900850] firmware: requesting iwlwifi-3945-1.ucode
[ 58.908662] Registered led device: iwl-phy0:radio
[ 58.909028] Registered led device: iwl-phy0:assoc
[ 58.909297] Registered led device: iwl-phy0:RX
[ 58.910385] Registered led device: iwl-phy0:TX

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi DSHR,

Do you see any improvements with this bug using the newer 2.6.27-3 kernel? Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
DSHR (s-heuer) wrote :

I had a couple of good boots (5-10) and then 2 failures in a row. Switching off Radio does not seem to help. The new kernel makes no difference either. Maybe I should reinstall the system - it has made its way from gutsy to hardy betas and now to intrepid.

I had absolutely no freezes during normal system operation.

Revision history for this message
DSHR (s-heuer) wrote :

As far as I can see, the systems locks during udevadm settle. Any suggestions as how to debug that any further?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.