Good, and I'll get the map changes in after the weekend.
Jack
On Sat, Oct 12, 2013 at 3:50 AM, Konstantin Belousov wrote:
> On Wed, Oct 09, 2013 at 10:56:25AM -0700, Jack Vogel wrote:
> > Give the new driver I just committed to HEAD a try to verify/falsify a
> fix
> > please.
> >
> Updated dri
On Wed, Oct 09, 2013 at 10:56:25AM -0700, Jack Vogel wrote:
> Give the new driver I just committed to HEAD a try to verify/falsify a fix
> please.
>
Updated driver seemingly fixed my issue with the drdb panic, thank you.
The tx busdma map leakage is still there.
> Regards,
>
> Jack
>
>
>
> On
Give the new driver I just committed to HEAD a try to verify/falsify a fix
please.
Regards,
Jack
On Wed, Oct 9, 2013 at 10:23 AM, hiren panchasara <
hiren.panchas...@gmail.com> wrote:
> Jack,
> I am also seeing similar panics at $work on a couple weeks old STABLE-9.
>
> Can you please look in
Jack,
I am also seeing similar panics at $work on a couple weeks old STABLE-9.
Can you please look into this issue?
cheers,
Hiren
1) HP DL360e Gen8, 2 x Xeon E5-2430 2.20GHz
panic: buf=0xfe002810d700 already enqueue at 995 prod=997 cons=995
cpuid = 17
KDB: stack backtrace:
db_trace_self_wra
On Sun, Sep 29, 2013 at 12:30:38AM +0300, Konstantin Belousov wrote:
> On a relatively old test machine, dual-socket X7DWU supermicro, Xeon
> X5272, with on-board 82575EB igb controllers, running the stress2
> udp blast test immediately causes the following
>
> panic: buf=0xf8001aa5c800 alread
