NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/52596: [netbsd-8] Another NetBSD 8 panic
The following reply was made to PR port-amd64/52596; it has been noted by GNATS.
From: Dominik Bialy <dmb%yenn.ulegend.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: dmb%yenn.ulegend.net@localhost
Subject: Re: kern/52596: [netbsd-8] Another NetBSD 8 panic
Date: Mon, 9 Oct 2017 23:31:00 +0200
On Fri, Oct 06, 2017 at 05:40:00AM +0000, gnats-admin%netbsd.org@localhost wrote:
> Thank you very much for your problem report.
> It has the internal identification `kern/52596'.
> The individual assigned to look at your
> report is: kern-bug-people.
>
> >Category: kern
> >Responsible: kern-bug-people
> >Synopsis: Another netbsd-8 panic
> >Arrival-Date: Fri Oct 06 05:40:00 +0000 2017
>
Could it be that the problem is ACPI-related?
In NetBSD 6, ACPI 3.0 was working OK on this machine,
but after the upgrade to 8, bootloader was rebooting
when booting the kernel, so I changed settings to
ACPI 2.0 in the BIOS settings, and it worked OK.
I see some ACPI-related functions in the backtrace,
so it made me nod...
I'm asking... if a bug in BIOS or the kernel ACPI code
could lead to this panic?
Dominik
Home |
Main Index |
Thread Index |
Old Index