still same problem

Hi guys.
After quite some time has passed since my last message, i have pulled wireless drivers from web site several times, still same problem, refresh of drivers didn't seem to affect the problem at all. I am lost, since you don't seem to take it seriously, but it hangs machine! Can someone give me an advice what I can do in order to help you to troubleshoot the issue?
I am not a programmer, but looks like a memory leak somewhere. If you give clear understandable instructions - I am glad to follow them! Regards
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Hi Dimitri,

I"m getting a similar problem to you, in that my computer is hanging shortly after loading ath9k and trying to set up a wireless connection. I've logged a bug report here:

http://bugzilla.kernel.org/show_bug.cgi?id=12110

but unfortunately, there hasn't been any progress or feedback on my comments since the 6th December. I'm willing to test, but I need some guidance on exactly how to get some useful debugging information.

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

If there is an oops it should hopefully come up.

Luis
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

!DSPAM:2,49602e56281331804284693!

Hi,

Quoted 6 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet. 2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 44 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 3 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hi,

I did not find the time to further investigate this issue. Well what I did today was compile the latest git-update and the latest hostapd. At least the machine does not crash that often, but with 802.11n I can't connect to the card ... but this might also be a problem with the card in my laptop. I hope I'll find the time to go on testing next week.

Quoted 48 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 6 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 9 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 4 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Quoted 50 lines · W. van den Akker

Quoted 46 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Regards
Dmitri

Quoted 70 lines · Dmitri Seletski

Quoted 50 lines · W. van den Akker

