Re: r194546 amd64: kernel panic in tcp_sack.c

Lawrence Stewart wrote:
I'm not intimately familiar with our SACK implementation, and these things are often extremely painful to track down. First step: is the panic reproducible?
So far I couldn't reproduce it, but I think the fact that I couldn't reproduce it has something to do with frequent reboots due to buildworld/buildkernel lately because of other problems.
How did you try to get it to save the core? A dump would be very useful to have around.
Since I'm not much of an expert in the kernel debugger, I tried to let it continue with the panic, i.e. typed 'continue' which produced a fatal trap 12 right after "Dumping XXXX MB: (~3 values were here)".

--
Kamigishi Rei
KREI-RIPE
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • [net80211] if_wi crashed in adhoc mode
    ... SCHED_4BSD, without PREEMPTION. ... The crash never happened ... Steps to reproduce: ... Fatal trap 12: page fault while in kernel mode ...
    (freebsd-current)
  • kernel panic caused by Opera 11.50
    ... Fatal trap 12: page fault while in kernel mode ... instruction pointer = 0x20:0xffffffff804bfff0 ... Step to reproduce: ...
    (freebsd-current)