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: Mon, 26 Jun 2006 20:59:33 +0200 [thread overview]
Message-ID: <20060626185933.GA21692@bm617259.muenchen.org> (raw)
In-Reply-To: <20060624144739.78bde590.akpm@osdl.org>
On Sat, 24 Jun 2006 23:50:07 +0200, Andrew Morton wrote:
> On Sat, 24 Jun 2006 13:36:28 -0700
> bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=6745
>> [...]
> We seem to have an awful lot of these "CD burner doesn't work but it
> did in
> 2.4" reports.
>
> Does anyone have the vaguest inklink of how we broke it?
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.
So it is only the combination that makes the bug appear.
I hope that with that information it will be possible to fix the kernel
so that it doesn't hang.
ciao
Christian
--
NP: Pantera - Strength Beyond Strength
next prev parent reply other threads:[~2006-06-26 18:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2006-06-25 19:40 Joerg Schilling
2006-06-26 0:01 ` Christian Lohmaier
2006-06-26 18:21 Joerg Schilling
2006-06-26 18:49 Christian Lohmaier
2006-06-28 7:18 Joerg Schilling
2006-06-28 7:29 Joerg Schilling
2006-06-28 11:19 ` 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=20060626185933.GA21692@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®