2.2.0pre2 SCSI problems, more (fwd)

Paul Mackerras paulus at cs.anu.edu.au
Wed Jan 6 09:41:57 EST 1999


Brad Midgley <brad at pht.com> wrote:

> i removed all devices from the second bus except for an 80M quantum drive
> that i used to boot from.  (everyone should be warned that you should boot
> from a non-mesh device when mesh debugging is on! :) 
> 
> a strange thing, and maybe bad news for debugging: the drive is discovered
> properly by the debugging kernel. maybe it's a timing issue. i hope the
> logs can tell you something. 

A timing issue sounds likely, as nothing much has changed in the mesh
driver (or the rest of the SCSI code AFAIK) lately.  If you set
mesh_debug_targets back to 0 but still have MESH_DBG defined, it won't
print all that debugging info but it will still record all the log
information (which is a relatively lightweight thing to do), and if
you get the target aborting, it will print the log.

Paul.

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request at lists.linuxppc.org ]]




More information about the Linuxppc-dev mailing list