On Sat, Nov 22, 2008 at 11:21 AM, Moritz Muehlenhoff <firstname.lastname@example.org> wrote:
> On Tue, Jun 05, 2007 at 11:12:58AM -0300, Rodrigo Campos wrote:
>> Package: linux-image-2.6.18-5-686
>> Version: 2.6.18.dfsg.1-13
>> Severity: grave
>> Justification: renders package unusable
>> Hi, the other day i upgrade from lastest linux-image-2.6.18-4-686 to
>> linux-image-2.6.18-5-686 from proposed-updates and all seems to be ok.
>> But yesterday after i power it on, i hit this kernel bug. I dot know
>> how to reproduce it, but the trace might be useful.
>> Let me know if you need any other extra information or tests, and feel
>> free to downgrade the severity
> Does this error still occur with more recent kernel versions?
No, it never happen again. I tried to reproduce before reporting the
bug, but I couldn't.
It happen just that time and never again. And since then I've tried
.18, .21, .22, .23, .24, .25, .26 debian kernels.
> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
I'm not running Etch, I'm running lenny/sid right now (with some of
experimental) in that computer. But I've run 2.6.24 when it was on
testing/unstable and did not hit this issue.
If besides I'm using lenny do you want me to try something, please let me know.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com