I experienced an unpleasant side affect with the latest kernel update for SuSE 9.1. One (older Pentium-S system) hangs early in the boot process after installing this update. Rolling back to the version supplied on the installation disks fixed this. The strange thing is, this didn't happen on any of the newer systems update before or afterwards, just this one. I can't find a reason why, but on a second try it resulted in the same behavior. Locked solid, even after waiting for over an hour. Keyboard dead, only responded to the power button. The last lines in the boot log read Setting up network interfaces: lo Any suggestions on how to find out what goes wrong here? Since I only have trusted local users, I'm not so worried about the implications of not having the latest kernel, but sure I would like to know what happened. I'm using the default kernel on this system. Regards, Arjen
Hi, I had the same problem with my server! It took me nearly 3 hours to figure out what was wrong and to roll back to the standard kernel from CD. I found out, that the kernel hangs as soon as the harddrive is mounted with write support! I don't know why.. it makes no sens. I too have an other System where it works perfectly. So SuSE Team! Fix this Bug! Its really anoying!!!!! I wont install the next kernelpatch until its tested and veryfied! I've better things to waste my time on! MFG Daniel Am Donnerstag, 17. Juni 2004 21:43 schrieb Arjen de Korte:
I experienced an unpleasant side affect with the latest kernel update for SuSE 9.1. One (older Pentium-S system) hangs early in the boot process after installing this update. Rolling back to the version supplied on the installation disks fixed this. The strange thing is, this didn't happen on any of the newer systems update before or afterwards, just this one.
I can't find a reason why, but on a second try it resulted in the same behavior. Locked solid, even after waiting for over an hour. Keyboard dead, only responded to the power button. The last lines in the boot log read
Setting up network interfaces: lo
Any suggestions on how to find out what goes wrong here? Since I only have trusted local users, I'm not so worried about the implications of not having the latest kernel, but sure I would like to know what happened. I'm using the default kernel on this system.
Regards, Arjen
Hi,
I had the same problem with my server! It took me nearly 3 hours to figure out what was wrong and to roll back to the standard kernel from CD. I found out, that the kernel hangs as soon as the harddrive is mounted with write support! I don't know why.. it makes no sens. I too have an other System where it works perfectly. So SuSE Team! Fix this Bug! Its really anoying!!!!! I wont install the next kernelpatch until its tested and veryfied! I've better things to waste my time on!
Your anger and dispair understood, but that kernel is tested, and we can't reproduce it here. Unfortunately, you don't even tell us which kernel package you're using, which filesystem types you are mounting, what type of hardware you have built in your box, ... This is a little more complicated than showing a broken "!" key. Thanks, Roman.
In article
Hi,
I had the same problem with my server! It took me nearly 3 hours to figure out what was wrong and to roll back to the standard kernel from CD. I found out, that the kernel hangs as soon as the harddrive is mounted with write support! I don't know why.. it makes no sens. I too have an other System where it works perfectly. So SuSE Team! Fix this Bug! Its really anoying!!!!! I wont install the next kernelpatch until its tested and veryfied! I've better things to waste my time on!
Your anger and dispair understood, but that kernel is tested, and we can't reproduce it here.
Sorry to disappoint you, but I have even had the hang - but not disc related so far as I can tell from surrounding activity - apparently 'mouse' related - on my Acer Travelmate 530 (memory extended to 512Mbytes - otherwise standard release hardware). I am using the Synaptic pad driver. With certain window managers (IceWM and OroboROX ) but not KDE (so far!) the entire system hangs - very occasionally (5/6 times in three days) when moving or clicking the pad. The only recourse is to use the power switch! However, I have had a file system hang (several times reproducibly) when trying to write large files across an NFS mount using a 100Mbit Ethernet. The OS kernel, however, does not appear to hang. If I boot in fail safe mode (ie Disc DMA disabled) then neither form of hanging occurs. I do note, however, that on booting normally at some stage in the boot sequence I see the error message Spurious 8259 interrupt IRQ 7 I hope this may offer a few thoughts! Keith Hopper -- City Desk Waikato University [PGP key available if desired]
Hi, I have a similar problem on one of my machines running SuSE Linux 9.1. The boot process hangs right after fsck has completed and reported all 4 drives as clean. The machine is not completely locked up, the terminal scrolls down when I press Return, it just doesn't continue to boot. Booting in failsafe mode leads to the same result. I have updated another SuSE 9.1 machine which boots up fine. Besides both machines are running 9.1 they are somewhat different, though. Working Machine: P4 3200 with 875P Chipset 1 GB RAM 3ware IDE-RAID controller with 4 drives attached Hardware RAID 10 reiserfs Machine which fails to boot: Athlon 3200 XP with nForce2 Chipset 1 GB RAM 2 IDE drives attached to the mainboard controllers 2 IDE drives attached to a Promise Ultra100TX2 PCI controller Boot device on the Promise controller no RAID all partitions ext3 Best regards, Stefan
Hi, this is excactly the same Problem I had. I had to disable the remount entry in /etc/boot.rootfsck to get the System booting again. Of course nothing wanted to work without write support to the system. But at least I got it up again an could solve the problem after a while. Anyhow.. as soon as I made a mount -n -o remount,rw / the HDD Led was constantly on and the system hanged. Sorry for my angry post yesterday.. I had a long day and came home just to see that my server is broken and I had to spend 3 hours in the cellar to get it working again. A bit frustrating ;o). So anyhow here are some data of my system: PII 266 Mhz Ausu Board (Don't know the Model right now) 128MB Ram 2,5GB HDD (So I can accknowleage the guessing of John with old HDD's) () Voodoo III Graphic Card 2 Networkcards -> One internal one to the DSL Modem My Partitions on the HDD are: 25MB ext3 /boot 512MB swap Swapspace 1,9GB ext3 / Kernelversion was the newest Kernel from YOU. MFG Daniel Am Freitag, 18. Juni 2004 07:20 schrieb Stefan Proels:
Hi,
I have a similar problem on one of my machines running SuSE Linux 9.1. The boot process hangs right after fsck has completed and reported all 4 drives as clean. The machine is not completely locked up, the terminal scrolls down when I press Return, it just doesn't continue to boot. Booting in failsafe mode leads to the same result.
I have updated another SuSE 9.1 machine which boots up fine. Besides both machines are running 9.1 they are somewhat different, though.
Working Machine: P4 3200 with 875P Chipset 1 GB RAM 3ware IDE-RAID controller with 4 drives attached Hardware RAID 10 reiserfs
Machine which fails to boot: Athlon 3200 XP with nForce2 Chipset 1 GB RAM 2 IDE drives attached to the mainboard controllers 2 IDE drives attached to a Promise Ultra100TX2 PCI controller Boot device on the Promise controller no RAID all partitions ext3
Best regards, Stefan
Am Freitag, 18. Juni 2004 07:20 schrieb Stefan Proels:
The boot process hangs right after fsck
From time to time I hear that machines hang after a kernel-update. Why doesn't YOU create a multikernel-system with the old _and_ the new kernel, so you can choose to boot from the old kernel, if the new hangs? The 2nd question is, why there are only rpms to download? Not everyone knows how extract the sources from a rpm-file. If you would like to build your own multikernel-system, to keep the old kernel you have to use something like rpm2cpio kernel-source-2.6.* | \ cpio -i --make-directories --no-absolute-filenames Al
On Jun 18, Al Bogner
Am Freitag, 18. Juni 2004 07:20 schrieb Stefan Proels:
The boot process hangs right after fsck From time to time I hear that machines hang after a kernel-update. Why doesn't YOU create a multikernel-system with the old _and_ the new kernel, so you can choose to boot from the old kernel, if the new hangs?
The 2nd question is, why there are only rpms to download? Not everyone knows how extract the sources from a rpm-file. And not everyone knows how to extract a tar file? I think that this is
I'm about to extend fou4s to backup the old kernel, install the new, and copy the old one back (necessary for /lib/modules). It will also warn if you haven't rebooted after an update. I only have to think about a way, that only the last working kernel is kept, and not the last 10 ;-) But it shouldn't be too hard. pointless ("There will always be a greater idiot"). Markus -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(at)gaugusch.at X Against HTML Mail / \
Hi Markus,
I'm about to extend fou4s to backup the old kernel, install the new, and copy the old one back (necessary for /lib/modules). It will also warn if you haven't rebooted after an update. I only have to think about a way, that only the last working kernel is kept, and not the last 10 ;-) But it shouldn't be too hard.
I'll be happy to update for that!
The 2nd question is, why there are only rpms to download? Not everyone knows how extract the sources from a rpm-file.
And not everyone knows how to extract a tar file? I think that this is pointless ("There will always be a greater idiot").
Yes, there will be, but still it's good practise to keep the old kernel. RedHat always did for me, and there where times when it's needed. Besides - everyone has started at one time and we where happy as hell to not have more stones in our way back then ;-). Greetings, Ralf
Am Freitag, 18. Juni 2004 07:20 schrieb Stefan Proels:
I have a similar problem on one of my machines running SuSE Linux 9.1. The boot process hangs right after fsck has completed and reported all 4 drives as clean.
Here too. If anyone is interested in my hardware details, you can have look at my posting in German, which shows hwinfo and the last working boot.msg - http://lists.suse.com/archive/suse-linux/2004-Jun/2602.html Feedback to SuSE was sent. Al
On Thursday 17 June 2004 14:00, Roman Drahtmueller wrote:
Hi,
I had the same problem with my server! It took me nearly 3 hours to figure out what was wrong and to roll back to the standard kernel from CD. I found out, that the kernel hangs as soon as the harddrive is mounted with write support! I don't know why.. it makes no sens. I too have an other System where it works perfectly. So SuSE Team! Fix this Bug! Its really anoying!!!!! I wont install the next kernelpatch until its tested and veryfied! I've better things to waste my time on!
Your anger and dispair understood, but that kernel is tested, and we can't reproduce it here.
Unfortunately, you don't even tell us which kernel package you're using, which filesystem types you are mounting, what type of hardware you have built in your box, ...
This is a little more complicated than showing a broken "!" key.
Thanks, Roman.
Roman: Several posts in the SuSE Linux English list seem to suggest this is related to machines useing older drives, often with reiserfs, although some users report other FS also hang, but again with older drives (4 - 10 gig ). Probably more related to the chipset than the drive, but I'm guessing here. -- _____________________________________ John Andersen
John Andersen wrote:
On Thursday 17 June 2004 14:00, Roman Drahtmueller wrote:
Hi,
I had the same problem with my server! It took me nearly 3 hours to figure out what was wrong and to roll back to the standard kernel from CD. I found out, that the kernel hangs as soon as the harddrive is mounted with write support! I don't know why.. it makes no sens. I too have an other System where it works perfectly. So SuSE Team! Fix this Bug! Its really anoying!!!!! I wont install the next kernelpatch until its tested and veryfied! I've better things to waste my time on!
Your anger and dispair understood, but that kernel is tested, and we can't reproduce it here.
Unfortunately, you don't even tell us which kernel package you're using, which filesystem types you are mounting, what type of hardware you have built in your box, ...
This is a little more complicated than showing a broken "!" key.
Thanks, Roman.
Roman: Several posts in the SuSE Linux English list seem to suggest this is related to machines useing older drives, often with reiserfs, although some users report other FS also hang, but again with older drives (4 - 10 gig ). Probably more related to the chipset than the drive, but I'm guessing here.
My 4 year old pizza box hangs too after upgrading. It stays forever in the fsck of the root fs (reiserfs). Is there a known workaround already? Rainer
John Andersen wrote:
On Thursday 17 June 2004 14:00, Roman Drahtmueller wrote:
Hi,
I had the same problem with my server! It took me nearly 3 hours to figure out what was wrong and to roll back to the standard kernel from CD. I found out, that the kernel hangs as soon as the harddrive is mounted with write support! I don't know why.. it makes no sens. I too have an other System where it works perfectly. So SuSE Team! Fix this Bug! Its really anoying!!!!! I wont install the next kernelpatch until its tested and veryfied! I've better things to waste my time on!
Your anger and dispair understood, but that kernel is tested, and we can't reproduce it here.
Unfortunately, you don't even tell us which kernel package you're using, which filesystem types you are mounting, what type of hardware you have built in your box, ...
This is a little more complicated than showing a broken "!" key.
Thanks, Roman.
Roman: Several posts in the SuSE Linux English list seem to suggest this is related to machines useing older drives, often with reiserfs, although some users report other FS also hang, but again with older drives (4 - 10 gig ). Probably more related to the chipset than the drive, but I'm guessing here.
My 4 year old pizza box hangs too after upgrading. It stays forever in the fsck of the root fs (reiserfs). Is there a known workaround already? Rainer
I have a two week old machine (Athlon XP 2400+, 512 MB, On-Board VGA and LAN) which hangs after updating to kernel-default-2.6.5-7.75.i586. I have twice installed SuSE 9.1 Pro and after that updated to said kernel, so I'm pretty sure that the new kernel is the cause. As far as I can tell, it dies most often (but not only) when the screen saver is active and I touch the mouse. The screen saver is closed, and in the same instant the machine freezes. If there's any information I can provide for the SuSE team to fix the kernel, please let me know. -- Mit freundlichen Grüßen / Yours sincerely Dipl. Inform. Ralph Seichter HORUS-IT Ahornweg 10 D-57635 Oberirsen Tel +49 2686 987880 Fax +49 2686 987889 http://horus-it.de/
participants (11)
-
Al Bogner -
Arjen de Korte -
Daniel Dewald -
John Andersen -
Keith Hopper -
Markus Gaugusch -
Ralf Ronneburger -
Ralph Seichter -
Roman Drahtmueller -
Stefan Proels -
suse-security＠diplan.de