From: Paul Fertser <fercerpav@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl
Date: Wed, 13 Oct 2010 03:05:44 +0400 [thread overview]
Message-ID: <20101012230543.GF1593@home.pavel.comp> (raw)
In-Reply-To: <20101012221229.GE1593@home.pavel.comp>
On Wed, Oct 13, 2010 at 02:12:29AM +0400, Paul Fertser wrote:
> On Sun, Oct 10, 2010 at 06:50:55PM +0200, G?bor Stefanik wrote:
> > 2010/10/10 Paul Fertser <fercerpav@gmail.com>:
> > > Even simply loading wl (without bringing the interface up etc) helps.
> > > Attached is a parsed mmiotrace of that (hail to nouveau). Alas simply
> > > replaying it (even with a 5ms delay inbetween writes) doesn't improve
> > > anything.
> >
> > That definitely won't help - if you just brainlessly replay an
> > mmiotrace, the writes will end up on the wrong SSB cores. You also
> > need to replay PCI config space writes. AFAIK there has been a patch
> > earlier on the list to show PCI config space accesses in mmiotrace.
>
> Before i was using the bleeding edge compat-wireless and now i compiled
> wireless-testing 4b8f8abb4f. With compat-wireless b43 reliably didn't work at
> all after cold booting, producing Fatal DMA error immediately with no used
> slots. With w-t (even unmodified!) b43 does work after cold boot :-O Once i've
> seen it produce Fatal DMA error again while transferring a file over scp (can't
> reproduce anymore, dmesg attached)
In fact, i can reliably reproduce Fatal DMA error on b43 cold boot with w-t
by ssh'ing zeroes to a host (connected via ethernet to AP) in about 3
minutes. And this doesn't seem to happen if i modprobe and rmmod wl beforehand
(without even bringing the interface up).
Any other tests i can do for you? :)
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav at gmail.com
prev parent reply other threads:[~2010-10-12 23:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 11:53 Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl Paul Fertser
2010-10-09 18:36 ` Paul Fertser
2010-10-09 20:37 ` Gábor Stefanik
2010-10-09 21:32 ` Paul Fertser
2010-10-09 21:37 ` Gábor Stefanik
2010-10-10 7:21 ` Paul Fertser
2010-10-10 15:39 ` Larry Finger
2010-10-10 17:03 ` Paul Fertser
2010-10-11 1:50 ` Larry Finger
2010-10-11 7:37 ` Rafał Miłecki
2010-10-13 6:58 ` PIO mode (was: Re: Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl) Paul Fertser
2010-10-17 22:35 ` PIO mode Larry Finger
2010-10-18 4:11 ` Paul Fertser
2010-10-18 19:57 ` Larry Finger
2010-10-19 0:43 ` Paul Fertser
2010-10-19 16:04 ` Larry Finger
2010-10-19 16:22 ` Paul Fertser
2010-10-19 17:02 ` Larry Finger
2010-10-20 17:37 ` Larry Finger
2010-10-20 17:54 ` Paul Fertser
2010-10-20 18:31 ` Larry Finger
2010-10-20 19:37 ` MMIO trace for "warm" boot of b43 on IdeaPad S9 (was: Re: PIO mode) Paul Fertser
2010-10-20 22:19 ` Larry Finger
2010-10-21 6:05 ` MMIO trace for "warm" boot of b43 on IdeaPad S9 Paul Fertser
2010-10-21 8:53 ` Transfer zeroes via ssh test (was: Re: PIO mode) Paul Fertser
2010-10-21 14:27 ` Larry Finger
2010-10-21 20:55 ` Michael Büsch
2010-10-10 16:50 ` Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl Gábor Stefanik
2010-10-12 22:12 ` Paul Fertser
2010-10-12 23:05 ` Paul Fertser [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=20101012230543.GF1593@home.pavel.comp \
--to=fercerpav@gmail.com \
--cc=b43-dev@lists.infradead.org \
/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).