Re: Bug#753816: [systemd] Broken audio
On Sat, 2014-07-05 at 18:58 +0200, Michael Biebl wrote: > Am 05.07.2014 18:38, schrieb Antonio Marcos López Alonso: > > El 05/07/14 17:06, Michael Biebl escribió: > >> Am 05.07.2014 17:56, schrieb Antonio Marcos López Alonso: > >>> Just in case, have you noticed I'm using an ALSA-Jack loopback setting > >>> for audio? > >> Under sysvinit, udev (including udevadm settle) is started before the > >> kmod init script, which loads snd_aloop. > >> That means, snd_aloop is loaded after snd_hda_intel. > >> > >> Under systemd, it looks like the snd_aloop module is loaded about the > >> same time systemd-udevd is started. There might be a race here and > >> snd_aloop is loaded before snd_hda_intel. > >> > >> This *might* be the reason, but I'm no expert on this matter. > >> > >> Can you try removing snd_aloop from /etc/modules and test if that makes > >> a difference. > >> > > > > OK removed snd_aloop and audio is back. Then reloaded the module, > > restarted JACK and audio is still fine. So as you said there must be > > some race condition in there. Should I keep this ticket opened? > > > > Hm, not sure what to do about this. We could order > systemd-load-modules.service after systemd-udevd.service. But that > doesn't guarantee the loading order of the modules and it feels like > papering over the underlying issue. > > I'm no sound expert, but I'd say that the loading order should not > matter. Maybe we need some input from the kernel team or some alsa > experts here. I think this is due to ALSA userland (or maybe higher levels) being stupid about device selection. I think the default is to use sound device 0, which can be whichever driver won the race. > I took the liberty to CC the Debian kernel team and the maintainer of > the snd_aloop module. I hope they can help us here. > > For reference the complete bug report is at [1] > > > Michael > > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753816 I think the usual workaround is to add 'index=1' to the snd-aloop line in /etc/modules. It is probably possible to do something more sophisticated in an ALSA configuration file. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Re: Kernel 3.2.0 panics
On 2014-07-05 19:29, Ben Hutchings wrote: > On Sat, 2014-07-05 at 13:41 -0700, AC wrote: >> Hi all, >> >> I've been searching for about a month trying to fix the kernel panic on >> boot for 3.2.0-4 with no luck so far. I get the well documented error: >> >> No filesystem could mount root: tried: >> Kernel Panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,0) >> (plus stack dump) >> >> however none of the suggested fixes (the few that exist) work. My >> system is a Pentium II and recently upgraded to wheezy. I've tried both >> the 3.2.0-4-686pae and the 3.2.0-4-486 images with identical results, >> they all end with the kernel panic above. >> >> I'm currently running kernel image 2.6.39 which is working fine, I just >> can't get any 3.2 image to work at all. Suggestions and help are very >> much appreciated. > > It sounds like your boot loader is not loading the initramfs, or the > initramfs is somehow corrupted. Are you using LILO or GRUB? I'm currently using LILO. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b8bd64.2090...@acarver.net
Re: Kernel 3.2.0 panics
On Sat, 2014-07-05 at 13:41 -0700, AC wrote: > Hi all, > > I've been searching for about a month trying to fix the kernel panic on > boot for 3.2.0-4 with no luck so far. I get the well documented error: > > No filesystem could mount root: tried: > Kernel Panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > (plus stack dump) > > however none of the suggested fixes (the few that exist) work. My > system is a Pentium II and recently upgraded to wheezy. I've tried both > the 3.2.0-4-686pae and the 3.2.0-4-486 images with identical results, > they all end with the kernel panic above. > > I'm currently running kernel image 2.6.39 which is working fine, I just > can't get any 3.2 image to work at all. Suggestions and help are very > much appreciated. It sounds like your boot loader is not loading the initramfs, or the initramfs is somehow corrupted. Are you using LILO or GRUB? Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Kernel 3.2.0 panics
Hi all, I've been searching for about a month trying to fix the kernel panic on boot for 3.2.0-4 with no luck so far. I get the well documented error: No filesystem could mount root: tried: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) (plus stack dump) however none of the suggested fixes (the few that exist) work. My system is a Pentium II and recently upgraded to wheezy. I've tried both the 3.2.0-4-686pae and the 3.2.0-4-486 images with identical results, they all end with the kernel panic above. I'm currently running kernel image 2.6.39 which is working fine, I just can't get any 3.2 image to work at all. Suggestions and help are very much appreciated. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b86302.2050...@acarver.net
Re: Bug#753816: [systemd] Broken audio
Am 05.07.2014 18:38, schrieb Antonio Marcos López Alonso: > El 05/07/14 17:06, Michael Biebl escribió: >> Am 05.07.2014 17:56, schrieb Antonio Marcos López Alonso: >>> Just in case, have you noticed I'm using an ALSA-Jack loopback setting >>> for audio? >> Under sysvinit, udev (including udevadm settle) is started before the >> kmod init script, which loads snd_aloop. >> That means, snd_aloop is loaded after snd_hda_intel. >> >> Under systemd, it looks like the snd_aloop module is loaded about the >> same time systemd-udevd is started. There might be a race here and >> snd_aloop is loaded before snd_hda_intel. >> >> This *might* be the reason, but I'm no expert on this matter. >> >> Can you try removing snd_aloop from /etc/modules and test if that makes >> a difference. >> > > OK removed snd_aloop and audio is back. Then reloaded the module, > restarted JACK and audio is still fine. So as you said there must be > some race condition in there. Should I keep this ticket opened? > Hm, not sure what to do about this. We could order systemd-load-modules.service after systemd-udevd.service. But that doesn't guarantee the loading order of the modules and it feels like papering over the underlying issue. I'm no sound expert, but I'd say that the loading order should not matter. Maybe we need some input from the kernel team or some alsa experts here. I took the liberty to CC the Debian kernel team and the maintainer of the snd_aloop module. I hope they can help us here. For reference the complete bug report is at [1] Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753816 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#753814: update-initramfs produce warnings about missing modules dir, when kernel is built with no modules
Package: initramfs-tools Version: 0.115 hello! i'm using self-built monolith kernels with no modules support, built with kernel-package. on every install/update that triggers update-initramfs, the latter starts to complain about missing /lib/modules//* update-initramfs: Generating /boot/initrd.img-3.14.4-167.14+pf+r4 WARNING: missing /lib/modules/3.14.4-167.14+pf+r4 Device driver support needs thus be built-in linux image! depmod: ERROR: could not open directory /lib/modules/3.14.4-167.14+pf+r4: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_TKOtDa/lib/modules/3.14.4-167.14+pf+r4/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_TKOtDa/lib/modules/3.14.4-167.14+pf+r4/modules.builtin: No such file or directory it doesn't cause any failure, though, initrd's build fine, and update doesn't break, but it's a bit annoying and may confuse people (especially with those "fatal" and "error" messages). could you please add some behaviour not to trigger depmod if we don't see "CONFIG_MODULES=y" in /boot/config-? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140705160119.69163...@ulf.tvoe.tv
