Re: wireless, ural-linux driver doesn't work
> Oct 22 13:03:19 fuzzy usbcore: registered new driver ural
> Oct 22 13:03:21 fuzzy scheduling while atomic: ip/0x00000002/6056
> Oct 22 13:03:21 fuzzy Call trace:
> Oct 22 13:03:21 fuzzy [c03345e8] schedule+0x740/0x7a4
> Oct 22 13:03:21 fuzzy [c0334818] wait_for_completion+0xa4/0x148
> Oct 22 13:03:21 fuzzy [c02283c0] usb_start_wait_urb+0xb8/0x12c
> Oct 22 13:03:21 fuzzy [c02284fc] usb_control_msg+0xc8/0xf8
> Oct 22 13:03:21 fuzzy [e104f078] ural_write+0x48/0x90 [ural]
> Oct 22 13:03:21 fuzzy [e105067c] ural_init_locked+0x48/0x6f0 [ural]
> Oct 22 13:03:21 fuzzy [e1050db0] ural_init+0x3c/0xbc [ural]
> Oct 22 13:03:21 fuzzy [c02cb67c] dev_open+0xb0/0xd8
> Oct 22 13:03:21 fuzzy [c02ccf90] dev_change_flags+0x6c/0x144
> Oct 22 13:03:21 fuzzy [c030fdac] devinet_ioctl+0x620/0x76c
> Oct 22 13:03:21 fuzzy [c03111e8] inet_ioctl+0x10c/0x120
> Oct 22 13:03:21 fuzzy [c02c089c] sock_ioctl+0x1c4/0x2e0
> Oct 22 13:03:21 fuzzy [c0084804] do_ioctl+0xac/0xc0
> Oct 22 13:03:21 fuzzy [c00848d0] vfs_ioctl+0xb8/0x460
> Oct 22 13:03:21 fuzzy [c0084cb8] sys_ioctl+0x40/0x74
This is obviously a bug in the driver, its doing scheduling operations
while holding a lock. It may be "undetected" when not using PREEMPT, but
the bug is there. Please report it to the driver author/maintainer.
Ben.
Reply to: