Re: Uh-oh, is it WMaker or my 2.0.33 kernel?
Kiyan Azarbar <kiyan@iname.com> writes:
> Everything just fried itself, then I found this in the syslog:
>
> May 11 03:22:42 palantir kernel: Unable to handle kernel paging request at =
> virtual address e90833c4
> May 11 03:22:42 palantir kernel: current->tss.cr3 =3D 00299000, %cr3 = 00
> 299000
> [cut]
>
> Anyone understand what's up? Is it just a problem with the memory
> management of the 2.0.33 kernel? Maybe I should switch back to
> 2.0.32, or perhaps the new 2.0 kernel is out and is stable?
>
> This sucks. Bash crashed my whole system today too. NOT a good
> day. And to think, I was actually beginning to yearn for an uptime
> of over a week (I used to shut my computer off at night, but now
> I've got=20 the rc5des client running nonstop, so...)
Such errors are ALWAYS bugs in the kernel even if evoked by an
application. If these bugs started with updating to 2.0.33 you should
go back to the previous kernel. I heard of some problems with the
memory management of 2.0.33, fortunately, never had these problems.
Torsten
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: