Brad Felmey wrote:

>On Wed, 2002-09-18 at 13:22, Bryan Whitehead wrote:
>
>  
>
>>Testing one of our 2GB Dual-Pentium III (1ghz) machines we get a hard 
>>lock with kernel enterprise.
>>kernel-enterprise-2.4.19.9mdk-1-1mdk.i586.rpm
>>
>>The lock up seems to be related to the scsi driver. aic7xxx. The last 
>>message that is echoed to the syslog consol is:
>>kernel: (scsi0:A:0:0): Locking max tag count at 64
>>
>>after that the machine is dead. No ping, but keyboard works enough for 
>>Alt-SysRq stuff. Only problem is Alt-SysRq keys won't work. :( syncing 
>>the disk results in the machine "trying" (It starts to sync the disk) 
>>but will never finish, there is no HD activity. Then the keyboard will 
>>not respond anymore.
>>
>>Trying to get a process list, or memory stats will finish off the lock 
>>also. (as in it will become so useless that reset button is only thing 
>>working).
>>
>>If my first sysrq key is to reboot it will.
>>
>>I ran memtest yesterday and all memory is ok. Mandrake 8.1 has no 
>>problems on this machine.
>>
>>Heavy disk activity triggers the lock, like installing an RPM. :)
>>
>>It will always hard lock when installing the "FlashPlayer-5.0-8mdk" RPM.
>>
>>any suggestions? or specific sysrq keys you'd like me to try in locked 
>>up state? (there is no oops or anything like that on the consol window)
>>    
>>
>
>I have a dual-1GHz PIII Coppermine system with 2GB on a Supermicro
>Serverworks board and Adaptec 3200S that has this exact problem. Only
>with highmem/kernel-enterprise after 2.4.8. RPM will kill the box
>exactly as you've described. I've had to retrograde the box and stay
>away from current kernels.
>  
>
I reported a bug some days earlier about problems with the enterprise 
kernel, but not the same scsi driver(mine is sym53c8xx)
And as I said this did'nt happen with the old 2.4.5 kernel(from 
mdk-cooker) it was running for almost a year, but now it's had a mem 
upgrade and is running the kernel-enterprise kernel, and we've 
experienced lockups with 2.4.18 and 2.4.19.
But this does'nt happen when using rpm, and the machine is alive, 
responding to ping etc. but could'nt read from the disks, and happens 
under high load(not very high, just compiling something could trigger it 
), at first I thought it was a gcc-3.2 issue, but when trying with 
kernel-enterprise-2.4.18.6mdk-1-1mdk this also happened, so I'll guess 
this might be related



Reply via email to