On Mon, Feb 11, 2013 at 4:08 PM, Yinghai Lu wrote:
> On Mon, Feb 11, 2013 at 2:41 PM, Bjorn Helgaas wrote:
>> [+cc linux-acpi, linux-pci]
>>
>> The _PRT describes motherboard interrupt wiring, which has nothing to
>> do with PCI bus numbers. Our current drivers/acpi/pci_irq.c caches
>> the PCI
On Mon, Feb 11, 2013 at 2:41 PM, Bjorn Helgaas wrote:
> [+cc linux-acpi, linux-pci]
>
> The _PRT describes motherboard interrupt wiring, which has nothing to
> do with PCI bus numbers. Our current drivers/acpi/pci_irq.c caches
> the PCI bus number along with the _PRT, and I think that's a
[+cc linux-acpi, linux-pci]
On Mon, Feb 11, 2013 at 01:06:27PM -0800, Yinghai Lu wrote:
> On Mon, Feb 11, 2013 at 11:57 AM, Yinghai Lu wrote:
> >>
> >> Bjorn, Rafael,
> >>
> >> acpi_pci_irq_add_prt need to be called after pci bridge get scanned,
> >> so we can not call it from pci_acpi_setup,
On Mon, Feb 11, 2013 at 11:57 AM, Yinghai Lu wrote:
>>
>> Bjorn, Rafael,
>>
>> acpi_pci_irq_add_prt need to be called after pci bridge get scanned,
>> so we can not call it from pci_acpi_setup, after we move dev_register
>> for pci_dev early.
>>
>> The attached debug patch move down that calling
On Mon, Feb 11, 2013 at 11:19 AM, Yinghai Lu wrote:
> On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley
> wrote:
>> On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
>>> On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
>>> > On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley
>>> > wrote:
>>> >>
On Mon, Feb 11, 2013 at 11:45 AM, Sedat Dilek wrote:
> On Mon, Feb 11, 2013 at 8:19 PM, Yinghai Lu wrote:
>> On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley
>> wrote:
>>> On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
> On Sun,
On Mon, Feb 11, 2013 at 8:19 PM, Yinghai Lu wrote:
> On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley
> wrote:
>> On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
>>> On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
>>> > On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley
>>> > wrote:
>>> >>
On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley wrote:
> On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
>> On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
>> > On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley
>> > wrote:
>> >> On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
>> >>>
On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
> On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
> > On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley
> > wrote:
> >> On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
> >>> On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
> >>> >
On 02/11/2013 07:40 AM, Yinghai Lu wrote:
> Can you try attached debug patch?
FWIW this fixes it for me. No more 'derived' or 'nobody' in dmesg.
thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 02/11/2013 07:40 AM, Yinghai Lu wrote:
Can you try attached debug patch?
FWIW this fixes it for me. No more 'derived' or 'nobody' in dmesg.
thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu ying...@kernel.org wrote:
On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley pe...@hurleysoftware.com
wrote:
On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
On Tue, 2013-02-05 at 15:26
On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley pe...@hurleysoftware.com wrote:
On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu ying...@kernel.org wrote:
On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley pe...@hurleysoftware.com
wrote:
On Sat,
On Mon, Feb 11, 2013 at 8:19 PM, Yinghai Lu ying...@kernel.org wrote:
On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley pe...@hurleysoftware.com
wrote:
On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu ying...@kernel.org wrote:
On Sun, Feb 10,
On Mon, Feb 11, 2013 at 11:45 AM, Sedat Dilek sedat.di...@gmail.com wrote:
On Mon, Feb 11, 2013 at 8:19 PM, Yinghai Lu ying...@kernel.org wrote:
On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley pe...@hurleysoftware.com
wrote:
On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
On Sun, Feb 10,
On Mon, Feb 11, 2013 at 11:19 AM, Yinghai Lu ying...@kernel.org wrote:
On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley pe...@hurleysoftware.com
wrote:
On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu ying...@kernel.org wrote:
On Sun, Feb 10,
On Mon, Feb 11, 2013 at 11:57 AM, Yinghai Lu ying...@kernel.org wrote:
Bjorn, Rafael,
acpi_pci_irq_add_prt need to be called after pci bridge get scanned,
so we can not call it from pci_acpi_setup, after we move dev_register
for pci_dev early.
The attached debug patch move down that
[+cc linux-acpi, linux-pci]
On Mon, Feb 11, 2013 at 01:06:27PM -0800, Yinghai Lu wrote:
On Mon, Feb 11, 2013 at 11:57 AM, Yinghai Lu ying...@kernel.org wrote:
Bjorn, Rafael,
acpi_pci_irq_add_prt need to be called after pci bridge get scanned,
so we can not call it from pci_acpi_setup,
On Mon, Feb 11, 2013 at 2:41 PM, Bjorn Helgaas bhelg...@google.com wrote:
[+cc linux-acpi, linux-pci]
The _PRT describes motherboard interrupt wiring, which has nothing to
do with PCI bus numbers. Our current drivers/acpi/pci_irq.c caches
the PCI bus number along with the _PRT, and I think
On Mon, Feb 11, 2013 at 4:08 PM, Yinghai Lu ying...@kernel.org wrote:
On Mon, Feb 11, 2013 at 2:41 PM, Bjorn Helgaas bhelg...@google.com wrote:
[+cc linux-acpi, linux-pci]
The _PRT describes motherboard interrupt wiring, which has nothing to
do with PCI bus numbers. Our current
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
> On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley
> wrote:
>> On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
>>> On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
>>> > On Tue, 5 Feb 2013, Peter Hurley wrote:
>>> >
>>> > > With
On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley wrote:
> On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
>> On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
>> > On Tue, 5 Feb 2013, Peter Hurley wrote:
>> >
>> > > With -next-20130204:
>> > >
>> > > [ 33.855570] irq 18: nobody cared
On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
> On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
> > On Tue, 5 Feb 2013, Peter Hurley wrote:
> >
> > > With -next-20130204:
> > >
> > > [ 33.855570] irq 18: nobody cared (try booting with the "irqpoll"
> > > option)
> > > [
On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
On Tue, 5 Feb 2013, Peter Hurley wrote:
With -next-20130204:
[ 33.855570] irq 18: nobody cared (try booting with the irqpoll
option)
[ 33.855580] Pid: 0, comm:
On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley pe...@hurleysoftware.com wrote:
On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
On Tue, 5 Feb 2013, Peter Hurley wrote:
With -next-20130204:
[ 33.855570] irq 18: nobody cared
On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu ying...@kernel.org wrote:
On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley pe...@hurleysoftware.com
wrote:
On Sat, 2013-02-09 at 22:14 -0500, Peter Hurley wrote:
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
On Tue, 5 Feb 2013, Peter Hurley
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
> On Tue, 5 Feb 2013, Peter Hurley wrote:
>
> > With -next-20130204:
> >
> > [ 33.855570] irq 18: nobody cared (try booting with the "irqpoll" option)
> > [ 33.855580] Pid: 0, comm: swapper/4 Not tainted 3.8.0-next-20130204-xeon
> >
On Tue, 2013-02-05 at 15:26 -0500, Alan Stern wrote:
On Tue, 5 Feb 2013, Peter Hurley wrote:
With -next-20130204:
[ 33.855570] irq 18: nobody cared (try booting with the irqpoll option)
[ 33.855580] Pid: 0, comm: swapper/4 Not tainted 3.8.0-next-20130204-xeon
#20130204
[
28 matches
Mail list logo
