lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo4-d2AQLacin7vSr8rXrp-tytzXjJ1+Xfqx7C5fP6iWog@mail.gmail.com>
Date:	Tue, 4 Oct 2011 09:03:40 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Paul Menzel <paulepanter@...rs.sourceforge.net>
Cc:	x86@...nel.org, linux-pci@...r.kernel.org, stable@...nel.org,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH v2] x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE

On Tue, Oct 4, 2011 at 8:37 AM, Paul Menzel
<paulepanter@...rs.sourceforge.net> wrote:
>
> Am Dienstag, den 27.09.2011, 08:09 -0600 schrieb Bjorn Helgaas:
> > On Tue, Sep 27, 2011 at 3:39 AM, Paul Menzel wrote:
> > > Am Dienstag, den 20.09.2011, 10:39 -0600 schrieb Bjorn Helgaas:
> > >> On Tue, Sep 20, 2011 at 4:20 AM, Paul Menzel wrote:
> > >> > ...
> > >> >
> > >> > Using coreboot [1] with this board the problem does not exist but this quirk also does not affect it either. To be safe though the check is tightened to only take effect when the BIOS from American Megatrends is used.
> > >> >
> > >> >        15:13 < ruik> but coreboot does not need that
> > >> >        15:13 < ruik> because i have there only one root bus
> > >> >        15:13 < ruik> the audio is behind a bridge
> > >>
> > >> I'd like to know more about this coreboot situation.  Would it be
> > >> possible to get a dmesg log from the system with coreboot?  I'd like
> > >> to see how coreboot configures this device differently.
> > >
> > > I had attached that to the Bugzilla report #30552 [2], but this is down
> > > at the moment. I saw that you got the output from someone on #coreboot
> > > though.
> > >
> > >> > CC: stable@...nel.org (≥ 2.6.34)
> > >> > CC: Bjorn Helgaas <bhelgaas@...gle.com>
> > >> > CC: Thomas Gleixner <tglx@...utronix.de>
> > >> > CC: Ingo Molnar <mingo@...hat.com>
> > >> > CC: H. Peter Anvin <hpa@...or.com>
> > >> > CC: x86@...nel.org
> > >> > CC: Jesse Barnes <jbarnes@...tuousgeek.org>
> > >> > Signed-off-by: Paul Menzel <paulepanter@...rs.sourceforge.net>
> > >>
> > >> Signed-off-by: Bjorn Helgaas <bhelgaas@...gle.com>
> > >>
> > >> This is fine with me.  I don't think it's the final solution, but I
> > >> think it's worth doing for now.
> > >
> > > Thank you. I could not see this in Linus’ tree [3] yet. Jesse, could you
> > > pick that up as you have done for the other commit? (Where is your
> > > (temporary) tree located?)
> >
> > Jesse's on vacation right now.
>
> It looks like Jesse is back from vacation. Jesse, I hope you could enjoy
> it and I am sorry for bothering you right after you have been back.
>
> Is it possible to get this patch in for Linux 3.1?

I mentioned this one to Jesse yesterday, but I'm sure he's busy
catching up after being out.  I agree it'd be nice get it in for 3.1.

But it's awfully late in the cycle (my fault), it's been broken since
2.6.34 (3e3da00c), and there's an easy workaround ("pci=use_crs"), so
it's not a disaster if it goes in 3.2.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