i’ve posted this info previously on the internet forum as i saw somebody
else having similar problems but as it looks like a wireless issue, i’m
reporting it here.
i’m using opensuse 11.4 x64 clean install on an asus M4A78LT-M,
integrated ATI card and with a usb wireless device, linksys wusb54gc
using the rt73usb driver and kde.Wireless device report version 0.1. Pc
works fine, fast with no issues as long as i do not have heavy traffic
on the wireless. If i download a file thru browser, ktorrent or i stream
an avi file to my TV using dlna, pc completely freezes in about 1-2
hours of the download start. /var/log/message shows nothing. The only 3
lines before the hard reboot is – mark----. i have already changed my
setup from dhcp to fix ip to exclude dhcp negotiation of the picture but
to no avail. I’ve removed Pulse audio as well as i recall similar issues
on previous opensuse version but no improvement. There is absolutely no
error or warn in any log files, just a a hard freeze. is a really hard
hang, monitor is black, no response from keyboard or mouse, nothing,
literally dead.
I’ve searching for issues with this wifi driver or with the asus
motherboard in linux but i could not find any. i though that usb wifi
device should be the culprit but before buy a different one, i’ll like
to be sure that indeed it is the root cause.
I’ll enable the magic sysrq keys and i’ll see if i can get something
with it on next freeze. Any tips are welcome
On 18/04/11 16:00, Mysterious wrote:
> Hi,
>
> i’ve posted this info previously on the internet forum as i saw somebody
> else having similar problems but as it looks like a wireless issue, i’m
> reporting it here.
It looks like i’ve found the culprit of the hard hangs and it was
tvmobili. I’ve unload it and download files all night and server did not
hang.
On 04/19/2011 03:57 AM, Mysterious wrote:
> On 18/04/11 16:00, Mysterious wrote:
>> Hi,
>>
>> i’ve posted this info previously on the internet forum as i saw somebody
>> else having similar problems but as it looks like a wireless issue, i’m
>> reporting it here.
>
>
> It looks like i’ve found the culprit of the hard hangs and it was tvmobili. I’ve
> unload it and download files all night and server did not hang.
That’s good to know. When bad things happen, wireless is usually blamed, but
once in a while it is not the problem.
I hope the tvmobili people help you sort out the issue.
On 19/04/11 17:18, Larry Finger wrote:
> On 04/19/2011 03:57 AM, Mysterious wrote:
>> On 18/04/11 16:00, Mysterious wrote:
>>> Hi,
>>>
>>> i’ve posted this info previously on the internet forum as i saw somebody
>>> else having similar problems but as it looks like a wireless issue, i’m
>>> reporting it here.
>>
>>
>> It looks like i’ve found the culprit of the hard hangs and it was
>> tvmobili. I’ve
>> unload it and download files all night and server did not hang.
>
> That’s good to know. When bad things happen, wireless is usually blamed,
> but once in a while it is not the problem.
>
> I hope the tvmobili people help you sort out the issue.
well, unfortunately i was wrong. This time took longer to hang, probably
not so much network traffic but at the end, it hard locked again with
tvmobile unloaded. Magic Sysrq key did not work, /var/log/message shows
nothing:
On 04/19/2011 03:47 PM, Mysterious wrote:
>
>> Apr 19 15:34:50 mysterious rsyslogd: – MARK –
>> Apr 20 22:13:43 mysterious kernel: imklog 5.6.5, log source = /proc/kmsg
>> started.
>> Apr 20 22:13:43 mysterious rsyslogd: [origin software=“rsyslogd”
>> swVersion=“5.6.5” x-pid=“1206” x-info=“http://www.rsyslog.com”] start
>> Apr 20 22:13:43 mysterious kernel: 15.978275] type=1400
>> audit(1303330421.490:2): apparmor=“STATUS” operation=“profile_load”
>> name="/bin/ping" pid=998 comm=“apparmor_parser”
>
>
> this is weird. It is 19 april here so how come that shows 20 ,one day ahead.
> Gonna check bios settings
The logging you are looking at is delayed by some time, and will not show
anything of a panic nature.
Set up your transfer for testing and then switch to the logging console by using
CTRL-ALT-F10. When the crash occurs, what shows on the screen? You will have to
transcribe it by hand or take a picture and post it.
On 20/04/11 01:05, Larry Finger wrote:
> On 04/19/2011 03:47 PM, Mysterious wrote:
>>
>>> Apr 19 15:34:50 mysterious rsyslogd: – MARK –
>>> Apr 20 22:13:43 mysterious kernel: imklog 5.6.5, log source = /proc/kmsg
>>> started.
>>> Apr 20 22:13:43 mysterious rsyslogd: [origin software=“rsyslogd”
>>> swVersion=“5.6.5” x-pid=“1206” x-info=“http://www.rsyslog.com”] start
>>> Apr 20 22:13:43 mysterious kernel: 15.978275] type=1400
>>> audit(1303330421.490:2): apparmor=“STATUS” operation=“profile_load”
>>> name="/bin/ping" pid=998 comm=“apparmor_parser”
>>
>>
>> this is weird. It is 19 april here so how come that shows 20 ,one day
>> ahead.
>> Gonna check bios settings
>
> The logging you are looking at is delayed by some time, and will not
> show anything of a panic nature.
>
> Set up your transfer for testing and then switch to the logging console
> by using CTRL-ALT-F10. When the crash occurs, what shows on the screen?
> You will have to transcribe it by hand or take a picture and post it.
>
> Set up your transfer for testing and then switch to the logging console
> by using CTRL-ALT-F10. When the crash occurs, what shows on the screen?
> You will have to transcribe it by hand or take a picture and post it.
>
HI, system freezed again but this time i could see the CTRL-ALT-F10
screen and it looks to me ( i’m not a developer) that it is rt73usb
driver related. He it goes
[92281.700339] BUG: unable to handle kernel NULL pointer deference at
00000000ac
[xxxxxxxxxxxx] Ip: <ffffffffa07d455f>] rt2x00lib_txdone+0x1f/0x360
[rt2x00lib]
[xxxxxxxxxxxx] PGD: 42c64067 PUD 42c63067 PMD 0
[xxxxxxxxxxxx] Oops: 0000#1] Preemp SMP
[xxxxxxxxxxxx] Last sysfs file:
/sys/device/pci0000:00/0000:00:18.3/temp_input
[xxxxxxxxxxxx] CPU 0
[xxxxxxxxxxxx] PID:5793 comm:Kworker/u:0 Tainted: P 2.6.37.1-1-2-desktop
[xxxxxxxxxxxx[ RIP:00/0:[<ffffffffa07d455f>]
rt2x00lib_txdonex0/x1f/0x360[rt2x00lib]
I hope this info is enough. Googling i came against some hits but it
looks like developers threads, far away for my knowledge.
I’m running mysterious:~ # uname -a
Linux mysterious 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10
+0100 x86_64 x86_64 x86_64 GNU/Linux
On 04/21/2011 12:57 PM, Mysterious wrote:
> On 20/04/11 01:05, Larry Finger wrote:
>
>> Set up your transfer for testing and then switch to the logging console
>> by using CTRL-ALT-F10. When the crash occurs, what shows on the screen?
>> You will have to transcribe it by hand or take a picture and post it.
>>
>
> HI, system freezed again but this time i could see the CTRL-ALT-F10 screen and
> it looks to me ( i’m not a developer) that it is rt73usb driver related. He it goes
>
> [92281.700339] BUG: unable to handle kernel NULL pointer deference at 00000000ac
> [xxxxxxxxxxxx] Ip: <ffffffffa07d455f>] rt2x00lib_txdone+0x1f/0x360 [rt2x00lib]
> [xxxxxxxxxxxx] PGD: 42c64067 PUD 42c63067 PMD 0
> [xxxxxxxxxxxx] Oops: 0000#1] Preemp SMP
> [xxxxxxxxxxxx] Last sysfs file: /sys/device/pci0000:00/0000:00:18.3/temp_input
> [xxxxxxxxxxxx] CPU 0
> [xxxxxxxxxxxx] PID:5793 comm:Kworker/u:0 Tainted: P 2.6.37.1-1-2-desktop
> [xxxxxxxxxxxx[ RIP:00/0:[<ffffffffa07d455f>]
> rt2x00lib_txdonex0/x1f/0x360[rt2x00lib]
>
> I hope this info is enough. Googling i came against some hits but it looks like
> developers threads, far away for my knowledge.
If possible, please include a link or 2 of any hits that you get with Google.
That saves some time for anyone that is trying to help.
On 21/04/11 20:50, Larry Finger wrote:
>
>
> If possible, please include a link or 2 of any hits that you get with
> Google. That saves some time for anyone that is trying to help.
>
> The email thread at
> http://us.generation-nt.com/answer/bug-rt2x00lib-txdone-2-6-37-rc8-help-201745812.html
> indicates that there is a race condition in kernel 2.6.37. Although the
> problem is likely fixed in later kernels, the changes are too large and
> invasive to be backported to 2.6.37.
>
> Please add the wireless repository at
> http://download.opensuse.org/repositories/driver:/wireless/openSUSE_11.4/ and
> install the package named compat-wireless-kmp-desktop. If it still has
> the problem, please report that failure to this thread.
>
Sorry about that. the link you posted is one that i’ve found.
both we’re talking about 2.6.37-rc8 kernel
I’ll add the repository and install the mentioned packet. do i have to
do something else after that? backlist something or simple reboot?
On 04/21/2011 02:16 PM, Mysterious wrote:
> On 21/04/11 20:50, Larry Finger wrote:
>>
>>
>> If possible, please include a link or 2 of any hits that you get with
>> Google. That saves some time for anyone that is trying to help.
>>
>> The email thread at
>> http://us.generation-nt.com/answer/bug-rt2x00lib-txdone-2-6-37-rc8-help-201745812.html
>>
>> indicates that there is a race condition in kernel 2.6.37. Although the
>> problem is likely fixed in later kernels, the changes are too large and
>> invasive to be backported to 2.6.37.
>>
>> Please add the wireless repository at
>> http://download.opensuse.org/repositories/driver:/wireless/openSUSE_11.4/ and
>> install the package named compat-wireless-kmp-desktop. If it still has
>> the problem, please report that failure to this thread.
>>
>
> Sorry about that. the link you posted is one that i’ve found.
> both we’re talking about 2.6.37-rc8 kernel
> I’ll add the repository and install the mentioned packet. do i have to do
> something else after that? backlist something or simple reboot?
On 21/04/11 22:32, Larry Finger wrote:
> On 04/21/2011 02:16 PM, Mysterious wrote:
>> On 21/04/11 20:50, Larry Finger wrote:
>>>
>>>
>>> If possible, please include a link or 2 of any hits that you get with
>>> Google. That saves some time for anyone that is trying to help.
>>>
>>> The email thread at
>>> http://us.generation-nt.com/answer/bug-rt2x00lib-txdone-2-6-37-rc8-help-201745812.html
>>>
>>>
>>> indicates that there is a race condition in kernel 2.6.37. Although the
>>> problem is likely fixed in later kernels, the changes are too large and
>>> invasive to be backported to 2.6.37.
>>>
>>> Please add the wireless repository at
>>> http://download.opensuse.org/repositories/driver:/wireless/openSUSE_11.4/
>>> and
>>> install the package named compat-wireless-kmp-desktop. If it still has
>>> the problem, please report that failure to this thread.
>>>
>>
>> Sorry about that. the link you posted is one that i’ve found.
>> both we’re talking about 2.6.37-rc8 kernel
>> I’ll add the repository and install the mentioned packet. do i have to do
>> something else after that? backlist something or simple reboot?
>
> The two following commands should do the trick
>
>
On 04/23/2011 03:30 PM, Mysterious wrote:
> On 21/04/11 22:32, Larry Finger wrote:
>> On 04/21/2011 02:16 PM, Mysterious wrote:
>>> On 21/04/11 20:50, Larry Finger wrote:
>>>>
>>>>
>>>> If possible, please include a link or 2 of any hits that you get with
>>>> Google. That saves some time for anyone that is trying to help.
>>>>
>>>> The email thread at
>>>> http://us.generation-nt.com/answer/bug-rt2x00lib-txdone-2-6-37-rc8-help-201745812.html
>>>>
>>>>
>>>>
>>>> indicates that there is a race condition in kernel 2.6.37. Although the
>>>> problem is likely fixed in later kernels, the changes are too large and
>>>> invasive to be backported to 2.6.37.
>>>>
>>>> Please add the wireless repository at
>>>> http://download.opensuse.org/repositories/driver:/wireless/openSUSE_11.4/
>>>> and
>>>> install the package named compat-wireless-kmp-desktop. If it still has
>>>> the problem, please report that failure to this thread.
>>>>
>>>
>>> Sorry about that. the link you posted is one that i’ve found.
>>> both we’re talking about 2.6.37-rc8 kernel
>>> I’ll add the repository and install the mentioned packet. do i have to do
>>> something else after that? backlist something or simple reboot?
>>
>> The two following commands should do the trick
>>
>>
>>
>> The path to rt73usb.ko should be different for the unload than the
>> following load.
>
> Excuse my ignorance. Before i installed the compat-wireless packet, that it is
> what my driver showed:
>
> mysterious:~ # modinfo rt73usb
> filename:
> /lib/modules/2.6.37.1-1.2-desktop/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
> license: GPL
> firmware: rt73.bin
> description: Ralink RT73 USB Wireless LAN driver.
> version: 2.3.0
>
>
>
>
> After installed, it shows:
>
> ysterious:~ # modinfo rt73usb
> filename:
> /lib/modules/2.6.37.1-1.2-desktop/updates/drivers/net/wireless/rt2x00/rt73usb.ko
> license: GPL
> firmware: rt73.bin
> description: Ralink RT73 USB Wireless LAN driver.
> version: 2.3.0
>
> does this mean that now i;m loading a newer driver or it is just the same but
> from different location?
Compat-wireless takes the wireless driver code from the code base of the
wireless developers and ports it for older kernels. Not only is the driver
loading from a different location, but it is essentially the driver that will be
in kernel 2.6.40, which is likely to be the kernel in openSUSE 12.1. It is the
latest and “greatest”.
>>
>> After installed, it shows:
>>
>> ysterious:~ # modinfo rt73usb
>> filename:
>> /lib/modules/2.6.37.1-1.2-desktop/updates/drivers/net/wireless/rt2x00/rt73usb.ko
>>
>> license: GPL
>> firmware: rt73.bin
>> description: Ralink RT73 USB Wireless LAN driver.
>> version: 2.3.0
>>
>> does this mean that now i;m loading a newer driver or it is just the
>> same but
>> from different location?
>
> Compat-wireless takes the wireless driver code from the code base of the
> wireless developers and ports it for older kernels. Not only is the
> driver loading from a different location, but it is essentially the
> driver that will be in kernel 2.6.40, which is likely to be the kernel
> in openSUSE 12.1. It is the latest and “greatest”.
Just want to provide an update. Since i loaded the rt73usb module from
the compat-wireless packet, i did not have hangs. Everything is working
quick and smooth.
On 04/27/2011 10:03 AM, Mysterious wrote:
>
> Just want to provide an update. Since i loaded the rt73usb module from the
> compat-wireless packet, i did not have hangs. Everything is working quick and
> smooth.
Very good to hear. The kernel developers are making progress.