Quoted 46 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]> wrote:
[...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Quoted 2 lines

Regards
Dmitri

I have tried all kernel versions till 2.6.28 and still have the same hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but because AP isnt supported untill 2.6.29 the report is closed.

I will test today 2.6.29.rc2 and see if it has any progress.

Quoted 72 lines · W. van den Akker

Quoted 71 lines · Dmitri Seletski

Quoted 51 lines · W. van den Akker

Quoted 47 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]>
wrote: [...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Quoted 8 lines

Quoted 2 lines

Regards
Dmitri

I have tried all kernel versions till 2.6.28 and still have the same hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but because AP isnt supported untill 2.6.29 the report is closed.

A better description of this is that AP support does not work (is not allowed) and therefore not supported on < 2.6.28.

Quoted 1 line

I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat-wireless (just updates your wireless stuff) for bleeding edge stuff.

http://wireless.kernel.org/en/developers/Documentation/git-guide
http://wireless.kernel.org/en/users/Download

Luis

Quoted 72 lines · W. van den Akker

Quoted 71 lines · Dmitri Seletski

Quoted 51 lines · W. van den Akker

Quoted 47 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]>
wrote: [...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Quoted 8 lines

Quoted 2 lines

Regards
Dmitri

I have tried all kernel versions till 2.6.28 and still have the same hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but because AP isnt supported untill 2.6.29 the report is closed.

A better description of this is that AP support does not work (is not allowed) and therefore not supported on < 2.6.28.

Quoted 1 line

I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat-wireless (just updates your wireless stuff) for bleeding edge stuff.

Quoted 82 lines · Luis R. Rodriguez

Quoted 72 lines · W. van den Akker

Quoted 71 lines · Dmitri Seletski

Quoted 51 lines · W. van den Akker

Quoted 47 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]>
wrote: [...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Quoted 8 lines

Quoted 2 lines

Regards
Dmitri

I have tried all kernel versions till 2.6.28 and still have the same hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but because AP isnt supported untill 2.6.29 the report is closed.

Quoted 8 lines

A better description of this is that AP support does not work (is not allowed) and therefore not supported on < 2.6.28.

Quoted 1 line

I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat-wireless (just updates your wireless stuff) for bleeding edge stuff.

I tested it today with kernel 2.6.29-rc2. But no change. The kernel hangs completly (without oops or what so ever, even nmi-watchdog has no results). It happend when I started the connection (from a IW4965 card). Then started up a Kmail connection, start up a browser sessie. Stop Kmail, and start Kmail.

It also happens when I do a hostapd start, hostapd stop, hostapd start.

Its a IBM 206 eserver, with no X running on it. The card is a WMP300N.

Any hints?

On Mon, Jan 19, 2009 at 2:31 PM, W. van den Akker <[email protected]>

Quoted 102 lines · Luis R. Rodriguez

Quoted 83 lines · W. van den Akker

Quoted 73 lines · Dmitri Seletski

Quoted 72 lines

Quoted 52 lines · W. van den Akker

Quoted 48 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]>
wrote: [...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press
reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Quoted 8 lines

Quoted 2 lines

Regards
Dmitri

I have tried all kernel versions till 2.6.28 and still have the same hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but because AP isnt supported untill 2.6.29 the report is closed.

Quoted 7 lines

A better description of this is that AP support does not work (is not allowed) and therefore not supported on < 2.6.28.

Quoted 1 line

I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat-wireless (just updates your wireless stuff) for bleeding edge stuff.

I tested it today with kernel 2.6.29-rc2. But no change. The kernel hangs completly (without oops or what so ever, even nmi-watchdog has no results). It happend when I started the connection (from a IW4965 card). Then started up a Kmail connection, start up a browser sessie. Stop Kmail, and start Kmail.

It also happens when I do a hostapd start, hostapd stop, hostapd start.

Its a IBM 206 eserver, with no X running on it. The card is a WMP300N.

Quoted 1 line

Any hints?

Since you are not getting any panic can you try wireless-testing git tree [1], this will get you the latest and greatest wireless drivers and mac80211/cfg80211 which are now being queued up for 2.6.30. See if you see the issue there. If so then you can use git bisect.

[1] http://wireless.kernel.org/en/developers/Documentation/git-guide

On Mon, Jan 19, 2009 at 2:31 PM, W. van den Akker <[email protected]>

Quoted 100 lines · Luis R. Rodriguez

Quoted 83 lines · W. van den Akker

Quoted 73 lines · Dmitri Seletski

Quoted 72 lines

Quoted 52 lines · W. van den Akker

Quoted 48 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 5 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]>
wrote: [...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to press
reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens, as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately when starting hostapd, stop it and then restart hostapd. So every change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 8 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 7 lines

Hi,

What is the status of your problem? I still have problems with it and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Perhaps try to upgrade kernel?

Quoted 8 lines

Quoted 2 lines

Regards
Dmitri

I have tried all kernel versions till 2.6.28 and still have the same hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but because AP isnt supported untill 2.6.29 the report is closed.

Quoted 7 lines

A better description of this is that AP support does not work (is not allowed) and therefore not supported on < 2.6.28.

Quoted 1 line

I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat-wireless (just updates your wireless stuff) for bleeding edge stuff.

I tested it today with kernel 2.6.29-rc2. But no change. The kernel hangs completly (without oops or what so ever, even nmi-watchdog has no results). It happend when I started the connection (from a IW4965 card). Then started up a Kmail connection, start up a browser sessie. Stop Kmail, and start Kmail.

It also happens when I do a hostapd start, hostapd stop, hostapd start.

Quoted 3 lines

Its a IBM 206 eserver, with no X running on it. The card is a WMP300N.

Any hints?

Since you are not getting any panic can you try wireless-testing git tree [1], this will get you the latest and greatest wireless drivers and mac80211/cfg80211 which are now being queued up for 2.6.30. See if you see the issue there. If so then you can use git bisect.

Quoted 2 lines · Luis R. Rodriguez

On Mon, Jan 19, 2009 at 2:31 PM, W. van den Akker
<[email protected]>

Quoted 122 lines · wrote:

Quoted 122 lines · Luis R. Rodriguez

Quoted 101 lines · W. van den Akker

Quoted 87 lines · Dmitri Seletski

Quoted 81 lines

Quoted 61 lines · W. van den Akker

Quoted 57 lines · On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:

Hi,

Quoted 7 lines · Luis R. Rodriguez

On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <[email protected]>
wrote: [...]
We need an oops trace of your crashes so far it seems you have not been able to get one, lets work on that. Until then it is not easy for us to provide you with patches to fix your issues.

I also have similar problems with an D-LINK DWA-547 and I'd really like to provide the oops trace, but unfortunately the machine seems to hang that fast, that even no oops trace is shown. Also magic-sysreq don't work anymore, neither via serial console nor via keyboard. Only chance I have in this moment is to
press
reset-button, which already caused a full xfs-filsystem-corruption with dataloss once :-(

My problem is, that the hang happens not immediately after loading the driver but "somewhen" while it is loaded.

I have seen two types of crash:

1.) first investigations on my side seem to show that it happens,
as soon as there is high dataload transfered, but I don't have detailed info yet.
2.) Running hostapd works fine while started first time, but no client is connected. When a client connects a system freeze occures "sometimes". Reproducably the system freezes immediately
when starting hostapd, stop it and then restart hostapd. So every
change in hostapd conf needs a full reboot, unloading the ath9k module and reload it does not prevent freeze, but after reboot I
can start hostapd once without a problem (only the metioned "sometime" freezes on client connect or high data-volume).

