public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net
Subject: Re: Linux 3.2.5
Date: Tue, 07 Feb 2012 11:19:43 +0100	[thread overview]
Message-ID: <4F30FABF.4060409@ladisch.de> (raw)
In-Reply-To: <20120207084037.GA6140@citd.de>

Matthias Schniedermeyer wrote:
> On 06.02.2012 10:16, Greg KH wrote:
>> I'm announcing the release of the 3.2.5 kernel.
>>
>> It contains one PCI patch, it is up to you to decide to upgrade or not.
>
> This one makes my Soundblaster Live (alsa/emu10k1) silent.
> It is detected, i can e.g. change the mixer, but i can't hear any sound.

Back in the PCI days, the Emu10k1 chip was known to be quite inefficient
(many small transfers, and IIRC even latency timer bugs) and to be
problematic when used with other high-bandwidth PCI chips like TV capture
cards.

> There is a difference in syslog output regarding aspm, the emu10k1 line
> is the same.

Your PCIe/PCI bridge (5:0.0, iTE IT8892) which handles the PCI bus is
affected by the change.

I do not know if this is an actual hardware bug, or if the bridge is
just too slow to wake up the PCIe link.

Please show the output of "lspci -v -s 5:0".

> pci 0000:05:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'

Does this mean that the new kernel _dis_ables ASPM, where it left it
enabled previously?

Please try that kernel parameter.


Regards,
Clemens

  reply	other threads:[~2012-02-07 10:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 18:16 Linux 3.2.5 Greg KH
2012-02-06 18:16 ` Greg KH
2012-02-07  8:40 ` Matthias Schniedermeyer
2012-02-07 10:19   ` Clemens Ladisch [this message]
2012-02-07 10:58     ` Matthias Schniedermeyer
2012-02-07 11:23       ` Matthias Schniedermeyer
2012-02-07 11:40       ` Clemens Ladisch
2012-02-07 11:48         ` Matthias Schniedermeyer
2012-02-07 12:28           ` Clemens Ladisch
2012-02-07 14:52             ` Matthias Schniedermeyer
2012-02-07 18:29               ` Matthias Schniedermeyer
2012-02-07 16:29             ` Linus Torvalds
2012-02-07 16:40               ` Matthew Garrett
2012-02-07 16:54               ` Matthias Schniedermeyer
2012-02-07 16:59                 ` Matthew Garrett
2012-02-07 17:07                   ` Matthias Schniedermeyer
2012-02-07 17:18                     ` Matthew Garrett
2012-02-28  0:13                   ` Greg KH
2012-02-28  0:19                     ` Matthew Garrett

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=4F30FABF.4060409@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=ms@citd.de \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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