[Bug 8307] Unstable system (Oopses?) since 2.6.10

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Mon Mar 28 17:32:41 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=8307
Ubuntu | linux





------- Additional Comments From fabbione at ubuntu.com  2005-03-28 18:32 UTC -------
(In reply to comment #2)
> Thank you for your swift response.

no problem. Other than we will release hoary in few days, so there is not much time
to get this one fixed (given that there is a fix)
 
> Everything I've said was about ext3 root filesystems, although a fat32 fs has
> been mounted for my girlfriend. 

Ok.

> When talking about this, I should point at the { DriveReady SeekComplete Error }
> things in the logs, too. After the 1st reinstall, I could not read audio cd's,
> and I thought this seekcomplete error things were related. Now, however, I still
> have them (see http://atlas.et.tudelft.nl/1200348/pub/bugs/kern.log ), but I can
> read the audio cd's. 

This is due to a loadmodule order issue. Probably ide-generic is loaded before the
module that handle specifically your chipset. A workaround is to force the latter
via /etc/modules. There should be a bug open for this, but i can't find it right
now.
It is in bugzilla anyway.



> 
> > I smell an hardware issue here. Can you please try to boot 
> > with the LiveCD (hoary) and see if the kernel still OOpses?
> I will download it and see. This will take some time as it's my girlfriends pc
> and I have upcoming examns :)

Ok.

> 
> > from the live cd you should be able to run a badblock over
> > the harddisk.
> I will do it with the warty live-cd, which is available now. 
> 
> So: 
> - I will try hoary live-cd later, to check for Oopses
> - I will run badblock, from warty (if that's ok too)

Yes, both of solutions are fine.

thanks
Fabio

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list