Trying to test a pullup request, I discovered that options FAST_IPSEC does not seem to play nicely with Xen: xen5# ping fubar PING fubar.york.redcrowgroup.com (192.168.3.8): 56 data bytes panic: m_copyback0: read-only Stopped in pid 3.1 (cryptoret) at netbsd:cpu_Debugger+0x4: popl %ebp db> bt cpu_Debugger(c041ed20,ca803e48,ca803e7c,c0317c26,c0488200) at netbsd:cpu_Debugger+0x4 panic(c041bc1d,ca804334,c07c0e00,b6cef66c,99) at netbsd:panic+0x12c m_copyback0(ca803ec4,9,1,ca803f26,9) at netbsd:m_copyback0+0x913 m_copyback(c07c0e00,9,1,ca803f26,1e5) at netbsd:m_copyback+0x42 esp_input_cb(0,24,c040d32f,0,0) at netbsd:esp_input_cb+0x45f cryptoret(c9fcbdec,52d000,c0537000,0,c010017c) at netbsd:cryptoret+0x12e db> I saw some changes to the xennet device related to m_copyback() a short while ago... might this be related? Any suggestions what might be going wrong? To duplicate, just add: options FAST_IPSEC to the XENU kernel, configure some SPD entries, and try to use them... (KAME IPSEC works fine in that instance, as does FAST_IPSEC on a "real" i386 box) I've sent-pr, it's port-xen/33162 . +j
Attachment:
signature.asc
Description: OpenPGP digital signature