I ran udevadm, here are the environment variables passed to the tascam_fw script. Looks like 3 events are triggered and the script is sometimes called without DEVNAME set:
sudo udevadm monitor --environment --udev calling: monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing
UDEV [5993.106245] add /devices/pci0000:00/0000:00:14.0/usb3/3-1 (usb) ACTION=add BUSNUM=003 DEVNAME=/dev/bus/usb/003/007 DEVNUM=007 DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=8006 ID_MODEL_ENC=8006 ID_MODEL_FROM_DATABASE=US-122 Audio/Midi Interface (without fw) ID_MODEL_ID=8006 ID_REVISION=0100 ID_SERIAL=1604_8006 ID_USB_INTERFACES=:ffffff: ID_VENDOR=1604 ID_VENDOR_ENC=1604 ID_VENDOR_FROM_DATABASE=Tascam ID_VENDOR_ID=1604 MAJOR=189 MINOR=262 PRODUCT=1604/8006/100 SEQNUM=3509 SUBSYSTEM=usb TYPE=255/255/255 USEC_INITIALIZED=5993072486
UDEV [5993.118743] add /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0 (usb) .MM_USBIFNUM=00 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0 DEVTYPE=usb_interface ID_MODEL_FROM_DATABASE=US-122 Audio/Midi Interface (without fw) ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class ID_USB_PROTOCOL_FROM_DATABASE=Vendor Specific Protocol ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass ID_VENDOR_FROM_DATABASE=Tascam INTERFACE=255/255/255 MODALIAS=usb:v1604p8006d0100dcFFdscFFdpFFicFFiscFFipFFin00 PRODUCT=1604/8006/100 SEQNUM=3510 SUBSYSTEM=usb TYPE=255/255/255 USEC_INITIALIZED=5993108279
UDEV [5993.120779] bind /devices/pci0000:00/0000:00:14.0/usb3/3-1 (usb) ACTION=bind BUSNUM=003 DEVNAME=/dev/bus/usb/003/007 DEVNUM=007 DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=8006 ID_MODEL_ENC=8006 ID_MODEL_FROM_DATABASE=US-122 Audio/Midi Interface (without fw) ID_MODEL_ID=8006 ID_REVISION=0100 ID_SERIAL=1604_8006 ID_USB_INTERFACES=:ffffff: ID_VENDOR=1604 ID_VENDOR_ENC=1604 ID_VENDOR_FROM_DATABASE=Tascam ID_VENDOR_ID=1604 MAJOR=189 MINOR=262 PRODUCT=1604/8006/100 SEQNUM=3511 SUBSYSTEM=usb TYPE=255/255/255 USEC_INITIALIZED=5993072486
Joe Spencer 602.777.2307
On Wed, Aug 8, 2018 at 11:38 PM Joseph Spencer joespenceris@gmail.com wrote:
OK,
I booted with nomodeset in the kernel options. This time I was able to plug the tascam us-122 in to usb and the UI didn't freeze; however, pulse audio never came up. I'm attaching the journalctl logs. You can see that it never gets past "task pulseaudio:1750 blocked for more than 120 seconds".
Joe Spencer 602.777.2307
On Wed, Aug 8, 2018 at 11:49 AM Joseph Spencer joespenceris@gmail.com wrote:
I'll give that a shot!
Also, I thought the following lines in journalctl were a bit odd:
first:
Aug 04 03:13:50 localhost.localdomain /lib/udev/tascam_fw[2834]: load /usr/share/alsa/firmware/usx2yloader/us122fw.ihx for 1604/8006/100 to /dev/bus/usb/003/002 Aug 04 03:13:50 localhost.localdomain /lib/udev/tascam_fw[2837]: load /usr/share/alsa/firmware/usx2yloader/us122fw.ihx for 1604/8006/100 to
second:
Aug 04 03:13:52 localhost.localdomain /lib/udev/tascam_fpga[2859]: calling /usr/bin/usx2yloader for Aug 04 03:13:52 localhost.localdomain /lib/udev/tascam_fpga[2861]: leaving Aug 04 03:13:52 localhost.localdomain kernel: usbcore: registered new interface driver snd-usb-usx2y Aug 04 03:13:52 localhost.localdomain /lib/udev/tascam_fpga[2864]: calling /usr/bin/usx2yloader for Aug 04 03:13:54 localhost.localdomain /lib/udev/tascam_fpga[2867]: leaving
I thought it was stranged that "to" and "for" had missing values after them.
So in the respective /lib/udev/tascam_f* scripts I added some debug output...
In /lib/udev/tascam_fpga I added:
debug_date=$(date +%S%N)
env > "/fpga-${debug_date}.env"
In /lib/udev/tascam_fw I added:
debug_date=$(date +%S%N) env > "/fw-${debug_date}.env"
Plugged my device in and sure enough, DEVNAME wasn't set in tascam_fw on the 2nd run, and DEVICE is never set in tascam_fpga.
Could it be that I don't have udev configured properly?
Joe Spencer 602.777.2307
On Wed, Aug 8, 2018 at 11:35 AM Takashi Iwai tiwai@suse.de wrote:
On Wed, 08 Aug 2018 18:46:13 +0200, Joseph Spencer wrote:
I installed the kernal-debug package along with debug info (Linux localhost.localdomain 4.17.11-200.fc28.x86_64+debug #1 SMP Mon Jul 30 14:53:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux).
I looked in /boot/config-4.17.11-200.fc28.x86_64+debug and I see that
the
debug options are now enabled (attaching this file in case there are
more
options I can enable).
I repeated another failure. The output in journalctl -f appears to me
to
be about the same (see attached)
Any pointers on what I could enable or do to debug this further?
If so, then try to disable i915 KMS. e.g. boot with nomodeset option, and check whether the crash still happens.
Takashi