I decided I was going to brave 5.0-CURRENT and give the snapshots
available on current.jp.freebsd.org a try. I found a couple issues with
installation disks (FWIW, I tried it on the lastest snapshot avail on
current.freebsd.org. I got the same results).

Anyway, I go through the standard kern/mfsroot floppy deal and when it
boots the kernel, everything seems to be going fine until I get the
following kernel panic:

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0xffffffab
fault code              = supervisor write, page not present
instruction pointer     = 0x8:0xc0a75ac0
stack pointer           = 0x10:0xc6978f68
frame pointer           = 0x10:0xc6978f80
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupts enabled, resume, IOPL = 0
current process         = 26 (irq10:sn0)
trap number             = 12
panic: page fault

syncing disks...
Uptime: 2s

FWIW, it's 5.0-20010804-JPSNAP #0 available off of current.jp.freebsd.org.
I noticed it said it was in sn0. So being industrious, I interrupted the
autoboot and did:

ok set hint.sn.0.disabled=1

Sure enough, that fixed the kernel panic, but here's the next odd piece,
my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940
dmesg reports that ahc0 is there. The lines from the dmesg are (hand

ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0x5000-0x50ff mem 0x50000000-0x50000fff 
irq 15 at device 15.0 on pci0
device_probe_and_attach: ahc0 attach returned 12

errno.h says ENOMEM is 12, so it seems that something in the ahc driver is
unable to allocate memory.  Dunno where or why, but something is fouling
it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent
snapshot if that would help). Sorry I can't help out any more, but the
debugging tools in the installation disks seem to lacking

Any help?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to