sysctl table check failed: /dev/ath .7.9 Unknown sysctl binary path

Bug #178648 reported by robilad
22
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

from dmesg:

[ 218.259003] ath_hal: module license 'Proprietary' taints kernel.
[ 218.287703] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 218.287727] sysctl table check failed: /dev/ath .7.9 Unknown sysctl binary path
[ 218.288009] Pid: 3197, comm: modprobe Tainted: P 2.6.24-2-generic #1
[ 218.288025] [<c0146515>] set_fail+0x45/0x60
[ 218.288034] [<c01467c6>] sysctl_check_table+0x296/0x5b0
[ 218.288038] [<c0134c58>] sysctl_head_finish+0x18/0x30
[ 218.288044] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.288048] [<c01337d9>] sysctl_set_parent+0x19/0x30
[ 218.288055] [<c0135000>] register_sysctl_table+0x50/0xa0
[ 218.288059] [<f8872077>] init_ath_hal+0x77/0x8d [ath_hal]
[ 218.288070] [<c0151296>] sys_init_module+0x126/0x19c0
[ 218.288088] [<c0184ca0>] __kmalloc+0x0/0x110
[ 218.288096] [<c01053a2>] sysenter_past_esp+0x6b/0xa9
[ 218.288107] =======================
[ 218.288114] sysctl table check failed: /dev/ath/hal .7.9.-2 Unknown sysctl binary path
[ 218.288422] Pid: 3197, comm: modprobe Tainted: P 2.6.24-2-generic #1
[ 218.288425] [<c0146515>] set_fail+0x45/0x60
[ 218.288430] [<c01467c6>] sysctl_check_table+0x296/0x5b0
[ 218.288436] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.288439] [<c0134c58>] sysctl_head_finish+0x18/0x30
[ 218.288445] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.288448] [<c01337d9>] sysctl_set_parent+0x19/0x30
[ 218.288454] [<c0135000>] register_sysctl_table+0x50/0xa0
[ 218.288458] [<f8872077>] init_ath_hal+0x77/0x8d [ath_hal]
[ 218.288467] [<c0151296>] sys_init_module+0x126/0x19c0
[ 218.288483] [<c0184ca0>] __kmalloc+0x0/0x110
[ 218.288491] [<c01053a2>] sysenter_past_esp+0x6b/0xa9
[ 218.288499] =======================
[ 218.288503] sysctl table check failed: /dev/ath/hal/dma_beacon_response_time .7.9.-2.-2 Unknown sysctl binary path
[ 218.288880] Pid: 3197, comm: modprobe Tainted: P 2.6.24-2-generic #1
[ 218.288884] [<c0146515>] set_fail+0x45/0x60
[ 218.288888] [<c01467c6>] sysctl_check_table+0x296/0x5b0
[ 218.288894] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.288899] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.288902] [<c0134c58>] sysctl_head_finish+0x18/0x30
[ 218.288908] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.288911] [<c01337d9>] sysctl_set_parent+0x19/0x30
[ 218.288917] [<c0135000>] register_sysctl_table+0x50/0xa0
[ 218.288921] [<f8872077>] init_ath_hal+0x77/0x8d [ath_hal]
[ 218.288929] [<c0151296>] sys_init_module+0x126/0x19c0
[ 218.288946] [<c0184ca0>] __kmalloc+0x0/0x110
[ 218.288953] [<c01053a2>] sysenter_past_esp+0x6b/0xa9
[ 218.288961] =======================
[ 218.288965] sysctl table check failed: /dev/ath/hal/sw_beacon_response_time .7.9.-2.-2 Unknown sysctl binary path
[ 218.289342] Pid: 3197, comm: modprobe Tainted: P 2.6.24-2-generic #1
[ 218.289346] [<c0146515>] set_fail+0x45/0x60
[ 218.289350] [<c01467c6>] sysctl_check_table+0x296/0x5b0
[ 218.289356] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.289361] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.289364] [<c0134c58>] sysctl_head_finish+0x18/0x30
[ 218.289371] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.289374] [<c01337d9>] sysctl_set_parent+0x19/0x30
[ 218.289380] [<c0135000>] register_sysctl_table+0x50/0xa0
[ 218.289384] [<f8872077>] init_ath_hal+0x77/0x8d [ath_hal]
[ 218.289392] [<c0151296>] sys_init_module+0x126/0x19c0
[ 218.289408] [<c0184ca0>] __kmalloc+0x0/0x110
[ 218.289416] [<c01053a2>] sysenter_past_esp+0x6b/0xa9
[ 218.289424] =======================
[ 218.289428] sysctl table check failed: /dev/ath/hal/swba_backoff .7.9.-2.-2 Unknown sysctl binary path
[ 218.289805] Pid: 3197, comm: modprobe Tainted: P 2.6.24-2-generic #1
[ 218.289808] [<c0146515>] set_fail+0x45/0x60
[ 218.289813] [<c01467c6>] sysctl_check_table+0x296/0x5b0
[ 218.289818] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.289824] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.289827] [<c0134c58>] sysctl_head_finish+0x18/0x30
[ 218.289832] [<c01467da>] sysctl_check_table+0x2aa/0x5b0
[ 218.289835] [<c01337d9>] sysctl_set_parent+0x19/0x30
[ 218.289842] [<c0135000>] register_sysctl_table+0x50/0xa0
[ 218.289846] [<f8872077>] init_ath_hal+0x77/0x8d [ath_hal]
[ 218.289855] [<c0151296>] sys_init_module+0x126/0x19c0
[ 218.289871] [<c0184ca0>] __kmalloc+0x0/0x110
[ 218.289878] [<c01053a2>] sysenter_past_esp+0x6b/0xa9
[ 218.289886] =======================

