From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
LKML <linux-kernel@vger.kernel.org>,
wireless <linux-wireless@vger.kernel.org>,
Peter Stuge <peter@stuge.se>
Subject: Re: BCM4312 Fails when xdm is started
Date: Fri, 21 Nov 2008 18:42:12 +0100 [thread overview]
Message-ID: <200811211842.13099.mb@bu3sch.de> (raw)
In-Reply-To: <4926E0F2.5060200@lwfinger.net>
On Friday 21 November 2008 17:25:22 Larry Finger wrote:
> A problem was recently posted to the bcm43xx mailing list that I am unable to
> solve. The machine in question is an HP Mini 2133 (HP product number FU346EA)
> with a BCM4312 PCIe wireless card. This card is known to work with the b43
> driver (I have one.) and it does work on this machine - at least initially.
>
> A problem occurs when xdm/kde is started. Suddenly a read operation on device
> hardware returns all ones as though the register does not exist, or if it were
> suddenly mismapped. If the OP doesn't try to run xdm, the same problem will
> eventually occur, it just takes longer.
Can you dump PCI config space and SSB registers (TMSLOW, maybe others, too).
It looks like a random bus write disabled the device.
> [ 0.000000] Zone PFN ranges:
> [ 0.000000] DMA 0x00000000 -> 0x00001000
> [ 0.000000] Normal 0x00001000 -> 0x000373fe
> [ 0.000000] HighMem 0x000373fe -> 0x0006feb0
>
> On my 64-bit HP machine, I see:
>
> Zone PFN ranges:
> DMA 0x00000000 -> 0x00001000
> DMA32 0x00001000 -> 0x00100000
> Normal 0x00100000 -> 0x00100000
>
> Is it "normal" for there not to be a DMA32 range with a 32-bit version of Linux?
Yeah, I think so.
--
Greetings Michael.
next prev parent reply other threads:[~2008-11-21 17:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200811151801.02369.yuval@avramzon.net>
[not found] ` <491EFB9D.3040002@lwfinger.net>
[not found] ` <200811151907.05636.yuval@avramzon.net>
[not found] ` <20081115174623.27321.qmail@stuge.se>
2008-11-21 16:25 ` BCM4312 Fails when xdm is started Larry Finger
2008-11-21 17:42 ` Michael Buesch [this message]
2008-11-21 18:28 ` Larry Finger
2008-11-22 6:39 ` Yuval Hager
2008-11-22 15:13 ` Michael Buesch
2008-11-22 15:32 ` Larry Finger
2008-11-22 15:54 ` Michael Buesch
2008-11-23 7:26 ` Yuval Hager
2008-11-23 11:49 ` Yuval Hager
2008-11-23 12:20 ` Michael Buesch
2008-11-23 15:42 ` Larry Finger
2008-11-23 17:42 ` Michael Buesch
[not found] ` <200811231955.41722.yuval@avramzon.net>
2008-11-23 18:08 ` Michael Buesch
2008-11-23 20:46 ` Peter Stuge
2008-11-23 21:09 ` Larry Finger
2008-11-24 8:49 ` Yuval Hager
2008-11-24 10:55 ` Michael Buesch
2008-11-24 16:11 ` Larry Finger
2008-11-25 5:43 ` Yuval Hager
2008-11-25 7:18 ` Peter Stuge
2008-12-07 9:29 ` Yuval Hager
2008-12-07 16:15 ` Larry Finger
2008-11-25 11:05 ` Michael Buesch
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=200811211842.13099.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peter@stuge.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.