The fault seems to be reproducable.
mount /cdrom
find /cdrom -type f -exec cat \{\} >/dev/null \; -ls
and pop it goes. Same stack trace. We could do a try-this-game this weekend (up
to
then I'm covered in work) if that would be helpfull.
Let me know what information you need.
Nick
On Tue, 16 Mar 1999, Nick Hibma wrote:
>
> In case someone who is interested in the following panic:
>
> Occurred under a lightly loaded system that was not doing anything apart
> from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512).
> Kernel current as of yesterday.
> No core file is available unfortunately.
>
>
> panic: vm_fault: fault on nofault entry, addr: c35c6000
> (blabla about debugger)
> > show registers
> cs 0x8
> ds 0x10
> es 0x10
> ss 0x10
> eax 0x12
> ecx 0xc00b8f00
> edx 0xc024d1a4 db_lengths+0x11c
> ebx 0xc0248255
> __set_sysctl_set_sym_sysctl__vm_swap_async_max+0x1d9
> esp 0xc6f23ca8
> ebp 0xc6f23cb0
> esi 0x100
> edi 0xc35c6000
> eip 0xc020f993 Debugger+0x37
> efl 0x256
> > trace
> panic
> vm_fault
> trap_pfault
> trap
> calltrap()
> --- trap
> slow_copyout
> spec_read
> ufsspec_read
> ufs_vnoperatespec
> vn_read
> read
> syscall
> Xint0x80syscall
>
>
> --
> ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy
>
>
>
--
ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
