From: "Gerhard Pircher" <gerhard_pircher@gmx.net>
To: jfannin@gmail.com, benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: BUG() in current git, __dma_alloc_coherent, Beige G3
Date: Mon, 16 Jun 2008 09:03:59 +0200 [thread overview]
Message-ID: <20080616070359.300020@gmx.net> (raw)
In-Reply-To: <1213591838.8129.123.camel@pasglop>
-------- Original-Nachricht --------
> Datum: Mon, 16 Jun 2008 14:50:38 +1000
> Von: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> An: Joseph Fannin <jfannin@gmail.com>
> CC: linuxppc-dev@ozlabs.org
> Betreff: Re: BUG() in current git, __dma_alloc_coherent, Beige G3
> > This is 100% reproducable. I can't really recall the last kernel I
> > built and booted successfully on this box -- the best I can say is
> > that the 2.6.24-ish kernel Ubuntu ships works.
> >
> > I should probably mention that I've been having a little trouble with
> > the IDE drive in this machine -- but the drive isn't the problem:
> >
> > * This is 100% reproducible with the current git kernel, and
> > doesn't happen w/the Ubuntu kernel
> > * The traceback and dump does not vary between boots
> > * The kernel BUGs out well before the disks are detected (and it's
> > a _drive_ problem)
> >
> > ... etc. :-) I don't want to send anyone on a wild goose chase, but
> > yeah, it's not the hardware. ;-)
> >
> > So, what can I do to help find the problem here? Git says no one's
> > touched that file in a while, and tracing through this problem is
> > above my skill level here. I'll attach my .config, and put the
> > vmlinux up:
I discovered this bug some time ago and reported it on the list.
See here for more info:
http://ozlabs.org/pipermail/linuxppc-dev/2008-May/056128.html
Anyway I don't think your machine needs dma-noncoherent.
best regards,
Gerhard
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
next prev parent reply other threads:[~2008-06-16 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 1:46 BUG() in current git, __dma_alloc_coherent, Beige G3 Joseph Fannin
2008-06-16 4:50 ` Benjamin Herrenschmidt
2008-06-16 7:03 ` Gerhard Pircher [this message]
2008-06-16 7:11 ` Benjamin Herrenschmidt
2008-06-16 7:30 ` Joseph Fannin
2008-06-16 9:05 ` Benjamin Herrenschmidt
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=20080616070359.300020@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=benh@kernel.crashing.org \
--cc=jfannin@gmail.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).