I've received two oopses now from my kernel while running
the 2.6.22 series. The first was with 2.6.22.1 back in July and
the second which happened just within the last day is 2.6.22.5.
They both appear to be the same bug and I don't think it's
hardware related. I'm attaching the entries from logcheck which
I received when they happened.
I'm not subscribed to the mailing list, so please make
sure to copy me directly on any replies. And let me know if
anyone needs any additional information to try to track this
down. Thanks for reading...
--
Mark Nipper e-contacts:
4320 Milam Street [email protected]
Bryan, Texas 77801-3920 http://nipsy.bitgnome.net/
(979)575-3193 AIM/Yahoo: texasnipsy ICQ: 66971617
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI++ D+ G e(*) h r(%) y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
"They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety."
-- Benjamin Franklin, _Historical Review of Pennsylvania_, 1759
----end random quote of the moment----
Hi Mark,
[Adding netdev to CC]
On 07/09/2007, Mark Nipper <[email protected]> wrote:
> I've received two oopses now from my kernel while running
> the 2.6.22 series. The first was with 2.6.22.1 back in July and
> the second which happened just within the last day is 2.6.22.5.
> They both appear to be the same bug and I don't think it's
> hardware related. I'm attaching the entries from logcheck which
> I received when they happened.
>
> I'm not subscribed to the mailing list, so please make
> sure to copy me directly on any replies. And let me know if
> anyone needs any additional information to try to track this
> down. Thanks for reading...
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/