So, is it still safe to conclude that 2.6.6 is the most save and stable
kernel version to date?
Both my Ultra 1 and Netra T1 run these kernels. The Ultra 1 had a 350
day uptime in totall without a single problem.
I did a reboot after that time, and neither partition even showed a
single problem so that is good for me!
Kumba wrote:
David S. Miller wrote:
From: Kumba <[EMAIL PROTECTED]>
Date: Sat, 25 Jun 2005 00:39:01 -0400
2.6.x was stable for the mosat part until 2.6.7. After that, it
went downhill for awhile. 2.6.7 is by far, extremely stable for me
on my Blade 100. Rumours are abound that 2.6.8.1 through 2.6.11
still cause lots of problems, mostly with scsi. I have yet to
actually try 2.6.12 on my Blade. Maybe a weekend project.
I think I can fix this bug if people give me some information about
the characteristics of the system afflicted by the problem. Answering
a few questions will go a long way:
1) All SMP or non-SMP?
2) Any consistency of cpu type. Ie. all UltraSPARC-II cpus?
(I think this is the most important data point to obtain)
3) All sym2 scsi controllers?
There is a bug in the UltraSPARC-II cpu, but my workaround in the
kernel may not be complete.
Thanks.
I haven't actually tried a newer 2.6.x on my Blade lately. Been
fighting my various mips machines to work right instead (the Blade100
just runs, the Octane likes to put up a fight sometimes). If I can
get around to it, I might try 2.6.12, and try patching it up with the
various cocktail of patches I add in ()grsec, nmap stealth, etc..).
I did manage to wedge a sym2 scsi card into my Blade, and that works
great under 2.6.7. If I get 2.6.12 working, I'll be sure to report
any oddities with that and the sym2 card. Might also test this ALi
usb2 card again and see if that works any better.
--Kumba
--
[email protected] mailing list
