On 28/12/09 04:49, Larry Finger wrote:
> Hi,
>
> In the latest Broadcom driver, I found code that sets the timeout field of the
> SSB configuration for some BCM4311 and all BCM4312 devices. Please test this
> patch following a cold boot.
>
Sadly it does not work. Tested with the mainline kernel. T
On 19/12/09 19:55, Chris Vine wrote:
> On Sat, 19 Dec 2009 10:43:29 -0600
> Larry Finger wrote:
>> Hi,
>>
>> If possible, please test this patch starting from a cold boot. It is a
>> variation of something we tried earlier, but enough different to try
>> it.
>>
>> Thanks,
>>
>> Larry
>
> I applied
On 29/11/09 23:15, Larry Finger wrote:
Does /sys/kernel/debug exist? If not, you would need to
mount -t debugfs debugfs /sys/kernel/debug
In /etc/fstab, there is a line
debugfs /sys/kernel/debug debugfs noauto 0 0
Thanks, that's much better. I hope these files make sense. If I've done
On 29/11/09 18:41, Larry Finger wrote:
> It seems that none of the "special" things that the wl driver does on my
> system has any affect on the DMA errors. I would appreciate if one of
> you would do the following:
>
> 1. Set CONFIG_MMIOTRACE=y in .config.
>
> 2. Apply the attached patch 'log_pcic
On 29/11/09 21:01, Gábor Stefanik wrote:
> Do not edit your config directly, use {menu|x|g}config. You need to
> enable the tracing framework to see mmiotrace.
>
Thanks, I used make menuconfig, set CONFIG_MMIOTRACE=y
rebooted but when I ran start_mmio_log it said:-
root:/home/andy# '/home/andy/s
On 29/11/09 18:41, Larry Finger wrote:
> It seems that none of the "special" things that the wl driver does on my
> system has any affect on the DMA errors. I would appreciate if one of
> you would do the following:
>
> 1. Set CONFIG_MMIOTRACE=y in .config.
>
I can't find that option. I have
CONF
On 29/11/09 02:59, Larry Finger wrote:
> It is not my day. This statement is the one that I wanted.
>
> Please see if this one does any good.
>
> Larry
>
>
>
> Index: wireless-testing/drivers/ssb/pci.c
> ===
> ---
On 28/11/09 17:12, Larry Finger wrote:
> Thanks for testing the other patch. To try to test the differences,
> I also dumped the PCI configuration writes and found one that wl does.
>
> Please see if this one helps.
>
> Larry
>
>
>
>
> Index: wireless-testing/drivers/ssb/driver
On 27/11/09 20:57, Larry Finger wrote:
> Please try this patch without the pm_qos patch to see if it helps. The
> Broadcom
> wl driver does this during the setup.
>
Sorry, it doesn't help. With a kernel compiled with
CONFIG_ACPI_PROCESSOR=y
it goes straight to the usual DMA errors.
Thanks for try
On 24/11/09 19:06, Larry Finger wrote:
> know what versions are giving the trouble. With SSB_DEBUG enabled, it will be
> in
> a log line as follows:
>
> ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
>
> If you are seeing the DMA error, please supply the above info.
>
I have been see
On 24/11/09 18:05, Larry Finger wrote:
> The wl driver needs lib80211 as a module. Check your .config for
> CONFIG_LIB80211.
>
> Larry
The wl driver works well for me with a monolithic kernel. The only
module I have is wl
andy:~$ lsmod
Module Size Used by
wl
On 24/11/09 20:25, Chris Vine wrote:
> For the record, and in case someone else needs it, I had to apply this
> one: one glue file didn't include sched.h as it should have done
> (presumably one of the other included headers happened to include it in
> kernel>= 2.6.31 but not after). I don't know w
On 20/11/09 10:54, Michael Buesch wrote:
Can somebody give me a genuine SPROM image for an LP-PHY card, please?
Just do this:
sudo cat $(find /sys/devices -name ssb_sprom)> ssb_sprom_copy
Does this help?
Andy
ssb_sprom_copy
Description: Binary data
__
On 14/11/09 11:24, Chris Vine wrote:
> Be aware that if you have been using the proprietary wl driver to send
> on your bug reports, you must do a cold boot before testing b43, as if
> you warm boot after having initialised the wireless device with the wl
> driver then the DMA bug disappears.
That
On 14/11/09 07:29, Matthew Garrett wrote:
>
> I should emphasise that this patch works by effectively disabling deep C
> states on your CPU, which in turn will increase your power consumption.
> It's very much either a workaround for broken hardware or something that
> covers up a more subtle bug s
On 13/11/09 21:38, Larry Finger wrote:
> Based on a suggestion by Matthew Garrett, please try the patch below.
>
I've only been using it for a few minutes but this looks very good. I
compile the kernel with lots of ACPI
CONFIG_ACPI=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=
On 13/11/09 17:36, Michael Buesch wrote:
> Please test the following patch. It changes more stuff related to the
> descriptor ring handling (remove the old patch first before applying this
> one).
> http://bu3sch.de/patches/wireless-testing/20091113-1834/patches/001-b43-rewrite-dma-ring-alloc.patc
On 13/11/09 13:18, Andrew Benton wrote:
> Since I applied Larry's patch I've not had any error's with a kernel
> compiled with
> # CONFIG_ACPI is not set
Wouldn't you know it, as soon as I sent that I got this:-
Nov 13 13:21:22 doughnut kernel: b43-phy0 ERROR
On 12/11/09 21:16, Michael Buesch wrote:
> Here you go:
> http://bu3sch.de/patches/wireless-testing/20091112-2213/patches/001-b43-rewrite-dma-ring-alloc.patch
> Please test this patch (also on 64bit-DMA devices that currently work).
>
> It seriously lacks some comments, but I'll add them later if
On 12/11/09 17:14, Larry Finger wrote:
> I guess I'm a failure at writing diagnostic patches. Until there is a DMA
> error,
> the only effect of the patch is to add a little extra time to the routine that
> fills in the descriptor structure, and it adds to the data and code size. If
> any
> of th
On 12/11/09 15:50, Larry Finger wrote:
> Sorry about the kernel mismatch. I developed that patch while offline and
> waiting at an auto repair place and forgot to refresh my sources before
> sending
> it. The revised version that Michael sent should work. If not, please let me
> know and I will se
On 12/11/09 00:37, Larry Finger wrote:
> Andy,
>
> Please try the patch below to see what we can learn from the DMA descriptor
> errors. Some of this code is temporary, but there are also some statements
> that
> will probably become permanent.
>
> Please post any messages that result.
The patch
On 11/11/09 19:12, Larry Finger wrote:
>
> Such an error in SLUB handling could be arising from a DMA problem in b43, but
> it could also arise from a memory error. Please run memtest86+ for an extended
> period so that a hardware error can be ruled out. A 24 hour run would be good.
> If that is no
I recompiled my kernel today (current wireless-testing) and disabled ACPI
entirely.
It worked fine for 10 minutes and then the internet connection died and left
this
in /var/log/sys.log
Nov 11 14:31:31 doughnut ntpd[398]: kernel time sync status change 2001
Nov 11 14:36:57 doughnut ntpd[398]: sy
On 11/11/09 02:58, Larry Finger wrote:
> On 11/10/2009 06:48 PM, Andrew Benton wrote:
>> Nov 11 00:04:37 doughnut kernel: b43-phy0 ERROR: Fatal DMA error:
>> 0x0400, 0x, 0x, 0x, 0x, 0x
>> Nov 11 00:04:37 doughnut kernel: b43-phy0:
Hello world,
I have a Dell inspiron 910 with a Broadcom wireless card.
andy:~$ lspci -vnn | grep 14e4
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312
802.11b/g [14e4:4315] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04b5]
Today I downloaded the current wireless-
26 matches
Mail list logo