Revision history for this message
Chuck Short (zulcss) wrote :

Patch to fix this problem have been sent to the kernel-team mailing list for review. Thanks for the bug report.

Changed in linux:
status: New → In Progress
Revision history for this message
berg (berg-foss) wrote :

still failling here....

initiallly the boot process at segment fault. After try CTRL_ALT_DEL , the computer should restart but it continues the boot process and diplay gdm login screen.

then I put my username and password but it stopped like it was analysing my password and dont step ahead

the system now cannot login at graphical display.the I try use the text terminal.

 Only on VT text terminal as normal user ( i dont remember my root password - I use sudo :) .

Using sudo -s or sudo su commands the terminal locked waiting complete the sudo su command and dont accept CTRL-C or CTRL BREAK , only accept CTRL-ALT-DEL and rebott computer.

Revision history for this message
berg (berg-foss) wrote :
Revision history for this message
berg (berg-foss) wrote :

see that at 2.6.22 kernel works fine bit at 2.6.24 ......

see at this post that there is others users with problem at ath_pci module
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/122703/comments/22

I was posting at this bug but I observed that he was more closely to ndiswrapper but I think that the kernel is the source too
https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/178453

Revision history for this message
berg (berg-foss) wrote :
Revision history for this message
berg (berg-foss) wrote :
Revision history for this message
Martin Vysny (vyzivus) wrote :

I can confirm this, on my 2.6.24-3-generic #1 SMP x86_64, newest Hardy. Attaching relevant dmesg output.

Revision history for this message
Amit Kucheria (amitk) wrote :

http://madwifi.org/ticket/1600

Slated for inclusion in 0.9.4 release of the driver - no release date yet.

Looks like we should pull in changeset 2815 of the madwifi driver from http://madwifi.org/changeset/2815

Revision history for this message
Amit Kucheria (amitk) wrote :

Fixed in LRM. Awaiting upload.

Changed in linux:
assignee: nobody → amitk
importance: Undecided → Medium
status: In Progress → Fix Committed
Revision history for this message
Martin Vysny (vyzivus) wrote :

Just updated the kernel and modules on Hardy and the wifi works without problems. I have the Atheros AR2413 802.11bg card.

Revision history for this message
Martin Vysny (vyzivus) wrote :

Sorry guys, I forgot to thank you. Many thanks!

Revision history for this message
Tim Gardner (timg-tpi) wrote :

2.6.24.5-4.12

Changed in linux:
assignee: amitk → nobody
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.