From: Borislav Petkov <petkov@uni-muenster.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
Cc: Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fw: Re: 2.6.9-rc2-mm4
Date: Thu, 30 Sep 2004 17:32:02 +0200 [thread overview]
Message-ID: <200409301732.03080.petkov@uni-muenster.de> (raw)
In-Reply-To: <200409301452.52134.bzolnier@elka.pw.edu.pl>
On Thursday 30 September 2004 14:52, Bartlomiej Zolnierkiewicz wrote:
> On Thursday 30 September 2004 06:46, Andrew Morton wrote:
> > ide broke :( Maybe Bart's bk tree?
>
> no, disk works just fine ;) If it is my tree I will happilly fix it.
>
> Borislav, could you apply only these patches from -mm4 and retest?
>
> linus.patch
> bk-ide-dev.patch
>
> > Begin forwarded message:
> >
> > Date: Wed, 29 Sep 2004 12:43:35 +0200
> > From: Borislav Petkov <petkov@uni-muenster.de>
> > To: Andrew Morton <akpm@osdl.org>
> > Cc: linux-kernel@vger.kernel.org
> > Subject: Re: 2.6.9-rc2-mm4
> >
> >
> > <snip>
> >
> > Hello,
> > I've already posted about problems with audio extraction but it went
> > unnoticed. Here's a recount: When I attempt to read an audio cd into wavs
> > with cdda2wav, the process starts but after a while the completion meter
> > freezes and klogd says "hdc: lost interrupt" and cdda2wav hangs itself.
> > Disabling DMA doesn't help as well as the boot option "pci=routeirq" too.
> > Older kernels like 2.6.7 do not show such behavior and there audio
> > extraction runs fine. Sysinfo attached.
> >
> > Regards,
> > Boris.
Hi people,
well, I've applied the above patches but no change - same "hdc: lost
interrupt" message. 2.6.9-rc3 behaves the same, as expected.
Regards,
Boris.
next parent reply other threads:[~2004-09-30 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040929214637.44e5882f.akpm@osdl.org>
[not found] ` <200409301452.52134.bzolnier@elka.pw.edu.pl>
2004-09-30 15:32 ` Borislav Petkov [this message]
2004-09-30 16:25 ` Bartlomiej Zolnierkiewicz
2004-09-30 21:46 ` Borislav Petkov
2004-09-30 23:30 ` Bartlomiej Zolnierkiewicz
2004-10-01 5:43 ` Borislav Petkov
2004-10-01 9:18 ` Jens Axboe
2004-10-01 9:54 ` Borislav Petkov
2004-10-01 9:54 ` Jens Axboe
2004-10-01 10:34 ` Borislav Petkov
2004-10-01 10:47 ` Jens Axboe
2004-10-01 11:03 ` Borislav Petkov
2004-10-01 18:42 ` Borislav Petkov
2004-10-03 7:51 ` Borislav Petkov
2004-10-04 15:54 ` Borislav Petkov
2004-10-04 17:36 ` Jens Axboe
2004-10-04 20:12 ` Borislav Petkov
2004-10-04 20:42 ` Jens Axboe
2004-10-04 21:11 ` Borislav Petkov
2004-10-05 7:12 ` Jens Axboe
2004-10-05 9:29 ` Borislav Petkov
2004-10-04 21:14 ` Borislav Petkov
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=200409301732.03080.petkov@uni-muenster.de \
--to=petkov@uni-muenster.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@elka.pw.edu.pl \
--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®