On Tue, 18 Oct 2005, Keith Geffert wrote: > I don't want to take up space on the BTS for this question.
please _always_ share knownledge. busy atm so forwarding that other can take a look. > Do you have a referral bug # I can read? or a mailing list thread with the > solution? > > On another search of lists.Debian.org > DB# 329989 > Seems to fit this exact situation. Which at one point *was* a Linux-2.6 > bug but reassigned to gcc-4.0, which, according to BTS is now fixed in > 4.0.2-1. > > If this truly is a gcc issue, and it is fixed. These packages need to be > rebuilt for this to be fixed across the board. > > That bug is now closed but unless the packages have been rebuilt the bug > still exists for the packages that were built with gcc version < 4.0.2-1. > > Maximilian Attems wrote: > >On Tue, Oct 18, 2005 at 12:58:18PM -0400, Keith Geffert wrote: > > > >>Loading snd_usb_audio fails with unresolved symbols. I use a Logitech > >>USB Mic frequently and after the 2.6.12 upgrade hotplug now fails to > >>load the alsa device module. 2.6.10-x-686 does not exhibit this > >>behavior. > >> > >>Sample syslog excerpt: > >>Oct 17 20:16:48 localhost kernel: usb 2-2: new full speed USB device > >>using uhci_hcd and address 2 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.170 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.89 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.173 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.112 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.110 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.150 > >>Oct 17 20:16:54 localhost kernel: snd_usb_audio: Unknown symbol > >>__compound_literal.102 > > > > > >that's a known issue alsa has a newer abi and needs an `alsaconf` run. > >if not please give dmesg and lspci -v output. > > > >-- > >maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
