Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

[Frans Pop]

> 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.

Something else to worry about is bisections. People seeing an unrelated 
issue with .27 after release may well be asked to do a bisection and 
could then run into the issue even if it is fixed before the release.

Guess we'll need to wait and see what the root cause is to know if that's 
a real concern or not.

> - it is not yet even clear whether the bug is caused by userspace (new
>   version of xorg drivers, bad interaction with PAT, ...) or some bug in
>   kernel code; it's even not yet certain at which exact combination of
>   software versions and hardware configuration this started to trigger

Extra datapoint. As far as I've seen this problem has not yet been 
reported by any people running Debian. This could point to X.Org as 
Debian currently has 7.3 while I think the reports so far have been with 
7.4.

I have been running .27-rc kernels myself on a HP 2510p laptop running 
Debian/lenny which does have the "bad" NIC (ICH9), but it's still working 
for me. I do have some vague resume from suspend problems, but for now 
I'm assuming those are unrelated.
I have been running the kernels both with and without PAT enabled.

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/