On Fri, 20 Aug 2010, Nima Misaghian wrote:
Hey,
I've been able to trivially
trigger a kernel panic while testing ifaddr list manipulation on -CURRENT (r
211427). The hardware is a four-core i386
machine with em interfaces.
The diff should give you an idea of what's going wrong. I am not
> Hey,
>
> > I've been able to trivially
> > trigger a kernel panic while testing ifaddr list manipulation on -CURRENT (r
> > 211427). The hardware is a four-core i386
> > machine with em interfaces.
>
> The diff should give you an idea of what's going wrong. I am not sure
> if I would want to
HI.
I have a reproducible panic with a similar path, though in different details.
So, the issue may be in if_igb instead.
This is 8-STABLE i386.
Sorry, serial console was not set up atm.
http://www.free-imagehosting.com/out.php/i4163_ifioctl.1.png
http://www.free-imagehosting.com/out.php/i4164_if
On Fri, 20 Aug 2010, pluknet wrote:
Hey,
I have a reproducible panic with a similar path, though in different details.
So, the issue may be in if_igb instead.
yeah, that looks like a driver problem at first glance.
/bz
--
Bjoern A. Zeeb This signature is about you not
On Tue, 17 Aug 2010, Nima Misaghian wrote:
Hey,
I?ve been able to trivially
trigger a kernel panic while testing ifaddr list manipulation on ?CURRENT (r
211427). The hardware is a four-core i386
machine with em interfaces.
The diff should give you an idea of what's going wrong. I am not sur
On Tue, 17 Aug 2010, Nima Misaghian wrote:
I?ve been able to trivially
trigger a kernel panic while testing ifaddr list manipulation on ?CURRENT (r
211427). The hardware is a four-core i386
machine with em interfaces.
This is the test script I?ve
used to trigger the problem:
[...]
I can r
I’ve been able to trivially
trigger a kernel panic while testing ifaddr list manipulation on –CURRENT (r
211427). The hardware is a four-core i386
machine with em interfaces.
This is the test script I’ve
used to trigger the problem:
#!/bin/sh
addr_loop()
{
while true
do
