Skip to contentSkip to conversation

linux-yocto: Adds new genericx86 and genericx86-64 SRCREVs for kernel 4.4

PATCH In review Alejandro Hernandez 2 participants 3 messages Jan 29, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 linux-yocto: Adds new genericx86 and genericx86-64 SRCREVs for kernel 4.4

The only issue I found was on poky-lsb - genericx86-64 using kernel 4.4 dmesg shows the following:

[drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!

I did some minimal digging and its supposed to be related to the i915 driver and it hasn't been fixed yet.

---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend new file +11 -0
new file mode 100644
index 0000000..b667892
@@ -0,0 +1,11 @@
+KBRANCH_genericx86  = "standard/base"
+KBRANCH_genericx86-64  = "standard/base"
+
+KMACHINE_genericx86 ?= "common-pc"
+KMACHINE_genericx86-64 ?= "common-pc-64"
+
+SRCREV_machine_genericx86    ?= "57af322eecf5750f8f09cb8b093d613caede5c48"
+SRCREV_machine_genericx86-64 ?= "57af322eecf5750f8f09cb8b093d613caede5c48"
+
+COMPATIBLE_MACHINE_genericx86 = "genericx86"
+COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
Signature · 1 line
2.1.4
#1 lore raw
Quoted 5 lines · Alejandro Hernandez

The only issue I found was on poky-lsb - genericx86-64 using kernel 4.4 dmesg shows the following:

[drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!

If I merge this, am I going to start seeing autobuilder failures and QA reports about this?

What do we plan to do about that?

Cheers,

Richard

#2 lore raw
Quoted 10 lines · Richard Purdie
Quoted 5 lines · Alejandro Hernandez

The only issue I found was on poky-lsb - genericx86-64 using kernel 4.4 dmesg shows the following:

[drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!

If I merge this, am I going to start seeing autobuilder failures and QA reports about this?

What do we plan to do about that?

This is supposed to be a minor bug, and will not cause any major problems, plus I went ahead and tested on poky-lsb, the error only shows up on lsb on the 64 bit NUC, and lsb wont use kernel 4.4 until later, so no AB or QA failures as far as I know.

Quoted 4 lines

Cheers,

Richard