From: Christian Lamparter <chunkeey@web.de>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [p54]: oops in p54_rx
Date: Mon, 8 Dec 2008 16:50:25 +0100 [thread overview]
Message-ID: <200812081650.26024.chunkeey@web.de> (raw)
In-Reply-To: <20081208153208.GC4221@roarinelk.homelinux.net>
On Monday 08 December 2008 16:32:08 Manuel Lauss wrote:
> On Mon, Dec 08, 2008 at 04:24:21PM +0100, Christian Lamparter wrote:
> > On Monday 08 December 2008 15:47:27 Manuel Lauss wrote:
> > [...]
> > > > > But what I can do is to stop the driver from oopsing...
> > > > >
> > > > > I guess a check to see if the device mode is set to something else than
> > > > > "NL80211_IFTYPE_UNSPECIFIED" and in p54_rx(_data) should prevent the oops.
> > > > > maybe we I should add a hex_dump as well.
> > > >
> > > > patch attached... tell me what it does on your dev.
> > >
> > > Thank you, but I think the card is faulty... it doesn't work even on winxp
> > > ("device cannot be started Code 10"-error). Do you still want me to test
> > > the patch?
> > Did you try the card in the same system with 4Gb and with the original SMC driver?
> > Well, either way... you could "confirm" that doesn't crash anymore ;-).
>
> Tested on another machine with 1gb ram. It doesn't crash anymore. If you're
> still interested, the log output is here http://mlau.at/files/p54log
>
interesting, the "logged" data has about the correct size.
But the data is totally screwed up.
So, yes you can kick it into the bin if you want to.
Regards,
Chr
prev parent reply other threads:[~2008-12-08 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 7:49 [p54]: oops in p54_rx Manuel Lauss
2008-12-08 13:08 ` Christian Lamparter
2008-12-08 13:26 ` Manuel Lauss
2008-12-08 14:09 ` Christian Lamparter
2008-12-08 14:48 ` Christian Lamparter
2008-12-08 14:47 ` Manuel Lauss
2008-12-08 15:24 ` Christian Lamparter
2008-12-08 15:32 ` Manuel Lauss
2008-12-08 15:50 ` Christian Lamparter [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=200812081650.26024.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mano@roarinelk.homelinux.net \
/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).