[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#238367: marked as done (kernel-image-2.4.24-sparc64: Lots of oopses)

Your message dated Thu, 25 Dec 2008 16:27:50 +0100
with message-id <20081225152750.GA5362@galadriel.inutil.org>
and subject line Re: Bug#238367: kernel-image-2.4.24-sparc64: Lots of oopses
has caused the Debian Bug report #238367,
regarding kernel-image-2.4.24-sparc64: Lots of oopses
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
238367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=238367
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kernel-image-2.4.24-sparc64
Severity: normal

Kernel tends to crash on Ultra 10.  X also tends to restart, or freeze up.
In one case I could switch back to text mode, where I still got a login
prompt, but the password prompt never comes up.  The system crashes in
many different ways; at one point I got a screen full of oopses.  This
is all during a single day without heavy use.

One suspicious thing is the following error message that always appears
while booting:

EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Adding Swap: 1048808k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal

This may be the same problem I've been experiencing with a self-compiled
2.4.21 kernel.  The machine is running testing; it had been stable for
a while after new year, but now it's back to its old multiple failures
per day.  :-(

--- End Message ---
--- Begin Message --- 
On Thu, Dec 25, 2008 at 08:07:38PM +0700, Jeroen Vermeulen wrote:
> Moritz Muehlenhoff wrote:
>> reassign 238367 linux-2.6
>> thanks
>>
>> On Wed, Mar 17, 2004 at 04:28:25PM +0100, Jeroen T. Vermeulen wrote:
>>> On Tue, Mar 16, 2004 at 02:47:00PM -0500, Ben Collins wrote:
>>>> This error is nothing, it can be ignored. Do your freezes always occur
>>>> when X is running? Can you make it crash without X?
>>> Yup, leaving the machine near-idle overnight without X also kills it.  Even
>>> ssh doesn't get through its thick metal skull after that.  I'll see if I can
>>> correlate it to anything in the crontab.
>>
>> Does this error still occur with more recent kernel versions?
>
> Hard to say now!  I don't remember the details of this bug off the top  
> of my head, nearly 5 years later, but depending which machine I saw it  
> on, I can say with certainty that it's one that either died or left my  
> control years ago.

Thanks, closing the bug then.

Cheers,
        Moritz

--- End Message ---
Reply to: