diff for duplicates of <1491441105.50673.2.camel@intel.com> diff --git a/a/1.txt b/N1/1.txt index 3aad0af..1de9f70 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,19 +1,21 @@ On Wed, 2017-04-05 at 13:37 -0500, Bjorn Helgaas wrote: > [+cc Michal, Ley Foon] -> +>=20 > On Tue, Apr 04, 2017 at 04:00:49PM -0700, Wesley Terpstra wrote: -> > +> >=20 > > Thank you very much for your detailed analysis of the log! -> > +> >=20 > > On Tue, Apr 4, 2017 at 1:56 PM, Bjorn Helgaas <helgaas@kernel.org> > > wrote: -> > > -> > > > +> > >=20 +> > > >=20 > > > > In particular, these are the lines that seem wrong to me: -> > > > [ 5.920000] pci 0000:00:00.0: bridge configuration invalid +> > > > [=C2=A0=C2=A0=C2=A0=C2=A05.920000] pci 0000:00:00.0: bridge configu= +ration invalid > > > > ([bus > > > > 00-00]), reconfiguring -> > > > [ 5.930000] pci 0000:01:00.0: bridge configuration invalid +> > > > [=C2=A0=C2=A0=C2=A0=C2=A05.930000] pci 0000:01:00.0: bridge configu= +ration invalid > > > > ([bus > > > > 00-00]), reconfiguring > > > This is normal but possibly worded more alarmingly than @@ -28,96 +30,122 @@ On Wed, 2017-04-05 at 13:37 -0500, Bjorn Helgaas wrote: > > bus > > number already. Right? > Yes. -> -> > -> > > -> > > > -> > > > [ 6.000000] pci 0000:04:00.0: [Firmware Bug]: reg 0x10: +>=20 +> >=20 +> > >=20 +> > > >=20 +> > > > [=C2=A0=C2=A0=C2=A0=C2=A06.000000] pci 0000:04:00.0: [Firmware Bug]= +: reg 0x10: > > > > invalid BAR > > > > (can't size) -> > > > [ 6.010000] pci 0000:06:00.0: [Firmware Bug]: reg 0x10: +> > > > [=C2=A0=C2=A0=C2=A0=C2=A06.010000] pci 0000:06:00.0: [Firmware Bug]= +: reg 0x10: > > > > invalid BAR > > > > (can't size) -> > > These are more worrisome. We discover the size of a BAR by +> > > These are more worrisome.=C2=A0=C2=A0We discover the size of a BAR by > > > writing > > > all ones to it and reading it back, which tells us how many bits > > > of -> > > the BAR are hard-wired to zero. This behavior is prescribed by +> > > the BAR are hard-wired to zero.=C2=A0=C2=A0This behavior is prescribe= +d by > > > the > > > PCI specs, so it's likely a hardware defect. > > So, you would say it's a hardware problem of the PCIe cards in > > question and I can safely ignore it? > Yes. -> -> > -> > > +>=20 +> >=20 +> > >=20 > > > This is because the xilinx host bridge doesn't support I/O space > > Yeah. I knew this, but thanks for confirming. -> > +> >=20 > > FYI, there is a bug in the pcie-xilinx bridge wrt legacy > > interrupts. > > I've seen several people discussing the same problem for the altera > > bridge and the "NW" xilinx bridge, but somehow this bridge still > > has > > the issue. I've attached a patch that solved the problem for me. -> This sounds familiar to me, too. Copying Michal & Ley Foon in case +> This sounds familiar to me, too.=C2=A0=C2=A0Copying Michal & Ley Foon in = +case > they > know something about it. We have fixed this in last year. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm it/drivers/pci/host/pcie- -altera.c?id=99496bd2971fc378226ad4413e5b72c4545714bd +altera.c?id=3D99496bd2971fc378226ad4413e5b72c4545714bd -> -> > +>=20 +> >=20 > > Without it I see: -> > -> > [ 6.230000] ------------[ cut here ]------------ -> > [ 6.230000] WARNING: CPU: 0 PID: 1 at +> >=20 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.230000] ------------[ cut here ]------------ +> > [=C2=A0=C2=A0=C2=A0=C2=A06.230000] WARNING: CPU: 0 PID: 1 at > > /scratch/terpstra/freedom-u-sdk/linux/kernel/irq/irqdomain.c:365 > > irq_domain_associate+0x190/0x200 -> > [ 6.240000] error: hwirq 0x4 is too large for dummy -> > [ 6.250000] CPU: 0 PID: 1 Comm: swapper Not tainted +> > [=C2=A0=C2=A0=C2=A0=C2=A06.240000] error: hwirq 0x4 is too large for du= +mmy +> > [=C2=A0=C2=A0=C2=A0=C2=A06.250000] CPU: 0 PID: 1 Comm: swapper Not tain= +ted > > 4.11.0-rc1-661305-g4f97179 #12 -> > [ 6.250000] Call Trace: -> > [ 6.260000] [<ffffffff80288660>] walk_stackframe+0x0/0x104 -> > [ 6.260000] [<ffffffff80288800>] show_stack+0x38/0x50 -> > [ 6.270000] [<ffffffff803c6e30>] dump_stack+0x2c/0x40 -> > [ 6.270000] [<ffffffff8028c600>] __warn+0x118/0x130 -> > [ 6.280000] [<ffffffff8028c658>] warn_slowpath_fmt+0x40/0x54 -> > [ 6.280000] [<ffffffff802c02a8>] +> > [=C2=A0=C2=A0=C2=A0=C2=A06.250000] Call Trace: +> > [=C2=A0=C2=A0=C2=A0=C2=A06.260000] [<ffffffff80288660>] walk_stackframe= ++0x0/0x104 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.260000] [<ffffffff80288800>] show_stack+0x38= +/0x50 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.270000] [<ffffffff803c6e30>] dump_stack+0x2c= +/0x40 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.270000] [<ffffffff8028c600>] __warn+0x118/0x= +130 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.280000] [<ffffffff8028c658>] warn_slowpath_f= +mt+0x40/0x54 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.280000] [<ffffffff802c02a8>] > > irq_domain_associate+0x18c/0x200 -> > [ 6.290000] [<ffffffff802c0a3c>] irq_create_mapping+0x90/0xe4 -> > [ 6.300000] [<ffffffff802c0be4>] +> > [=C2=A0=C2=A0=C2=A0=C2=A06.290000] [<ffffffff802c0a3c>] irq_create_mapp= +ing+0x90/0xe4 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.300000] [<ffffffff802c0be4>] > > irq_create_fwspec_mapping+0x154/0x288 -> > [ 6.300000] [<ffffffff802c0d7c>] irq_create_of_mapping+0x64/0x84 -> > [ 6.310000] [<ffffffff804f9cb8>] +> > [=C2=A0=C2=A0=C2=A0=C2=A06.300000] [<ffffffff802c0d7c>] irq_create_of_m= +apping+0x64/0x84 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.310000] [<ffffffff804f9cb8>] > > of_irq_parse_and_map_pci+0x38/0x50 -> > [ 6.310000] [<ffffffff80407e00>] pci_fixup_irqs+0x6c/0x114 -> > [ 6.320000] [<ffffffff80408e64>] xilinx_pcie_probe+0x308/0x3f0 -> > [ 6.330000] [<ffffffff8042cba4>] platform_drv_probe+0x3c/0x88 -> > [ 6.330000] [<ffffffff8042aec0>] really_probe+0xbc/0x260 -> > [ 6.340000] [<ffffffff8042b138>] __driver_attach+0xd4/0xdc -> > [ 6.340000] [<ffffffff80429200>] bus_for_each_dev+0x68/0xb8 -> > [ 6.350000] [<ffffffff8042b640>] driver_attach+0x24/0x38 -> > [ 6.350000] [<ffffffff80429db8>] bus_add_driver+0x1b4/0x22c -> > [ 6.360000] [<ffffffff8042bdc0>] driver_register+0x68/0x12c -> > [ 6.360000] [<ffffffff8042da78>] +> > [=C2=A0=C2=A0=C2=A0=C2=A06.310000] [<ffffffff80407e00>] pci_fixup_irqs+= +0x6c/0x114 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.320000] [<ffffffff80408e64>] xilinx_pcie_pro= +be+0x308/0x3f0 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.330000] [<ffffffff8042cba4>] platform_drv_pr= +obe+0x3c/0x88 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.330000] [<ffffffff8042aec0>] really_probe+0x= +bc/0x260 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.340000] [<ffffffff8042b138>] __driver_attach= ++0xd4/0xdc +> > [=C2=A0=C2=A0=C2=A0=C2=A06.340000] [<ffffffff80429200>] bus_for_each_de= +v+0x68/0xb8 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.350000] [<ffffffff8042b640>] driver_attach+0= +x24/0x38 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.350000] [<ffffffff80429db8>] bus_add_driver+= +0x1b4/0x22c +> > [=C2=A0=C2=A0=C2=A0=C2=A06.360000] [<ffffffff8042bdc0>] driver_register= ++0x68/0x12c +> > [=C2=A0=C2=A0=C2=A0=C2=A06.360000] [<ffffffff8042da78>] > > __platform_driver_register+0x48/0x5c -> > [ 6.370000] [<ffffffff8000db38>] +> > [=C2=A0=C2=A0=C2=A0=C2=A06.370000] [<ffffffff8000db38>] > > xilinx_pcie_driver_init+0x20/0x34 -> > [ 6.380000] [<ffffffff80000d48>] do_one_initcall+0x98/0x140 -> > [ 6.380000] [<ffffffff80000f38>] +> > [=C2=A0=C2=A0=C2=A0=C2=A06.380000] [<ffffffff80000d48>] do_one_initcall= ++0x98/0x140 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.380000] [<ffffffff80000f38>] > > kernel_init_freeable+0x148/0x218 -> > [ 6.390000] [<ffffffff805ad19c>] kernel_init+0x18/0x114 -> > [ 6.390000] [<ffffffff80286cac>] ret_from_syscall+0xc/0x10 -> > [ 6.400000] ---[ end trace 8023adf5befc91e0 ]--- -> > +> > [=C2=A0=C2=A0=C2=A0=C2=A06.390000] [<ffffffff805ad19c>] kernel_init+0x1= +8/0x114 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.390000] [<ffffffff80286cac>] ret_from_syscal= +l+0xc/0x10 +> > [=C2=A0=C2=A0=C2=A0=C2=A06.400000] ---[ end trace 8023adf5befc91e0 ]--- +> >=20 > > ... that said, I am not confident my patch is the right fix. So > > consider this a bug report + work-around only. :) -> > -> > > -> > > Yeah, everything seems mostly working. The "invalid BAR" things +> >=20 +> > >=20 +> > > Yeah, everything seems mostly working.=C2=A0=C2=A0The "invalid BAR" t= +hings > > > *could* be an issue -- those registers are not what the PCI spec > > > says > > > they should be. @@ -127,11 +155,11 @@ altera.c?id=99496bd2971fc378226ad4413e5b72c4545714bd > > 06:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 > > PCIe > > SATA 6Gb/s Controller (rev 11) -> > +> >=20 > > I am going to plug them in to an Intel machine with 4.11 and see if > > I > > get the same warnings. -> +>=20 Regards Ley Foon diff --git a/a/content_digest b/N1/content_digest index 3baa93a..6debdfd 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,20 +15,22 @@ "b\0" "On Wed, 2017-04-05 at 13:37 -0500, Bjorn Helgaas wrote:\n" "> [+cc Michal, Ley Foon]\n" - "> \n" + ">=20\n" "> On Tue, Apr 04, 2017 at 04:00:49PM -0700, Wesley Terpstra wrote:\n" - "> > \n" + "> >=20\n" "> > Thank you very much for your detailed analysis of the log!\n" - "> > \n" + "> >=20\n" "> > On Tue, Apr 4, 2017 at 1:56 PM, Bjorn Helgaas <helgaas@kernel.org>\n" "> > wrote:\n" - "> > > \n" - "> > > > \n" + "> > >=20\n" + "> > > >=20\n" "> > > > In particular, these are the lines that seem wrong to me:\n" - "> > > > [\302\240\302\240\302\240\302\2405.920000] pci 0000:00:00.0: bridge configuration invalid\n" + "> > > > [=C2=A0=C2=A0=C2=A0=C2=A05.920000] pci 0000:00:00.0: bridge configu=\n" + "ration invalid\n" "> > > > ([bus\n" "> > > > 00-00]), reconfiguring\n" - "> > > > [\302\240\302\240\302\240\302\2405.930000] pci 0000:01:00.0: bridge configuration invalid\n" + "> > > > [=C2=A0=C2=A0=C2=A0=C2=A05.930000] pci 0000:01:00.0: bridge configu=\n" + "ration invalid\n" "> > > > ([bus\n" "> > > > 00-00]), reconfiguring\n" "> > > This is normal but possibly worded more alarmingly than\n" @@ -43,96 +45,122 @@ "> > bus\n" "> > number already. Right?\n" "> Yes.\n" - "> \n" - "> > \n" - "> > > \n" - "> > > > \n" - "> > > > [\302\240\302\240\302\240\302\2406.000000] pci 0000:04:00.0: [Firmware Bug]: reg 0x10:\n" + ">=20\n" + "> >=20\n" + "> > >=20\n" + "> > > >=20\n" + "> > > > [=C2=A0=C2=A0=C2=A0=C2=A06.000000] pci 0000:04:00.0: [Firmware Bug]=\n" + ": reg 0x10:\n" "> > > > invalid BAR\n" "> > > > (can't size)\n" - "> > > > [\302\240\302\240\302\240\302\2406.010000] pci 0000:06:00.0: [Firmware Bug]: reg 0x10:\n" + "> > > > [=C2=A0=C2=A0=C2=A0=C2=A06.010000] pci 0000:06:00.0: [Firmware Bug]=\n" + ": reg 0x10:\n" "> > > > invalid BAR\n" "> > > > (can't size)\n" - "> > > These are more worrisome.\302\240\302\240We discover the size of a BAR by\n" + "> > > These are more worrisome.=C2=A0=C2=A0We discover the size of a BAR by\n" "> > > writing\n" "> > > all ones to it and reading it back, which tells us how many bits\n" "> > > of\n" - "> > > the BAR are hard-wired to zero.\302\240\302\240This behavior is prescribed by\n" + "> > > the BAR are hard-wired to zero.=C2=A0=C2=A0This behavior is prescribe=\n" + "d by\n" "> > > the\n" "> > > PCI specs, so it's likely a hardware defect.\n" "> > So, you would say it's a hardware problem of the PCIe cards in\n" "> > question and I can safely ignore it?\n" "> Yes.\n" - "> \n" - "> > \n" - "> > > \n" + ">=20\n" + "> >=20\n" + "> > >=20\n" "> > > This is because the xilinx host bridge doesn't support I/O space\n" "> > Yeah. I knew this, but thanks for confirming.\n" - "> > \n" + "> >=20\n" "> > FYI, there is a bug in the pcie-xilinx bridge wrt legacy\n" "> > interrupts.\n" "> > I've seen several people discussing the same problem for the altera\n" "> > bridge and the \"NW\" xilinx bridge, but somehow this bridge still\n" "> > has\n" "> > the issue. I've attached a patch that solved the problem for me.\n" - "> This sounds familiar to me, too.\302\240\302\240Copying Michal & Ley Foon in case\n" + "> This sounds familiar to me, too.=C2=A0=C2=A0Copying Michal & Ley Foon in =\n" + "case\n" "> they\n" "> know something about it.\n" "We have fixed this in last year.\n" "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm\n" "it/drivers/pci/host/pcie-\n" - "altera.c?id=99496bd2971fc378226ad4413e5b72c4545714bd\n" + "altera.c?id=3D99496bd2971fc378226ad4413e5b72c4545714bd\n" "\n" - "> \n" - "> > \n" + ">=20\n" + "> >=20\n" "> > Without it I see:\n" - "> > \n" - "> > [\302\240\302\240\302\240\302\2406.230000] ------------[ cut here ]------------\n" - "> > [\302\240\302\240\302\240\302\2406.230000] WARNING: CPU: 0 PID: 1 at\n" + "> >=20\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.230000] ------------[ cut here ]------------\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.230000] WARNING: CPU: 0 PID: 1 at\n" "> > /scratch/terpstra/freedom-u-sdk/linux/kernel/irq/irqdomain.c:365\n" "> > irq_domain_associate+0x190/0x200\n" - "> > [\302\240\302\240\302\240\302\2406.240000] error: hwirq 0x4 is too large for dummy\n" - "> > [\302\240\302\240\302\240\302\2406.250000] CPU: 0 PID: 1 Comm: swapper Not tainted\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.240000] error: hwirq 0x4 is too large for du=\n" + "mmy\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.250000] CPU: 0 PID: 1 Comm: swapper Not tain=\n" + "ted\n" "> > 4.11.0-rc1-661305-g4f97179 #12\n" - "> > [\302\240\302\240\302\240\302\2406.250000] Call Trace:\n" - "> > [\302\240\302\240\302\240\302\2406.260000] [<ffffffff80288660>] walk_stackframe+0x0/0x104\n" - "> > [\302\240\302\240\302\240\302\2406.260000] [<ffffffff80288800>] show_stack+0x38/0x50\n" - "> > [\302\240\302\240\302\240\302\2406.270000] [<ffffffff803c6e30>] dump_stack+0x2c/0x40\n" - "> > [\302\240\302\240\302\240\302\2406.270000] [<ffffffff8028c600>] __warn+0x118/0x130\n" - "> > [\302\240\302\240\302\240\302\2406.280000] [<ffffffff8028c658>] warn_slowpath_fmt+0x40/0x54\n" - "> > [\302\240\302\240\302\240\302\2406.280000] [<ffffffff802c02a8>]\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.250000] Call Trace:\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.260000] [<ffffffff80288660>] walk_stackframe=\n" + "+0x0/0x104\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.260000] [<ffffffff80288800>] show_stack+0x38=\n" + "/0x50\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.270000] [<ffffffff803c6e30>] dump_stack+0x2c=\n" + "/0x40\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.270000] [<ffffffff8028c600>] __warn+0x118/0x=\n" + "130\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.280000] [<ffffffff8028c658>] warn_slowpath_f=\n" + "mt+0x40/0x54\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.280000] [<ffffffff802c02a8>]\n" "> > irq_domain_associate+0x18c/0x200\n" - "> > [\302\240\302\240\302\240\302\2406.290000] [<ffffffff802c0a3c>] irq_create_mapping+0x90/0xe4\n" - "> > [\302\240\302\240\302\240\302\2406.300000] [<ffffffff802c0be4>]\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.290000] [<ffffffff802c0a3c>] irq_create_mapp=\n" + "ing+0x90/0xe4\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.300000] [<ffffffff802c0be4>]\n" "> > irq_create_fwspec_mapping+0x154/0x288\n" - "> > [\302\240\302\240\302\240\302\2406.300000] [<ffffffff802c0d7c>] irq_create_of_mapping+0x64/0x84\n" - "> > [\302\240\302\240\302\240\302\2406.310000] [<ffffffff804f9cb8>]\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.300000] [<ffffffff802c0d7c>] irq_create_of_m=\n" + "apping+0x64/0x84\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.310000] [<ffffffff804f9cb8>]\n" "> > of_irq_parse_and_map_pci+0x38/0x50\n" - "> > [\302\240\302\240\302\240\302\2406.310000] [<ffffffff80407e00>] pci_fixup_irqs+0x6c/0x114\n" - "> > [\302\240\302\240\302\240\302\2406.320000] [<ffffffff80408e64>] xilinx_pcie_probe+0x308/0x3f0\n" - "> > [\302\240\302\240\302\240\302\2406.330000] [<ffffffff8042cba4>] platform_drv_probe+0x3c/0x88\n" - "> > [\302\240\302\240\302\240\302\2406.330000] [<ffffffff8042aec0>] really_probe+0xbc/0x260\n" - "> > [\302\240\302\240\302\240\302\2406.340000] [<ffffffff8042b138>] __driver_attach+0xd4/0xdc\n" - "> > [\302\240\302\240\302\240\302\2406.340000] [<ffffffff80429200>] bus_for_each_dev+0x68/0xb8\n" - "> > [\302\240\302\240\302\240\302\2406.350000] [<ffffffff8042b640>] driver_attach+0x24/0x38\n" - "> > [\302\240\302\240\302\240\302\2406.350000] [<ffffffff80429db8>] bus_add_driver+0x1b4/0x22c\n" - "> > [\302\240\302\240\302\240\302\2406.360000] [<ffffffff8042bdc0>] driver_register+0x68/0x12c\n" - "> > [\302\240\302\240\302\240\302\2406.360000] [<ffffffff8042da78>]\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.310000] [<ffffffff80407e00>] pci_fixup_irqs+=\n" + "0x6c/0x114\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.320000] [<ffffffff80408e64>] xilinx_pcie_pro=\n" + "be+0x308/0x3f0\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.330000] [<ffffffff8042cba4>] platform_drv_pr=\n" + "obe+0x3c/0x88\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.330000] [<ffffffff8042aec0>] really_probe+0x=\n" + "bc/0x260\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.340000] [<ffffffff8042b138>] __driver_attach=\n" + "+0xd4/0xdc\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.340000] [<ffffffff80429200>] bus_for_each_de=\n" + "v+0x68/0xb8\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.350000] [<ffffffff8042b640>] driver_attach+0=\n" + "x24/0x38\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.350000] [<ffffffff80429db8>] bus_add_driver+=\n" + "0x1b4/0x22c\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.360000] [<ffffffff8042bdc0>] driver_register=\n" + "+0x68/0x12c\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.360000] [<ffffffff8042da78>]\n" "> > __platform_driver_register+0x48/0x5c\n" - "> > [\302\240\302\240\302\240\302\2406.370000] [<ffffffff8000db38>]\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.370000] [<ffffffff8000db38>]\n" "> > xilinx_pcie_driver_init+0x20/0x34\n" - "> > [\302\240\302\240\302\240\302\2406.380000] [<ffffffff80000d48>] do_one_initcall+0x98/0x140\n" - "> > [\302\240\302\240\302\240\302\2406.380000] [<ffffffff80000f38>]\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.380000] [<ffffffff80000d48>] do_one_initcall=\n" + "+0x98/0x140\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.380000] [<ffffffff80000f38>]\n" "> > kernel_init_freeable+0x148/0x218\n" - "> > [\302\240\302\240\302\240\302\2406.390000] [<ffffffff805ad19c>] kernel_init+0x18/0x114\n" - "> > [\302\240\302\240\302\240\302\2406.390000] [<ffffffff80286cac>] ret_from_syscall+0xc/0x10\n" - "> > [\302\240\302\240\302\240\302\2406.400000] ---[ end trace 8023adf5befc91e0 ]---\n" - "> > \n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.390000] [<ffffffff805ad19c>] kernel_init+0x1=\n" + "8/0x114\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.390000] [<ffffffff80286cac>] ret_from_syscal=\n" + "l+0xc/0x10\n" + "> > [=C2=A0=C2=A0=C2=A0=C2=A06.400000] ---[ end trace 8023adf5befc91e0 ]---\n" + "> >=20\n" "> > ... that said, I am not confident my patch is the right fix. So\n" "> > consider this a bug report + work-around only. :)\n" - "> > \n" - "> > > \n" - "> > > Yeah, everything seems mostly working.\302\240\302\240The \"invalid BAR\" things\n" + "> >=20\n" + "> > >=20\n" + "> > > Yeah, everything seems mostly working.=C2=A0=C2=A0The \"invalid BAR\" t=\n" + "hings\n" "> > > *could* be an issue -- those registers are not what the PCI spec\n" "> > > says\n" "> > > they should be.\n" @@ -142,13 +170,13 @@ "> > 06:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230\n" "> > PCIe\n" "> > SATA 6Gb/s Controller (rev 11)\n" - "> > \n" + "> >=20\n" "> > I am going to plug them in to an Intel machine with 4.11 and see if\n" "> > I\n" "> > get the same warnings.\n" - "> \n" + ">=20\n" "\n" "Regards\n" Ley Foon -4b0cc36a47972364d063c78d18205ccc0b9512a6283f0529b1728ef236634149 +96e4f7af5215fc5b7e6a9b309b468b92a97d0e4751019264bdd4361f8d3e1daa
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.