From: "Roland Vossen" <rvossen@broadcom.com>
To: "Pedram Navid" <pedram.navid@gmail.com>
Cc: "Henry Ptasinski" <henryp@broadcom.com>,
"ali@internetdog.org" <ali@internetdog.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmsmac: fifo 0: descriptor error
Date: Fri, 19 Aug 2011 16:29:25 +0200 [thread overview]
Message-ID: <4E4E7345.5020701@broadcom.com> (raw)
In-Reply-To: <CAPoLzpeuPy9T7Q471pBz7A-RLuZykjo-apadm-nGjVdQhM9-7Q@mail.gmail.com>
Hello Pedram,
Bugzilla seems to be AWOL today so lets continue the discussion by email.
I noticed this issue is still pending. It is weird that the problem
persists between cold reboots (which points to a hardware error) but is
also dependent on the kernel version in use (which points to a software
error).
Would you happen to have additional cards to try ?
Can you email a log file containing the 'fifo 0: descriptor error' bug ?
Do you think that temperature has an effect on the bug occurring, does
it make a difference if you let your machine cool down between reboots ?
I identified an issue today that gives the same error message, but that
issue only occurs on 64 bit platforms, and you report that you also see
it on 32 bit platforms.
Can you run a memory test on your system, e.g. one that tests the memory
during an overnight test ? Reason is that the error message occurs
because the DMA engine read invalid data from memory.
Thanks, Roland.
On 08/12/2011 02:33 AM, Pedram Navid wrote:
> Hi Henry,
>
> I have filed this as bug 40972 along with the answers to your
> questions: https://bugzilla.kernel.org/show_bug.cgi?id=40972
>
> In short, yes, the error does appear immediately after a full
> power-off shutdown as soon as I bring the interface up after loading
> the module. Not always, but more often than not.
>
> I am running 32-bit but have used 64bit prior. I reinstalled my system
> thinking that it was a problem with 64-bit libraries. The full lsmod
> is on the bug report.
>
> I am currently running fine again. I will keep my laptop on throughout
> the day in the hopes that it goes down. Let me know if you need
> anything else.
>
> Thanks so much
> Pedram
prev parent reply other threads:[~2011-08-19 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6264DDFA6754194CAB6452BFF5202C330F5F2115@SXGM-401.fg.rbc.com>
2011-08-10 22:48 ` Fwd: Pedram Navid
2011-08-11 2:15 ` brcmsmac: fifo 0: descriptor error Ali Bahar
2011-08-11 10:35 ` Pedram Navid
2011-08-11 22:26 ` Henry Ptasinski
2011-08-12 0:33 ` Pedram Navid
2011-08-19 14:29 ` Roland Vossen [this message]
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=4E4E7345.5020701@broadcom.com \
--to=rvossen@broadcom.com \
--cc=ali@internetdog.org \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pedram.navid@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 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).