As this machine is productive, I suspended testing for now. I will change the card into a non-productive environment in the next days. As soon as I find more details, I'll report.

Quoted 10 lines

Please test with the latest drivers from wireless-testing/compat-wireless and restart in single user mode, we want to ensure X is not running at all and you are in a
virtual terminal. We also do not want Network Manager or wpa_supplicant running in the background. To increase the resolution upon bootup try booting with vga=ask (vga=791 works well for me), then try to associate to your access point without
encryption manually using iwconfig.

Quoted 2 lines

Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant is running.

Quoted 8 lines

Hi,

What is the status of your problem? I still have problems with it
and have no progress...

gr,
Willem

Hello Willem.

I think I have had similar issue to yours.

Car was working for short period of time and after a while crashed
computer. I was advised to change kernel version, i updated it to 2.6.27.9 and problem has gone away since.
It's something to do with DMA.

Quoted 4 lines

Perhaps try to upgrade kernel?

Regards
Dmitri

Quoted 8 lines

I have tried all kernel versions till 2.6.28 and still have the same
hang-ups. I think indeed its a DMA-hardware-ath9k related problem. The patch in 2.6.27.8 didnt work for me. I have filled a bugreport on
bugzilla.kernel but because AP isnt supported untill 2.6.29 the report
is closed.

A better description of this is that AP support does not work (is not
allowed) and therefore not supported on < 2.6.28.

Quoted 5 lines

Quoted 1 line

I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat- wireless
(just updates your wireless stuff) for bleeding edge stuff.

I tested it today with kernel 2.6.29-rc2. But no change. The kernel hangs
completly (without oops or what so ever, even nmi-watchdog has no results). It happend when I started the connection (from a IW4965 card).
Then started up a Kmail connection, start up a browser sessie. Stop Kmail, and start Kmail.

It also happens when I do a hostapd start, hostapd stop, hostapd start.

Its a IBM 206 eserver, with no X running on it. The card is a WMP300N.

Quoted 8 lines

Quoted 1 line

Any hints?

Since you are not getting any panic can you try wireless-testing git tree [1], this will get you the latest and greatest wireless drivers and mac80211/cfg80211 which are now being queued up for 2.6.30. See if
you see the issue there. If so then you can use git bisect.

Also the latest wireless testing git has the same problem. No Oops, trace or any panic visible.

Some nasty problem here.....

gr,
Willem

So my theory is that I was triggering the same problem using SMP/ Hyperthreading, I suspect your system is not a smaller single processor system? That would at least support that theory. I think the problem could be a spinlock locking problem in the interrupt handler, or something like that. I've programmed drivers, wrote a good part of the IVTV driver, and this behavior reminds me of what I saw there at times during development (it would be stable on UP systems, lock like this on SMP systems). I have been peeking around in the code some to get familiar with it, but of course may take some time for me to start grasping what is going on to be able to contribute any help myself. So this is just what I'm thinking, since freezes like this often seem to be something wrong in the interrupt handler for SMP/preemption configured systems. If you are using SMP, maybe trying it with just one processor enabled would be a good test to see if this is really true there too.

Quoted 7 lines

So my theory is that I was triggering the same problem using SMP/ Hyperthreading, I suspect your system is not a smaller single processor system? That would at least support that theory. I think the problem could be a spinlock locking problem in the interrupt handler, or something like that. I've programmed drivers, wrote a good part of the IVTV driver, and this behavior reminds me of what I saw there at times during development (it would be stable on UP

Quoted 8 lines

systems, lock like this on SMP systems). I have been peeking around in the code some to get familiar with it, but of course may take some time for me to start grasping what is going on to be able to contribute any help myself. So this is just what I'm thinking, since freezes like this often seem to be something wrong in the interrupt handler for SMP/preemption configured systems. If you are using SMP, maybe trying it with just one processor enabled would be a good test to see if this is really true there too.

Hil Chris,

This is correct. Its a SMP system with HT. So I think your assumption is right. It must be in that direction.

I will try to test it with one CPU disabled.
I will report back.

I have tested with 1 CPU disabled. Running now for about 2 hours without hangups (I have several connection drops, but it will reconnect).

