[+cc lists, etc.; sorry, this has been merged already, but I forgot to
cc: everybody the first time]
On Wed, Feb 4, 2015 at 1:18 PM, Bjorn Helgaas wrote:
> Hi Linus,
>
> These are a regression fix for read-only BARs, a DesignWare fix that keeps
> drivers from using MSI-X (which isn't supported),
On Fri, Jan 30, 2015 at 3:49 PM, Yinghai Lu wrote:
> On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas wrote:
>> On Tue, Jan 27, 2015 at 6:54 PM, Yinghai Lu wrote:
>>> On Tue, Jan 27, 2015 at 3:24 PM, Tony Luck wrote:
On Mon, Jan 26, 2015 at 7:43 PM, Yinghai Lu wrote:
> Can you please ge
On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas wrote:
> On Tue, Jan 27, 2015 at 6:54 PM, Yinghai Lu wrote:
>> On Tue, Jan 27, 2015 at 3:24 PM, Tony Luck wrote:
>>> On Mon, Jan 26, 2015 at 7:43 PM, Yinghai Lu wrote:
Can you please get boot bog with "debug ignore_logleve"?
we shoul
On Fri, Jan 30, 2015 at 12:01 PM, Tony Luck wrote:
> On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas wrote:
>> Tony, does the system work as it did before? Is the only problem that
>> now we have more warnings than we did before?
>
> Yup - things seem to be working. Just have a bunch of new conso
On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas wrote:
> Tony, does the system work as it did before? Is the only problem that
> now we have more warnings than we did before?
Yup - things seem to be working. Just have a bunch of new console messages.
It seems that at least some of them are valid
On Tue, Jan 27, 2015 at 6:54 PM, Yinghai Lu wrote:
> On Tue, Jan 27, 2015 at 3:24 PM, Tony Luck wrote:
>> On Mon, Jan 26, 2015 at 7:43 PM, Yinghai Lu wrote:
>>> Can you please get boot bog with "debug ignore_logleve"?
>>>
>>> we should get print out from
>>>
>>> + dev_printk(KERN_D
On Tue, Jan 27, 2015 at 3:24 PM, Tony Luck wrote:
> On Mon, Jan 26, 2015 at 7:43 PM, Yinghai Lu wrote:
>> Can you please get boot bog with "debug ignore_logleve"?
>>
>> we should get print out from
>>
>> + dev_printk(KERN_DEBUG, &dev->dev, "%pR clipped to %pR\n",
>> +
On Tue, Jan 27, 2015 at 6:03 AM, Bjorn Helgaas wrote:
> Just to make sure we're planning the same thing, I expect that we will
> fix or workaround both issues so it works just as well as v3.18 by the
> time v3.19 is released. This is a system in the field, and we should
> be able to figure out ho
On Mon, Jan 26, 2015 at 7:43 PM, Yinghai Lu wrote:
> Can you please get boot bog with "debug ignore_logleve"?
>
> we should get print out from
>
> + dev_printk(KERN_DEBUG, &dev->dev, "%pR clipped to %pR\n",
> +&orig_res, res);
Attached ... but I don't
On Mon, Jan 26, 2015 at 9:55 PM, Yinghai Lu wrote:
> On Mon, Jan 26, 2015 at 3:53 PM, Bjorn Helgaas wrote:
>> On Mon, Jan 26, 2015 at 01:24:51PM -0800, Tony Luck wrote:
>>> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas wrote:
>>> > Sorry for the inconvenience. Can you collect a complete dmesg
On Mon, Jan 26, 2015 at 3:53 PM, Bjorn Helgaas wrote:
> On Mon, Jan 26, 2015 at 01:24:51PM -0800, Tony Luck wrote:
>> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas wrote:
>> > Sorry for the inconvenience. Can you collect a complete dmesg log and
>> > "lspci -vv" output, too (from the kernel wit
On Mon, Jan 26, 2015 at 1:24 PM, Tony Luck wrote:
> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas wrote:
>> Sorry for the inconvenience. Can you collect a complete dmesg log and
>> "lspci -vv" output, too (from the kernel with the reverted commit)?
>> That will have more useful information than
On Mon, Jan 26, 2015 at 01:24:51PM -0800, Tony Luck wrote:
> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas wrote:
> > Sorry for the inconvenience. Can you collect a complete dmesg log and
> > "lspci -vv" output, too (from the kernel with the reverted commit)?
> > That will have more useful infor
On Mon, Jan 26, 2015 at 1:58 PM, Tony Luck wrote:
> I'm seeing these new messages in v3.19-rc6 on ia64:
Hi Tony,
Sorry for the inconvenience. Can you collect a complete dmesg log and
"lspci -vv" output, too (from the kernel with the reverted commit)?
That will have more useful information than
I'm seeing these new messages in v3.19-rc6 on ia64:
pci :01:00.0: can't claim BAR 6 [mem 0xfffe-0x pref]:
no compatible bridge window
pci :01:00.1: can't claim BAR 6 [mem 0xfffe-0x pref]:
no compatible bridge window
pci :03:00.0: can't claim BAR 6 [mem 0xffe
Hi Linus,
These are fixes for:
- A resource management problem that causes a Radeon "Fatal error during
GPU init" on machines where the BIOS programmed an invalid Root Port
window. This was a regression in v3.16.
- An Atheros AR93xx device that doesn't handle PCI bus resets correctl
16 matches
Mail list logo
