|
|
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Tuesday 20 October 2009 14:50:09 Cyrill Gorcunov wrote: > On 10/20/09, Denys Fedoryschenko <denys@xxxxxxxxxxx> wrote: > > On Tuesday 20 October 2009 06:04:35 Cyrill Gorcunov wrote: > >> On 10/20/09, Denys Fedoryschenko <denys@xxxxxxxxxxx> wrote: > >> > On Tuesday 20 October 2009 00:22:39 Michal Ostrowski wrote: > >> >> I'm assuming that there was a race in us sending patches at nearly > >> >> the same > >> >> time I'm convinced now that the flush_lock can die, and the patch I > >> >> sent > >> >> out kills it. > >> > > >> > o_O > >> > > >> > I am drowning in patches. Just let me know which one to test :-) > >> > >> Oh ;) Try out latest Michal's patch (and then mine). I'll continue > >> digg this issue at next spare time slot. Thanks! > > > > Tried your patch, panic almost immediately > > Here is a text of panic message over netconsole > > http://www.nuclearcat.com/files/panic_pppoe3.txt > > It is different now, before it was pppoe_device_event, now in pppoe_rcv > > Thanks a lot! I'll back with new one in a couple of hours. Meanwhile i > suppose you may try Michal's patch as well. I did, it didn't help. Maybe i can run some debugging options in kernel? Also i can add debug(printk) lines in kernel if you want, to see where is bug appearing. Note, i told to Michal, so will tell here, this pc is hyperthreading P4, as i know it is very good to trigger various SMP race conditions. I can try also it with nosmp if u want. -- To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html