From: Jens Axboe <axboe@suse.de>
To: Borislav Petkov <petkov@uni-muenster.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>,
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: Fri, 1 Oct 2004 12:47:23 +0200 [thread overview]
Message-ID: <20041001104723.GH3008@suse.de> (raw)
In-Reply-To: <200410011234.12462.petkov@uni-muenster.de>
On Fri, Oct 01 2004, Borislav Petkov wrote:
> > > > I don't see any changes that could impact this from 2.6.7 to 2.6.8. We
> > > > tightened the dma alignment (from 4 to 32 bytes), but should not cause
> > > > problems going in that direction. Unless the other path is buggy, of
> > > > course.
> > > >
> > > > Does dma make a difference? Please try 2.6.9-rc3 as well.
> > >
> > > Sorry guys,
> > >
> > > still a no go. Tested today 2.6.8.1 and 2.6.9-rc3 both with DMA
> > > on/off. same lost interrupt message. How about a hardware problem?
> > > Maybe the cd-drive is showing some hidden "features" under certain
> > > conditions, although it is highly unlikely since 2.6.7 runs fine.
> > > strange...
> >
> > I can't say, probably you need to look outside of ide changes to locate
> > the problem. Have you tried disabling acpi on your box?
>
> I'm not sure whether adding the boot option acpi=off is enough to
> disable ACPI in 2.6, but if this is the case 2.6.9-rc3 is still a no
> go with acpi disabled. How about APIC?
maybe it would be more useful if you tried the -bk snapshots in between
2.6.7 and 2.6.8 to locate where the problem started. try the 2.6.8-rc
first, then try the snapshots in between when you find where the problem
was introduced.
--
Jens Axboe
next prev parent reply other threads:[~2004-10-01 10:50 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 ` Fw: Re: 2.6.9-rc2-mm4 Borislav Petkov
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 [this message]
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=20041001104723.GH3008@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=petkov@uni-muenster.de \
/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