kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI

[Lachlan O'Dea]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18 Feb 2004, at 10:41, Scott Long wrote:

> Jason M. Leonard wrote:
>> Without seeing the actual SCSI errors it is hard to say, but I was
>> experiencing a very similar issue with my PE2650.  Disabling write 
>> caching
>> on the RAID 1 container cleared it up.  I do not know if that is the 
>> best
>> way to go about it, but this server had to be in production pronto, 
>> so I
>> was happy.
>> :Fuzz
>
> If there is any way that you could send me the errors that you were
> getting, I would appreciate it.

Hi Scott,

This may be completely unrelated, but I just went from 5.2-RELEASE to 
5.2.1-RC2. After a while started seeing lots of these on the console:

aac0: command 0xXXXXXX timeout after 8597 seconds

and, less often:

swap_pager: indefinite wait buffer: device: aacd0s1e , blkno: 2, size: 
4096

I managed to observe the system in top the second time this happened. 
One after another, each process freezes forever in getblk. Kind of 
scary to watch :-).

With 5.2-RELEASE, I was seeing the blocked processes, but I don't 
recall seeing all of that console output before. I haven't actually 
seen experienced any problems with 5.2-RELEASE for a while, I just have 
to avoid long-running find(1) processes. (E.g. put 
daily_status_security_enable="NO" in periodic.conf).

- --
Lachlan O'Dea
Computer Associates
Senior Software Engineer
tel: +61 3 8416 5627
fax: +61 3 8416 5810
mobile: +61 412 390 650
odela01 at ca.com

Relax and enjoy your shoes!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFAMqu7oBZahcUBONoRAjwEAJ9lgMapehhkWm31HW+F0UjS9yXTKQCeJ55i
y7ovo0uuLjuzqQk39Aaf6kw=
=gGgc
-----END PGP SIGNATURE-----