The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alex Riesen <fork0@users.sourceforge.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: akpm@digeo.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.2-rc1-mm2: alsa-101.patch (+lspci)
Date: Sat, 24 Jan 2004 01:08:33 +0100	[thread overview]
Message-ID: <20040124000833.GA1280@steel.home> (raw)

(forgot lspci, resend)

The patch disables sound for me. The programs play sound normally,
without any errors, there is just nothing out of the boxes.
Everything, I could think of, is unmuted.
Reverting the patch brings sound back.

I applied _not_ all of the -mm patches, so probably there is something
very important but not containing alsa anywhere in patch name.

It is an SMP (ht) machine.

Drivers:
snd_intel8x0           29476  0 
snd_ac97_codec         51204  1 snd_intel8x0
snd_pcm                88608  2 snd_pcm_oss,snd_intel8x0
snd_timer              22916  1 snd_pcm
snd_page_alloc          9220  2 snd_intel8x0,snd_pcm
snd_mpu401_uart         6656  1 snd_intel8x0
snd_rawmidi            21024  1 snd_mpu401_uart
snd_seq_device          7048  1 snd_rawmidi
snd                    45028  9 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               7776  1 snd

gcc (GCC) 3.3.2 20031022 (Gentoo Linux 3.3.2-r2, propolice)

alsa-lib is 1.0.1.

Applied patches (in order):
pci-probing-typo.patch
acpi.patch
acpi-20031203-fix.patch
acpi-frees-irq0.patch
sched-find_busiest_node-resolution-fix.patch
sched-domains.patch
sched-clock-fixes.patch
sched-build-fix.patch
sched-sibling-map-to-cpumask.patch
p4-clockmod-sibling-map-fix.patch
p4-clockmod-more-than-two-siblings.patch
sched-domains-i386-ht.patch
sched-domain-tweak.patch
sched-no-drop-balance.patch
sched-arch_init_sched_domains-fix.patch
sched-find_busiest_group-clarification.patch
sched-remove-noisy-printks.patch
show_task-free-stack-fix.patch
oops-dump-preceding-code.patch
alsa-101.patch

Alsa was applied last, and kernel was tested to work (with sound)
before applying alsa-101.

The only message in log: "kernel: intel8x0: clocking to 48000"
(in both kernels, working and not).

strace didn't any errors on the silent kernel.


The car is an onboard audio controller of Gigabyte GA9IPE1000 Pro:

00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02)
	Subsystem: Giga-byte Technology: Unknown device a002
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 0: I/O ports at d800 [size=256]
	Region 1: I/O ports at dc00 [size=64]
	Region 2: Memory at f2201000 (32-bit, non-prefetchable) [size=512]
	Region 3: Memory at f2202000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-


                 reply	other threads:[~2004-01-24  0:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040124000833.GA1280@steel.home \
    --to=fork0@users.sourceforge.net \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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