On Wednesday 05 January 2005 18:26, J. Martin Petersen wrote: > > I just got another "netstat: kvm_read: Bad address". > > vm.kvm_free was 675278848 two seconds earlier and a couple of > > seconds later (and also currently). > > We just had another hard hang, and this time I managed to break to the > debugger on the serial console. I got this stack trace > <http://www.aub.dk/~jmp/fw/trace>, which seems to indicate that pf is > messing up somehow.
This looks like pf.c, rev. 1.25 (HEAD) 1.18.2.6 (RELENG_5) and is an endless loop, not a deadlock. I hope you can verify that updating to these revisions solves the issue. Please get back to me if not. Thanks in advance. > I of course didn't have the ddb man or the handbook section on kernel > debugging at hand, so I've just printed it for the next time it happens. > > Both 'show witness' and 'show locks' came up empty. What's the most > effective way to hunt down these deadlocks with the online kernel debugger? -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News
pgpdtRXn4kKUV.pgp
Description: PGP signature