You are not logged in.

#1 2012-01-31 15:53:37

sound
Member
Registered: 2011-11-02
Posts: 5

Realtek wireless usb device crashes Arch

Hi,

As my built-in wireless card is not working (described here, solutions also very welcome) I use a Realtek usb wireless adapter. Until yesterday, where i upgraded my system, this worked reasonably well. However, when I now plug in the usb device, after loading the system crashed. There is no kernel panic, but dbus seems to stop working. After plugging in the usb device I run wicd-curses, which crashed with the following error:

EXCEPTION! Please report this to the maintainer and file a bug report with the backtrace below:

EXCEPTION! Please report this to the maintainer and file a bug report with the backtrace below:
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 779, in dbus_scan_finished
    self.unlock_screen()
  File "/usr/share/wicd/curses/wicd-curses.py", line 607, in unlock_screen
    self.update_netlist(force_check=True)
  File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 693, in update_netlist
    self.update_ui()
  File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 918, in update_ui
    canvas = self.frame.render( (self.size),True )
  File "/usr/lib/python2.7/site-packages/urwid/widget.py", line 132, in cached_render
  File "/usr/lib/python2.7/site-packages/urwid/container.py", line 596, in render
  File "/usr/lib/python2.7/site-packages/urwid/widget.py", line 132, in cached_render
  File "/usr/lib/python2.7/site-packages/urwid/container.py", line 875, in render
  File "/usr/lib/python2.7/site-packages/urwid/widget.py", line 170, in finalize_render
  File "/usr/lib/python2.7/site-packages/urwid/listbox.py", line 333, in render
  File "/usr/lib/python2.7/site-packages/urwid/listbox.py", line 221, in calculate_visible
  File "/usr/lib/python2.7/site-packages/urwid/listbox.py", line 508, in _set_focus_complete
  File "/usr/lib/python2.7/site-packages/urwid/listbox.py", line 70, in get_focus
TypeError: list indices must be integers, not NoneType

When I run something afterwards using sudo, it blocks indefinitely. dmesg says the following:

