[hsflinux] Problem with Debian and the hsf driver

Tue Sep 4 08:54:56 EDT 2012

Hello!

During the last two days I was trying to set up my modem for fax use.

I am running Debian with the 2.6.32-5-amd64 kernel. My modem is identified
as “Conexant Systems, Inc. SoftV92 SpeakerPhone SoftRing Modem with SmartSP
(rev 01)”.

Therefor I have downloaded the lates version of your drivers
(hsfmodem-7.80.02.06x86_64full.tar.gz). The “make install” command runs
well.

Running “hsfconfig” afterwards says the following:

----------

Warning: no device detected by hsf driver - HDA modems may require reboot

Note: HDA support not compiled in the driver 

----------

So I did a reboot of my system. During the boot I saw the following:

----------

Sep  3 00:07:16 vmserver kernel: [   20.814361] BUG: unable to handle kernel
paging request at ffff8800bff66000

Sep  3 00:07:16 vmserver kernel: [   20.814497] IP: [<ffffffffa02dda91>]
hsfengine1480_+0xd1/0x340 [hsfengine]

Sep  3 00:07:16 vmserver kernel: [   20.814659] PGD 1002063 PUD 11067 PMD
12067 PTE 0

Sep  3 00:07:16 vmserver kernel: [   20.814859] Oops: 0000 [#1] SMP 

Sep  3 00:07:16 vmserver kernel: [   20.814980] last sysfs file:
/sys/devices/platform/i8042/serio1/input/input5/event5/uevent

Sep  3 00:07:16 vmserver kernel: [   20.815039] CPU 1 

Sep  3 00:07:16 vmserver kernel: [   20.815120] Modules linked in: snd_pcm
snd_timer i5000_edac hsfpcibasic2(+) ioatdma snd soundcore snd_page_alloc
edac_core psmouse i2c_i801 shpchp hsfserial serio_raw pci_hotplug rng_core
pcspkr i5k_amb dca container i2c_core processor hsfsoar button evdev
hsfengine(P) hsfosspec ext4 mbcache jbd2 crc16 dm_mod raid10 raid456
async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx
raid1 raid0 multipath linear md_mod sg sr_mod cdrom ata_generic sd_mod
crc_t10dif usbhid hid ata_piix ahci uhci_hcd libata floppy thermal mptsas
mptscsih mptbase scsi_transport_sas ehci_hcd e1000e scsi_mod usbcore
nls_base thermal_sys [last unloaded: scsi_wait_scan]

Sep  3 00:07:16 vmserver kernel: [   20.817950] Pid: 688, comm: modprobe
Tainted: P           2.6.32-5-amd64 #1 System Product Name

Sep  3 00:07:16 vmserver kernel: [   20.817950] RIP:
0010:[<ffffffffa02dda91>]  [<ffffffffa02dda91>] hsfengine1480_+0xd1/0x340
[hsfengine]

Sep  3 00:07:16 vmserver kernel: [   20.817950] RSP: 0018:ffff8802bc97bb78
EFLAGS: 00010202

Sep  3 00:07:16 vmserver kernel: [   20.817950] RAX: 0000000000000031 RBX:
ffff8800bff66000 RCX: 00000000bff66000

Sep  3 00:07:16 vmserver kernel: [   20.817950] RDX: 0000000000000031 RSI:
ffff8800000f6695 RDI: ffffffffa039d5e6

Sep  3 00:07:16 vmserver kernel: [   20.817950] RBP: ffff8802bb72c110 R08:
ffff8802bc97bae6 R09: ffffffff8147d200

Sep  3 00:07:16 vmserver kernel: [   20.817950] R10: 0000000000100000 R11:
ffffffff81153802 R12: ffffffffa018c3a0

Sep  3 00:07:16 vmserver kernel: [   20.817950] R13: ffff8802bc97bb8c R14:
0000000000000031 R15: ffff8802baecb600

Sep  3 00:07:16 vmserver kernel: [   20.817950] FS:  00007ffc342ef700(0000)
GS:ffff88000a680000(0000) knlGS:0000000000000000

Sep  3 00:07:16 vmserver kernel: [   20.817950] CS:  0010 DS: 0000 ES: 0000
CR0: 000000008005003b

Sep  3 00:07:16 vmserver kernel: [   20.817950] CR2: ffff8800bff66000 CR3:
00000002bc059000 CR4: 00000000000006e0

Sep  3 00:07:16 vmserver kernel: [   20.817950] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000

Sep  3 00:07:16 vmserver kernel: [   20.817950] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400

Sep  3 00:07:16 vmserver kernel: [   20.817950] Process modprobe (pid: 688,
threadinfo ffff8802bc97a000, task ffff8802bd370710)

Sep  3 00:07:16 vmserver kernel: [   20.817950] Stack:

Sep  3 00:07:16 vmserver kernel: [   20.817950]  0000000000000000
00000000000f6690 6e55a180deadaffe ffff8802bd27e680

Sep  3 00:07:16 vmserver kernel: [   20.817950] <0> ffff8802bb72c110
ffffffffa018c3a0 ffff8802baecb600 0000000000000000

Sep  3 00:07:16 vmserver kernel: [   20.817950] <0> ffffffffa0462320
ffffffffa02d88d3 00000004baecb600 ffff8802ba71c000

Sep  3 00:07:16 vmserver kernel: [   20.817950] Call Trace:

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa02d88d3>] ?
hsfengine1664_+0x93/0xc0 [hsfengine]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa02d8477>] ?
hsfengine508_+0x17/0x40 [hsfengine]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa02b1456>] ?
cnxthsf_7800206x86_64full_ComCtrl_Open+0x76/0x270 [hsfengine]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa0189d4a>] ?
cnxthsf_7800206x86_64full_cnxt_serial_add+0x25a/0x5d0 [hsfserial]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff81195bff>] ?
snprintf+0x44/0x4c

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff811a57e7>] ?
pci_enable_resources+0x27/0x12e

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa018a770>] ?
cnxt_event_handler+0x0/0x374 [hsfserial]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa045e264>] ?
cnxthwpci_probe+0x1c7/0x293 [hsfpcibasic2]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff811a2d06>] ?
local_pci_probe+0x12/0x16

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff811a3956>] ?
pci_device_probe+0xc0/0xe9

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff81221504>] ?
driver_probe_device+0xa3/0x14b

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff812215fb>] ?
__driver_attach+0x4f/0x6f

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff812215ac>] ?
__driver_attach+0x0/0x6f

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff81220dd3>] ?
bus_for_each_dev+0x43/0x74

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff81220793>] ?
bus_add_driver+0xaf/0x1f8

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff812218b3>] ?
driver_register+0xa7/0x111

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa042b000>] ?
cnxthwpci_init+0x0/0xff [hsfpcibasic2]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff811a3b9c>] ?
__pci_register_driver+0x50/0xb8

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffffa042b000>] ?
cnxthwpci_init+0x0/0xff [hsfpcibasic2]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff8100a065>] ?
do_one_initcall+0x64/0x174

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff8107ab78>] ?
sys_init_module+0xc5/0x21a

