From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio
Date: Thu, 25 Sep 2014 14:04:31 -0400 [thread overview]
Message-ID: <5424592F.5070801@canonical.com> (raw)
In-Reply-To: <CAErSpo7unezE4hRYDUsHbmAV+dxgaMFqBOU=svpUEFKieG=omA@mail.gmail.com>
On 09/25/2014 12:04 PM, Bjorn Helgaas wrote:
> On Thu, Sep 25, 2014 at 9:49 AM, Joseph Salisbury
> <joseph.salisbury@canonical.com> wrote:
>> On 09/16/2014 06:27 PM, Yinghai Lu wrote:
>>> On Tue, Sep 16, 2014 at 1:21 PM, Joseph Salisbury
>>> <joseph.salisbury@canonical.com> wrote:
>>>> A new bug[0] was opened due to enabling PCI_REALLOC_ENABLE_AUTO, which
>>>> is similar to the original bug[1] we discussed.
>>>>
>>>> Just wondering if there have been any additional ideas on realloc since
>>>> this was last discussed?
>>>>
>>>> [0] http://pad.lv/1363313
>>>> [1] http://pad.lv/1245938
> As a side-note, this looks like a regression and I should have given
> it more attention, but I don't track all the vendor bug databases. If
> you open a kernel.bug bugzilla and mark it as a regression, I *do*
> track that regularly. For regressions, it's helpful if you can attach
> dmesg logs from working and non-working kernels that are as close
> together as possible. It'd be ideal if those were upstream kernels,
> but I doubt you apply any patches that would be relevant, so I think
> logs from Ubuntu kernels would be enough.
>
> Bjorn
Thanks, Bjorn. I'll open a bugzilla bug and ask the bug reporters for
the requested dmesg data. Thanks again for the feedback.
Joe
next prev parent reply other threads:[~2014-09-25 18:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:54 [PATCH 0/2] PCI: Don't enable realloc automatically when above 4g 64bit mmio is not supported Yinghai Lu
2013-12-08 23:54 ` [PATCH 1/2] PCI: pcibus address to resource converting take bus instead of dev Yinghai Lu
2013-12-09 17:52 ` Bjorn Helgaas
2013-12-09 19:21 ` Yinghai Lu
2013-12-09 20:03 ` Yinghai Lu
2013-12-09 20:43 ` Greg KH
2013-12-09 20:47 ` Yinghai Lu
2013-12-09 21:06 ` Bjorn Helgaas
2013-12-08 23:54 ` [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio Yinghai Lu
2013-12-09 17:54 ` Bjorn Helgaas
2013-12-09 19:20 ` Yinghai Lu
2013-12-09 19:42 ` Bjorn Helgaas
2013-12-09 20:10 ` Yinghai Lu
2013-12-09 20:20 ` Bjorn Helgaas
2013-12-09 20:44 ` Yinghai Lu
2013-12-09 21:05 ` Bjorn Helgaas
2013-12-11 19:19 ` Joseph Salisbury
2013-12-11 19:55 ` Yinghai Lu
2014-01-08 16:38 ` Joseph Salisbury
2014-01-10 16:19 ` Joseph Salisbury
2014-01-10 17:13 ` Yinghai Lu
2014-01-10 21:54 ` Joseph Salisbury
2014-01-10 23:12 ` Yinghai Lu
2014-09-16 20:21 ` Joseph Salisbury
2014-09-16 22:27 ` Yinghai Lu
2014-09-17 7:46 ` Yinghai Lu
2014-09-24 23:48 ` Bjorn Helgaas
2014-09-25 18:19 ` Joseph Salisbury
2014-09-25 18:24 ` Yinghai Lu
2014-09-25 15:49 ` Joseph Salisbury
2014-09-25 16:04 ` Bjorn Helgaas
2014-09-25 18:04 ` Joseph Salisbury [this message]
2014-09-25 18:23 ` Yinghai Lu
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=5424592F.5070801@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@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.