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@xxxxxxx> 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
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