I have also tested with 2 CPU's and HT-disabled (noht parameter) but that had no effect.

So SMP looks like the cause of the problem here.

Quoted 9 lines · W. van den Akker

I have tested with 1 CPU disabled. Running now for about 2 hours without
hangups (I have several connection drops, but it will reconnect).

I have also tested with 2 CPU's and HT-disabled (noht parameter) but that
had no effect.

So SMP looks like the cause of the problem here.

Thanks for testing this! I'm running most of my tests with a dual core system, so SMP is being used, but with two cores, not two separate chips. I don't think there should be much difference there, but certainly our hardware configuration is different.

Could you please describe your hardware with more details so that we can
see whether we could find a similar system to try to reproduce this? Is
this the IBM 206 eserver with WMP300N you mentioned in an earlier message in the thread? That seems to be (by default) a uni-processor setup, so I would like to make sure we understand what is the exact hardware used here since I do not think we have been able to reproduce this type of issue so far in any dual core systems.

- Jouni

Quoted 26 lines · Jouni Malinen

Quoted 9 lines · W. van den Akker

I have tested with 1 CPU disabled. Running now for about 2 hours without
hangups (I have several connection drops, but it will reconnect).

I have also tested with 2 CPU's and HT-disabled (noht parameter) but that
had no effect.

So SMP looks like the cause of the problem here.

Thanks for testing this! I'm running most of my tests with a dual core system, so SMP is being used, but with two cores, not two separate chips. I don't think there should be much difference there, but certainly our hardware configuration is different.

Could you please describe your hardware with more details so that we can
see whether we could find a similar system to try to reproduce this? Is
this the IBM 206 eserver with WMP300N you mentioned in an earlier message in the thread? That seems to be (by default) a uni-processor setup, so I would like to make sure we understand what is the exact hardware used here since I do not think we have been able to reproduce this type of issue so far in any dual core systems.

Quoted 1 line

- Jouni

This is a patch (against yesterdays current wireless-testing kernel)
that shows basically what we did in the IVTV driver,
essentially holding a spin_lock() in the interrupt handler. So it isn't even used, since compiled out, if a system isn't SMP. When the system is SMP it prevents multiple instances of the interrupt handler from happening. This seemed to be the magic fix there, I'm not sure if this is totally correct for this driver, but it's a patch to test (hopefully the
spinlock I used makes some sense, seems this also is good since wouldn't want to reset the card and have interrupts happen while that's going on?). It's at least an example showing what I suspect could
fix it, and would be interesting if you had the ability to test it on your SMP
system to see if it is just the interrupt handler where it's happening.

Quoted 29 lines · Chris Kennedy

Quoted 26 lines · Jouni Malinen

Quoted 9 lines · W. van den Akker

I have tested with 1 CPU disabled. Running now for about 2 hours without
hangups (I have several connection drops, but it will reconnect).

I have also tested with 2 CPU's and HT-disabled (noht parameter) but that
had no effect.

So SMP looks like the cause of the problem here.

Thanks for testing this! I'm running most of my tests with a dual core system, so SMP is being used, but with two cores, not two separate chips. I don't think there should be much difference there, but certainly our hardware configuration is different.

Could you please describe your hardware with more details so that we can
see whether we could find a similar system to try to reproduce this? Is
this the IBM 206 eserver with WMP300N you mentioned in an earlier message in the thread? That seems to be (by default) a uni-processor setup, so I would like to make sure we understand what is the exact hardware used here since I do not think we have been able to reproduce this type of issue so far in any dual core systems.

Quoted 1 line

- Jouni

Quoted 15 lines

This is a patch (against yesterdays current wireless-testing kernel)
that shows basically what we did in the IVTV driver,
essentially holding a spin_lock() in the interrupt handler. So it isn't even used, since compiled out, if a system isn't SMP. When the system is SMP it prevents multiple instances of the interrupt handler from happening. This seemed to be the magic fix there, I'm not sure if this is totally correct for this driver, but it's a patch to test (hopefully the
spinlock I used makes some sense, seems this also is good since wouldn't want to reset the card and have interrupts happen while that's going on?). It's at least an example showing what I suspect could
fix it, and would be interesting if you had the ability to test it on your SMP
system to see if it is just the interrupt handler where it's happening.

Thanks Chris,

I applied the patch.... but no luck. Systems still hangs.

Quoted 56 lines · W. van den Akker

Quoted 44 lines · Chris Kennedy

Quoted 29 lines · Jouni Malinen

