From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: 3.0: rt2800usb(Kernel PANIC) vs. rt2780sta(GOOD/2.6.38)
Date: Wed, 27 Jul 2011 19:33:05 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1107271851410.25432@p34.internal.lan> (raw)
Hi,
Kernel 3.0 (rt2800usb driver- horrid, and then it panics moments after,
see picture below)
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=301 ttl=64 time=146 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=302 ttl=64 time=274 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=303 ttl=64 time=197 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=304 ttl=64 time=115 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=305 ttl=64 time=243 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=306 ttl=64 time=265 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=307 ttl=64 time=183 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=308 ttl=64 time=201 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=309 ttl=64 time=236 ms
Then it crashes if you use the network:
http://home.comcast.net/~jpiszcz/20110727/photo.JPG
With the rt2870sta driver, the machine has been solid for months (2.6.38)
with consistent low pings:
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=2 ttl=64 time=1.38 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=3 ttl=64 time=0.520 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=4 ttl=64 time=1.11 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=5 ttl=64 time=0.573 ms
64 bytes from atomw.internal.lan (192.168.0.2): icmp_req=6 ttl=64 time=0.562 ms
Can we please get the rt2870sta back into the kernel?
If not, can someone recommend a USB wireless stick that works in Linux
that is not based on RALINK that does not crash the kernel and gets as
good as pings as the one I have (most highest rated on Amazon that
everyone seems to buy) with the rt2870sta driver?
http://www.amazon.com/Medialink-Wireless-Adapter-802-11n-Compatible/dp/B002RM08RE
Justin.
next reply other threads:[~2011-07-27 23:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 23:33 Justin Piszcz [this message]
2011-07-28 5:34 ` Andreas Hartmann
2011-07-28 16:18 ` Larry Finger
2011-07-30 11:30 ` Stanislaw Gruszka
2011-07-30 11:32 ` [PATCH] rt2x00: rt2800: fix zeroing skb structure Stanislaw Gruszka
2011-07-30 11:39 ` Justin Piszcz
2011-07-30 14:20 ` Justin Piszcz
2011-07-30 14:32 ` Justin Piszcz
2011-07-30 15:05 ` Andreas Hartmann
2011-07-30 17:07 ` Justin Piszcz
2011-07-30 17:10 ` Justin Piszcz
2011-07-31 3:41 ` Adam Cozzette
2011-07-31 10:09 ` Justin Piszcz
2011-07-30 18:07 ` Larry Finger
2011-08-03 16:00 ` Stanislaw Gruszka
2011-08-03 17:31 ` Justin Piszcz
2011-08-03 17:44 ` Justin Piszcz
2011-08-03 18:32 ` Justin Piszcz
2011-08-03 18:33 ` Stanislaw Gruszka
2011-08-03 18:35 ` Justin Piszcz
2011-08-03 18:42 ` Justin Piszcz
2011-08-03 18:49 ` Justin Piszcz
2011-08-04 8:03 ` Justin Piszcz
2011-08-04 12:43 ` Stanislaw Gruszka
2011-08-05 16:13 ` [rt2x00-users] " Aleksandar Milivojevic
2011-07-30 13:41 ` Gertjan van Wingerde
2011-07-30 14:02 ` Ivo Van Doorn
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=alpine.DEB.2.02.1107271851410.25432@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®