mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Lohmaier <cloph@openoffice.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6745] New: kernel hangs when trying to read    atip wiith cdrecord
Date: Wed, 28 Jun 2006 13:19:38 +0200	[thread overview]
Message-ID: <20060628111937.GA4126@bm617259.muenchen.org> (raw)
In-Reply-To: <44A22FC3.nail3NU1XXW6C@burner>

On Wed, 28 Jun 2006 09:30:22 +0200, Joerg Schilling wrote:
> Christian Lohmaier wrote:
>>I updated the bug-report with some info I collected from another bug. 
>
>>Apparently my drive sends additional interrupts that confuses the kernel 
>>and make it hang. 
>>The problem is triggered with newer versions of cdrecord (cdrtools 
>>2.01a33 and newer) where cdrecord changed its driver interface. 
> 
> cdrtools-2.01a33 is extremely old (2 years).
> 
> It did not introduce new SCSI commands (compared to prevuious versions) and I
> would be interested why this problem is discussed late.

Because that problems only occurs in the combination of recent cdrtools with
kernel 2.6.x
I for myself have been using kernel 2.4.x until recently I switched to 2.6.x

> The only new thing with cdrecord-2.01a33 is that it started to transfer more 
> than 4 bytes with the "read buffer" command. As this is only issued in case that
> the "read buffer" command did succeed with 4 bytes transfer count and as 
> cdrecord does not transfer more than the drive advertizes, I am just depending 
> on a kernel that does not freeze from the SCSI command I am issuing.

OK - thats already a hint. Maybe this helps the kernel-devs.

ciao
Christian
-- 
NP: Papa Roach - Between Angels And Insects

  reply	other threads:[~2006-06-28 11:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28  7:29 Joerg Schilling
2006-06-28 11:19 ` Christian Lohmaier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-28  7:18 Joerg Schilling
2006-06-26 18:49 Christian Lohmaier
2006-06-26 18:21 Joerg Schilling
2006-06-25 19:40 Joerg Schilling
2006-06-26  0:01 ` Christian Lohmaier
2006-06-25 10:53 Joerg Schilling
2006-06-25 11:06 ` Andrew Morton
2006-06-25 11:46   ` Joerg Schilling
2006-06-25 19:35     ` Joerg Schilling
     [not found] <200606242036.k5OKaSvp031813@fire-2.osdl.org>
2006-06-24 21:47 ` Andrew Morton
2006-06-25 11:05   ` Jan Engelhardt
2006-06-25 11:36     ` Andrew Morton
2006-06-25 19:00       ` Christian Lohmaier
2006-06-25 11:07   ` Arjan van de Ven
2006-06-25 11:37     ` Andrew Morton
2006-06-26 18:59   ` Christian Lohmaier

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=20060628111937.GA4126@bm617259.muenchen.org \
    --to=cloph@openoffice.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

all inboxes | Powered by JetHome®