system locks up with SuSE 9.3
We have 3 computers with Asus A8V motherboard. 1 has no raid and uses the on board Marvell Gigabit ethernet.... NO problems (driver sk98lin loaded) 2 with raid 0 , when Marvell Gigabit ethernet is used (sk98lin driver) System locks up 3 with raid 1, when Marvell Gigabit ethernet is used (sk98lin driver) system locks up So the right drivers are used, but on the systems with raid (VIA VT8237) the system will hang sooner or later (but within minutes). Wilko -- +------------------------------------------------------------+ | Dr. Wilko Keegstra priv.phone: +31594514153,+31610477915| | Groningen University email: W.Keegstra@rug.nl | | Dept.of Biophys.Chemistry | | Nijenborgh 4 phone: +31503634224 | | 9747 AG GRONINGEN fax : +31503634800 | | The Netherlands | +------------------------------------------------------------+
We have 3 computers with Asus A8V motherboard.
So the right drivers are used, but on the systems with raid (VIA VT8237) the system will hang sooner or later (but within minutes).
Is this with Linux software raid, or some other contraption which makes use of the on-board raid chips? Thanks, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
On Wed, 2005-09-07 at 21:05 +1200, Volker Kuhlmann wrote:
We have 3 computers with Asus A8V motherboard.
So the right drivers are used, but on the systems with raid (VIA VT8237) the system will hang sooner or later (but within minutes).
Is this with Linux software raid, or some other contraption which makes use of the on-board raid chips?
Thanks,
Volker
-- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
It is NOT linux software raid, I used on board VIA VT8237 raid chip to build the raid (from the BIOS). Wilko
Am Mittwoch, 7. September 2005 10:07 schrieb Wilko Keegstra:
We have 3 computers with Asus A8V motherboard. 1 has no raid and uses the on board Marvell Gigabit ethernet.... NO problems (driver sk98lin loaded) 2 with raid 0 , when Marvell Gigabit ethernet is used (sk98lin driver) System locks up 3 with raid 1, when Marvell Gigabit ethernet is used (sk98lin driver) system locks up
So the right drivers are used, but on the systems with raid (VIA VT8237) the system will hang sooner or later (but within minutes).
I have two computers with Asus A8V deluxe mobo, 4 sata (software raid) and 1 ata. Problems when using lftp mirror to get data from this computers after reboot --> Kernel oops in sk98lin. If I made some network traffic (rsync-ed something from another box to the Asus box) before doing the lftp thing, everything was fine and the box was somewhat stable until the next reboot. For more details, see my posts "suse 9.3 - nfs or ftp - freeze" 7.6.2005 in this list and/or "Suse 9.3 und Asus A8V - freeze" 7.6.2005 in "suse-linux" list. Software raid on 4* SATA works fine as long as all disks are found on boot. (Known problem with VT8237, see http://www.heise.de/newsticker/meldung/62189) My solution for the sk98lin problem: Just installed OpenSuse with Kernel 2.6.13, which includes a replacement for the sk98lin: skge. This one works great!! Note: I did a system update from 9.3 to oss10-beta4 and had to change the settings for the network card via yast to use skge instead of sk98lin. Did not test the other stuff yet (NFS, bad block IDE on promise ..) Burkhard
Burkhard Carstens wrote:
Am Mittwoch, 7. September 2005 10:07 schrieb Wilko Keegstra:
We have 3 computers with Asus A8V motherboard. 1 has no raid and uses the on board Marvell Gigabit ethernet.... NO problems (driver sk98lin loaded) 2 with raid 0 , when Marvell Gigabit ethernet is used (sk98lin driver) System locks up 3 with raid 1, when Marvell Gigabit ethernet is used (sk98lin driver) system locks up
So the right drivers are used, but on the systems with raid (VIA VT8237) the system will hang sooner or later (but within minutes).
I have two computers with Asus A8V deluxe mobo, 4 sata (software raid) and 1 ata. Problems when using lftp mirror to get data from this computers after reboot --> Kernel oops in sk98lin. If I made some network traffic (rsync-ed something from another box to the Asus box) before doing the lftp thing, everything was fine and the box was somewhat stable until the next reboot.
For more details, see my posts "suse 9.3 - nfs or ftp - freeze" 7.6.2005 in this list and/or "Suse 9.3 und Asus A8V - freeze" 7.6.2005 in "suse-linux" list.
Software raid on 4* SATA works fine as long as all disks are found on boot. (Known problem with VT8237, see http://www.heise.de/newsticker/meldung/62189)
My solution for the sk98lin problem:
Just installed OpenSuse with Kernel 2.6.13, which includes a replacement for the sk98lin: skge. This one works great!! Note: I did a system update from 9.3 to oss10-beta4 and had to change the settings for the network card via yast to use skge instead of sk98lin.
Did not test the other stuff yet (NFS, bad block IDE on promise ..)
Burkhard
I have 2.6.13 running with 9.3 with the sk98lin driver, worked for all kernel.org kernels previous to 2.6.13. I stuck with sk98lin as the skge driver is new and said not to be as capable(?), besides sk98lin worked from 9.1 to 9.3. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
I have 2.6.13 running with 9.3 with the sk98lin driver, worked for all kernel.org kernels previous to 2.6.13. I stuck with sk98lin as the skge driver is new and said not to be as capable(?), besides sk98lin worked from 9.1 to 9.3.
Only tested suse 9.3 and now openSuse-10-beta4. Never tried vanilla kernel .. As mentioned, sk98lin kind of worked here, too. However, I found a reproducible way to kill the machine. With the skge, this doesn't happen anymore. Performance is acceptable (~70Mbyte/sec) tested with: "netcat -l -p 10001 > /dev/null" on the a8v box and "dd if=/dev/zero bs=4M | netcat a8vbox 10001" on another box. Currently I am backing up my data and preparing for a fresh install of oss-10-beta4. Then I will test the overall stability, especially NFS. greets, Burkhard
Hello All, I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA. --ryan
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup. The video card is probably a PCI-E Quadro FX 4400, btw. -Ken Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
-- Ken Siersma, Software Engineer EKK, Inc. phone: (248) 624-9957 fax: (248) 624-7158 http://www.ekkinc.com -- "Our lives begin to end the day we become silent about things that matter." -MLK Jr.
Ken, I tried as you suggested but the result is the same. Could the RAM be an issue? I know that some systems have issues with Large amounts of RAM. How much RAM did the xw9300 you worked on have? --ryan Ken Siersma wrote:
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup.
The video card is probably a PCI-E Quadro FX 4400, btw.
-Ken
Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
Mine had 8GB. I don't suspect that 8 more would make a difference comapred to my machine, but you may want to try booting with 'mem=1GB' to see if it will at least boot. What are the details of the kernel panic? -Ken Ryan Biltz wrote:
Ken,
I tried as you suggested but the result is the same. Could the RAM be an issue? I know that some systems have issues with Large amounts of RAM. How much RAM did the xw9300 you worked on have?
--ryan
Ken Siersma wrote:
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup.
The video card is probably a PCI-E Quadro FX 4400, btw.
-Ken
Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
-- Ken Siersma, Software Engineer EKK, Inc. phone: (248) 624-9957 fax: (248) 624-7158 http://www.ekkinc.com -- "Our lives begin to end the day we become silent about things that matter." -MLK Jr.
I tried it with mem=1GB..again the result is the same. The kernel panic during failsafe boot shows the following: A page of cryptic code passes (Initializing CPUs) ... Stack: blah blah Call Trace: blah blah Code: blah blah console shuts up.... 0>Kernel Panic - not syncing: Aiee, killing interrupt handler! BTW...the cpus are not 250s they're 272s (dual core). --ryan Ken Siersma wrote:
Mine had 8GB. I don't suspect that 8 more would make a difference comapred to my machine, but you may want to try booting with 'mem=1GB' to see if it will at least boot. What are the details of the kernel panic?
-Ken
Ryan Biltz wrote:
Ken,
I tried as you suggested but the result is the same. Could the RAM be an issue? I know that some systems have issues with Large amounts of RAM. How much RAM did the xw9300 you worked on have?
--ryan
Ken Siersma wrote:
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup.
The video card is probably a PCI-E Quadro FX 4400, btw.
-Ken
Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
I see. I don't think I can help you, because my procs were 250s. Sounds to me like your kernel panic is related to the CPUs. -Ken Ryan Biltz wrote:
I tried it with mem=1GB..again the result is the same. The kernel panic during failsafe boot shows the following:
A page of cryptic code passes (Initializing CPUs) ... Stack: blah blah Call Trace: blah blah Code: blah blah console shuts up.... 0>Kernel Panic - not syncing: Aiee, killing interrupt handler!
BTW...the cpus are not 250s they're 272s (dual core).
--ryan
Ken Siersma wrote:
Mine had 8GB. I don't suspect that 8 more would make a difference comapred to my machine, but you may want to try booting with 'mem=1GB' to see if it will at least boot. What are the details of the kernel panic?
-Ken
Ryan Biltz wrote:
Ken,
I tried as you suggested but the result is the same. Could the RAM be an issue? I know that some systems have issues with Large amounts of RAM. How much RAM did the xw9300 you worked on have?
--ryan
Ken Siersma wrote:
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup.
The video card is probably a PCI-E Quadro FX 4400, btw.
-Ken
Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
-- Ken Siersma, Software Engineer EKK, Inc. phone: (248) 624-9957 fax: (248) 624-7158 http://www.ekkinc.com -- "Our lives begin to end the day we become silent about things that matter." -MLK Jr.
You can try to deactivate dual core in the BIOS. Then you should be able to finish installation and update to the newest SuSE kernel. After that you can reactivate dual core and everything should work fine. Markus Ken Siersma wrote:
I see. I don't think I can help you, because my procs were 250s. Sounds to me like your kernel panic is related to the CPUs.
-Ken
Ryan Biltz wrote:
I tried it with mem=1GB..again the result is the same. The kernel panic during failsafe boot shows the following:
A page of cryptic code passes (Initializing CPUs) ... Stack: blah blah Call Trace: blah blah Code: blah blah console shuts up.... 0>Kernel Panic - not syncing: Aiee, killing interrupt handler!
BTW...the cpus are not 250s they're 272s (dual core).
--ryan
Ken Siersma wrote:
Mine had 8GB. I don't suspect that 8 more would make a difference comapred to my machine, but you may want to try booting with 'mem=1GB' to see if it will at least boot. What are the details of the kernel panic?
-Ken
Ryan Biltz wrote:
Ken,
I tried as you suggested but the result is the same. Could the RAM be an issue? I know that some systems have issues with Large amounts of RAM. How much RAM did the xw9300 you worked on have?
--ryan
Ken Siersma wrote:
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup.
The video card is probably a PCI-E Quadro FX 4400, btw.
-Ken
Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
I tried this...I deactivated dual core in the bios. Rebooted and choose normal startup and the again it locked up. Same spot as last time. No luck. --ryan Markus Jungemann wrote:
You can try to deactivate dual core in the BIOS. Then you should be able to finish installation and update to the newest SuSE kernel. After that you can reactivate dual core and everything should work fine.
Markus
Ken Siersma wrote:
I see. I don't think I can help you, because my procs were 250s. Sounds to me like your kernel panic is related to the CPUs.
-Ken
Ryan Biltz wrote:
I tried it with mem=1GB..again the result is the same. The kernel panic during failsafe boot shows the following:
A page of cryptic code passes (Initializing CPUs) ... Stack: blah blah Call Trace: blah blah Code: blah blah console shuts up.... 0>Kernel Panic - not syncing: Aiee, killing interrupt handler!
BTW...the cpus are not 250s they're 272s (dual core).
--ryan
Ken Siersma wrote:
Mine had 8GB. I don't suspect that 8 more would make a difference comapred to my machine, but you may want to try booting with 'mem=1GB' to see if it will at least boot. What are the details of the kernel panic?
-Ken
Ryan Biltz wrote:
Ken,
I tried as you suggested but the result is the same. Could the RAM be an issue? I know that some systems have issues with Large amounts of RAM. How much RAM did the xw9300 you worked on have?
--ryan
Ken Siersma wrote:
This is interesting, because I recently installed SuSE 9.3 on an xw9300, and did not have a kernel panic in the normal startup. SuSE installed and booted up fine for me, which was a big improvement over 9.2 on that machine. I suggest that you try passing the following options to the normal startup kernel: "3 vga=normal". That should boot into runlevel 3 and boot without any special effects happening on the console. That way you'll see if you are really getting a kernel panic in the normal startup.
The video card is probably a PCI-E Quadro FX 4400, btw.
-Ken
Ryan Biltz wrote:
>Hello All, > > I have successfully installed suse 9.3 on an HP xw9300 >workstation....well...sort of. Once the installation is done the >system reboots. I choose normal startup (SuSE 9.3 professional) >on the GRUB boot loader menu and the system freezes. I reboot >again this time in failsafe mode and I immediately get a kernel >panic. I'm assuming it is the exact error happening during normal >startup just not hidden by the system trying to load the suse >splash screen. Has anyone come accross this? It is a dual >opteron 250 with 16GB of RAM. I forget what the video card is. I >know it is an NVIDIA card worth ~$4000. TIA. > >--ryan > > >
On Wednesday 07 September 2005 20:34, Ryan Biltz wrote:
I tried it with mem=1GB..again the result is the same. The kernel panic during failsafe boot shows the following:
A page of cryptic code passes (Initializing CPUs) ... Stack: blah blah Call Trace: blah blah Code: blah blah console shuts up.... 0>Kernel Panic - not syncing: Aiee, killing interrupt handler!
Well - i hope you can see yourself that "blah blah" this is not a very useful bug report. -Andi
Hi Ryan, We have the same type of machines but currently with one processor in each, however, we could not boot without SMP kernel. On our machines we boot using "pci=noacpi numa=off" and it helps so far. Good luck! Ödön On Wed, 2005-09-07 at 09:50 -0700, Ryan Biltz wrote:
Hello All,
I have successfully installed suse 9.3 on an HP xw9300 workstation....well...sort of. Once the installation is done the system reboots. I choose normal startup (SuSE 9.3 professional) on the GRUB boot loader menu and the system freezes. I reboot again this time in failsafe mode and I immediately get a kernel panic. I'm assuming it is the exact error happening during normal startup just not hidden by the system trying to load the suse splash screen. Has anyone come accross this? It is a dual opteron 250 with 16GB of RAM. I forget what the video card is. I know it is an NVIDIA card worth ~$4000. TIA.
--ryan
--
Ödön Farkas
participants (9)
-
Andi Kleen -
Burkhard Carstens -
Ken Siersma -
Markus Jungemann -
Ryan Biltz -
Sid Boyce -
Volker Kuhlmann -
Wilko Keegstra -
Ödön Farkas