kernel update screwed my system
Hi, I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine. I'm used to having to recompile my Nvidia graphics driver, and reconfigure vmware whenever I get a new kernel like this. Now the problem I seem to have is with my on-board NIC. In the past I have used Nvidia's nvnet kernel module to support the CK804 network interface, but this now seems to be screwed. Has anyone else noticed this behaviour? Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did. Any hints/tips on how I might fix this would be greatly appreciated. Sys details: Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64 Yours, Jon -- Jonathan Brooks (Ph.D.) Research Fellow PaIN Group, Department of Physiology Anatomy & Genetics Le Gros Clark Place, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: 01865-282654 fax: 01865-282656
Okay please ignore my previous email - a hard reboot fixed it(?). God know why. Cheers, The-boy-who-cried-wolf Jonathan Brooks wrote:
Hi,
I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine.
I'm used to having to recompile my Nvidia graphics driver, and reconfigure vmware whenever I get a new kernel like this. Now the problem I seem to have is with my on-board NIC. In the past I have used Nvidia's nvnet kernel module to support the CK804 network interface, but this now seems to be screwed. Has anyone else noticed this behaviour?
Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did.
Any hints/tips on how I might fix this would be greatly appreciated.
Sys details:
Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64
Yours,
Jon
-- Jonathan Brooks (Ph.D.) Research Fellow PaIN Group, Department of Physiology Anatomy & Genetics Le Gros Clark Place, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: 01865-282654 fax: 01865-282656
Jonathan Brooks wrote:
Okay please ignore my previous email - a hard reboot fixed it(?). God know why.
I had the same experience last year when a security update to my 9.3 system included a kernel upgrade. The problem, I think, was that the modules got moved into the active directory when I upgraded the kernel, and it took a while for me to notice that some services were dying when they restarted. I had forgotten to reboot my computer, and the old kernel was trying to load the new modules. A reboot loaded and started the new kernel, and everything worked fine after that. John Perry
Hi Jonathan, * On Thu, May 25, 2006 at 12:57 PM (+0100), Jonathan Brooks wrote:
I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine.
I noticed such a strange behaviour at my system, too. I am using SuSE 10.0 x86_64, kernel vanilla-2.6.16.18 on an AMD Athlon X2 4800+, EPOX 9NPA+ Ultra (nForce4 Ultra chipset): Sometimes it happens that I don't have onboard sound, network and USB support after booting up. As far as I found out (it hasn't occured often enough to let me have a systematic look for the failure): - just a "reboot" doesn't seem to help. After booting up, the failure will be there again. - but, like it happened to you, "shutdown" and "power on" has solved it whenever it happend. - just doing a "/etc/rc.d/boot.coldplug restart" seems to fix it without rebooting or shutting down - a few seconds after entering this command, the devices seem to come up normally. I am not absolutely sure, but it also seems that it rather happens after the system was "hard powered off" (powered off using the power supplys's switch on the computer's rear side), but, as I said before, I haven't investigated it systematically, so I cannot say if this really triggers it.
Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did.
Any hints/tips on how I might fix this would be greatly appreciated.
Sys details:
Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64
Our systems are indeed quite similar (same CPU series, same chipset, same distribution version). The main difference seems to be the kernel version. So perhaps you could try to restart "coldplug" if it happens again and see whether it helps. If so, it will be a strong indication that we are really experiencing the same problem. Best regards, Steffen
participants (3)
-
John E. Perry -
Jonathan Brooks -
Steffen Moser