linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Cox <jkc@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org, sparmaintainer@unisys.com,
	devel@driverdev.osuosl.org, Jet Chen <jet.chen@intel.com>
Subject: Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP
Date: Mon, 07 Apr 2014 09:24:37 -0500	[thread overview]
Message-ID: <5342B525.80407@redhat.com> (raw)
In-Reply-To: <20140407140958.GA7346@kroah.com>


On 04/07/2014 09:09 AM, Greg Kroah-Hartman wrote:
> On Mon, Apr 07, 2014 at 07:17:25PM +0800, Fengguang Wu wrote:
>> Hi Ken,
>>
>> I got the below dmesg and the first bad commit is
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>
>> commit 12e364b9f08aa335dc7716ce74113e834c993765
>> Author:     Ken Cox <jkc@redhat.com>
>> AuthorDate: Tue Mar 4 07:58:07 2014 -0600
>> Commit:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> CommitDate: Tue Mar 4 16:58:21 2014 -0800
>>
>>      staging: visorchipset driver to provide registration and other services
> I think Sasha has already sent a fix to resolve this issue that I'll be
> sending to Linus in a day or so.
>
> Ken, is Sasha's patch going to resolve this issue as well?  It looks
> like people haven't tested what happens when the module is loaded
> without the hardware present in the system :(
You are exactly right.  The driver needs to check for hardware early on 
before trying to use it.  Unfortunately, Sasha's patch will not resolve 
this one.  I'll work with Ben Romer to get a patch out ASAP.

Thanks,
Ken Cox

  reply	other threads:[~2014-04-07 14:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 11:17 [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP Fengguang Wu
2014-04-07 14:04 ` Ken Cox
2014-04-07 14:09 ` Greg Kroah-Hartman
2014-04-07 14:24   ` Ken Cox [this message]
2014-04-07 19:23     ` Greg Kroah-Hartman
2014-04-07 19:46       ` Greg Kroah-Hartman
     [not found] ` <C97001BC43954D438ACB059713BA5CDF92040F0F00@USEA-EXCH7.na.uis.unisys.com>
2014-04-08  2:53   ` Fengguang Wu
2014-04-08 15:39     ` Romer, Benjamin M
     [not found]   ` <53444220.50009@intel.com>
     [not found]     ` <C97001BC43954D438ACB059713BA5CDF92040F0F06@USEA-EXCH7.na.uis.unisys.com>
     [not found]       ` <53458A3A.1050608@intel.com>
2014-04-09 23:01         ` Fengguang Wu
2014-04-09 23:10           ` H. Peter Anvin
2014-04-10 13:19             ` Romer, Benjamin M
2014-04-11  2:28               ` H. Peter Anvin
2014-04-11 13:51                 ` Romer, Benjamin M
2014-04-11 16:33                   ` H. Peter Anvin
2014-04-11 17:35                     ` Jet Chen
2014-04-11 17:40                       ` H. Peter Anvin
2014-04-11 17:51                         ` Romer, Benjamin M
2014-04-30 10:02                         ` Paolo Bonzini
2014-04-11 17:49                       ` Romer, Benjamin M
2014-04-13 11:51                       ` Borislav Petkov
2014-04-13 12:20                         ` Jet Chen
2014-04-09 23:10           ` H. Peter Anvin

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=5342B525.80407@redhat.com \
    --to=jkc@redhat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jet.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparmaintainer@unisys.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;
as well as URLs for NNTP newsgroup(s).