Ticket #2227 (new defect)

Opened 4 years ago

Last modified 4 years ago

iwconfig key restricted hanging up

Reported by: linux-ink Owned by: openmoko-kernel
Priority: high Milestone: FSO
Component: kernel Version:
Severity: critical Keywords: wifi
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

I tryed setting up direct WiFi?? network access (without hardware Access Points) for FSO M5-equiped FR by hands (I successfully used such scenario for configuring wireless-networking for some OLPCs & traditional notebooks):

# iwconfig eth0 mode ad-hoc # iwconfig eth0 essid "my-wifi" # iwconfig eth0 eth0 AR6000 802.11g ESSID:"my-wifi"

Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# iwconfig eth0 channel 1 # iwconfig eth0 key restricted 1234567890 # iwconfig eth0 eth0 AR6000 802.11g ESSID:""

Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:1234-5678-90 Security mode:restricted Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I lost my ESSID at this step and try setting up this one once again:

# iwconfig eth0 essid "my-wifi"

After that system hangs up and blinking by red LED in AUX button.

Seems like "restricted" key is key point for this situation -- with open key all works good.

Attachments

ar6k-dodge-locking-bug.patch (1.1 KB) - added by werner 4 years ago.
quick and dirty work-around for locking bug

Change History

Changed 4 years ago by werner

quick and dirty work-around for locking bug

comment:1 Changed 4 years ago by werner

I lost my ESSID at this step and try setting up this one once again:

This is the driver's way of remembering that the changes haven't
been sent to the hardware yet.

After that system hangs up and blinking by red LED in AUX button.

This, however, it shouldn't do. I can reproduce it. Digging ...

  • Werner

comment:2 Changed 4 years ago by werner

Grrr, did I mention that I hate web-based interfaces, particularly if
they don't know what a "back" button it for ?

The last line of my comment is obsolete. It should have been:

... It's a locking inconsistency in the AR6k driver. I've attached a
patch that avoids the problem but that may introduce a race condition.

It seems that there may be a more severe issue with how the driver
locks against access from interrupts. This needs a bit more investigating.

  • Werner
Note: See TracTickets for help on using tickets.