public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Wyart <damien.wyart@free.fr>
To: Greg KH <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	James@superbug.demon.co.uk, Takashi Iwai <tiwai@suse.de>
Subject: Re: ALSA message with 2.6.19-rc4-mm2 (not -mm1)
Date: Thu, 02 Nov 2006 23:02:41 +0100	[thread overview]
Message-ID: <878xitpkvy.fsf@brouette.noos.fr> (raw)
In-Reply-To: <20061102192607.GA13635@kroah.com> (Greg KH's message of "Thu\, 2 Nov 2006 11\:26\:07 -0800")

Hello,

> > I notice these messages when 2.6.19-rc4-mm2 boots (also with
> > rc3-mm1) but 2.6.19-rc4-mm1 did NOT display them. Related to the
> > driver tree ?

* Greg KH <greg@kroah.com> [061102 20:26]:
> How many different sound cards do you have in your machine?

Only one, a Sound Blaster Live.

> Can you send me the output of 'ls /sys/class/sound/' with the
> 2.6.19-rc4 (or any other non-mm) kernel?

With 2.6.19-rc4-mm2, this gives:
admmidi  amidi  card0      dmmidi  hwC0D0  midi      midiC0D1  mixer    pcmC0D0p  pcmC0D2c  pcmC0D3p  sequencer   timer
adsp     audio  controlC0  dsp     hwC0D2  midiC0D0  midiC0D2  pcmC0D0c pcmC0D1c  pcmC0D2p  seq       sequencer2

While Vanilla 2.6.19-rc4 leads to:
admmidi  amidi  controlC0  dsp     hwC0D2  midiC0D0  midiC0D2  pcmC0D0c pcmC0D1c  pcmC0D2p  seq        sequencer2
adsp     audio  dmmidi     hwC0D0  midi    midiC0D1  mixer     pcmC0D0p pcmC0D2c  pcmC0D3p  sequencer  timer

Seems there is an additional 'card0' entry in the first case.


With Vanilla, the relevant part of the bootlog is:

Nov  2 22:49:03 brouette kernel: Advanced Linux Sound Architecture Driver Version 1.0.13 (Sun Oct 22 08:56:16 2006 UTC).
Nov  2 22:49:03 brouette kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 21 (level, low) -> IRQ 21
Nov  2 22:49:03 brouette kernel: ALSA device list:
Nov  2 22:49:03 brouette kernel:   #0: SB Live [Unknown] (rev.10, serial:0x80671102) at 0xdf20, irq 21

so exactly the same as in mm2, without the error messages.

As rc4-mm1 doesn't show the problem (and so gives the very same output
as plain rc4), I still wonder if this is an interaction with the driver
tree ?

-- 
Damien Wyart

  reply	other threads:[~2006-11-02 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 10:26 ALSA message with 2.6.19-rc4-mm2 (not -mm1) Damien Wyart
2006-11-02 18:27 ` Andrew Morton
2006-11-02 19:26 ` Greg KH
2006-11-02 22:02   ` Damien Wyart [this message]
2006-11-02 22:22     ` Greg KH
2006-11-03  6:53       ` Damien Wyart
2006-11-03  7:08         ` Greg KH
2006-11-03  9:38           ` Damien Wyart
2006-11-06 15:34       ` Takashi Iwai
2006-11-06 17:30         ` Damien Wyart

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=878xitpkvy.fsf@brouette.noos.fr \
    --to=damien.wyart@free.fr \
    --cc=James@superbug.demon.co.uk \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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