All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Hathaway <jesse@mbuki-mvuki.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: Regression causes a hang on boot with a Comtrol PCI card
Date: Fri, 22 Mar 2019 15:02:11 -0500	[thread overview]
Message-ID: <CANSNSoXhiYP4Ad3hO1v03aMOX1VtUao2yCLgj_J0z9fCNwWo5w@mail.gmail.com> (raw)
In-Reply-To: <20190321232310.GL251185@google.com>

> So apparently the hang happens while we're running the "final" PCI
> fixups.  This happens after all the rest of PCI is initialized.
>
> Can you boot v5.0 vanilla with "initcall_debug"?  Maybe we can narrow
> it down to a specific quirk.

yup, added the "initcall_debug" output to the ticket:
https://bugzilla.kernel.org/show_bug.cgi?id=202927, here is the tail end

[   14.896337] NET: Registered protocol family 1
[   14.901314] initcall af_unix_init+0x0/0x4e returned 0 after 4866 usecs
[   14.908694] calling  ipv6_offload_init+0x0/0x7f @ 1
[   14.914238] initcall ipv6_offload_init+0x0/0x7f returned 0 after 1 usecs
[   14.921821] calling  vlan_offload_init+0x0/0x20 @ 1
[   14.927365] initcall vlan_offload_init+0x0/0x20 returned 0 after 0 usecs
[   14.934948] calling  pci_apply_final_quirks+0x0/0x126 @ 1
[   14.941106] pci 0000:00:1a.0: calling  quirk_usb_early_handoff+0x0/0x6a0 @ 1

thanks, Jesse Hathaway

  reply	other threads:[~2019-03-22 20:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 16:50 Regression causes a hang on boot with a Comtrol PCI card Jesse Hathaway
2019-03-13 23:21 ` Bjorn Helgaas
2019-03-14 20:57   ` Jesse Hathaway
2019-03-21 20:36     ` Jesse Hathaway
2019-03-21 23:23     ` Bjorn Helgaas
2019-03-22 20:02       ` Jesse Hathaway [this message]
2019-04-01 19:43         ` Jesse Hathaway
2019-04-01 21:13         ` Bjorn Helgaas
2019-04-02 14:29           ` Alan Stern
2019-04-02 14:49             ` Mathias Nyman
2019-04-02 18:26               ` Alan Stern
2019-04-04 15:41             ` Jesse Hathaway
2019-04-04 17:16               ` Alan Stern
2019-04-04 17:36                 ` Jesse Hathaway
2019-04-04 19:14                   ` Alan Stern
2019-04-05 21:27                     ` Jesse Hathaway
2019-04-06 15:32                       ` Alan Stern
2019-04-15 21:47                         ` Jesse Hathaway
2019-04-16 15:00                           ` Alan Stern
2019-04-23 20:18                             ` Jesse Hathaway
2019-04-24 14:20                               ` Alan Stern

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=CANSNSoXhiYP4Ad3hO1v03aMOX1VtUao2yCLgj_J0z9fCNwWo5w@mail.gmail.com \
    --to=jesse@mbuki-mvuki.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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.