[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -current panic

I have the same panic on my box.  Submitted a bug report, kernel/1837.

Here is the traceback of my crash:

_m_tag_delete_chain(e0a50b08,0,e015d224,10b) at _m_tag_delete_chain+0x5b
_m_freem(e0877180,ef6faea8,24,18) at _m_freem+0x44
_nfs_readdirrpc(ef7ddf3c,ef6faf14,e0a33d80,e01442c6,e0364018) at _nfs_readdirrpc+0xbc0
_nfs_doio(e1d0a9f4,e0a33d80,0,0) at _nfs_doio+0354
_nfssvc_iod(ef6bbd6c,0,0,0,0,0e03b9f18,e010035b,0,1,0,0,e0100355,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,ef6fcff0,10,0,0,0,0,3b7000,0,0,0,0,0,0,ef6fcec8,ef6fcf14,0,0,0,0,0,0,0,0,18,14c0000,120,0) at _nfssvc_iod+0x139
_start_nfsio(0) at _start_nfsio+0x14
Bad frame pointer: 0xe03b9f18

Quoting Marco S Hyman (marc@snafu.org):
> Marco S Hyman writes:
>  > On my laptop I can repeat this panic:
>  > 
>  > 	uvm_fault
>  > 	kernel: page fault trap
>  > 	stopped at _m_tag_delete_chain
> Same fault at same location with GENERIC compiled from sources as of
> an hour or so ago.   Let me know if any other info is needed.
> // marc

// david lebel <lebel@{lebel.org,nobiaze.com,openbsd.org}> //
// http://www.lebel.org/           http://www.nobiaze.com/ //
// pgp: 3633 6999 D47E 73ED 099F  4341 08A4 8E48 EF56 61D1 //