On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
/boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
syms=[0x4+0x5540+0x702d|]
snip
embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15
panic: pmap_mapdev: Couldn't
On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
Sorry if this is the second copy, I'm not sure if it went out the first
time or not
On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
/boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
syms=[0x4+0x5540+0x702d|]
snip
On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
Disable acpi. acpi is broken.
I had the same problem until today. If ACPI was enabled, I would get a
panic on boot. I removed MAXMEM from my kernel conf, recompiled, and
On Sun, 2003-01-26 at 19:08, walt wrote:
Steve Kargl wrote:
On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
Is there any reason, on newer motherboards, to need the MAXMEM option?
I don't know. I've always used MAXMEM. Guess it's
time to remove it from my kernel config
In the last episode (Jan 23), Vincent Poy said:
Greetings everyone,
With the latest -CURRENTs ever since atleast September 12, 2002
that I have tested on several different machines ranging from
PII/PIII/PIV Desktop and Notebooks, whenever the following option is
added to the GENERIC
On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
/boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
syms=[0x4+0x5540+0x702d|]
snip
embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15
panic: pmap_mapdev: Couldn't alloc kernel virtual memory
Debugger(panic)
Stopped at
