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 19:29:44 +0100 [thread overview]
Message-ID: <20120207182944.GA8595@citd.de> (raw)
In-Reply-To: <20120207145205.GA22034@citd.de>
On 07.02.2012 15:52, Matthias Schniedermeyer wrote:
> I guess this whole mess is Mainboard specifc.
> I have a another, very similar system but with an Asus P8H67-M PRO
> Mainbaord.
>
> I just remotly booted that machine into 3.2.5, so i can't verify if the
> sound works, but as the dmesg-output appears identical to the previous
> boot of 3.2.0 so i guess i will work.
>
> This is all i get for the system for aspm
> dmesg | grep -i aspm
> [ 0.777824] e1000e 0000:02:00.0: Disabling ASPM L0s
>
> So that mainboard has another BIOS/UEFI-Firmware and the
> PCIe-PCI-Bridge, the Soundblaster-Live is behind, is from another
> manufacture.
>
> lspci -v -s 5:0
> 05:00.0 PCI bridge: ASMedia Technology Inc. ASM108x PCIe to PCI Bridge Controller (rev 01) (prog-if 01 [Subtractive decode])
> Flags: bus master, fast devsel, latency 0
> Bus: primary=05, secondary=06, subordinate=06, sec-latency=32
> I/O behind bridge: 0000b000-0000bfff
> Capabilities: [c0] Subsystem: ASUSTeK Computer Inc. Device 8489
Now that i'm back home i could test this other machine.
Unpatched 3.2.5 works fine, i guess because of the different Bridge-Chip
and/or Firmware.
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.
next prev parent reply other threads:[~2012-02-07 18:30 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
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 [this message]
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=20120207182944.GA8595@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