Skip to contentSkip to conversation

did compat-wireless-2011-01-27 crash dhcpcd?

DISCUSSION James 6 participants 11 messages Jan 27, 2011 – Feb 2, 2011

lore
Share & tools
lore

James

author
#0 lore raw

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

BUG: unable to handle kernel NULL pointer dereference at 00000000000001dc
IP: [<ffffffff8130fb9d>] wext_handle_ioctl+0xae/0x165
PGD 2262a9067 PUD 2262c7067 PMD 0
Oops: 0000 [#1] SMP
last sysfs file:
/sys/devices/pci0000:00/0000:00:08.0/0000:02:09.0/net/wlan0/type
CPU 0
Modules linked in: ath9k(+) mac80211 compat ath9k_common ath9k_hw ath

cfg80211 nvidia(P) [last unloaded: cfg80211]

Pid: 1795, comm: dhcpcd Tainted: P 2.6.37 #14
ALiveNF5-eSATA2+ /To Be Filled By O.E.M.

RIP: 0010:[<ffffffff8130fb9d>]  [<ffffffff8130fb9d>]
wext_handle_ioctl+0xae/0x165
RSP: 0018:ffff88022632fd68  EFLAGS: 00010283
RAX: 0000000000000104 RBX: ffff88022632fdf8 RCX: 000000000000001b
RDX: 0000000000008b1b RSI: 000000000000e050 RDI: ffff8801d2431000
RBP: 0000000000000001 R08: ffffffff8130f43d R09: 000000000000000a
R10: 0000000000000000 R11: 0000000001e683bc R12: 00007fff01d6fa40
R13: ffffffff815d7f10 R14: 0000000000000000 R15: 00007fff01d6fb60
FS:  00007fcad00c1700(0000) GS:ffff8800cec00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000000001dc CR3: 000000022760c000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process dhcpcd (pid: 1795, threadinfo ffff88022632e000, task
ffff8802285f7380)
Stack:
 0000000000000008 0000000000008b1b 00007fca00008b1b ffffffff812c3834
 0000000000008b1b ffffffff815d7f10 00007fff01d6fa40 0000000000000000
 0000000000000000 ffffffff812c48b8 ffff8801d24315c8 ffff8801d24315b8
Call Trace:
 [<ffffffff812c3834>] ? dev_get_by_name_rcu+0x89/0x95
 [<ffffffff812c48b8>] ? dev_ioctl+0x5f9/0x63b
 [<ffffffff812b687a>] ? sk_prot_alloc+0x8b/0xe3
 [<ffffffff812b2a4d>] ? sock_ioctl+0x225/0x232
 [<ffffffff81093845>] ? get_empty_filp+0x9d/0x155
 [<ffffffff8109ee1b>] ? do_vfs_ioctl+0x479/0x4c6
 [<ffffffff812b3e20>] ? sock_alloc_file+0xc9/0x127
 [<ffffffff81090bd0>] ? fd_install+0x27/0x4d
 [<ffffffff8109eeb3>] ? sys_ioctl+0x4b/0x6f
 [<ffffffff81001e3b>] ? system_call_fastpath+0x16/0x1b
Code: 85 c0 74 4a 48 8b 00 48 85 c0 74 42 48 8b 80 f8 01 00 00 48 85 c0

74 36 0f b7 70 08 8d 8a 00 75 ff ff 39 f1 73 28 48 8b 00 89 c9 <4c> 8b 04 c8 4d 85 c0 74 1a 81 fa df 8b 00 00 77 12 48 8d 4c 24 RIP [<ffffffff8130fb9d>] wext_handle_ioctl+0xae/0x165
RSP <ffff88022632fd68>
CR2: 00000000000001dc

---[ end trace 31d89d579b4bd813 ]---

Registered led device: ath9k-phy0::radio Registered led device: ath9k-phy0::assoc Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
ieee80211 phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 mem=0xffffc90003a00000, irq=17

#1 lore raw
Quoted 11 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'

Quoted 3 lines

cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Hauke

author
#2 lore raw
Quoted 14 lines · Hauke Mehrtens
Quoted 10 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'

Quoted 3 lines

cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

Quoted 7 lines

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Hauke
--

I'm not using any tools.
The call trace happens after I do a modprobe.
I'm guessing it doesn't like dhcpcd.

Do I really need CONFIG_WIRELESS_EXT?

#3 lore raw
Quoted 23 lines · James
Quoted 14 lines · Hauke Mehrtens
Quoted 10 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'

Quoted 3 lines

cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

Quoted 7 lines

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Hauke
--

Quoted 6 lines

I'm not using any tools.
The call trace happens after I do a modprobe.
I'm guessing it doesn't like dhcpcd.

Do I really need CONFIG_WIRELESS_EXT?
--

Something is trying to use wext. This is from your original message:

BUG: unable to handle kernel NULL pointer dereference at 00000000000001dc
IP: [<ffffffff8130fb9d>] wext_handle_ioctl+0xae/0x165

How are you trying to bring up the interface, in order to use dhcpcd on it? Anyways, I would say that, yes, you do need CONFIG_WIRELESS_EXT.

-Brian

#4 lore raw
Quoted 28 lines · Brian Prodoehl
Quoted 27 lines · James
Quoted 14 lines · Hauke Mehrtens
Quoted 10 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'

Quoted 3 lines

cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

Quoted 7 lines

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Hauke
--

I'm not using any tools.
The call trace happens after I do a modprobe.
I'm guessing it doesn't like dhcpcd.

Quoted 8 lines
Quoted 2 lines

Do I really need CONFIG_WIRELESS_EXT?
--

Something is trying to use wext. This is from your original message:

BUG: unable to handle kernel NULL pointer dereference at 00000000000001dc
IP: [<ffffffff8130fb9d>] wext_handle_ioctl+0xae/0x165

There's still something wrong in compat if that causes it to crash though.

johannes

author
#5 lore raw

enable CONFIG_WIRELESS_EXT

In reply to Brian Prodoehl
Quoted 6 lines · Brian Prodoehl

How are you trying to bring up the interface, in order to use dhcpcd on it? Anyways, I would say that, yes, you do need CONFIG_WIRELESS_EXT.

-Brian

I had to enable Device Drivers->Network device support->Wireless LAN->Intel PRO/Wireless 2100 Network Connection to get CONFIG_WIRELESS_EXT=y
I propose there should be a new obvious kernel option to enable CONFIG_WIRELESS_EXT.

#6 lore raw

Re: enable CONFIG_WIRELESS_EXT

Quoted 5 lines · On Fri, 28 Jan 2011 11:07:28 -0500 James wrote:
Quoted 4 lines · Brian Prodoehl

How are you trying to bring up the interface, in order to use dhcpcd on it? Anyways, I would say that, yes, you do need CONFIG_WIRELESS_EXT.

Quoted 7 lines
Quoted 2 lines

-Brian

I had to enable Device Drivers->Network device support->Wireless LAN->Intel PRO/Wireless 2100 Network Connection to get CONFIG_WIRELESS_EXT=y
I propose there should be a new obvious kernel option to enable CONFIG_WIRELESS_EXT.

What wireless driver are you using?

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

#7 lore raw
In reply to James
Quoted 20 lines · James
Quoted 19 lines · Hauke Mehrtens
Quoted 10 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'

Quoted 3 lines

cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Quoted 8 lines
Quoted 2 lines

Hauke
--

I'm not using any tools.
The call trace happens after I do a modprobe.
I'm guessing it doesn't like dhcpcd.

Do I really need CONFIG_WIRELESS_EXT?

This still doesn't feel like the entire story. Do you have NetworkManager running, by chance?

-Brian

author
#8 lore raw
Quoted 26 lines · Brian Prodoehl
Quoted 25 lines · James
Quoted 13 lines · Hauke Mehrtens
Quoted 4 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17

Quoted 8 lines

ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

Quoted 7 lines

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Hauke
--

I'm not using any tools.
The call trace happens after I do a modprobe.
I'm guessing it doesn't like dhcpcd.

Quoted 6 lines
Quoted 1 line

Do I really need CONFIG_WIRELESS_EXT?

This still doesn't feel like the entire story. Do you have NetworkManager running, by chance?

-Brian

No Network Manager, I use Gentoo.
dhcpcd is running
I disabled wpa_suppliucant from auto starting.

Any ideas of what other processes to check for?

#9 lore raw
Quoted 31 lines · James
Quoted 30 lines · Brian Prodoehl
Quoted 19 lines · James
Quoted 18 lines · Hauke Mehrtens
Quoted 4 lines · James

cfg80211: Calling CRDA to update world regulatory domain Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 Backport based on linux-next.git next-20110121
ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17

Quoted 8 lines

ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
cfg80211: wext will not work because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will not work.

WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was not set in your kernel config and iwconfig does not work without wext.

See: http://www.spinics.net/lists/linux-wireless/msg63449.html

Quoted 7 lines
Quoted 2 lines

Hauke
--

I'm not using any tools.
The call trace happens after I do a modprobe.
I'm guessing it doesn't like dhcpcd.

Do I really need CONFIG_WIRELESS_EXT?

This still doesn't feel like the entire story.  Do you have NetworkManager running, by chance?

Quoted 7 lines
Quoted 2 lines

-Brian

No Network Manager, I use Gentoo.
dhcpcd is running
I disabled wpa_suppliucant from auto starting.

Any ideas of what other processes to check for?

I dug through the source of dhcpcd a bit, and it uses wext to fetch the SSID. So, maybe that does explain it. I guess the real fix is for dhcpcd to get updated to use nl80211.

#10 lore raw
Quoted 3 lines · Brian Prodoehl

I dug through the source of dhcpcd a bit, and it uses wext to fetch the SSID. So, maybe that does explain it. I guess the real fix is for dhcpcd to get updated to use nl80211.

You got me curious now. Why does dhcpd need ssid?

Signature · 1 line
Kalle Valo