Quoted 9 lines · W. van den Akker

I have tested with 1 CPU disabled. Running now for about 2 hours without
hangups (I have several connection drops, but it will reconnect).

I have also tested with 2 CPU's and HT-disabled (noht parameter) but that
had no effect.

So SMP looks like the cause of the problem here.

Thanks for testing this! I'm running most of my tests with a dual core
system, so SMP is being used, but with two cores, not two separate chips. I don't think there should be much difference there, but certainly our hardware configuration is different.

Could you please describe your hardware with more details so that we can
see whether we could find a similar system to try to reproduce this? Is
this the IBM 206 eserver with WMP300N you mentioned in an earlier message in the thread? That seems to be (by default) a uni- processor
setup, so I would like to make sure we understand what is the exact hardware used here since I do not think we have been able to reproduce
this type of issue so far in any dual core systems.

Quoted 1 line

- Jouni

This is a patch (against yesterdays current wireless-testing kernel)
that shows basically what we did in the IVTV driver,
essentially holding a spin_lock() in the interrupt handler. So it isn't even used, since compiled out, if a system isn't SMP. When the
system is SMP it prevents multiple instances of the interrupt handler
from happening. This seemed to be the magic fix there, I'm not sure if
this is totally correct for this driver, but it's a patch to test (hopefully the
spinlock I used makes some sense, seems this also is good since

Quoted 8 lines

wouldn't want to reset the card and have interrupts happen while that's going on?). It's at least an example showing what I suspect could
fix it, and would be interesting if you had the ability to test it on
your SMP
system to see if it is just the interrupt handler where it's happening.

Thanks Chris,

Quoted 2 lines

I applied the patch.... but no luck. Systems still hangs.

Running for about a week with one CPU. The driver works ok and the connection is rock-solid.

Any progress on the dual-CPU lockup?

gr,

Willem

Signature · 3 lines

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Quoted 7 lines · W. van den Akker

I have tested with 1 CPU disabled. Running now for about 2 hours without hangups (I have several connection drops, but it will reconnect).

I have also tested with 2 CPU's and HT-disabled (noht parameter) but that had no effect.

So SMP looks like the cause of the problem here.

Thanks for testing this! I'm running most of my tests with a dual core system, so SMP is being used, but with two cores, not two separate chips. I don't think there should be much difference there, but certainly our hardware configuration is different.

Could you please describe your hardware with more details so that we can see whether we could find a similar system to try to reproduce this? Is this the IBM 206 eserver with WMP300N you mentioned in an earlier message in the thread? That seems to be (by default) a uni-processor setup, so I would like to make sure we understand what is the exact hardware used here since I do not think we have been able to reproduce this type of issue so far in any dual core systems.

Quoted 7 lines

So my theory is that I was triggering the same problem using SMP/ Hyperthreading, I suspect your system is not a smaller single processor system? That would at least support that theory. I think the problem could be a spinlock locking problem in the interrupt handler, or something like that. I've programmed drivers, wrote a good part of the IVTV driver, and this behavior reminds me of what I saw there at times during development (it would be stable on UP

Quoted 8 lines

systems, lock like this on SMP systems). I have been peeking around in the code some to get familiar with it, but of course may take some time for me to start grasping what is going on to be able to contribute any help myself. So this is just what I'm thinking, since freezes like this often seem to be something wrong in the interrupt handler for SMP/preemption configured systems. If you are using SMP, maybe trying it with just one processor enabled would be a good test to see if this is really true there too.

Hil Chris,

This is correct. Its a SMP system with HT. So I think your assumption is right. It must be in that direction.

I will try to test it with one CPU disabled.
I will report back.

Hi guys.
After quite some time has passed since my last message, i have pulled wireless drivers from web site several times, still same problem, refresh of drivers didn't seem to affect the problem at all. I am lost, since you don't seem to take it seriously, but it hangs machine! Can someone give me an advice what I can do in order to help you to troubleshoot the issue?
I am not a programmer, but looks like a memory leak somewhere. If you give clear understandable instructions - I am glad to follow them! Regards

Hi guys.
After quite some time has passed since my last message, i have pulled wireless drivers from web site several times, still same problem, refresh of drivers didn't seem to affect the problem at all. I am lost, since you don't seem to take it seriously, but it hangs machine! Can someone give me an advice what I can do in order to help you to troubleshoot the issue?
I am not a programmer, but looks like a memory leak somewhere. If you give clear understandable instructions - I am glad to follow them! Regards