Current git cannot find root device on x86-64(HP nx6325), NFS broken
Quoted 8 lines · Rafael J. Wysocki
Quoted 7 lines
Hi,
Current mainline (commit
22ae77bc7ac115b9d518d5cbc13d39317079b2b0) can't find the root device (it's handled by statically compiled-insata_sil) and generally causes the "invalid module format" message to appear for all modules loaded from the initrd on my HP nx6325 (the distro is openSUSE 11.1).
Quoted 6 lines
Quoted 4 lines
I don't know which commit might have made this happen, but the breakage was introduced during the last three days (commit
601cc11d054ae4b5e9b5babec3d8e4667a2cb9b5is certainly good). I'll bisect tomorrow if there are no ideas.I bisected "invalid module format" woes to 9cb610d.
My system also fails to load modules from initrd unless 9cb610d is reverted. Something is wrong with the "module: remove the SHF_ALLOC flag on the __versions section" patch.
Larry
Quoted 13 lines · Larry Finger
Quoted 12 lines · Rafael J. Wysocki
Quoted 11 lines
Hi,
Current mainline (commit
22ae77bc7ac115b9d518d5cbc13d39317079b2b0) can't find the root device (it's handled by statically compiled-insata_sil) and generally causes the "invalid module format" message to appear for all modules loaded from the initrd on my HP nx6325 (the distro is openSUSE 11.1).I don't know which commit might have made this happen, but the breakage was introduced during the last three days (commit
601cc11d054ae4b5e9b5babec3d8e4667a2cb9b5is certainly good). I'll bisect tomorrow if there are no ideas.
Quoted 5 lines
Quoted 1 line
I bisected "invalid module format" woes to 9cb610d.
My system also fails to load modules from initrd unless 9cb610d is reverted. Something is wrong with the "module: remove the
SHF_ALLOCflag on the__versionssection" patch.
This is fixed in the current -git, although I had to apply the patch from
http://patchwork.kernel.org/patch/16776/
to fix an Oops on boot.
Thanks,
Rafael
Quoted 8 lines · Rafael J. Wysocki
Quoted 3 lines · Larry Finger
My system also fails to load modules from initrd unless 9cb610d is reverted. Something is wrong with the "module: remove the
SHF_ALLOCflag on the__versionssection" patch.This is fixed in the current -git, although I had to apply the patch from
http://patchwork.kernel.org/patch/16776/
to fix an Oops on boot.
Thanks for the heads-up, particularly on the 16776 patch above. I was in the middle of a bisection to isolate that one.
Do you know anything about a regression that leads to "phy0: Failed to initialize wep: -2" messages? It is the 3rd one that I'm chasing and seems to affect all wireless drivers. For this one, removing and reinserting the driver corrects the problem.
Larry
Quoted 10 lines · Larry Finger
Quoted 8 lines · Rafael J. Wysocki
Quoted 3 lines · Larry Finger
My system also fails to load modules from initrd unless 9cb610d is reverted. Something is wrong with the "module: remove the
SHF_ALLOCflag on the__versionssection" patch.This is fixed in the current -git, although I had to apply the patch from
http://patchwork.kernel.org/patch/16776/
to fix an Oops on boot.
Quoted 7 lines
Thanks for the heads-up, particularly on the 16776 patch above. I was in the middle of a bisection to isolate that one.
Do you know anything about a regression that leads to "phy0: Failed to initialize wep: -2" messages? It is the 3rd one that I'm chasing and seems to affect all wireless drivers. For this one, removing and reinserting the driver corrects the problem.
No, I didn't know about this one. Has it been reported anywhere already?
Rafael
Quoted 8 lines · Rafael J. Wysocki
Quoted 5 lines · Larry Finger
Do you know anything about a regression that leads to "phy0: Failed to initialize wep: -2" messages? It is the 3rd one that I'm chasing and seems to affect all wireless drivers. For this one, removing and reinserting the driver corrects the problem.
No, I didn't know about this one. Has it been reported anywhere already?
Only on the wireless mail list. Once I get the bad commit, I'll post it in LKML.
Larry
Quoted 11 lines · Larry Finger
Quoted 8 lines · Rafael J. Wysocki
Quoted 5 lines · Larry Finger
Do you know anything about a regression that leads to "phy0: Failed to initialize wep: -2" messages? It is the 3rd one that I'm chasing and seems to affect all wireless drivers. For this one, removing and reinserting the driver corrects the problem.
No, I didn't know about this one. Has it been reported anywhere already?
Only on the wireless mail list.
A pointer to the wireless mailing list thread would do too. :-)
Quoted 1 line
Once I get the bad commit, I'll post it in LKML.
OK, thanks.
Best,
Rafael