All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 17 Jan 2016 21:04:44 +0000	[thread overview]
Message-ID: <569C01EC.2040906@keynet-technology.com> (raw)
In-Reply-To: <20160115172640.GC28453@localhost>

Bjorn,

I have added the DMESG and lspci logs for different kernels and
motherbaords on that Bugzilla for you.

Not yet been able to build a 4.4 kernel yet - will try shortly.
Appreciate any pointers for further debug.

thanks
Richard

On 15/01/2016 17:26, Bjorn Helgaas wrote:
> Hi Richard,
> 
> 
> Thanks for your report.  I opened this bug report:
> 
>   https://bugzilla.kernel.org/show_bug.cgi?id=110851
> 
> Can you please attach the complete dmesg logs from the old machine
> running 3.0.76 and the new machine running 3.0.76 to that bugzilla?
> Also please attach the complete "lspci -vvv" output for all the
> devices in the new machine.
> 
> Is there any chance you can try a current kernel, e.g., v4.4, on the
> new machine?  Even if you can't install a new kernel permanently, the
> dmesg log of PCI enumeration is enough to show whether we detect the
> Kodicom devices or not.
> 
> Bjorn


  reply	other threads:[~2016-01-17 22:19 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 [this message]
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
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=569C01EC.2040906@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 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.