On Wed, Jun 05, 2013 at 01:13:45PM +0300, Konstantin Belousov wrote:
K> On Wed, Jun 05, 2013 at 01:50:43PM +0400, Gleb Smirnoff wrote:
K> > On Wed, Jun 05, 2013 at 10:18:21AM +0200, Ian FREISLICH wrote:
K> > I> I have the following recurring panic on all my heavily network
K>
On Wed, Jun 05, 2013 at 01:50:43PM +0400, Gleb Smirnoff wrote:
> On Wed, Jun 05, 2013 at 10:18:21AM +0200, Ian FREISLICH wrote:
> I> I have the following recurring panic on all my heavily network
> I> loaded -CURRENT routers. The current process is always different.
> I>
On Wed, Jun 05, 2013 at 10:18:21AM +0200, Ian FREISLICH wrote:
I> I have the following recurring panic on all my heavily network
I> loaded -CURRENT routers. The current process is always different.
I>
I> Gleb, can you please chime in with what you've managed to uncover.
The
Hi
I have the following recurring panic on all my heavily network
loaded -CURRENT routers. The current process is always different.
Gleb, can you please chime in with what you've managed to uncover.
Unread portion of the kernel message buffer:
processor eflags= interrupt en
