netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Daniel Gryniewicz <dang@fprintf.net>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org
Subject: Re: [PATCH, RFT] bcm43xx: Busting the 1G limit
Date: Mon, 19 Jun 2006 22:43:08 +0200	[thread overview]
Message-ID: <200606192243.09039.mb@bu3sch.de> (raw)
In-Reply-To: <1150730630.9048.2.camel@athena.fprintf.net>

On Monday 19 June 2006 17:23, Daniel Gryniewicz wrote:
> On Sat, 2006-06-17 at 19:28 +0200, Michael Buesch wrote:
> > Hi,
> > 
> > This patch adds full 32-bit and 64-bit DMA support
> > to the bcm43xx driver. Well, it _should_ do this. I can
> > not test it, as I don't have a machine to trigger the 1G
> > limit.
> > The 1G limit should be exploitable on an AMD64 machine
> > with more than 1G RAM.
> > 
> > Please test and report, if it works or not. In the
> > case of "works not", please provide full dmesg log.
> > 
> > Note that I am not sure which cards actually support
> > full 32-bit or even 64-bit mode. Older cards might still
> > only support 30-bit DMA.
> 
> Hi.
> 
> I tried this on both 2.6.17-rc6 and on wireless-dev, and got pretty much
> the same panic on both (modulo locking).  My box is a turion with 2 GB
> of ram and a BCM4318.  Here's the panic from wireless-dev:
> 
> Unable to handle kernel NULL pointer dereference at 0000000000000020
> RIP:
> <ffffffff88104f24>{:bcm43xx:bcm43xx_dma_handle_xmitstatus+436}

I am still not absolutely sure where this oops comes from.
Could you remove at least 1G of your RAM and retry?

-- 
Greetings Michael.

  reply	other threads:[~2006-06-19 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17 17:28 [PATCH, RFT] bcm43xx: Busting the 1G limit Michael Buesch
2006-06-19 15:23 ` Daniel Gryniewicz
2006-06-19 20:43   ` Michael Buesch [this message]
2006-06-19 23:06     ` Daniel Gryniewicz

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=200606192243.09039.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=dang@fprintf.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).