Re: [SLE] 8.1 - Kernel panic, install support non-existent
See forwarded msg. below. -------- Original Message --------
He should try to mount his (hopefully) reiserfs partitions with option barrier=none. A update kernel is in progress.
The kernels in ftp.suse.com:/pub/people/mantel/test have the barrier feature removed. He should use one of them and report back if it solves the problem for him. We're still trying to verify that this is really the cause of the spontaneous freezes reported on some systems.
On Thu, 31 Oct 2002, Michael Hasenstein wrote:
See forwarded msg. below.
-------- Original Message --------
He should try to mount his (hopefully) reiserfs partitions with option barrier=none. A update kernel is in progress.
The kernels in
ftp.suse.com:/pub/people/mantel/test
have the barrier feature removed. He should use one of them and report back if it solves the problem for him. We're still trying to verify that this is really the cause of the spontaneous freezes reported on some systems.
What does it look like to mount barrier=none? Is this just as good as installing a new kernel? Mostly because I don't want to go through this hastle right now, but I too am having the kernel panic problems. Preston
On Thu, 31 Oct 2002, Preston Crawford wrote:
What does it look like to mount barrier=none? Is this just as good as installing a new kernel? Mostly because I don't want to go through this hastle right now, but I too am having the kernel panic problems.
Add this option to the line in /etc/fstab. For example, if by default it is "defaults", change it to "defaults,barrier=none". Michael
On Fri, 1 Nov 2002, Michael Hasenstein wrote:
On Thu, 31 Oct 2002, Preston Crawford wrote:
What does it look like to mount barrier=none? Is this just as good as installing a new kernel? Mostly because I don't want to go through this hastle right now, but I too am having the kernel panic problems.
Add this option to the line in /etc/fstab. For example, if by default it is "defaults", change it to "defaults,barrier=none".
Do you have more background on this? I mean, does this potentially cause any problems? Do I need to do this on all partitions (I have one hard drive using reiserfs and a second drive for data using ext3)? Just making sure before I do it. Preston
Preston Crawford wrote:
Do you have more background on this? I mean, does this potentially cause any problems? Do I need to do this on all partitions (I have one hard drive using reiserfs and a second drive for data using ext3)? Just making sure before I do it.
this is a reiserfs feature/option only
I have this message repeating over and over agian in messages and warn in /var/logs: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[0], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[1], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[2], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[3], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[4], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[5], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[6], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[8], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[9], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[A], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[B], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[C], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[D], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[E], disabling event Both logs are 130some megs and there are many backups of them. What do I do to stop this?
try booting with option acpi=off (enter at the lilo prompt) Bob Rea wrote:
I have this message repeating over and over agian in messages and warn in /var/logs: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[0], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[1], disabling event
On Wednesday 30 October 2002 1:17 am, you wrote:
try booting with option acpi=off (enter at the lilo prompt)
Bob Rea wrote:
I have this message repeating over and over agian in messages and warn in /var/logs: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[0], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[1], disabling event
I use grub, it was the default. How do I handle this in grub? -- Bob Rea mailto:gapetard@stsams.org http://www.petard.us Freedom is only privilege extended unless enjoyed by one and all --Billy Bragg
Bob Rea wrote:
On Wednesday 30 October 2002 1:17 am, you wrote:
try booting with option acpi=off (enter at the lilo prompt)
Bob Rea wrote:
I have this message repeating over and over agian in messages and warn in /var/logs: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[0], disabling event Nov 1 03:17:49 gandalf kernel: ACPI-0906: *** Error: Acpi_ev_gpe_dispatch: No handler or method for GPE[1], disabling event
I use grub, it was the default. How do I handle this in grub?
The same way.. pass it at the boot prompt or add it to /boot/grub/menu.list Jim
On Friday 01 November 2002 21:12, Michael Hasenstein wrote:
Add this option to the line in /etc/fstab. For example, if by default it is "defaults", change it to "defaults,barrier=none".
I think I've solved my kernel panic problem. Installed Mantel's latest build! Two major fixes in the Mantel build included: - Fix error handling in acl-ext3: Users triggerable error may panic the kernel if the FS error behavior is set to panic. - work around severe bug in older VIA southbridges I'm not sure what the first one entails, though I use ext3. But the second one definitely affected me. Now running 8.1 for over 2 hours with no sign of a panic, whereas I couldn't get it to run more than 15 minutes before. I've been running all kinds of programs and such pushing it to the limit, and nothing. If this *is* the case, it may be time to put a patch on YOU that includes some/all of the mantel fixes. But only 2 hours so far. If there's no panic overnight, I'm going to assume the Mantel kernel to be a success. :-P Joe
participants (5)
-
Bob Rea -
Jim Bonnet -
Joe Sullivan -
Michael Hasenstein -
Preston Crawford