Antonio, It was reported sometime ago that that there was a change in the kernel level that was blocking successive slamr dependent ppp0 sessions, A complete reboot was necessary to enable the next dialout. The fact that a mere in Fedora # service slmodemd stop # service slmodemd start # wvdial is now enabling dialouts is in fact in Good News. Under Debian/Ubuntu the counterpart is $ sudo /etc/init.d/sl-modem-daemon restart Perhaps Sasha can analyze your kernel error message: BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:85 in_atomic():0, irqs_disabled():1 Pid: 6883, comm: slmodemd Tainted: P 2.6.27.19-170.2.35.fc10.i686.PAE #1 [<c042ce79>] __might_sleep+0xc6/0xcb [<c0526cb6>] copy_to_user+0x36/0x10a [<f8e4d272>] amrmo_read+0x49/0x5f [slamr] [<f8e4d229>] ? amrmo_read+0x0/0x5f [slamr] [<c049935e>] vfs_read+0x81/0xdc [<c0499452>] sys_read+0x3b/0x60 [<c0408b8b>] sysenter_do_call+0x12/0x34 MarvS ---------- Forwarded message ---------- From: Antonio Olivares <olivares14031@xxxxxxxxx> Date: Sat, Mar 21, 2009 at 10:06 PM Subject: slamr: BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:85 To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> Dear Marv, I keep seeing this message over and over. BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:85 in_atomic():0, irqs_disabled():1 Pid: 6883, comm: slmodemd Tainted: P 2.6.27.19-170.2.35.fc10.i686.PAE #1 [<c042ce79>] __might_sleep+0xc6/0xcb [<c0526cb6>] copy_to_user+0x36/0x10a [<f8e4d272>] amrmo_read+0x49/0x5f [slamr] [<f8e4d229>] ? amrmo_read+0x0/0x5f [slamr] [<c049935e>] vfs_read+0x81/0xdc [<c0499452>] sys_read+0x3b/0x60 [<c0408b8b>] sysenter_do_call+0x12/0x34 I have submitted my name over here: http://www.kerneloops.org/submitresult.php?email=olivares14031%40gmail.com&number=298940 I know ahead of time that it is not a kernel problem because slamr is running and it "taints" the kernel. Machine is running fine other than the above message, but I keep seeing it once in a while. NOTE: to use the slamr driver either in Fedora or in Slax, I have to do the following in Fedora # service slmodemd stop # service slmodemd start # wvdial and connection succeeds again, otherwise modem does not respond. In slax the process is similar # /etc/rc.d/rc.slmodemd stop # /etc/rc.d/rc.slmodemd start then use # wvdial and connection succeeds. Just my experience. Sorry to bother, but in case someone else sees the same happening. Regards, Antonio
