I used 5000ms. I still freeze up with 2.4.3 + 6.1.10.
Unfortunately i could not see any messages and nothing got logged.
This time an fsck allowed me to boot back to 2.4.1.
The visible symptoms were the same as before (2.4.3 + 6.1.8) but this time I was
unable to flip virtual consoles before the freeze so I dont even
know 100% what is causing it - it boots fine - and the scsi driver
makes no complaints - it all looks normal. X starts up and I can login.
it starts ok and windows start popping up - shortly thereafter it freezes
- just like before.
I will try investigate further and see if I can get any more log messages.
Is there any debug boot option or compile flag that will help me find out more
what is going on?
/var/log/messages says this about scsi.
Apr 7 19:56:13 snap kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev
6.1.10
Apr 7 19:56:13 snap kernel: <Adaptec 2940 Ultra2 SCSI adapter>
Apr 7 19:56:13 snap kernel: aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs
Apr 7 19:56:13 snap kernel:
Apr 7 19:56:13 snap kernel: Vendor: YAMAHA Model: CRW8424S Rev: 1.0d
Apr 7 19:56:13 snap kernel: Type: CD-ROM ANSI SCSI
revision: 02
Apr 7 19:56:13 snap kernel: Vendor: SEAGATE Model: ST318275LW Rev: 0001
Apr 7 19:56:13 snap kernel: Type: Direct-Access ANSI SCSI
revision: 02
Apr 7 19:56:13 snap kernel: (scsi0:A:5): 80.000MB/s transfers (40.000MHz, offset 15,
16bit)
Apr 7 19:56:13 snap kernel: Vendor: SEAGATE Model: ST318275LW Rev: 0001
Apr 7 19:56:13 snap kernel: Type: Direct-Access ANSI SCSI
revision: 02
Apr 7 19:56:13 snap kernel: (scsi0:A:6): 80.000MB/s transfers (40.000MHz, offset 15,
16bit)
Apr 7 19:56:13 snap kernel: scsi0:0:5:0: Tagged Queuing enabled. Depth 253
Apr 7 19:56:13 snap kernel: scsi0:0:6:0: Tagged Queuing enabled. Depth 253
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
