mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [pci] 38ada4d7c6b: general protection fault: 0000 [#1] SMP
Date: Wed, 18 Mar 2015 08:21:07 +0100	[thread overview]
Message-ID: <20150318081204-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1426553156.1126.11.camel@intel.com>

On Tue, Mar 17, 2015 at 08:45:56AM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next
> commit 38ada4d7c6b416b2c41e67b721ebcfeec89e4751 ("pci: disable msi/msix at probe time")
> 
> 
> +------------------------------------------+------------+------------+
> |                                          | 91435d5741 | 38ada4d7c6 |
> +------------------------------------------+------------+------------+
> | boot_successes                           | 30         | 0          |
> | early-boot-hang                          | 1          |            |
> | boot_failures                            | 0          | 29         |
> | BUG:unable_to_handle_kernel              | 0          | 9          |
> | Oops                                     | 0          | 9          |
> | RIP:pci_bus_read_config_word             | 0          | 29         |
> | Kernel_panic-not_syncing:Fatal_exception | 0          | 29         |
> | backtrace:__pci_register_driver          | 0          | 29         |
> | backtrace:piix_init                      | 0          | 9          |
> | backtrace:kernel_init_freeable           | 0          | 29         |
> | general_protection_fault                 | 0          | 20         |
> | backtrace:virtio_pci_driver_init         | 0          | 20         |
> +------------------------------------------+------------+------------+

Thanks a lot for the report!
This was a result of pushing a bad commit out, I have since
found and fixed this.
Just to clarify, you are testing all public heads?
Or does head need to confirm to some naming scheme?

Also, it seems you are testing in a KVM based VM, is that right?
If so, including the kvm userspace (QEMU?) version and command line
used could be benefitial in case people want to re-run the test.

Thanks!

> _______________________________________________
> LKP mailing list
> LKP@linux.intel.com
> 


      reply	other threads:[~2015-03-18  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  0:45 Huang Ying
2015-03-18  7:21 ` Michael S. Tsirkin [this message]

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=20150318081204-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ying.huang@intel.com \
    /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

Powered by JetHome