[opensuse] Hard lock on openSUSE 12.2 when using rt3290sta WiFi
This is a new problem I've been trying to solve today... maybe someone here can shed some light on the problem? I've got a Zotac Giga ID70 (Intel i3 2100T, 4GB RAM, Nvidia GT430, RTL8111/8168B NIC, and RT3290 WiFi). Everything works out of the box except WiFi. I downloaded the WiFi driver (either from Zotac direct or from RT, they are the same), and did a make, make install, modprobe rt3290sta. WiFi came alive immediately, I was able to connect to my router, and everything seemed to be working properly. I tried downloading a file, and got a hard lock. Could not ssh in, keyboard and mouse were unresponsive. The only way to recover was a hard reset. I rebooted and tried again, this time by streaming a random YouTube video. Again a complete lock-up with only a hard reset. The lock-up only happens if I start downloading any stream of data. Normal use (eg web searches that don't result in a large stream of data are fine, but as soon as the data stream is large enough or continuous... lock-up). In /var/log/messages, as long as I have the rt3290sta module loaded into kernel, even while I'm using the wired network, the log is filling up with an endless stream of: ----------------------- Oct 7 13:18:55 linux-h9h2 kernel: [ 1152.434371] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:18:59 linux-h9h2 kernel: [ 1156.429200] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:03 linux-h9h2 kernel: [ 1160.425117] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:07 linux-h9h2 kernel: [ 1164.419865] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:10 linux-h9h2 kernel: [ 1167.575217] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Oct 7 13:19:15 linux-h9h2 kernel: [ 1172.410595] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:19 linux-h9h2 kernel: [ 1176.405356] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:23 linux-h9h2 kernel: [ 1180.401192] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:27 linux-h9h2 kernel: [ 1184.396089] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:31 linux-h9h2 kernel: [ 1188.390846] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:35 linux-h9h2 kernel: [ 1192.386671] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI ----------------------- With a new line every few seconds, but not much else going on to indicate anything useful for figuring out what's wrong. At the lockup point, there is nothing in the log that indicates a problem that was recorded immediately before the lock-up. These are the message lines immediately before the hard lock: ----------------------- Oct 7 12:49:43 linux-h9h2 kernel: [ 724.396228] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Oct 7 12:50:03 linux-h9h2 kernel: [ 744.384929] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 12:50:32 linux-h9h2 dbus-daemon[597]: dbus[597]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Oct 7 12:50:32 linux-h9h2 dbus[597]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Oct 7 12:50:33 linux-h9h2 dbus-daemon[597]: dbus[597]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 7 12:50:33 linux-h9h2 dbus[597]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 7 12:51:03 linux-h9h2 kernel: [ 804.321825] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 ----------------------- Relevant output of lspci: ----------------------- 03:00.0 Network controller: Ralink corp. Device 3290 03:00.1 Bluetooth: Ralink corp. Device 3298 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) ----------------------- I've searched around and not found much other than a discussion on the Ubuntu side of things from about 2 years ago that appears (to me anyway) to be similar, but not the same. Has anyone had any success with this WiFi card? Got it working? C. -- openSUSE 12.2 x86_64, KDE 4.9.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, don't know directly what your issue is but I did some looking around and found that accourding to http://standards.ieee.org/findstds/standard/802.3bf-2011.html TSSI is time synchronization service interface. I imagine maybe your clock is off?-- just a wild guess. anyway -e On Sun, 2012-10-07 at 13:51 +0200, C wrote:
This is a new problem I've been trying to solve today... maybe someone here can shed some light on the problem?
I've got a Zotac Giga ID70 (Intel i3 2100T, 4GB RAM, Nvidia GT430, RTL8111/8168B NIC, and RT3290 WiFi). Everything works out of the box except WiFi. I downloaded the WiFi driver (either from Zotac direct or from RT, they are the same), and did a make, make install, modprobe rt3290sta. WiFi came alive immediately, I was able to connect to my router, and everything seemed to be working properly.
I tried downloading a file, and got a hard lock. Could not ssh in, keyboard and mouse were unresponsive. The only way to recover was a hard reset.
I rebooted and tried again, this time by streaming a random YouTube video. Again a complete lock-up with only a hard reset. The lock-up only happens if I start downloading any stream of data. Normal use (eg web searches that don't result in a large stream of data are fine, but as soon as the data stream is large enough or continuous... lock-up).
In /var/log/messages, as long as I have the rt3290sta module loaded into kernel, even while I'm using the wired network, the log is filling up with an endless stream of:
----------------------- Oct 7 13:18:55 linux-h9h2 kernel: [ 1152.434371] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:18:59 linux-h9h2 kernel: [ 1156.429200] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:03 linux-h9h2 kernel: [ 1160.425117] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:07 linux-h9h2 kernel: [ 1164.419865] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:10 linux-h9h2 kernel: [ 1167.575217] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Oct 7 13:19:15 linux-h9h2 kernel: [ 1172.410595] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:19 linux-h9h2 kernel: [ 1176.405356] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:23 linux-h9h2 kernel: [ 1180.401192] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:27 linux-h9h2 kernel: [ 1184.396089] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:31 linux-h9h2 kernel: [ 1188.390846] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:35 linux-h9h2 kernel: [ 1192.386671] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI -----------------------
With a new line every few seconds, but not much else going on to indicate anything useful for figuring out what's wrong.
At the lockup point, there is nothing in the log that indicates a problem that was recorded immediately before the lock-up. These are the message lines immediately before the hard lock:
----------------------- Oct 7 12:49:43 linux-h9h2 kernel: [ 724.396228] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Oct 7 12:50:03 linux-h9h2 kernel: [ 744.384929] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 12:50:32 linux-h9h2 dbus-daemon[597]: dbus[597]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Oct 7 12:50:32 linux-h9h2 dbus[597]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Oct 7 12:50:33 linux-h9h2 dbus-daemon[597]: dbus[597]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 7 12:50:33 linux-h9h2 dbus[597]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 7 12:51:03 linux-h9h2 kernel: [ 804.321825] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 -----------------------
Relevant output of lspci:
----------------------- 03:00.0 Network controller: Ralink corp. Device 3290 03:00.1 Bluetooth: Ralink corp. Device 3298 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) -----------------------
I've searched around and not found much other than a discussion on the Ubuntu side of things from about 2 years ago that appears (to me anyway) to be similar, but not the same.
Has anyone had any success with this WiFi card? Got it working?
C. -- openSUSE 12.2 x86_64, KDE 4.9.2
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Oct 7, 2012 at 8:45 PM, Eric Gunther wrote:
Hi,
don't know directly what your issue is but I did some looking around and found that accourding to http://standards.ieee.org/findstds/standard/802.3bf-2011.html TSSI is time synchronization service interface.
I imagine maybe your clock is off?-- just a wild guess.
I thought about that too. I'm using NTP to set system time, and my EFI/BIOS time is set to roughly the same. So... unless my NTP is really messed up, it should be close to accurate. I haven't made any headway on solving this at all. The driver "works" when it's loaded. The WiFi card is seen and it immediately will connect to my router. It works fine right up until I try to stream a large amount of data (YouTube video or Speedtest.net for example)... then it hard locks. http://ubuntuforums.org/showthread.php?p=10441038 is the closest I've found anywhere that looks similar. I haven't been able to figure out if it's me... openSUSE... the driver... or what. I plan on swapping HDs in the coming week so I can try out other Linux distros. If they lock up with the WiFi driver... well I guess that will point to the driver. I can't think of any other way to try and narrow this down. Any other ideas are welcome :-P If I can narrow the problem down a bit, I will have something for a bug report. Right now, it's just a lockup with (as yet) no helpful log info that I can find. C. -- openSUSE 12.2 x86_64, KDE 4.9.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
did a bit more investigation: Try searching google for giwscan, from what it looks like to me the first entry may help, This is the first entry http://lkml.indiana.edu/hypermail/linux/kernel/0612.2/1394.html They are talking about a (sounds like) similar problem... Maybe you can find a solution there. Also sysctl may aid in the final solution or at least an interim one. -e On Mon, 2012-10-08 at 08:06 +0200, C wrote:
On Sun, Oct 7, 2012 at 8:45 PM, Eric Gunther wrote:
Hi,
don't know directly what your issue is but I did some looking around and found that accourding to http://standards.ieee.org/findstds/standard/802.3bf-2011.html TSSI is time synchronization service interface.
I imagine maybe your clock is off?-- just a wild guess.
I thought about that too. I'm using NTP to set system time, and my EFI/BIOS time is set to roughly the same. So... unless my NTP is really messed up, it should be close to accurate.
I haven't made any headway on solving this at all. The driver "works" when it's loaded. The WiFi card is seen and it immediately will connect to my router. It works fine right up until I try to stream a large amount of data (YouTube video or Speedtest.net for example)... then it hard locks.
http://ubuntuforums.org/showthread.php?p=10441038 is the closest I've found anywhere that looks similar.
I haven't been able to figure out if it's me... openSUSE... the driver... or what. I plan on swapping HDs in the coming week so I can try out other Linux distros. If they lock up with the WiFi driver... well I guess that will point to the driver. I can't think of any other way to try and narrow this down. Any other ideas are welcome :-P If I can narrow the problem down a bit, I will have something for a bug report. Right now, it's just a lockup with (as yet) no helpful log info that I can find.
C. -- openSUSE 12.2 x86_64, KDE 4.9.2
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 8, 2012 at 9:05 AM, Eric Gunther wrote:
did a bit more investigation: Try searching google for giwscan, from what it looks like to me the first entry may help,
This is the first entry http://lkml.indiana.edu/hypermail/linux/kernel/0612.2/1394.html They are talking about a (sounds like) similar problem... Maybe you can find a solution there. Also sysctl may aid in the final solution or at least an interim one.
Thanks for helping out with the search Eric. I still haven't made much progress on this one. There is very little info on this issue that seems directly relevant. The computer will lock up - less often - as long as that module is loaded, even if I'm not using the WiFi. If I --force unload the moule then things are fine. It's definitely something related to the WiFi driver. There are still zero hints in the log files. I haven't played much with the sysctl side of things yet for this problem. I'm planning on installing a new/decond drive in this computer to do a little moe in-depth experimenting with other configurations... basically so I don't break my main install any more than I already have. That will take 2 or 3 weeks until I can do that - in the mean-time I'll just used the wired NIC. C. -- openSUSE 12.2 x86_64, KDE 4.9.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
You are most definitely welcome. I am glad that I can help in some way, although the way I often fix problems is to mess up the computer... so I find it very likely that you are right to be cautious, particularly in the realm of sysctl. Good Luck -e On Fri, 2012-10-12 at 11:17 +0200, C wrote:
On Mon, Oct 8, 2012 at 9:05 AM, Eric Gunther wrote:
did a bit more investigation: Try searching google for giwscan, from what it looks like to me the first entry may help,
This is the first entry http://lkml.indiana.edu/hypermail/linux/kernel/0612.2/1394.html They are talking about a (sounds like) similar problem... Maybe you can find a solution there. Also sysctl may aid in the final solution or at least an interim one.
Thanks for helping out with the search Eric. I still haven't made much progress on this one. There is very little info on this issue that seems directly relevant. The computer will lock up - less often - as long as that module is loaded, even if I'm not using the WiFi. If I --force unload the moule then things are fine. It's definitely something related to the WiFi driver. There are still zero hints in the log files. I haven't played much with the sysctl side of things yet for this problem.
I'm planning on installing a new/decond drive in this computer to do a little moe in-depth experimenting with other configurations... basically so I don't break my main install any more than I already have. That will take 2 or 3 weeks until I can do that - in the mean-time I'll just used the wired NIC.
C. -- openSUSE 12.2 x86_64, KDE 4.9.2
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 7 Oct 2012 13:51:39 +0200
C
This is a new problem I've been trying to solve today... maybe someone here can shed some light on the problem?
I've got a Zotac Giga ID70 (Intel i3 2100T, 4GB RAM, Nvidia GT430, RTL8111/8168B NIC, and RT3290 WiFi). Everything works out of the box except WiFi. I downloaded the WiFi driver (either from Zotac direct or from RT, they are the same), and did a make, make install, modprobe rt3290sta. WiFi came alive immediately, I was able to connect to my router, and everything seemed to be working properly.
I tried downloading a file, and got a hard lock. Could not ssh in, keyboard and mouse were unresponsive. The only way to recover was a hard reset.
I rebooted and tried again, this time by streaming a random YouTube video. Again a complete lock-up with only a hard reset. The lock-up only happens if I start downloading any stream of data. Normal use (eg web searches that don't result in a large stream of data are fine, but as soon as the data stream is large enough or continuous... lock-up).
In /var/log/messages, as long as I have the rt3290sta module loaded into kernel, even while I'm using the wired network, the log is filling up with an endless stream of:
----------------------- Oct 7 13:18:55 linux-h9h2 kernel: [ 1152.434371] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:18:59 linux-h9h2 kernel: [ 1156.429200] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:03 linux-h9h2 kernel: [ 1160.425117] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:07 linux-h9h2 kernel: [ 1164.419865] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:10 linux-h9h2 kernel: [ 1167.575217] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Oct 7 13:19:15 linux-h9h2 kernel: [ 1172.410595] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:19 linux-h9h2 kernel: [ 1176.405356] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:23 linux-h9h2 kernel: [ 1180.401192] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:27 linux-h9h2 kernel: [ 1184.396089] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:31 linux-h9h2 kernel: [ 1188.390846] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 13:19:35 linux-h9h2 kernel: [ 1192.386671] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI -----------------------
With a new line every few seconds, but not much else going on to indicate anything useful for figuring out what's wrong.
At the lockup point, there is nothing in the log that indicates a problem that was recorded immediately before the lock-up. These are the message lines immediately before the hard lock:
----------------------- Oct 7 12:49:43 linux-h9h2 kernel: [ 724.396228] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Oct 7 12:50:03 linux-h9h2 kernel: [ 744.384929] RT3290_AsicTxAlcGetAutoAgcOffset: Incorrect desired TSSI or current TSSI Oct 7 12:50:32 linux-h9h2 dbus-daemon[597]: dbus[597]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Oct 7 12:50:32 linux-h9h2 dbus[597]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Oct 7 12:50:33 linux-h9h2 dbus-daemon[597]: dbus[597]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 7 12:50:33 linux-h9h2 dbus[597]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 7 12:51:03 linux-h9h2 kernel: [ 804.321825] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 -----------------------
Relevant output of lspci:
----------------------- 03:00.0 Network controller: Ralink corp. Device 3290 03:00.1 Bluetooth: Ralink corp. Device 3298 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) -----------------------
I've searched around and not found much other than a discussion on the Ubuntu side of things from about 2 years ago that appears (to me anyway) to be similar, but not the same.
Has anyone had any success with this WiFi card? Got it working?
C. Hi You might want to post in the forum - wireless subforum user lwfinger (a wireless kernel dev) may be able to provide some insight.
-- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop up 11:59, 3 users, load average: 0.00, 0.01, 0.05 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
C -
Eric Gunther -
Malcolm