All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Daiker <daikerjohn@gmail.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Michael Buesch <mb@bu3sch.de>,
	Dave Young <hidave.darkstar@gmail.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	bcm43xx-dev@lists.berlios.de
Subject: Re: b43 dma error
Date: Wed, 09 Sep 2009 22:39:05 -0700	[thread overview]
Message-ID: <4AA890F9.90604@gmail.com> (raw)
In-Reply-To: <69e28c910909081106p413b70d8u83a48a63943f123e@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]

On 09/08/2009 11:06 AM, Gábor Stefanik wrote:
> On Tue, Sep 8, 2009 at 7:50 PM, John Daiker<daikerjohn@gmail.com>  wrote:
>> On 09/08/2009 07:54 AM, Larry Finger wrote:
>>>
>>> Michael Buesch wrote:
>>>>
>>>> On Tuesday 08 September 2009 15:47:32 Dave Young wrote:
>>>>>
>>>>> I tested wireless-testing b43 driver, but got "Fatal DMA error"
>>>>> then the controller keep restarting...
>>>>>
>>>>> Please tell what I can provide or test, Thanks.
>>>>
>>>> Is this a regression? If so, please bisect.
>>>
>>> It is something specific to his system as I don't see anything like
>>> this. In addition, there are some users on the openSUSE forums that
>>> have implemented the latest compat-wireless and switched away from
>>> Broadcom wl to b43 on their LP PHY devices. So far, no complaints from
>>> them.
>>>
>>> Please reboot so that we see the ssb output as well. Use the command
>>>
>>> dmesg | egrep "ssb|b43"
>>>
>>> That way we will be able to see exactly what kind of device you have
>>> and what revisions are in it. AFAIK, the testing to date has been
>>> limited to Rev 1 PHYs and Rev 2 radios.
>>>
>>> Larry
>>>
>>
>> I can confirm the same issue.  I have a HP Mini 1116NR with a Broadcom 4312.
>>   Looks to be a PHY 1, Radio 2:
>>
>> --snip--
>> [  456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
>> [  456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062,
>> Revision 2
>> --snip--
>>
>> I've attached the output of 'dmesg | egrep "ssb|b43"', my kernel config, and
>> lspci -vv and lspci -nn
>>
>> Note: With the dmesg output, I had unloaded the b43 module previous
>> 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43
>> verbose=3'
>>
>> John Daiker
>>
>
> Again, please test with v478 or v5xx firmware.
>

I've tried with the v478 firmware (was using 410.2160 earlier).  I do 
not see the 'Fatal DMA error' messages anymore.

On another note, however, I can't connect to a network.  The device 
seems to alternate between being idle, and scanning for APs.

--snip--
[   73.273722] phy0: device no longer idle - scanning
[   74.561178] phy0: device now idle
[   79.545776] phy0: device no longer idle - scanning
[   80.828232] phy0: device now idle
[   85.817930] phy0: device no longer idle - scanning
[   87.100240] phy0: device now idle
[   92.090713] phy0: device no longer idle - scanning
[   93.372367] phy0: device now idle
[   98.362829] phy0: device no longer idle - scanning
[   99.644362] phy0: device now idle
--snip--

I've attached the relevant portion of my dmesg output for your review.

Where would I got about finding the v5xx firmware?

JD

[-- Attachment #2: dmesg4.out --]
[-- Type: text/plain, Size: 5767 bytes --]

[    2.757126] ata1.00: 32014080 sectors, multi 0: LBA 
[    2.760697] ata1.00: configured for UDMA/66
[    2.764095] scsi 0:0:0:0: Direct-Access     ATA      SanDisk pSSD 16G SSD  PQ: 0 ANSI: 5
[    2.767539] sd 0:0:0:0: [sda] 32014080 512-byte logical blocks: (16.3 GB/15.2 GiB)
[    2.770945] sd 0:0:0:0: [sda] Write Protect is off
[    2.774063] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.774130] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.777645]  sda: sda1 sda2 < sda5 >
[    2.783573] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.805784] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.884226] usb 2-4: new high speed USB device using ehci_hcd and address 2
[    3.021207] usb 2-4: configuration #1 chosen from 1 choice
[    3.031363] PM: Starting manual resume from disk
[    3.034864] PM: Resume from partition 8:5
[    3.034870] PM: Checking hibernation image.
[    3.035379] PM: Resume from disk failed.
[    3.050990] kjournald starting.  Commit interval 5 seconds
[    3.054614] EXT3-fs: mounted filesystem with writeback data mode.
[    5.133366] udev: starting version 141
[    5.288161] rtc_cmos 00:03: RTC can wake from S4
[    5.296623] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    5.301658] rtc0: alarms up to one month, 114 bytes nvram, hpet irqs
[    5.408379] b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    5.412941] b43-pci-bridge 0000:01:00.0: setting latency timer to 64
[    5.415969] intel_rng: FWH not detected
[    5.484223] ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0
[    5.919876] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    5.924500]   alloc irq_desc for 27 on node -1
[    5.924510]   alloc kstat_irqs on node -1
[    5.924538] HDA Intel 0000:00:1b.0: irq 27 for MSI/MSI-X
[    5.924601] HDA Intel 0000:00:1b.0: setting latency timer to 64
[    6.065608] cfg80211: Calling CRDA to update world regulatory domain
[    6.135544] cfg80211: World regulatory domain updated:
[    6.140053] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    6.144677] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    6.149242] 	(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    6.153577] 	(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    6.157648] 	(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    6.161316] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    6.164837] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[    6.196723] Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04711/0xa00000
[    6.217255] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
[    6.217323] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2
[    6.236154] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input6
[    6.253094] phy0: Selected rate control algorithm 'minstrel'
[    6.254037] Broadcom 43xx driver loaded [ Features: P, Firmware-ID: FW13 ]
[    6.524646] Adding 714852k swap on /dev/sda5.  Priority:-1 extents:1 across:714852k 
[    6.655873] EXT3 FS on sda1, internal journal
[    7.594436] RPC: Registered udp transport module.
[    7.594446] RPC: Registered tcp transport module.
[    7.707497] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   16.004269] sky2 eth0: enabling interface
[   16.048220] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[   16.077797] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
[   16.093394] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[   16.260549] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[   16.262985] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
[   16.528117] b43-phy0 debug: Chip initialized
[   16.528356] b43-phy0 debug: 64-bit DMA initialized
[   16.528488] b43-phy0 debug: QoS enabled
[   16.552302] b43-phy0 debug: Wireless interface started
[   16.552387] b43-phy0 debug: Adding Interface type 2
[   16.565100] phy0: device now idle
[   16.726639] phy0: device no longer idle - scanning
[   18.021167] phy0: device now idle
[   22.278870] CPU0 attaching NULL sched-domain.
[   22.278883] CPU1 attaching NULL sched-domain.
[   22.293140] CPU0 attaching sched-domain:
[   22.293150]  domain 0: span 0-1 level SIBLING
[   22.293159]   groups: 0 1
[   22.293172] CPU1 attaching sched-domain:
[   22.293179]  domain 0: span 0-1 level SIBLING
[   22.293185]   groups: 1 0
[   24.988037] Clocksource tsc unstable (delta = -127524381 ns)
[   37.001487] phy0: device no longer idle - scanning
[   38.284344] phy0: device now idle
[   67.002945] phy0: device no longer idle - scanning
[   68.284208] phy0: device now idle
[   73.273722] phy0: device no longer idle - scanning
[   74.561178] phy0: device now idle
[   79.545776] phy0: device no longer idle - scanning
[   80.828232] phy0: device now idle
[   85.817930] phy0: device no longer idle - scanning
[   87.100240] phy0: device now idle
[   92.090713] phy0: device no longer idle - scanning
[   93.372367] phy0: device now idle
[   98.362829] phy0: device no longer idle - scanning
[   99.644362] phy0: device now idle
[  104.634101] phy0: device no longer idle - scanning
[  105.916364] phy0: device now idle
[  110.906370] phy0: device no longer idle - scanning
[  112.188368] phy0: device now idle
[  117.178654] phy0: device no longer idle - scanning
[  118.460356] phy0: device now idle
[  123.449877] phy0: device no longer idle - scanning
[  124.733330] phy0: device now idle
[  129.723029] phy0: device no longer idle - scanning
[  131.005131] phy0: device now idle
[  157.003343] phy0: device no longer idle - scanning
[  158.285317] phy0: device now idle

  parent reply	other threads:[~2009-09-10  5:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 13:47 b43 dma error Dave Young
2009-09-08 14:08 ` Gábor Stefanik
2009-09-09  7:54   ` Dave Young
2009-09-08 14:38 ` Michael Buesch
2009-09-08 14:54   ` Larry Finger
2009-09-08 17:50     ` John Daiker
2009-09-08 18:06       ` Gábor Stefanik
2009-09-08 18:15         ` Michael Buesch
2009-09-08 18:26           ` Larry Finger
2009-09-10  5:39         ` John Daiker [this message]
2009-09-10  6:24           ` John Daiker
2009-09-08 18:13       ` Michael Buesch
2009-09-08 18:26         ` John Daiker
2009-09-08 18:16       ` Larry Finger
2009-09-08 18:24         ` Gábor Stefanik
2009-09-08 18:30           ` Larry Finger
2009-09-08 18:32             ` Gábor Stefanik
2009-09-09  2:07               ` Larry Finger
2009-09-09  7:41                 ` Markus Mueller
2009-09-08 18:32             ` John Daiker
2009-09-09  8:05             ` Dave Young
2009-09-09  8:02     ` Dave Young
2009-09-09  7:56   ` Dave Young
2009-09-10  1:28     ` Dave Young

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=4AA890F9.90604@gmail.com \
    --to=daikerjohn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netrolller.3d@gmail.com \
    /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.