[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200811221654.09399.mb@bu3sch.de>
Date: Sat, 22 Nov 2008 16:54:09 +0100
From: Michael Buesch <mb@...sch.de>
To: Larry Finger <Larry.Finger@...inger.net>
Cc: Yuval Hager <yuval@...amzon.net>, bcm43xx-dev@...ts.berlios.de,
LKML <linux-kernel@...r.kernel.org>,
wireless <linux-wireless@...r.kernel.org>,
Peter Stuge <peter@...ge.se>
Subject: Re: BCM4312 Fails when xdm is started
On Saturday 22 November 2008 16:32:08 Larry Finger wrote:
> Michael Buesch wrote:
>
> > Somebody disabled MMIO and busmastering.
> > And somebody cleared the CACHE_LINE_SIZE register.
>
> Are these all the read/write bits in the configuration area? Should I conclude
> that someone zeroed this area?
Yeah well. I'm not sure. It _looks_ like someone completely cut the physical
power line to the card and it reset its complete PCI config.
So well, X does poke with the PCI devices. But as you said it also happens if
X doesn't run, I'd rule that out.
But I would not rule out a fucked BIOS, yet.
Does the BIOS have any powersave options and/or spread-spectrum options for
the PCI-bus? Can you try to turn them all off?
I have a machine that has PCI-slot autodetect and turns of the PCI clock, if
it doesn't detect a card on that slot. Also turn that off, if you have it, too.
> In case the kernel memory diagnostics don't help, is there any way to trap
> writes to the configuration registers?
Well, if we have random memory corruption, that can hit memory and MMIO.
It doesn't hurt to turn on all debugging options. Often you get some hint
by doing so.
--
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists