I've upgraded to Kernel 2.6.5.7-108-default through Yast on SuSE 9.1 which causes the following messages when rebooting: bad: scheduling while atomic! Call trace: [<collcf17>] schedule+0x697/0x6d0 ... many more of the above ... Any suggestions on what might be wrong? Thanks, -- Mark -----Original Message----- From: mafmailbox@earthlink.net Sent: Sep 7, 2004 8:54 PM To: suse-linux-e@suse.com Subject: [SLE] Upgrade to Kernel 2.6.5.7-108-default causes looping error message I'm running SuSE 9.1 on a x386 machine with software RAID for /, swap, /home, etc. formatted as reiserfs. Upgrading to Kernel 2.6.5.7-108-default through Yast causes an endless looping message when I reboot my system after the install. I've tried several variations of installing the system and then upgrading the kernel... I've run mk_initrd and lilo, and have not run mk_initrd and lilo... (I believe Yast now does this after the installation for me.) I have verified that I am running lilo as a boot loader. I have upgraded other packages separately (including mkinitrd), rebooted successfully, and then upgraded the kernel to verify that it was that upgrade that caused the problems... the most recent time with only a minimal install on the machine. After reinstall, I am able to reboot successfully with failsafe. The repeating message scrolls to fast for me to read the message. I am not able to locate it in a log after the next reboot or when rebooting with a rescue disk. Any suggestions on how to proceed, or am I missing something with the Kernel 2.6.5.7-108 upgrade? Thanks, Mark mafmailbox@earthlink.net -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com