On Sun, 27 Dec 2020, John D. Baker wrote:
> There are a couple of other machines I can check without much trouble.
A HP/Compaq ProLiant ML310g4, an IBM System X 3650, and an HP Pavilion
desktop all have no trouble with the new ACPI.
(For completeness, an HP Pavilion dv2000 laptop still hangs
On Mon, 30 Nov 2020 08:01:41 +0100, Martin Husemann
wrote:
> Just netbsd.gdb would be enough to map the address from your backtrace,
> the address did not match my local build, could have been either hid
> or uid.
Finally got a chance to test this again. Still panics with a very
up-to-date
On Sun, Nov 29, 2020 at 06:23:40PM -0600, John D. Baker wrote:
> On Sun, 29 Nov 2020 17:55:41 - (UTC), chris...@astron.com (Christos
> Zoulas) wrote:
>
> > If you have netbsd.gdb and the crash file it should be simple...
>
> No crashdump as it boots -current via NFS. When next the machine
On Sun, 29 Nov 2020 17:55:41 - (UTC), chris...@astron.com (Christos
Zoulas) wrote:
> If you have netbsd.gdb and the crash file it should be simple...
No crashdump as it boots -current via NFS. When next the machine is
available as a test target I'll see about putting a -current GENERIC
and
In article ,
John D. Baker wrote:
>After updating to the latest -current (9.99.76) with the recent ACPI
>subsystem update, my Dell Optiplex 760 panics attaching acpi0:
Something is overwriting allocated memory. Can you find which free does
this?
Cleanup:
if (Hid)
{
ACPI_FREE
After updating to the latest -current (9.99.76) with the recent ACPI
subsystem update, my Dell Optiplex 760 panics attaching acpi0:
[ 1.030] acpi0 at mainbus0: Intel ACPICA 20201113
[ 1.030] panic: kmem_free(0xb0ea614b6780, 32) != allocated size 0;
overwrote?
[ 1.030] cpu0:
