You are not logged in.

#1 2019-11-01 09:08:44

orwah
Member
Registered: 2019-11-01
Posts: 3

TASCAM US-122 => kernel panic?

Hi all,

I have a TASCAM US-122 interface, and I've followed the setup on the wiki [1] but when I plug in the interface my computer panics with a flashing capslock. I found a thread elsewhere that suggested booting with it plugged in, so I did that, managed to have my computer operational, but still the interface was not working, so I tried plugging/unplugging a few times, and managed to get this:

[   96.612015] usb 1-2: new full-speed USB device number 5 using xhci_hcd
[   96.752819] usb 1-2: New USB device found, idVendor=1604, idProduct=8006, bcdDevice= 1.00
[   96.752825] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   96.813365] usb 1-2: USB disconnect, device number 5
[   98.585268] usb 1-2: new full-speed USB device number 6 using xhci_hcd
[   98.726364] usb 1-2: New USB device found, idVendor=1604, idProduct=8007, bcdDevice= 0.01
[   98.726370] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   98.776128] usbcore: registered new interface driver snd-usb-usx2y
[  108.491735] general protection fault: 0000 [#1] PREEMPT SMP PTI
[  108.491738] CPU: 3 PID: 1215 Comm: modprobe Tainted: G     U     OE     5.3.7-arch1-2-ARCH #1
[  108.491739] Hardware name: Dell Inc. Precision 3510/00D152, BIOS 1.19.3 08/20/2018
[  108.491743] RIP: 0010:__kmalloc+0xa3/0x270
[  108.491745] Code: 77 48 8b 70 08 48 39 f2 75 e7 4c 8b 28 4d 85 ed 0f 84 99 01 00 00 41 8b 58 20 49 8b 38 48 8d 8a 00 02 00 00 4c 89 e8 4c 01 eb <48> 33 1b 49 33 98 68 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 ae
[  108.491746] RSP: 0018:ffffa907015f7bd0 EFLAGS: 00010206
[  108.491747] RAX: 714f3ada6f1bfb6f RBX: 714f3ada6f1bfb6f RCX: 0000000000046203
[  108.491748] RDX: 0000000000046003 RSI: 0000000000046003 RDI: 000000000002f120
[  108.491749] RBP: 0000000000000dc0 R08: ffff8e834dc06f40 R09: ffff8e8348eff780
[  108.491750] R10: 0000000000000000 R11: 000000000000000c R12: 00000000000000d8
[  108.491751] R13: 714f3ada6f1bfb6f R14: ffffffff883f1a7b R15: ffff8e834dc06f40
[  108.491752] FS:  00007fa6c01a5740(0000) GS:ffff8e834fac0000(0000) knlGS:0000000000000000
[  108.491753] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  108.491754] CR2: 0000560ec3e75000 CR3: 000000043b46e006 CR4: 00000000003606e0
[  108.491755] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  108.491755] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[  108.491756] Call Trace:
[  108.491761]  pkcs7_verify+0xdb/0x8b0
[  108.491763]  verify_pkcs7_signature+0x86/0x150
[  108.491765]  mod_verify_sig+0x80/0xa3
[  108.491768]  load_module+0x6bd/0x2400
[  108.491771]  ? insert_vmap_area.constprop.0+0x93/0xd0
[  108.491773]  ? _raw_spin_unlock+0x16/0x30
[  108.491776]  ? vmap_page_range_noflush+0x23c/0x350
[  108.491778]  ? map_vm_area+0x31/0x40
[  108.491779]  ? __vmalloc_node_range+0x1ad/0x230
[  108.491782]  ? __se_sys_init_module+0x114/0x180
[  108.491783]  __se_sys_init_module+0x114/0x180
[  108.491787]  do_syscall_64+0x5f/0x1c0
[  108.491789]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  108.491791] RIP: 0033:0x7fa6c02d0d2e
[  108.491792] Code: 48 8b 0d 55 01 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 01 0c 00 f7 d8 64 89 01 48
[  108.491793] RSP: 002b:00007fff30396f78 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[  108.491794] RAX: ffffffffffffffda RBX: 0000560ec3e640a0 RCX: 00007fa6c02d0d2e
[  108.491795] RDX: 0000560ec361a400 RSI: 00000000000042c9 RDI: 0000560ec3e72520
[  108.491796] RBP: 0000560ec361a400 R08: 0000560ec3e6301a R09: 0000000000000000
[  108.491797] R10: 0000560ec3e63010 R11: 0000000000000246 R12: 0000560ec3e72520
[  108.491797] R13: 0000560ec3e64040 R14: 0000000000040000 R15: 0000560ec3e640a0
[  108.491799] Modules linked in: snd_seq snd_usb_usx2y snd_usbmidi_lib snd_rawmidi snd_seq_d_sched cmac algif_hash algif_skcipher af_alg bnep joydev mousedev i915 radeon iwlmvm x86_pkg_ iTCO_wdt btintel i2c_algo_bit uvcvideo kvm_intel drm_kms_helper videobuf2_vmalloc videobuf2_rse_keymap wmi_bmof videobuf2_common snd_hda_codec dell_wmi_descriptor intel_wmi_thunderbolt intel_gtt vfat snd_hwdep videodev intel_cstate iwlwifi snd_pcm fat agpgart dell_smm_hwmon loothermal_device sysimgblt cfg80211 intel_rapl_perf psmouse pcspkr
[  108.491822]  input_leds e1000e soundcore i2c_i801 intel_rapl_common memstick fb_sys_fops imal_zone evdev dell_smo8800 mac_hid dell_rbtn int3400_thermal rfkill ac acpi_thermal_rel nfsdg crypto_user acpi_call(OE) ip_tables x_tables crct10dif_pclmul crc32_pclmul ghash_clmulni_inrtsx_pci xhci_pci cryptd glue_helper xhci_hcd scsi_mod i8042 serio aes_x86_64 ext4 crc32c_gen
[  108.491842] ---[ end trace 879c08ae6ff1eb93 ]---
[  108.491844] RIP: 0010:__kmalloc+0xa3/0x270
[  108.491845] Code: 77 48 8b 70 08 48 39 f2 75 e7 4c 8b 28 4d 85 ed 0f 84 99 01 00 00 41 8b c7 0f 0f 94 c0 84 c0 74 ae
[  108.491846] RSP: 0018:ffffa907015f7bd0 EFLAGS: 00010206
[  108.491847] RAX: 714f3ada6f1bfb6f RBX: 714f3ada6f1bfb6f RCX: 0000000000046203
[  108.491848] RDX: 0000000000046003 RSI: 0000000000046003 RDI: 000000000002f120
[  108.491849] RBP: 0000000000000dc0 R08: ffff8e834dc06f40 R09: ffff8e8348eff780
[  108.491850] R10: 0000000000000000 R11: 000000000000000c R12: 00000000000000d8
[  108.491851] R13: 714f3ada6f1bfb6f R14: ffffffff883f1a7b R15: ffff8e834dc06f40
[  108.491852] FS:  00007fa6c01a5740(0000) GS:ffff8e834fac0000(0000) knlGS:0000000000000000
[  108.491853] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  108.491853] CR2: 0000560ec3e75000 CR3: 000000043b46e006 CR4: 00000000003606e0
[  108.491854] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  108.491855] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

I'm no expert but wouldn't pkcs7_verify in the trace indicate a dodgy signature on my snd-usb-usx2y module? Would it be worth trying building from source?

My kernel version: 5.3.7-arch1-2-ARCH

[1] https://wiki.archlinux.org/index.php/Pr … cam_US-122

Thanks

Offline

#2 2019-11-01 11:17:18

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,359

Re: TASCAM US-122 => kernel panic?

The fxload package is rather old and it's upstream code doesn't appear to have been updated since 2008 .

There also appear to be several models with number 122, which one do you have ?


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#3 2019-11-01 13:46:57

orwah
Member
Registered: 2019-11-01
Posts: 3

Re: TASCAM US-122 => kernel panic?

It just says US-122 on it, nothing else. I think it's a first gen, it has the blue rubber on it.

Offline

#4 2019-11-02 11:58:22

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,359

Re: TASCAM US-122 => kernel panic?

I've searched  a bit and fxload did work in alsa unofficial wiki in 2018 , so there's a chance it will still work now.

To test things I suggest to remove the udev rules and load the firmware manually.

from a root terminal :

insert the device, run lsusb
note the bus & device number

# fxload -s /usr/share/alsa/firmware/usx2yloader/tascam_loader.ihx -I /usr/share/alsa/firmware/usx2yloader/us122fw.ihx -D /dev/bus/usb/abc/def
# usx2yloader

replace abc with the actual bus number and def with the actual device number you noted above..
post the outputs .
(you may want to use a pastebin client )


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#5 2019-11-05 18:23:52

orwah
Member
Registered: 2019-11-01
Posts: 3

Re: TASCAM US-122 => kernel panic?

Sorry for the late reply @Lone_Wolf, thanks for your help. I tried but unfortunately after a short while it locked up again. sad

Offline

#6 2019-11-05 23:53:55

loqs
Member
Registered: 2014-03-06
Posts: 9,074

Re: TASCAM US-122 => kernel panic?

Have you tried linux-lts?  To see if the issue is newer than 4.19.

Offline

Board footer

Powered by FluxBB