From: Alan Stern <stern@rowland.harvard.edu> To: Bjorn Helgaas <helgaas@kernel.org> Cc: Paul Menzel <pmenzel+linux-pci@molgen.mpg.de>, <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>, David Woodhouse <dwmw2@infradead.org>, Andy Shevchenko <andy.shevchenko@gmail.com>, <linux-usb@vger.kernel.org> Subject: Re: `pci_apply_final_quirks()` taking half a second Date: Fri, 29 Dec 2017 11:14:51 -0500 (EST) [thread overview] Message-ID: <Pine.LNX.4.44L0.1712291111580.24019-100000@netrider.rowland.org> (raw) In-Reply-To: <20171228212723.GB211339@bhelgaas-glaptop.roam.corp.google.com> On Thu, 28 Dec 2017, Bjorn Helgaas wrote: > On Tue, Dec 26, 2017 at 04:55:20PM +0100, Paul Menzel wrote: > > Am 08.04.2017 um 17:41 schrieb Bjorn Helgaas: > > >On Fri, Apr 07, 2017 at 11:07:15PM +0200, Paul Menzel wrote: > > > > >>Measuring where time is spent during boot with `systemd-bootchart` > > >>on an Asus A780FullHD, it turns out that half a second is spent in > > >>`pci_apply_final_quirks()`. > > > > > >I agree, that seems like a crazy amount of time. > > > > > >Can you figure out how to turn on pr_debug() (via the dynamic debug > > >mess or whatever) and boot with "initcall_debug"? That should tell us > > >how long each quirk took. > > > > I am sorry for taking so long to reply. I finally added `dyndbg=file > > quirks.c +p` to the command line of Linux 4.13.13. This is on > > another AMD system (Asus F285M Pro). > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 197 usecs for > > 0000:00:10.0 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 127 usecs for > > 0000:00:10.1 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 88643 usecs for > > 0000:00:12.0 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 137 usecs for > > 0000:00:12.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > pci_fixup_amd_ehci_pme+0x0/0x30 returned after 1 usecs for > > 0000:00:12.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 85770 usecs for > > 0000:00:13.0 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 134 usecs for > > 0000:00:13.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > pci_fixup_amd_ehci_pme+0x0/0x30 returned after 1 usecs for > > 0000:00:13.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 125 usecs for > > 0000:03:00.0[…] > > ``` > > > > So it’s `pci fixup quirk_usb_early_handoff` taking around 85 ms, and > > that twice. > > Wow. That's pretty painful, but of course I don't know how to fix it. > From looking at quirk_usb_early_handoff(), it may depend on BIOS > details. Maybe the USB folks will have some ideas. Can we see the output from lspci? It would help to know what the 12.0 and 13.0 devices are. Alan Stern
WARNING: multiple messages have this Message-ID (diff)
From: Alan Stern <stern@rowland.harvard.edu> To: Bjorn Helgaas <helgaas@kernel.org> Cc: Paul Menzel <pmenzel+linux-pci@molgen.mpg.de>, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>, Andy Shevchenko <andy.shevchenko@gmail.com>, linux-usb@vger.kernel.org Subject: `pci_apply_final_quirks()` taking half a second Date: Fri, 29 Dec 2017 11:14:51 -0500 (EST) [thread overview] Message-ID: <Pine.LNX.4.44L0.1712291111580.24019-100000@netrider.rowland.org> (raw) On Thu, 28 Dec 2017, Bjorn Helgaas wrote: > On Tue, Dec 26, 2017 at 04:55:20PM +0100, Paul Menzel wrote: > > Am 08.04.2017 um 17:41 schrieb Bjorn Helgaas: > > >On Fri, Apr 07, 2017 at 11:07:15PM +0200, Paul Menzel wrote: > > > > >>Measuring where time is spent during boot with `systemd-bootchart` > > >>on an Asus A780FullHD, it turns out that half a second is spent in > > >>`pci_apply_final_quirks()`. > > > > > >I agree, that seems like a crazy amount of time. > > > > > >Can you figure out how to turn on pr_debug() (via the dynamic debug > > >mess or whatever) and boot with "initcall_debug"? That should tell us > > >how long each quirk took. > > > > I am sorry for taking so long to reply. I finally added `dyndbg=file > > quirks.c +p` to the command line of Linux 4.13.13. This is on > > another AMD system (Asus F285M Pro). > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 197 usecs for > > 0000:00:10.0 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 127 usecs for > > 0000:00:10.1 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 88643 usecs for > > 0000:00:12.0 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 137 usecs for > > 0000:00:12.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > pci_fixup_amd_ehci_pme+0x0/0x30 returned after 1 usecs for > > 0000:00:12.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 85770 usecs for > > 0000:00:13.0 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 134 usecs for > > 0000:00:13.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > pci_fixup_amd_ehci_pme+0x0/0x30 returned after 1 usecs for > > 0000:00:13.2 > > Dez 26 16:21:46 asus-f2a85-pro kernel: pci fixup > > quirk_usb_early_handoff+0x0/0x6b0 returned after 125 usecs for > > 0000:03:00.0[…] > > ``` > > > > So it’s `pci fixup quirk_usb_early_handoff` taking around 85 ms, and > > that twice. > > Wow. That's pretty painful, but of course I don't know how to fix it. > From looking at quirk_usb_early_handoff(), it may depend on BIOS > details. Maybe the USB folks will have some ideas. Can we see the output from lspci? It would help to know what the 12.0 and 13.0 devices are. Alan Stern --- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-29 16:14 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-07 21:07 `pci_apply_final_quirks()` taking half a second Paul Menzel 2017-04-08 15:41 ` Bjorn Helgaas 2017-04-08 17:00 ` David Woodhouse 2017-04-08 19:06 ` Bjorn Helgaas 2017-05-03 18:42 ` Andy Shevchenko 2017-12-26 15:55 ` Paul Menzel 2017-12-28 21:27 ` Bjorn Helgaas 2017-12-28 21:27 ` Bjorn Helgaas 2017-12-29 16:14 ` Alan Stern [this message] 2017-12-29 16:14 ` Alan Stern 2017-12-29 16:14 ` Alan Stern 2017-12-31 7:18 ` Paul Menzel 2017-12-31 7:18 ` Paul Menzel 2017-12-31 21:16 ` Alan Stern 2017-12-31 21:16 ` Alan Stern 2017-12-31 21:16 ` Alan Stern 2018-01-01 10:21 ` Paul Menzel 2018-01-01 10:21 ` Paul Menzel 2018-01-01 15:47 ` Alan Stern 2018-01-01 15:47 ` Alan Stern 2018-01-01 15:47 ` Alan Stern 2018-06-24 16:49 ` `quirk_usb_handoff_ohci` takes over 73 ms (twice) on AMD system (was: `pci_apply_final_quirks()` taking half a second) Paul Menzel 2018-06-24 16:49 ` `pci_apply_final_quirks()` taking half a second Paul Menzel
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=Pine.LNX.4.44L0.1712291111580.24019-100000@netrider.rowland.org \ --to=stern@rowland.harvard.edu \ --cc=andy.shevchenko@gmail.com \ --cc=dwmw2@infradead.org \ --cc=helgaas@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=pmenzel+linux-pci@molgen.mpg.de \ /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: linkBe 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.