From: Paul Mackerras <paulus@cs.anu.edu.au>
To: brad@pht.com
Cc: linuxppc-dev@lists.linuxppc.org, p1rabbit@halcyon.com
Subject: Re: 2.2.0pre2 SCSI problems, more (fwd)
Date: Wed, 6 Jan 1999 09:41:57 +1100 [thread overview]
Message-ID: <199901052241.JAA04815@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.990104192040.452A-100000@cricket> (message from Brad Midgley on Mon, 4 Jan 1999 19:41:15 -0700 (MST))
Brad Midgley <brad@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@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-05 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-05 2:41 2.2.0pre2 SCSI problems, more (fwd) Brad Midgley
1999-01-05 22:41 ` Paul Mackerras [this message]
1999-01-06 17:05 ` Brad Midgley
1999-01-13 2:53 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
1999-01-04 13:24 Geert Uytterhoeven
1999-01-04 17:18 ` Brad Midgley
1999-01-04 18:04 ` Peter Abrahamsen
1999-01-04 22:45 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199901052241.JAA04815@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=brad@pht.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=p1rabbit@halcyon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).