"Too many connections" error on boot caused by ALC892 soundchip

Bug #720799 reported by Richard
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 10.10 throws a "Too many connections" error on boot. I think there error is caused by the "ALC892" soundchip. When I disable the sound option in the bios no error occurred. The board is a Gigabyte GA-870A-UD3.

Here is the relevant part from the syslog:

[...]
Feb 17 16:54:46 ***-PC kernel: [ 11.957934] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 17 16:54:46 ***-PC kernel: [ 11.962042] lp0: using parport0 (interrupt-driven).
Feb 17 16:54:46 ***-PC kernel: [ 12.055202] hda_codec: ALC892: BIOS auto-probing.
Feb 17 16:54:46 ***-PC kernel: [ 12.061425] Too many connections
Feb 17 16:54:46 ***-PC kernel: [ 12.062721] HDA Intel 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Feb 17 16:54:46 ***-PC kernel: [ 12.062774] alloc irq_desc for 50 on node 0
Feb 17 16:54:46 ***-PC kernel: [ 12.062776] alloc kstat_irqs on node 0
[...]

Revision history for this message
Richard (richardeb) wrote :
Revision history for this message
Richard (richardeb) wrote :
Revision history for this message
Richard (richardeb) wrote :
Revision history for this message
Richard (richardeb) wrote :
tags: added: kernel-sound
tags: added: kj-triage
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

I am wondering if this is related / the cause of Bug #722294.

summary: - "Too many connections" error on boot caused by Soundchip
+ "Too many connections" error on boot caused by ALC982 soundchip
summary: - "Too many connections" error on boot caused by ALC982 soundchip
+ "Too many connections" error on boot caused by ALC892 soundchip
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

There is mention of this problem here:
http://marc.info/?l=linux-kernel&m=129072236030208&w=2

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Using today's mainline kernel (2.6.38-999-generic #201103011141) I don' t see this message anymore, however this doesn' t help with my original sound issue (Bug #722294).

Revision history for this message
tazzik (flyingsouth) wrote :

I have an Asus P8P67 Pro motherboard with this sounds chip.

I was getting the error "Too Many Connections" on boot, I read that if you made the audio AC97 and not HD then it would solve the problem. It did - though I got some crackling on audio.

I then (for some unknown reason) disabled audio completely and booted up - obviously with no sound. I rebooted and enabled HD audio and now no sound works at all HD or AC97. Nothing at all :(

Please fix it!

Revision history for this message
Kimiko Koopman (kimiko) wrote :

More discussion of this problem ("Too many connections" error, and no sound output on Realtek ALC892) is here:
http://ubuntuforums.org/showthread.php?t=1635278

Here
http://www.linuxforums.org/forum/gaming-multimedia-entertainment/168732-solved-no-sound-alsa-except-microphone.html
someone seems to have solved the problem by building new sound modules from source provided by Realtek:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false
When I tried to follow that however, I ended up with sound modules that wouldn't load because of "unknown symbol"s.

Could someone more tech-savvy alert the kernel/alsa folks upstream to this problem?

Revision history for this message
Kimiko Koopman (kimiko) wrote :

This bug seems to be the same as #692029.
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/692029

I'm not sure which of the two reports should be marked as a duplicate of the other though.

Revision history for this message
Christopher (cwkeller) wrote :

Same scenario: ASUS P8H67-M Pro w/i3-2105: "ALC892: BIOS auto-probing. Too many connections", if HD disabled in BIOS no error but no sound either.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.