IBM X31 hangs in "loading hardware driver" with Hardy

Bug #195218 reported by JFC
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Johnathon
linux-source-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My IBM X31 don't boot since I updated from Gutsy to Hardy. It hangs at "loading hardware driver".
I can boot with a 2.6.22-14 kernel but not with 2.6.24 (5, 7 or 8).

JFC (ubuntu-inax)
description: updated
Revision history for this message
Johnathon (kirrus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please attempt to collect and add the following additional information whilst running the problematic kernel, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Revision history for this message
JFC (ubuntu-inax) wrote :

The problem occurs with kernels 2.6.24 but I can't collect any informations with them because they don't boot. Here are the informations when I boot on kernel 2.6.22-14:

jfc@jfc-x31:/tmp$ uname -a
Linux jfc-x31 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

Revision history for this message
JFC (ubuntu-inax) wrote :
Revision history for this message
Johnathon (kirrus) wrote :

Hi,

Could you try to take a photo of the crash, and attach it to this report?

Revision history for this message
JFC (ubuntu-inax) wrote :

I did some more tests with kernel 2.6.24-8.

 - The boot stop at loading hardware driver (photo_1)
 - After 2min30 "fail" is displayed and the boot resumes (photo_2)
 - Then the boot stops at "starting hardware abstraction layer hald"

I waited 15min and nothing happened, but I had access to a console and took uname, dmesg.log and lspci-vvnn.log.

Revision history for this message
JFC (ubuntu-inax) wrote :
Revision history for this message
JFC (ubuntu-inax) wrote :
Revision history for this message
JFC (ubuntu-inax) wrote :

Linux jfc-x31 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

Revision history for this message
JFC (ubuntu-inax) wrote :
Revision history for this message
JFC (ubuntu-inax) wrote :

The I tried to remove the modem driver (which is not free) and rebooted.
- The boot stopped 2min30 at "loading hardware driver" as before
- But it didn't stop at "starting hardware abstraction layer hald" and Gnome started, but I lost the WIFI

I took uname, dmesg-2.log and lspci-vvnn-2.log.

Linux jfc-x31 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

Revision history for this message
JFC (ubuntu-inax) wrote :
Revision history for this message
Johnathon (kirrus) wrote :

Awesome, thanks for all the information!
Confirming and assigning to the Kernel Team.

Changed in linux-source-2.6.22:
assignee: kirrus → ubuntu-kernel-team
status: Incomplete → Confirmed
Revision history for this message
JFC (ubuntu-inax) wrote :

I received a update with a new kernel (2.6.24-10) today and have the same problem with it.

Revision history for this message
Johnathon (kirrus) wrote :

Can you try downloading and using the Hardy Live CD fromhttp://cdimage.ubuntu.com/releases/hardy/ ?
It contains an updated version of the kernel. If you can, please verify if this bug still exists in hardy or not and report back your results. General information regarding this release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

Changed in linux-source-2.6.22:
assignee: ubuntu-kernel-team → kirrus
status: Confirmed → Incomplete
Revision history for this message
JFC (ubuntu-inax) wrote :

Hi,
I downloaded the live CD Hardy alpha 5 and had the same problem.
The kernel included in the live CD is 2.6.24-8 which is not newer the last version I received from the Hardy automatic updates (2.6.24-10).
By the way, this bug is affected to "linux-source-2.6.22 (Ubuntu)" but the problem is with 2.6.24 kernels.

Revision history for this message
Johnathon (kirrus) wrote :

Thanks, re-assigning...

Changed in linux-source-2.6.22:
assignee: kirrus → ubuntu-kernel-team
status: Incomplete → Confirmed
Revision history for this message
marcogoni (cogoni) wrote :

This is a duplicate of another bug (#189398). The problem is due to the new kernel wanting to load the cryptographic modules like padlock_aes and geode_aes. To solve it, just put them in the blacklist. In this way the generic AES module gets loaded and wifi works. Hope it solves your problem too.
marco

PS. see this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/189398

Changed in linux:
status: Confirmed → In Progress
Revision history for this message
Johnathon (kirrus) wrote :

I don't think it is a duplicate, on reading the report (its reporting a completely different error message). JFC, if you want, you can try blacklisting the "padlock_aes" and "geode_aes" modules.

Changed in linux:
status: In Progress → Confirmed
Revision history for this message
Johnathon (kirrus) wrote :

Not in 2.6.22 kernel, invalidating specific package.

Changed in linux-source-2.6.22:
status: New → Invalid
Revision history for this message
marcogoni (cogoni) wrote :

Johnathon,
I am pretty sure it's the same problem.
We'll see.

marco

Revision history for this message
Johnathon (kirrus) wrote :

marcogoni: You don't need to be so agressive-sounding!

JFC, can you please try blacklisting the modules, here's how:
open a terminal, and type "sudo gedit /etc/modprobe.d/blacklist", add the two modules using the following syntax:
blacklist module-name
Save and exit gedit once you're done.

If it works, this is a dup of bug 189398, if not, its a separate issue.

Changed in linux:
assignee: ubuntu-kernel-team → kirrus
status: Confirmed → Incomplete
Revision history for this message
marcogoni (cogoni) wrote :

Not aggressive sounding at all.
It just happens that I have the same hardware and I know what happens, while you decided to contradict me just on the base of pure speculation.

Thanks for your work.

Revision history for this message
Johnathon (kirrus) wrote :

Hello Marcogoni,

Yes, aggressive. To me, "We'll see." in that form is aggressive, though that could be my countries cultural norms coming through ;)

The reason I "decided to contradict" you, was because the error messages appear different. If they had been the same, this would be a duplicate of that one already :)

Revision history for this message
JFC (ubuntu-inax) wrote :

Hi,

Sorry for my late answer but I just come back from skiing ;-)
I blacklisted the two modules (padlock_aes and geode_aes) and :
 - The boot stops (about 10 sec) at "loading hardware driver" but ends with the "OK" status
 - The WIFI is OK now.

I also tested with the new kernel (2.6.24-11) and the result was the same as with the others 2.6.24 kernels.

I tried to boot with the aes modules (not blacklisted) and I had the "fail" status at the "loading hardware driver" step, but I never saw the "Error inserting padlock_aes" message as Marco had.

Revision history for this message
Johnathon (kirrus) wrote :

So it is defiantly related, although not giving the same error. Wierd. Marking as duplicate :)

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.