Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: Matt Wu <Matt_Wu@acersoftech.com.cn>,
	alsa-devel@lists.sourceforge.net, olivier.ricordeau@wanadoo.fr
Subject: [BUG] buggy ali5451 driver
Date: Mon, 04 Nov 2002 12:47:52 +0100	[thread overview]
Message-ID: <m24raxpndj.fsf@vador.mandrakesoft.com> (raw)

regarding ali5451 problems that show up on kml, i just had access to
oliver's laptop which has the infamous ali5451.

both oss' trident and alsa's snd-ali5451 cannot 

# modprobe snd-ali5451
PCI: Found IRQ 4 for device 00:08:0
URQ routing conflict for 00:08:0, have irq 5, want irq 4

then kernel cries:
hda: status timeout: status=0x80 { Busy }
hda: DMA disabled
hda: drive not ready for command.

disks cannot anymore be accessed. the system is still fine (no oops,
no freeze).
the vfs & ext3 then ended in I/O error since the disks answered
themselves busy to the eide controller.


the bugs ali5451 chips suffer may be related to :

- either the poor ressources allocation on laptios, which is poorer &
  poorer since acpi "invade" laptops

- or driver misconception regarding irq sharing


the cars is "M5451 PCI South Bridge Audio" manufactured by Acer
Laboratories Inc. [ALi] (with pci ids : 0x10b9 0x5451)


irq 5 has been allocated to ali snd card, pcmcia cardbus controller
(managed by yenta_socket).


olivier <olivier.ricordeau@wanadoo.fr> is the owner of that fscking
chip.

this is a compaq laptop.

i have access to another compaq laptop that works well with oss
trident.  this is a compaq laptop too.



kernel is 2.4.18 based and alsa was tested with 0.9.0rc3 & rc5



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com

             reply	other threads:[~2002-11-04 11:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 11:47 Thierry Vignaud [this message]
2002-11-04 13:37 ` [BUG] buggy ali5451 driver Olivier Ricordeau
2002-11-04 14:12 ` Takashi Iwai
2002-11-04 14:25   ` Olivier Ricordeau
2002-11-04 14:45     ` Olivier Ricordeau
2002-11-04 11:20       ` drclaw
2002-11-04 15:20         ` Olivier Ricordeau
2002-11-04 11:49           ` drclaw
2002-11-04 15:53           ` Olivier Ricordeau
2002-11-04 12:28             ` drclaw
2002-11-04 16:31               ` Olivier Ricordeau
2002-11-05  8:36                 ` Thierry Vignaud
2002-11-06  7:41                   ` Olivier Ricordeau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m24raxpndj.fsf@vador.mandrakesoft.com \
    --to=tvignaud@mandrakesoft.com \
    --cc=Matt_Wu@acersoftech.com.cn \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=olivier.ricordeau@wanadoo.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox