From: Christian Lamparter <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Memory errors from p54usb
Date: Wed, 17 Dec 2008 17:36:37 +0100 [thread overview]
Message-ID: <200812171736.38289.chunkeey@web.de> (raw)
In-Reply-To: <49492245.9010500@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Wednesday 17 December 2008 17:01:09 Larry Finger wrote:
> Christian Lamparter wrote:
> > Ohh, it always gets better. ;)
> > Anyway, I'll see what I can do tomorrow.
> >
> > In the meantime, I remembered that I put a heat sink on my chip a while ago,
> > but I'm not sure if this had any effect here... But back in the summer, it allowed me
> > fix the iperf stalls I had, but that was after days with 60Gb traffic...
>
> That would be a good idea; however, it is winter in my hemisphere (I don't care
> what the calender says.), and the room is cool. In addition, my device is a Dell
> Wireless 1450, which comes with a pretty hefty heat sink on its own.
Your had already one? Perhaps, I got a very old one then. (Rev A01)
> I'll throw printk's into every place I can think of and try to provide more info.
maybe this printk could shed some light into the dark...
(In station mode: "status" should be either 0(ACKed) or 1(not ACKed/timeout)
and (2 [ device is sleeping - but we don't set the PSM yet, so this is not expected])
Regards,
Chr
[-- Attachment #2: p54test.diff --]
[-- Type: text/x-diff, Size: 646 bytes --]
diff -Nurp p54-free-on-tx/p54common.c p54-eee/p54common.c
--- p54-free-on-tx/p54common.c 2008-12-14 14:49:03.000000000 +0100
+++ p54-eee/p54common.c 2008-12-17 17:28:44.153744168 +0100
@@ -800,6 +800,12 @@ static void p54_rx_frame_sent(struct iee
info->status.ack_signal = p54_rssi_to_dbm(dev,
(int)payload->ack_rssi);
skb_pull(entry, sizeof(*hdr) + pad + sizeof(*entry_data));
+ if (payload->status) {
+ struct ieee80211_hdr *hd = (void*) skb->data;
+ printk(KERN_DEBUG "frame_control:%x status %d\n",
+ hd->frame_control,
+ payload->status);
+ }
ieee80211_tx_status_irqsafe(dev, entry);
goto out;
}
prev parent reply other threads:[~2008-12-17 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 14:53 Memory errors from p54usb Larry Finger
2008-12-15 19:51 ` Christian Lamparter
2008-12-16 4:17 ` Larry Finger
2008-12-16 13:31 ` Christian Lamparter
2008-12-16 16:55 ` Larry Finger
2008-12-16 17:13 ` Christian Lamparter
2008-12-16 17:50 ` Larry Finger
2008-12-16 18:29 ` Christian Lamparter
[not found] ` <200812162029.22491.chunkeey@web.de>
[not found] ` <49481CCC.1030903@lwfinger.net>
2008-12-16 21:56 ` Christian Lamparter
2008-12-17 3:21 ` Larry Finger
2008-12-17 14:20 ` Christian Lamparter
2008-12-17 16:01 ` Larry Finger
2008-12-17 16:36 ` 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=200812171736.38289.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.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 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.