Sep  3 00:07:16 vmserver kernel: [   20.817950]  [<ffffffff81010b42>] ?
system_call_fastpath+0x16/0x1b

Sep  3 00:07:16 vmserver kernel: [   20.817950] Code: c1 e0 08 09 c1 0f b6
43 08 09 c1 0f b6 43 0d 89 cb 49 03 9f e0 00 00 00 c1 e0 08 09 c2 0f b7 c2
85 c0 0f 84 4e 01 00 00 41 89 c6 <0f> b6 03 ff c8 83 f8 01 0f 87 11 01 00 00
44 0f b6 63 04 48 c7 

Sep  3 00:07:16 vmserver kernel: [   20.817950] RIP  [<ffffffffa02dda91>]
hsfengine1480_+0xd1/0x340 [hsfengine]

Sep  3 00:07:16 vmserver kernel: [   20.817950]  RSP <ffff8802bc97bb78>

Sep  3 00:07:16 vmserver kernel: [   20.817950] CR2: ffff8800bff66000

Sep  3 00:07:16 vmserver kernel: [   20.817950] ---[ end trace
038881adb326e318 ]---

----------

I am neither a linux kernel expert nor a linux driver programmer, but for me
it seems like the module is crashing during startup?

I’ve tried to generate a report with “hsfconfig –dumpdiag”, but the programs
hangs at the point: Probing "/dev/ttySHSF"...

(Maybe because the kernel module is not working?)

So do you have any suggestions what I can do to get the modem working?

Regards,

Björn Gernert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxant.com/pipermail/hsflinux/attachments/20120904/21f05521/attachment.html 