[opensuse] How to recover from kernel panic ?
Hi, last night I did an online-update of my OpenSuse 11.4. Now it runs into kernel panic so I can't get the system up anymore. The failover entry of grub doesn't help either. It's a rather unspectacular AMD 5200 that worked w/o issues until now. Is there an way to repair the system without a new install? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 06.02.2012 13:47, schrieb Andreas:
Hi, last night I did an online-update of my OpenSuse 11.4. Now it runs into kernel panic so I can't get the system up anymore. The failover entry of grub doesn't help either.
It's a rather unspectacular AMD 5200 that worked w/o issues until now.
Is there an way to repair the system without a new install?
You could boot into text-console mode. Just extend the command line upon boot by "3" Does the kernel panic somehow indicate which module has the problem? Christoph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 06.02.2012 14:27, schrieb Christoph Bartoschek:
Am 06.02.2012 13:47, schrieb Andreas:
Hi, last night I did an online-update of my OpenSuse 11.4. Now it runs into kernel panic so I can't get the system up anymore. The failover entry of grub doesn't help either.
It's a rather unspectacular AMD 5200 that worked w/o issues until now.
Is there an way to repair the system without a new install?
You could boot into text-console mode. Just extend the command line upon boot by "3"
Does the kernel panic somehow indicate which module has the problem?
The background of the screen is a green striped image with the suse logo. There are some text lines that say: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.37.6-0.11-desktop #1 Call Trace: ..... Does this help? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 06.02.2012 15:53, schrieb Andreas:
Am 06.02.2012 14:27, schrieb Christoph Bartoschek:
Am 06.02.2012 13:47, schrieb Andreas:
Hi, last night I did an online-update of my OpenSuse 11.4. Now it runs into kernel panic so I can't get the system up anymore. The failover entry of grub doesn't help either.
It's a rather unspectacular AMD 5200 that worked w/o issues until now.
Is there an way to repair the system without a new install?
You could boot into text-console mode. Just extend the command line upon boot by "3"
Does the kernel panic somehow indicate which module has the problem?
The background of the screen is a green striped image with the suse logo.
There are some text lines that say: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.37.6-0.11-desktop #1 Call Trace: .....
Does this help?
The call trace could help. Add the splash=0 option to the boot menu. It should disable the suse logo. If runlevel 3 does not work. Is S working? Christoph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 06.02.2012 16:20, schrieb Christoph Bartoschek:
Am 06.02.2012 15:53, schrieb Andreas:
Am 06.02.2012 14:27, schrieb Christoph Bartoschek:
Am 06.02.2012 13:47, schrieb Andreas:
Hi, last night I did an online-update of my OpenSuse 11.4. Now it runs into kernel panic so I can't get the system up anymore. The failover entry of grub doesn't help either.
It's a rather unspectacular AMD 5200 that worked w/o issues until now.
Is there an way to repair the system without a new install?
You could boot into text-console mode. Just extend the command line upon boot by "3"
Does the kernel panic somehow indicate which module has the problem?
The background of the screen is a green striped image with the suse logo.
There are some text lines that say: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.37.6-0.11-desktop #1 Call Trace: .....
Does this help?
The call trace could help.
Add the splash=0 option to the boot menu. It should disable the suse logo.
If runlevel 3 does not work. Is S working?
No. Both run into a panic. :( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 06.02.2012 17:06, schrieb Andreas:
Am 06.02.2012 16:20, schrieb Christoph Bartoschek:
Am 06.02.2012 15:53, schrieb Andreas:
Am 06.02.2012 14:27, schrieb Christoph Bartoschek:
Am 06.02.2012 13:47, schrieb Andreas:
Hi, last night I did an online-update of my OpenSuse 11.4. Now it runs into kernel panic so I can't get the system up anymore. The failover entry of grub doesn't help either.
It's a rather unspectacular AMD 5200 that worked w/o issues until now.
Is there an way to repair the system without a new install?
You could boot into text-console mode. Just extend the command line upon boot by "3"
Does the kernel panic somehow indicate which module has the problem?
The background of the screen is a green striped image with the suse logo.
There are some text lines that say: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.37.6-0.11-desktop #1 Call Trace: .....
Does this help?
The call trace could help.
Add the splash=0 option to the boot menu. It should disable the suse logo.
If runlevel 3 does not work. Is S working?
No. Both run into a panic. :(
So I would check whether one can repair the issue with the installation DVD. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andreas -
Christoph Bartoschek