Subject: m_copym0 panic - old hat?
To: None <current-users@netbsd.org>
From: Patrick Welche <prlw1@newn.cam.ac.uk>
List: current-users
Date: 07/21/2003 18:44:41
A computer running a Jun 30 1.6U/i386 kernel, gives me panics of the form:

m_copym0(0,0,5a8,1,0) at netbsd:m_copym0+0x41
m_copym(0,0,5a8,1,c0ad4200) at netbsd:m_copym+0x1c
tcp_output(c096762c,c0934d04,0,800,c0359860) at netbsd:tcp_output+0xb9b
tcp_input(c0ad4200,14,6,1,c0ad4200) at netbsd:tcp_input+0x29d3
ip_input(c0ad4200,c0179928,c08a1000,c086f9a4,0) at netbsd:ip_input+0x7a4
ipintr(1f,bfbf001f,1f,bfbf001f,480e5514) at netbsd:ipintr+0x87
Bad frame pointer: 0xc07fc900

every time I try to copy large files such as /var/crash/netbsd.0.core.gz

(I'll hopefully get a USB drive soon and be able to look at those core
dumps) Is this a known problem long fixed?
(It works fine serving the odd web page / mail message, just not sustained
transfer)

Cheers,

Patrick