public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc
Date: Mon, 21 Nov 2005 08:00:40 +1100	[thread overview]
Message-ID: <1132520441.6052.41.camel@gaston> (raw)
In-Reply-To: <59EA4A9E-0F86-4D53-8DDD-56F6DDC6E726@mac.com>


> This is the only possibility that I can think of, but I'm having a  
> hard time getting enough lines of pre-BUG output.  Is there any way  
> to turn off the BUG() lines and just show the printks before that point?

There is a patch from Thibault that fixes it, it should be in 2.6.15-rc2

Ben.



  reply	other threads:[~2005-11-20 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051017005855.132266ac.akpm@osdl.org>
     [not found] ` <1129536482.7620.76.camel@gaston>
     [not found]   ` <6DFB5723-0042-46FE-811F-BF372B068014@mac.com>
2005-10-19 17:48     ` [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc Kyle Moffett
2005-10-19 22:13       ` Benjamin Herrenschmidt
2005-10-19 23:14         ` Kyle Moffett
2005-10-20  1:36           ` Benjamin Herrenschmidt
2005-11-20 18:29             ` Kyle Moffett
2005-11-20 21:00               ` Benjamin Herrenschmidt [this message]
2005-11-21 21:21                 ` Bug in promise_new ide conteroller (was: Re: [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc) Kasper Sandberg
2005-10-15 22:29 [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc Kyle Moffett

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=1132520441.6052.41.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    /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