On Tue, 17 Oct 2000, Gary E. Miller wrote:
> Yo All!
>
> Help! See below for my kernel oops. I have not been able to use any
> kernel after 2.4.0-test5 due to this problem. It happens shortly
> after booting the kernel and is very repeatable.
>
> This is a dual PII system with PIIX4 ide, 53c875 scsi and Raid 1.
> It is not a production system so I am open to any patches or
> tests.
>
> The system would not even stay up long enough to run ksymoops so
> I had to copy the data and run it under 2.2.17.
>
> Any ideas out there?
Hi,
Are you sure that you used the right System.map?
> Trace; c01df362 <scsi_dispatch_cmd+1c6/26c>
^^^
Here, scsi_dispatch_cmd() isn't that large.. it's only 0x168 in size.
(scsi_dispatch_cmd+0x1c6 is very close to scsi_wait_req():down (&sem))
If you want to try some light troubleshooting, grab kdb..
ftp://oss.sgi.com/www/projects/kdb/download/ix86/kdb-v1.5-2.4.0-test9-pre9.gz
.. and check what both cpus were up to at lock time. A stack trace of
both cpus might help developers locate the trouble.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
