From: Richard F <lists@keynet-technology.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: Hint HB6 - kernel doesn't see chips behind it.
Date: Wed, 27 Jan 2016 14:54:25 +0000 [thread overview]
Message-ID: <56A8DA21.7060607@keynet-technology.com> (raw)
In-Reply-To: <20160119033839.GA3339@localhost>
Bjorn,
Would someone be able take a quick look at my logs and give me any kind
of steer as to where to look? I'm happy to do some more debugging with
a bit of guidance.
https://bugzilla.kernel.org/show_bug.cgi?id=110851
Thanks
Richard
On 19/01/2016 03:38, Bjorn Helgaas wrote:
> On Mon, Jan 18, 2016 at 02:48:59PM +0000, Richard F wrote:
>> I posted a DMESG with 4.3.3 to Bugzilla now.
>> 4.4.0 crashed on boot, not sure why yet.
>
> Thanks for all the data you collected! I haven't had a chance to look
> at them yet, but maybe others will take a look also.
>
> Crashing on boot is a much more serious problem than failure to find a
> card. Any information you can collect about the v4.4.0 problem would
> be extremely useful. A serial console log would be ideal, but even a
> photo or video of the boot might be helpful. Boot with
> "ignore_loglevel" to make sure we see all the messages.
>
> Bjorn
>
next prev parent reply other threads:[~2016-01-27 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:54 Hint HB6 - kernel doesn't see chips behind it Richard F
2016-01-15 17:26 ` Bjorn Helgaas
2016-01-17 21:04 ` Richard F
2016-01-18 14:48 ` Richard F
2016-01-19 3:38 ` Bjorn Helgaas
2016-01-19 10:16 ` Richard F
2016-01-19 17:41 ` Richard F
2016-01-27 14:54 ` Richard F [this message]
2016-01-27 21:55 ` Bjorn Helgaas
2016-01-28 10:23 ` Richard F
2016-01-29 16:24 ` Bjorn Helgaas
2016-01-30 17:54 ` Richard F
2016-02-01 19:06 ` Bjorn Helgaas
2016-02-01 20:06 ` Richard F
2016-02-01 23:35 ` Bjorn Helgaas
2016-02-03 13:52 ` Richard F
2016-02-03 15:51 ` Bjorn Helgaas
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=56A8DA21.7060607@keynet-technology.com \
--to=lists@keynet-technology.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).