From: Linus Torvalds <torvalds@linux-foundation.org>
To: bugzilla-daemon@bugzilla.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug 41622] [REGRESSION][BISECTED] Notebook crashes upon detecting the PCI subsystem with kernels >= 2.6.24-rc7
Date: Fri, 22 Jun 2012 11:20:57 -0700 [thread overview]
Message-ID: <CA+55aFxKDZaCq-GP2LJpLnDKc=Zd1pmnr8Rq7bBXH9eGuyiyew@mail.gmail.com> (raw)
In-Reply-To: <20120622121523.4DF5911F873@bugzilla.kernel.org>
On Fri, Jun 22, 2012 at 5:15 AM, <bugzilla-daemon@bugzilla.kernel.org> wrote:
>
> If, on the other hand, I apply the patch mentioned in comment #17 of this bug
> report, then everything boots and works OK (for suitable values of "OK).
Gaah. These emails always happen at the most inconvenient time.
Maybe we should just try that patch in
https://bugzilla.kernel.org/show_bug.cgi?id=41622#c17
but it really needs to happen early in a merge window. We didn't do
that for 3.2, maybe we can do it for 3.6?
Bjorn, what do you think? Sizing up transparent bridges really is a
bit unnecessary.
Although I really don't see what the difference there is any more.
Yinghai noticed that the prefetchability of the cardbus bridge
changed, but the commit that changed that apparently made no
difference. What other changes does the transparent bridge sizing
cause?
Linus
next parent reply other threads:[~2012-06-22 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41622-5873@https.bugzilla.kernel.org/>
[not found] ` <20120622121523.4DF5911F873@bugzilla.kernel.org>
2012-06-22 18:20 ` Linus Torvalds [this message]
2012-06-22 19:52 ` [Bug 41622] [REGRESSION][BISECTED] Notebook crashes upon detecting the PCI subsystem with kernels >= 2.6.24-rc7 Bjorn Helgaas
2011-08-19 17:53 Rogério Brito
2011-08-19 18:49 ` Rogério Brito
2011-08-24 17:47 ` [Bug 41622] " Linus Torvalds
2011-08-24 19:30 ` Rogério Brito
2011-08-24 20:51 ` Rogério Brito
2011-08-24 21:23 ` Bjorn Helgaas
2011-08-25 14:49 ` Rogério Brito
2011-08-25 16:53 ` Bjorn Helgaas
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='CA+55aFxKDZaCq-GP2LJpLnDKc=Zd1pmnr8Rq7bBXH9eGuyiyew@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.