| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
OK, I've been thinking about this, and here is what we have. |
| 5 |
(1) Some U1/U2 systems do very well on these kernels; |
| 6 |
(2) Some are unusable: I have one which on 2.6.xx, has mean time between |
| 7 |
(very hard lock) failure of about a day, on kernel-2.4.32, it's never |
| 8 |
(literally). |
| 9 |
(3) Weeve and (I believe) squash are as in point 2. |
| 10 |
|
| 11 |
Now, I am not imagining things: a system which responds to nothing at all |
| 12 |
is hard to make up. |
| 13 |
|
| 14 |
Further, my unusable-with-2.6 system is 2x400; stable ones are I think a |
| 15 |
bit slower. |
| 16 |
|
| 17 |
Here's the clue: I tried the 2x400 system with a cdrecord, (which works |
| 18 |
perfectly on 2.4.xx) with 2.6.15-rc4. It wrote the disk. Then it tried |
| 19 |
to fixate it. |
| 20 |
That killed it within about 1 second. I *think* fixating is one long |
| 21 |
system call (I haven't read cdrecord yet), and scsi disk activity I know |
| 22 |
is the general killer. So maybe looking at cdrecord's fixating system |
| 23 |
activity can tell where the problem is. (I do know cdrecord on this |
| 24 |
system with 2.6.xx has a 100% failure rate, based on several attempts.) |
| 25 |
|
| 26 |
Thoughts, Comments? |
| 27 |
(By the way, I regret my rash remarks from earlier.) |
| 28 |
Regards, |
| 29 |
Ferris |
| 30 |
- -- |
| 31 |
Ferris McCormick (P44646, MI) <fmccor@g.o> |
| 32 |
Developer, Gentoo Linux (Devrel, Sparc) |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v1.4.2.1 (GNU/Linux) |
| 35 |
|
| 36 |
iD8DBQFEAR06Qa6M3+I///cRAmq7AJ9SCiBS/sXieWdWF/Xu6nBMxIplngCdF2/3 |
| 37 |
Ku3jz0TMhUjvbnbT1md+Y/0= |
| 38 |
=tMFQ |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
-- |
| 41 |
gentoo-sparc@g.o mailing list |
Archives