| |||||||||||||
Probable e1000e corruption culprit found (and 2.6.27.1 released)Probable e1000e corruption culprit found (and 2.6.27.1 released)Posted Oct 17, 2008 0:38 UTC (Fri) by paragw (subscriber, #45306)In reply to: Probable e1000e corruption culprit found (and 2.6.27.1 released) by nevets Parent article: Probable e1000e corruption culprit found (and 2.6.27.1 released)
>As for the CONFIG_SHARED_IOREMAP_SPACE, I don't think that is needed. That may have protected the bug with ftrace, but it does not protect other bugs writing into bad memory areas.
Well it could have saved some people's cards from bricking - who knows how many other cards allow bricking if bad stuff is written to some magic ioremap()able area. Difference between writing to other areas vs. writing to ioremap space is that as we witnessed the later is fatal, former is always recoverable on boot.
(Log in to post comments)
|
|||||||||||||