[  480.356687] INFO: task kworker/0:0:4 blocked for more than 120 seconds.
[  480.356695] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  480.356701] kworker/0:0     D 00000001000040f8     0     4      2 0x00000000
[  480.356711]  ffff88007b7c7d30 0000000000000046 ffff880000000000 0000000000000086
[  480.356722]  ffff88007b7b1560 ffff88007b7c7fd8 ffff88007b7c7fd8 ffff88007b7c7fd8
[  480.356731]  ffffffff8180d020 ffff88007b7b1560 ffff88007b7c7ca0 ffffffff81066925
[  480.356740] Call Trace:
[  480.356757]  [<ffffffff81066925>] ? console_unlock+0x1f5/0x270
[  480.356766]  [<ffffffff81081ea2>] ? __queue_work+0xe2/0x490
[  480.356775]  [<ffffffff81425f0f>] schedule+0x3f/0x60
[  480.356781]  [<ffffffff814275f4>] __mutex_lock_slowpath+0x154/0x370
[  480.356792]  [<ffffffff813748b0>] ? __linkwatch_run_queue+0x1e0/0x1e0
[  480.356798]  [<ffffffff81427826>] mutex_lock+0x16/0x30
[  480.356804]  [<ffffffff81372375>] rtnl_lock+0x15/0x20
[  480.356811]  [<ffffffff813748be>] linkwatch_event+0xe/0x30
[  480.356818]  [<ffffffff81082a26>] process_one_work+0x116/0x4d0
[  480.356825]  [<ffffffff810833be>] worker_thread+0x15e/0x350
[  480.356831]  [<ffffffff81083260>] ? manage_workers.isra.29+0x230/0x230
[  480.356838]  [<ffffffff810883fc>] kthread+0x8c/0xa0
[  480.356846]  [<ffffffff8142b874>] kernel_thread_helper+0x4/0x10
[  480.356852]  [<ffffffff81088370>] ? kthread_worker_fn+0x190/0x190
[  480.356858]  [<ffffffff8142b870>] ? gs_change+0x13/0x13
[  480.356906] INFO: task wpa_supplicant:1338 blocked for more than 120 seconds.
[  480.356921] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  480.356923] wpa_supplicant  D 000000010000302b     0  1338      1 0x00000000
[  480.356928]  ffff88004c41fc68 0000000000000086 ffffffff00000000 dead000000100100
[  480.356933]  ffff88005af68720 ffff88004c41ffd8 ffff88004c41ffd8 ffff88004c41ffd8
[  480.356938]  ffffffff8180d020 ffff88005af68720 ffffffff8117a5d0 dead000000100100
[  480.356943] Call Trace:
[  480.356949]  [<ffffffff8117a5d0>] ? __pollwait+0xf0/0xf0
[  480.356953]  [<ffffffff81425f0f>] schedule+0x3f/0x60
[  480.356956]  [<ffffffff814275f4>] __mutex_lock_slowpath+0x154/0x370
[  480.356962]  [<ffffffff813fa9c0>] ? iw_handler_get_private+0x60/0x60
[  480.356965]  [<ffffffff81427826>] mutex_lock+0x16/0x30
[  480.356969]  [<ffffffff81372375>] rtnl_lock+0x15/0x20
[  480.356972]  [<ffffffff813f9ad5>] wext_ioctl_dispatch+0x65/0x240
[  480.356976]  [<ffffffff813f9dd0>] ? call_commit_handler+0x40/0x40
[  480.356979]  [<ffffffff813f9f86>] wext_handle_ioctl+0x46/0x90
[  480.356984]  [<ffffffff81365ed0>] dev_ioctl+0xe0/0x610
[  480.356988]  [<ffffffff81128d2c>] ? tlb_flush_mmu+0x6c/0x90
[  480.356992]  [<ffffffff8113024d>] ? unmap_region+0x10d/0x130
[  480.356996]  [<ffffffff8134ac3a>] sock_ioctl+0xfa/0x2c0
[  480.357000]  [<ffffffff8117976f>] do_vfs_ioctl+0x8f/0x500
[  480.357004]  [<ffffffff81179c71>] sys_ioctl+0x91/0xa0
[  480.357008]  [<ffffffff81429702>] system_call_fastpath+0x16/0x1b
[  480.357012] INFO: task sudo:1400 blocked for more than 120 seconds.
[  480.357014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  480.357016] sudo            D ffff88005ca6ffd8     0  1400   1112 0x00000000
[  480.357021]  ffff88005ca6faf8 0000000000000082 800000004a884067 ffff88007f6cb700
[  480.357026]  ffff88007a304020 ffff88005ca6ffd8 ffff88005ca6ffd8 ffff88005ca6ffd8
[  480.357031]  ffff88006c004020 ffff88007a304020 0000000000000001 ffff88007a624a80
[  480.357036] Call Trace:
[  480.357040]  [<ffffffff8108bfbe>] ? __mutex_init+0x2e/0x30
[  480.357045]  [<ffffffff811813a1>] ? inode_init_always+0x101/0x1c0
[  480.357050]  [<ffffffff811c662f>] ? proc_alloc_inode+0x6f/0xb0
[  480.357053]  [<ffffffff81181499>] ? alloc_inode+0x39/0xa0
[  480.357056]  [<ffffffff81425f0f>] schedule+0x3f/0x60
[  480.357060]  [<ffffffff814275f4>] __mutex_lock_slowpath+0x154/0x370
[  480.357064]  [<ffffffff81427826>] mutex_lock+0x16/0x30
[  480.357068]  [<ffffffff813555fb>] ? __alloc_skb+0x4b/0x240
[  480.357072]  [<ffffffff81372375>] rtnl_lock+0x15/0x20
[  480.357075]  [<ffffffff81372396>] rtnetlink_rcv+0x16/0x40
[  480.357080]  [<ffffffff8138b869>] netlink_unicast+0x2d9/0x320
[  480.357084]  [<ffffffff8138bc36>] netlink_sendmsg+0x2c6/0x320
[  480.357088]  [<ffffffff8134bfde>] sock_sendmsg+0x10e/0x130
[  480.357092]  [<ffffffff811522bb>] ? __kmalloc+0x15b/0x1a0
[  480.357097]  [<ffffffff81350c9b>] ? sk_prot_alloc+0x13b/0x290
[  480.357101]  [<ffffffff8104f403>] ? __wake_up+0x53/0x70
[  480.357105]  [<ffffffff8138a63d>] ? netlink_table_ungrab+0x2d/0x30
[  480.357108]  [<ffffffff8138a729>] ? netlink_insert+0xe9/0x170
[  480.357112]  [<ffffffff8134e5bd>] sys_sendto+0x13d/0x190
[  480.357117]  [<ffffffff81165972>] ? fd_install+0x62/0x80
[  480.357120]  [<ffffffff8134c66a>] ? sock_map_fd+0x2a/0x40
[  480.357124]  [<ffffffff81429702>] system_call_fastpath+0x16/0x1b

It seems like the firmware is malfunctioning. Loading the firmware seems to work fine:

[  337.427154] r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"

On my Ubuntu system, this crashes do not occur. What I am very surprised of is that Ubuntu is loading the firmware rtl8192sfw.bin. Could this be the cause of the problem? I also tried replacing the arch linux firmware for that device with the one I used in Ubuntu, however it did not work. Is there any way to tell Arch, that this is in fact a rtl8192-device and not 8712. Or doesn't it matter, because the problem is unrelated? dmesg also says in Arch that the firmware is from the staging repo:

r8712u: module is from the staging directory, the quality is unknown, you have been warned.

Is there any better firmware available?

Cheers,
sound

Offline

#2 2012-01-31 18:12:40

sound
Member
Registered: 2011-11-02
Posts: 5

Re: Realtek wireless usb device crashes Arch

ok, I wouldn't call it solved, but at least I found the reason for this behaviour: It is already filed as a bug report, see here: https://bugs.archlinux.org/task/27996

Offline

Board footer

Powered by FluxBB