On Fri, 22 Jul 2016, Jochen Sprickerhof wrote:
> thanks for clearing this up so quickly :). Just as a follow up, Tuxedo
> released
> a new BIOS version including microcode 0x8a and I tested that 3.20160607.1
> doesn't fail with that anymore.
Yeah, information about their BIOS update was forwarded
Package: intel-microcode
Followup-For: Bug #828819
Dear Maintainer,
thanks for clearing this up so quickly :). Just as a follow up, Tuxedo released
a new BIOS version including microcode 0x8a and I tested that 3.20160607.1
doesn't fail with that anymore.
Cheers Jochen
Hi Together,
we updated the microcode that comes with the BIOS.
Here you can download the updated BIOS:
[1]http://www.linux-onlineshop.de/forum/index.php?page=Thread&threadID=321
--
Mit freundlichen Grüßen / Kind regards
Tobias Fischer
TUXEDO Computers.com
--
TUXEDO Computers GmbH ~ Zeppelinstr
Well, more information:
Report for the same issue on Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1353103
All reports of this issue being "fixed" by a firmware update (in Debian,
Arch and Fedora) are for firmware updates that come with microcode 0x8a
already, effectively rendering the micr
On Mon, 04 Jul 2016, Mike Palmer wrote:
> Jul 3 22:12:30 carbon kernel: [1.670464] microcode: CPU0
> sig=0x406e3, pf=0x80, revision=0x8a
Well, basically it is not doing anything because your BIOS has the new
microcode already...
I wanted to confirm the "pf", and it is the same pf as the othe
>From the kernel log this is all I see now that it is working.
Jul 3 22:12:30 carbon kernel: [1.670464] microcode: CPU0
sig=0x406e3, pf=0x80, revision=0x8a
Jul 3 22:12:30 carbon kernel: [1.670477] microcode: CPU1
sig=0x406e3, pf=0x80, revision=0x8a
Jul 3 22:12:30 carbon kernel: [1.6
Mike,
After the BIOS update, do you have any "microcode" entries in the kernel
log? Could you send them to the bug report?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The
I had exactly the same issue with an ASUS UX305CA ultrabook.
Downgrading to the previous version of intel-microcode resolved it for
me as well. I was able to get intel-microcode 3.20160607.1 working by
upgrading from UX305CA.205 to UX305CA.300 BIOS revision from ASUS.
---
# dmidecode 3.0
* Henrique de Moraes Holschuh [2016-06-28 22:21]:
> Can you send to this bug report the "microcode: ... sig=..., pf=..."
> line logged by the kernel that does boot, please?
microcode: CPU0 sig=0x406e3, pf=0x80, revision=0x6a
signature.asc
Description: PGP signature
On Tue, 28 Jun 2016, Jochen Sprickerhof wrote:
> * Henrique de Moraes Holschuh [2016-06-28 10:06]:
> > Should a firmware update not be available yet from your system vendor,
> > please request on their support channels a BIOS/UEFI update that has:
>
> There is no update available, I've send them
* Henrique de Moraes Holschuh [2016-06-28 10:06]:
> Just out of curiosity, is your system a "Tuxedo InfinityBook 13v2" from
> tuxedocomputers.com ?
Yes, it is.
> Should a firmware update not be available yet from your system vendor,
> please request on their support channels a BIOS/UEFI update t
On Tue, 28 Jun 2016, Jochen Sprickerhof wrote:
> microcode : 0x6a
AFAIK, this microcode revision level is subtly incompatible with Linux
due to documented processor errata. Unfortunately, your system really
needs a firmware and microcode update to run Debian in a stable way.
Worse, it looks
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 78
model name : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
stepping: 3
microcode : 0x6a
cpu MHz : 499.992
cache size : 4096 KB
physical id : 0
siblings
Processing commands for cont...@bugs.debian.org:
> severity 828819 grave
Bug #828819 [intel-microcode] intel-microcode: i7-6500U doesn't boot in 4/5
cases with 3.20160607.1
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
8
14 matches
Mail list logo
