linux-kernel - Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5342B059.1030401@redhat.com>
Date:	Mon, 07 Apr 2014 09:04:09 -0500
From:	Ken Cox <jkc@...hat.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, sparmaintainer@...sys.com,
	devel@...verdev.osuosl.org, Jet Chen <jet.chen@...el.com>
Subject: Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP


On 04/07/2014 06:17 AM, 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@...hat.com>
> AuthorDate: Tue Mar 4 07:58:07 2014 -0600
> Commit:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> CommitDate: Tue Mar 4 16:58:21 2014 -0800
>
--snip--
> [   24.135101] FPGA image file name: xlinx_fpga_firmware.bit
> [   24.137595] GPIO INIT FAIL!!
> [   24.141283] driver version 1.0.0.0 loaded
> [   24.142539] chipset driver version 1.0.0.0 loadedinvalid opcode: 0000 [#1] PREEMPT SMP
> [   24.144793] Modules linked in:
> [   24.145303] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.0-rc5-00621-g12e364b #1
> [   24.145303] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
> [   24.145303] task: ffff88001157a010 ti: ffff88001157c000 task.ti: ffff88001157c000
> [   24.145303] RIP: 0010:[<ffffffff81e37115>]  [<ffffffff81e37115>] visorchipset_init+0x7b/0x8c5
The problem is that the driver is trying to call firmware code that only 
exists on Unisys s-Par hardware.  I will add a check to make sure the 
driver is running on the correct platform before trying to call into the 
firmware.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/