Re: panic m_demote: m_nextpkt not NULL

2014-09-08 Thread Mark Atkinson
uffer: M> panic: > m_demote: m_nextpkt not NULL M> cpuid = 0 > > Sorry for that. Was fixed in r271123. Thank you and Jean-Sébastien for the pointer, I was able rebuild the kernel quickly on Fri with just this change and it's working fine. -BEGIN PGP SIGNATURE- Version:

Re: panic m_demote: m_nextpkt not NULL

2014-09-05 Thread Gleb Smirnoff
On Fri, Sep 05, 2014 at 08:38:10AM -0700, Mark Atkinson wrote: M> r271093 GENERIC amd64. Received this panic in the tcp reassembly code: M> Unread portion of the kernel message buffer: M> panic: m_demote: m_nextpkt not NULL M> cpuid = 0 Sorry for that. Was fixed in r271123. --

Re: panic m_demote: m_nextpkt not NULL

2014-09-05 Thread Jean-Sébastien Pédron
On 05.09.2014 17:38, Mark Atkinson wrote: > r271093 GENERIC amd64. Received this panic in the tcp reassembly code: Gleb Smirnof fixed this in r271123. I had this same panic yesterday after around 3h of uptime each time, but today, everything's fine. -- Jean-Sébastien Pédron signature.asc De

panic m_demote: m_nextpkt not NULL

2014-09-05 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 r271093 GENERIC amd64. Received this panic in the tcp reassembly code: Unread portion of the kernel message buffer: panic: m_demote: m_nextpkt not NULL cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame