Hi guys, lists,
It's me, the bi-weekly panic guy. Guess what, it crashed today. As an
act of desperation I disabled the pipe dumping script after previous
crash, which today turned out to be merely a coincidence and didn't
prevent panics. (I thought it to be a longshot anyway, but it was the
only
2011/2/19 Pawel Tyll :
> Hi guys, lists,
>
> It's me, the bi-weekly panic guy. Guess what, it crashed today. As an
> act of desperation I disabled the pipe dumping script after previous
> crash, which today turned out to be merely a coincidence and didn't
> prevent panics. (I thought it to be a lon
I've never seen a trace like this, and no absolutely nothing about dummynet,
sorry.
If it is in some way em's fault, then making sure you have the latest code
would be
a good idea. I have a test driver that is under selective test, it does
effect the code
path that you seem to be in, so it might be
On Sat, Feb 19, 2011 at 8:40 PM, Jack Vogel wrote:
> I've never seen a trace like this, and no absolutely nothing about dummynet,
> sorry.
> If it is in some way em's fault, then making sure you have the latest code
> would be
> a good idea. I have a test driver that is under selective test, it do
> Same backtrace as reported here?
I'm unable to get the new backtrace, but judging from what I can see
on the console pre-reboot, it's exactly the same deal since
8.0-RELEASE - panic with dummynet as main star.
> What revision of the em(4) driver code are you using? I know Jack has
> been working
> I was actually going to suggest Pawl try a different network device if
> possible. I'm using dummynet on a network gateway equipped with
> on-board bge(4). I haven't had any crashes, but then again, I'm not
> seeing that many packets either.
It seems to be closely related to amount of processed p
> I've never seen a trace like this, and no absolutely nothing about dummynet,
> sorry.
> If it is in some way em's fault, then making sure you have the latest code
> would be
> a good idea. I have a test driver that is under selective test, it does
> effect the code
> path that you seem to be i
