From: Chris Vine <chris@cvine.freeserve.co.uk>
To: William Bourque <william.bourque@polymtl.ca>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
bcm43xx-dev@lists.berlios.de
Subject: Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!
Date: Sun, 28 Feb 2010 20:54:58 +0000 [thread overview]
Message-ID: <20100228205458.3e06dd35@boulder.homenet> (raw)
In-Reply-To: <4B8AD742.9000201@polymtl.ca>
On Sun, 28 Feb 2010 15:51:14 -0500
William Bourque <william.bourque@polymtl.ca> wrote:
> Chris Vine wrote:
> > On Sun, 28 Feb 2010 19:58:11 +0100
> > Michael Buesch <mb@bu3sch.de> wrote:
> >> It says 8k for all of my devices there. So an MMIO write to 0x2000
> >> and above writes to completely random memory.
> >>
> > My BCM4312 device is 16K:
> >
> > Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
>
>
> Now that you mention it, mine as well :
>
> 01:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g
> (rev 01) Subsystem: Hewlett-Packard Company Device 1507
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at feafc000 (64-bit, non-prefetchable) [size=16K]
>
> Are all the failing devices have a 16k mem space?
And with 64-bit layout? (Michael's was 32-bit.)
Chris
next prev parent reply other threads:[~2010-02-28 20:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69e28c911002260708g45d3c0f7u6abf13b1babe549f@mail.gmail.com>
[not found] ` <201002271620.31410.mb@bu3sch.de>
[not found] ` <201002271708.29817.mb@bu3sch.de>
[not found] ` <4B894A61.1070302@lwfinger.net>
[not found] ` <69e28c911002271145s590df31en9d2f8b2c47932451@mail.gmail.com>
[not found] ` <4B899DA3.4030100@lwfinger.net>
[not found] ` <69e28c911002271534o8cab111vf7fcc1b93b6c4b47@mail.gmail.com>
[not found] ` <a221c0101002271542o5d928e56n8a22602860aeb761@mail.gmail.com>
[not found] ` <69e28c911002271544y62c93255k8a6dbb0adb2b5928@mail.gmail.com>
[not found] ` <20100228001655.4c9fd9ce@boulder.homenet>
[not found] ` <4B8AAF42.8000602@polymtl.ca>
2010-02-28 18:42 ` LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??! Gábor Stefanik
2010-02-28 18:47 ` Rafał Miłecki
2010-02-28 18:52 ` Gábor Stefanik
2010-02-28 18:58 ` Michael Buesch
2010-02-28 20:30 ` Chris Vine
2010-02-28 20:33 ` Michael Buesch
2010-02-28 20:51 ` William Bourque
2010-02-28 20:54 ` Chris Vine [this message]
2010-02-28 19:44 ` William Bourque
2010-02-28 20:03 ` Chris Vine
[not found] ` <a221c0101002271703p3f344ec4t78d5c8b77c6d1290@mail.gmail.com>
[not found] ` <a221c0101002271828ye265d72y774320c08a4a15da@mail.gmail.com>
[not found] ` <69e28c911002280814v56f2f553x847c8bae94e6aaab@mail.gmail.com>
2010-02-28 22:19 ` Nathan Schulte
2010-02-28 23:03 ` Gábor Stefanik
2010-02-28 23:38 ` Nathan Schulte
2010-03-01 0:22 ` Michael Buesch
2010-03-02 21:57 ` Michael Buesch
2010-03-02 22:11 ` Larry Finger
2010-03-02 22:25 ` William Bourque
2010-03-02 22:29 ` Michael Buesch
2010-03-02 22:50 ` William Bourque
2010-03-04 0:30 ` Larry Finger
2010-03-04 0:47 ` Gábor Stefanik
2010-03-04 1:32 ` Larry Finger
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=20100228205458.3e06dd35@boulder.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=william.bourque@polymtl.ca \
/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).