public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org
Subject: Re: Linux 3.2.5
Date: Tue, 7 Feb 2012 12:23:45 +0100	[thread overview]
Message-ID: <20120207112345.GA14427@citd.de> (raw)
In-Reply-To: <20120207105835.GA12864@citd.de>

On 07.02.2012 11:58, Matthias Schniedermeyer wrote:
> On 07.02.2012 11:19, Clemens Ladisch wrote:
> > 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".
> 
> With 3.2.4 running:
> lspci -v -s 5:0
> 05:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 
> 10) (prog-if 00 [Normal decode])
>         Flags: bus master, fast devsel, latency 0
>         Bus: primary=05, secondary=06, subordinate=06, sec-latency=32
>         I/O behind bridge: 0000c000-0000cfff
>         Memory behind bridge: fbe00000-fbefffff
>         Capabilities: <access denied>

Ups. I did that with my user-account. Now with root:
lspci -v -s 5:0
05:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 10) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=05, secondary=06, subordinate=06, sec-latency=32
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: fbe00000-fbefffff
        Capabilities: [70] Express PCI/PCI-X Bridge, MSI 00
        Capabilities: [90] Power Management version 2
        Capabilities: [a0] Subsystem: Gammagraphx, Inc. (or missing ID) Device 0000
        Capabilities: [100] Device Serial Number 00-00-00-00-00-00-00-00





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.


  reply	other threads:[~2012-02-07 11:24 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
2012-02-07 10:58     ` Matthias Schniedermeyer
2012-02-07 11:23       ` Matthias Schniedermeyer [this message]
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=20120207112345.GA14427@citd.de \
    --to=ms@citd.de \
    --cc=akpm@linux-foundation.org \
    --cc=clemens@ladisch.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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