Unfortunately there's lots of little bugs still in the 2.6 kernels that only get some people. Test1, 2 & 3 worked beautifully for me but both 4 & 5 wouldn't use half my hardware or was very much degraded performance. 6 & 7 were better but it's still bouncing around - even with 11 I'm getting degraded performance on some devices. And a final release is planned for the end of this month...
My contention is that they don't advertise how to file bug reports well enough. Most users try the development kernels and then either find they work and stick with them or find they don't and go back to a stable kernel. I think that's the main reason a stable kernel isn't really stable until it gets to about a .10 release. Ah, well. Anybody know where to file kernel bugs, btw? bugs.gentoo.org seems like a really bad idea... -----Original Message----- From: Simon Mushi [mailto:[EMAIL PROTECTED] Sent: Saturday, December 06, 2003 9:47 PM To: [EMAIL PROTECTED] Subject: Re: [gentoo-user] ext3 problem in 2.6.0test10&11 kernels Jerry, Thanks for teh response...at least I am a bit more sure that me or my machine isn;t totally crazy as one friend who had gone to 2.6.0 in a breeze was claiming. I guess I'll just scan the messaage boards for any other ppl with related problems and otherwise sit tight till the final release is made...I;m not in a big hurry 2.4 is still doing me fine. Simon On Sat, 6 Dec 2003, Jerry McBride wrote: > On Friday 05 December 2003 07:55 pm, Simon Mushi wrote: > > Hey people, > > > > So I finally managed to compile and boot up my 2.6.0-test11-r1 > > gentoo-sources...set up nvidia drivers and my 2 sound cards and it > > all ran fine for about 20 minutes when for some reason I realised > > that my ext3 based root partition was now read-only...kinda strange > > I had an emerge process that crashed on some crazy error and I could > > not create a new directory. This happened time and time again, I > > would be fine for about 20 minutes before the kernel raised a > > "ext3-fs error in start_transaction: Journal has aborted" and all my > > file systems became read-only and I had to reboot. > > > > Funny thing is when I boot into my old 2.4.20-r5 kernel...it is as > > if nothing at all happened...my system runs fine...I took the pains > > to try out 2.6.0.10-test10-mm sources and same thing happened. > > > > Does anyone have idea as to what I can do? Is 2.6 for me? > > > > I've had the exact same problems with the mm-sources starting with > test9-mm4 > to the current mm patchset. My fix was to stop using mm-sources until I can > convince Andrew Morton that there a problem in the patches. The latest > 2.6.0-test11 sources has the basics of what I need all ready in it anyways. > > It's not just ext3, it's whatever you use on root that get's mounted > read-only. The really odd thing is, under /proc/mount it clearly shows that > root is mounted . > > The way to fix this, after booting, is remount the root partition > with: mount -t ext2 /dev/hda2 / -o remount,rw Remember you should > alter this command to fit your particular setup. > > As a side note, the last, working mm-sources was 2.6.0-test9-mm2. > > Cheers. > > > -- > > ************************************************************************ ****** > Registered Linux User Number 185956 > http://groups.google.com/groups?hl=en&safe=off&group=linux > Join me in chat at #linux-users on irc.freenode.net This > email account no longers accepts attachments or messages containing html. > 11:25am up 66 days, 16:18, 7 users, load average: 0.00, 0.02, > 0.00 > > > -- > [EMAIL PROTECTED] mailing list > > -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
