Subject: Re: Panic, i386, memory-related
To: None <netbsd-user@dcf77-zeit.netscum.dyndns.dk>
From: maximum entropy <entropy@tappedin.com>
List: current-users
Date: 02/06/2002 16:04:58
>Date: Wed, 6 Feb 2002 20:20:55 +0100 (CET)
>From: BOUWSMA Beery <netbsd-user@dcf77-zeit.netscum.dyndns.dk>
>
>I had this panic a few months ago and forgot about it after hacking
>around it, but I see it again with a recent -current kernel. This
>is on one particular machine I have two copies of:
>
>BIOS MEMORY MAP (7 ENTRIES):
> addr 0x0 size 0x9fc00 type 0x1
> addr 0x9fc00 size 0x400 type 0x2
> addr 0xf50a2 size 0xaf5e type 0x2
> addr 0x100000 size 0xf00000 type 0x1
> addr 0x100000 size 0xf00000 type 0x1
>WARNING: CAN'T ALLOCATE MEMORY SEGMENT (0x100000/0xf00000/0x1) FROM IOMEM EXTENT MAP!
> addr 0x1000000 size 0x3800000 type 0x1
> addr 0xffff50a2 size 0xaf5e type 0x2
>loading 0x4000-0x9f000 (0x4-0x9f)
>loading 0x2cd000-0x1000000 (0x2cd-0x1000)
>loading 0x2cd000-0x1000000 (0x2cd-0x1000)
>loading 0x1000000-0x1000000 (0x1000-0x1000)
>panic: uvm_page_physload: start >= end
I submitted a patch for this problem in PR port-i386/13399 last July.
After some discussion with Masanori Kanaoka <kanaoka@ann.hi-ho.ne.jp>
the report has languished there, presumably never to be looked at
again...
--
entropy -- it's not just a good idea, it's the second law.