public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Jens Axboe <axboe@suse.de>
Cc: Fabio Coatti <cova@ferrara.linux.it>,
	akpm@osdl.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok
Date: Mon, 31 Jan 2005 21:49:13 +1000	[thread overview]
Message-ID: <41FE1B39.6030702@torque.net> (raw)
In-Reply-To: <20050131110550.GA5058@suse.de>

Jens Axboe wrote:
> On Mon, Jan 31 2005, Fabio Coatti wrote:
> 
>>Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto:
>>
>>>>At this point k3b is stuck in D stat, needs reboot.
>>>
>>>The most likely suspect is the REQ_BLOCK_PC scsi changes. Can you try
>>>2.6.11-rc2-mm1 with bk-scsi backed out? (attached)
>>
>>just tried, right guess :)
>>backing out that patch the problem disappears.
>>Let me know if you need to narrow further that issue.
> 
> 
> Doug, it looks like your REQ_BLOCK_PC changes are buggy. Let me know if
> you cannot find the full post and I'll forward it to you.

Jens,
Hmm. Found the thread on lkml. I got an almost identical
lock up in k3b with a USB external cd/dvd drive recently.
My laptop didn't need rebooting (probably since the root
fs is one an ide disk).

That is a quite large patch that you referenced. I'll
try and replicate and report back.

Doug Gilbert


  reply	other threads:[~2005-01-31 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 23:34 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok Fabio Coatti
2005-01-31  8:00 ` Jens Axboe
2005-01-31 10:08   ` Fabio Coatti
2005-01-31 11:05     ` Jens Axboe
2005-01-31 11:49       ` Douglas Gilbert [this message]
2005-01-31 11:49         ` Jens Axboe
2005-01-31 13:09           ` Douglas Gilbert
2005-01-31 13:53             ` Jens Axboe

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=41FE1B39.6030702@torque.net \
    --to=dougg@torque.net \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=cova@ferrara.linux.it \
    --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