Date: Wed, 15 Aug 2001 23:30:19 -0700 From: unsafe at any speed <erich@ucsd.edu> To: mobile@freebsd.org Subject: panic when copying file on PCMCIA-attached hard drive Message-ID: <3B7B687B.3F30355E@ucsd.edu>
next in thread | raw e-mail | index | archive | help
I have a Thinkpad 560X running 4.4 PRERELEASE (CVSUPed 6 Aug about 23:45
PDT) with a 12GB Hitachi hard drive connected via a Road Warrior
PCMCIA/IDE adapter. The entire disk is one FAT32 slice, mounted as /mnt.
I can read files from this disk all day long, and even rm files, but
when I cp a small file from /mnt to /mnt the system panics with a "fatal
trap 12: page fault while in kernel mode".
I don't know if this broke recently or not, I just started using this
hard drive in FreeBSD.
The entire error message (with possible errors from writing it down) is,
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xe0aa7ffc
fault code = supervisor read, page not present
instruction pointer = 0x8: 0xc017a3d7
stack pointer = 0x10: 0xc762ad0c
frame pointer = 0x10: 0xc762ad1c
code segment = base 0x0, limit 0xfffff type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL=0
current process = 307 (cp)
interrupt mask = none
trap number = 12
panic: page fault
dmesg snippets:
pcic-pci0: <TI PCI-1250 PCI-CardBus Bridge> mem 0x20822000-0x20822fff at
device
2.0 on pci0
pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr
save][CSC pa
rallel isa irq]
pcic-pci1: <TI PCI-1250 PCI-CardBus Bridge> mem 0x20821000-0x20821fff at
device
2.1 on pci0
pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr
save][CSC pa
rallel isa irq]
....
pcic0: <Intel i82365SL-A/B> at port 0x3e0 iomem 0xd0000 on isa0
pcic0: Polling mode
pccard0: <PC Card bus (classic)> on pcic0
pccard1: <PC Card bus (classic)> on pcic0
....
ata3 at port 0x250-0x25f irq 10 slot 0 on pccard0
ad6: 11513MB <HITACHI_DK23AA-12> [23392/16/63] at ata3-master BIOSPIO
kernel configuration has...
device card
device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000
I'm going to try CVSUPing again, update my kernconf according to
whatever changes I figure out from LINT and UPDATING, and build a debug
kernel so I can proceed from there if I still have problems. But I
thought I should raise a flag in the meantime in case this is important,
or in case someone can point out that I did something stupid. :)
Eric Hedstrom
erich@ucsd.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B7B687B.3F30355E>