Cannot get slmodem working, kernel BUG

Renan Birck · 2009-08-04 04:43:45

Hello,

I'm trying to get the dial-up modem on my old computer working, to have a backup in case my DSL goes down. The modem is an LG LM-I56N, which uses a SmartLink chipset. I have used the same modem successfully on Linux, but a long time ago, with Ubuntu 5.10.

[root@kirlian ~]# lspci | grep -i modem
00:0c.0 Modem: Smart Link Ltd. LM-I56N (rev 02)

So I installed the slmodem package, but when I try to load the module slamr, I get this:

[root@kirlian ~]# modprobe slamr
Morto

On dmesg there is a kernel BUG:

slamr: SmartLink AMRMO modem.
BUG: unable to handle kernel paging request at 75626564
IP: [<c026fe45>] strnlen+0x15/0x40
*pde = 00000000
Oops: 0000 [#1] PREEMPT SMP
last sysfs file: /sys/devices/platform/w83627hf.656/pwm2
Modules linked in: slamr(P+) nfnetlink_queue nfnetlink fuse xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 vboxnetadp vboxnetflt iptable_filter ip_tables vboxdrv xt_state nf_conntrack xt_NFQUEUE x_tables vmnet vsock vmci vmmon w83627hf hwmon_vid nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 ufs ext2 mbcache ppdev nvidia(P) ohci_hcd lp i2c_core psmouse parport_pc ehci_hcd parport sis_agp serio_raw sg pcspkr usbcore agpgart shpchp pci_hotplug thermal processor evdev fan button battery ac snd_intel8x0 snd_ac97_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore ac97_bus slhc sis900 mii rtc_cmos rtc_core rtc_lib reiserfs sr_mod floppy cdrom sd_mod ata_generic pata_sis libata scsi_mod

Pid: 1313, comm: modprobe Tainted: P           (2.6.30-ARCH #1) To Be Filled By O.E.M.
EIP: 0060:[<c026fe45>] EFLAGS: 00010097 CPU: 1
EIP is at strnlen+0x15/0x40
EAX: 75626564 EBX: c05d7260 ECX: 75626564 EDX: fffffffe
ESI: c05d6e7a EDI: 75626564 EBP: ffffffff ESP: f6915c90
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process modprobe (pid: 1313, ti=f6914000 task=f5f9d800 task.ti=f6914000)
Stack:
 98180e36 c026e462 804b2b2e 00000000 ffffea4c 00000004 00000000 ffffffff
 0000000a ffffffff ffffffff 98180e36 c05d6e7a f8856cbe f6915ddc f8856cc0
 c026f10f 00000004 00000000 ffffffff 0000000a ffffffff ffffffff ffffffff
Call Trace:
 [<c026e462>] ? string+0x62/0x110
 [<c026f10f>] ? vsnprintf+0x22f/0x450
 [<c026f481>] ? vscnprintf+0x21/0x40
 [<c013be4f>] ? vprintk+0x8f/0x3b0
 [<c022ab71>] ? sysfs_find_dirent+0x31/0x50
 [<c01e5b3b>] ? iput+0x2b/0x70
 [<c03cec94>] ? printk+0x23/0x3f
 [<f801f03e>] ? amrmo_pci_probe+0x3e/0x410 [slamr]
 [<c028134a>] ? local_pci_probe+0x1a/0x40
 [<c0282611>] ? pci_device_probe+0x81/0xb0
 [<c0302559>] ? driver_probe_device+0x89/0x170
 [<c03026d1>] ? __driver_attach+0x91/0xa0
 [<c0302640>] ? __driver_attach+0x0/0xa0
 [<c0301bf2>] ? bus_for_each_dev+0x62/0xa0
 [<c0302382>] ? driver_attach+0x22/0x40
 [<c0302640>] ? __driver_attach+0x0/0xa0
 [<c030135e>] ? bus_add_driver+0xce/0x2b0
 [<c02824f0>] ? pci_device_remove+0x0/0x60
 [<c0302a4f>] ? driver_register+0x6f/0x130
 [<c0282aa9>] ? __pci_register_driver+0x49/0xd0
 [<f801f4c2>] ? amrmo_init+0xb2/0x106 [slamr]
 [<c010115f>] ? do_one_initcall+0x3f/0x190
 [<c018c927>] ? tracepoint_module_notify+0x47/0x50
 [<c0159ff6>] ? notifier_call_chain+0x46/0x80
 [<f801f410>] ? amrmo_init+0x0/0x106 [slamr]
 [<c015a43d>] ? __blocking_notifier_call_chain+0x6d/0xa0
 [<c016e4c7>] ? sys_init_module+0xb7/0x1f0
 [<c01257ec>] ? do_page_fault+0xfc/0x330
 [<c0103c93>] ? sysenter_do_call+0x12/0x28
Code: 83 c4 04 5f c3 e8 0c b4 ec ff 8d b6 00 00 00 00 8d bf 00 00 00 00 83 ec 04 65 8b 0d 14 00 00 00 89 0c 24 31 c9 89 c1 89 c8 eb 06 <80> 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 8b 14 24 65 33 15 14
EIP: [<c026fe45>] strnlen+0x15/0x40 SS:ESP 0068:f6915c90
CR2: 0000000075626564
---[ end trace 648535fe9605c368 ]---
note: modprobe[1313] exited with preempt_count 2

Any ideas? I know not much can be done since it's a closed-source module, but anyway I'd like to try to fix it.

Thanks!

djszapi · 2009-08-08 10:27:37

Hello Renan!

It seems worse because of oops messages after a simple modprobe

I think you need for reporting it to the author if it's really closed driver. Could you try it with another kernel version, or other distribution, can it work?

Arch Linux

#1 2009-08-04 04:43:45

Cannot get slmodem working, kernel BUG

#2 2009-08-08 10:27:37

Re: Cannot get slmodem working, kernel BUG

Board footer