public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Dave Gilbert <gilbertd@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: css hang; somewhere between test12 and test13pre4ac2
Date: Mon, 25 Dec 2000 15:01:07 +0100	[thread overview]
Message-ID: <20001225150107.D303@suse.de> (raw)
In-Reply-To: <20001225121037.B303@suse.de> <Pine.LNX.4.10.10012251336230.666-100000@tardis.home.dave>
In-Reply-To: <Pine.LNX.4.10.10012251336230.666-100000@tardis.home.dave>; from gilbertd@treblig.org on Mon, Dec 25, 2000 at 01:38:46PM +0000

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

On Mon, Dec 25 2000, Dave Gilbert wrote:
> > The most likely suspect (as someone else pointed out) is not at
> > all css (I'm not even sure what you mean by css hang?) but UDF.
> 
> I mean a complete system hang when playing a CSS disc - doesn't even ping.
> Doesn't recover.

Hmm

> > Given the fs changes. Since sysrq still works, it would help a
> > lot if you could capture sysrq-p repeatedly and send it in.
> 
> I think at this point the only thing that works is sysrq-b - at least the
> sysrq-u's and sysrq-s's that I've given don't seem to have cleanly
> unmounted the file system.

Could you at least check? You may need some sort of serial console too..

> > Do you have any non-css discs to beat on UDF?
> 
> Yep one disc (Scanners) - it is fine - hence my reason for beleiving it is
> a CSSism (although I guess CSS makes other demands on the UDF code).

Not so. Once a css "session" has been established, data is read just
like off any other CD. But try with this patch applied, it could be
a NULL pointer deref at the wrong time.

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs

[-- Attachment #2: idecd_log-2 --]
[-- Type: text/plain, Size: 268 bytes --]

--- drivers/ide/ide-cd.c~	Sat Dec 23 23:59:52 2000
+++ drivers/ide/ide-cd.c	Sun Dec 24 00:03:38 2000
@@ -333,7 +333,7 @@
 {
 	int log = 0;
 
-	if (sense == NULL || pc->quiet)
+	if (sense == NULL || pc == NULL || pc->quiet)
 		return 0;
 
 	switch (sense->sense_key) {

  reply	other threads:[~2000-12-25 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-24 23:42 css hang; somewhere between test12 and test13pre4ac2 Dave Gilbert
2000-12-25  1:04 ` Mohammad A. Haque
2000-12-25  1:05 ` Mohammad A. Haque
2000-12-25 11:10 ` Jens Axboe
2000-12-25 13:38   ` Dave Gilbert
2000-12-25 14:01     ` Jens Axboe [this message]
2000-12-25 17:56       ` Dave Gilbert
2000-12-25 15:50   ` Mohammad A. Haque
2000-12-25 16:01     ` Jens Axboe
2000-12-25 16:05       ` Mohammad A. Haque

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=20001225150107.D303@suse.de \
    --to=axboe@suse.de \
    --cc=gilbertd@treblig.org \
    --cc=linux-kernel@vger.kernel.org \
    /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