On Wed, Sep 24, 2008 at 7:01 PM, David Miller <davem@xxxxxxxxxxxxx> wrote: > From: "Dave Airlie" <airlied@xxxxxxxxx> > Date: Wed, 24 Sep 2008 18:59:34 +1000 > >> On Wed, Sep 24, 2008 at 5:36 PM, David Miller <davem@xxxxxxxxxxxxx> wrote: >> The driver seems quite happy to access the NVRAM, I think Thomas has >> some backtraces that show >> it clearly doing silly reentrant things... > > I don't dispute that the locking is dodgy and likely needs to be fixed > like e1000. > > I'm asking what userland tool or kernel event is triggering the nvram > access. > > It shouldn't even touch the thing after probing and initializing > the card. Hopefully tglx can supply some traces, I think getting an interrupt during device startup can possibly access the nvram http://www.tglx.de/~tglx/wtf2.txt seems to suggest bad things could happen. Dave. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
