On Thu, Sep 25, 2008 at 12:28 PM, Jeff Garzik <jeff@xxxxxxxxxx> wrote: > Jiri Kosina wrote: >> >> On Thu, 25 Sep 2008, Dave Airlie wrote: >> >>> Well I'm out of the race, my attempts to re-write my eeprom using an >>> eeprom from an equivalent laptop have totally failed and my BIOS won't boot >>> anymore - so my laptop is == a brick. >> >> Uh oh. Shouldn't we put something like the patch below in Linus' tree >> unless we get this sorted out? Otherwise more and more people who use -rc >> kernels will run into this, and will get their hardware [hopefully >> temporarily, but not all users are able to re-flash their network card >> EEPROMs, right] bricked. >> >> I know that it is quite aggressive and is going to disable wired >> networking on a lot of systems that have been functioning properly, >> therefore RFC ... >> >> >> >> From: Jiri Kosina <jkosina@xxxxxxx> >> Subject: [PATCH] [RFC] E1000E: temporarily disable e1000e driver >> >> E1000E: temporarily disable e1000e driver > > That seems a bit drastic, particularly when the debugging was beginning to > point to another culprit. > > We have equal case at this point to disable r8169 and i915_drm, no? > No we actually are more likely unable to do anything from the kernel, if its happening from userspace firstly we need a reflash utility that is safe, otherwise people who have the issue can't reproduce it, and people who don't have the issue don't want to play with it. I think e1000e may enable a BAR or something that causes the issue to break this hw., I haven't seen it broken on any machine where e1000e wasn't loaded yet. Again the r8169 might be the same issue, but it maybe because the bar was enabled. 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
