Posts: 530
Threads: 26
Joined: Feb 2015
Reputation:
0
This error started showing up at boot time after updating to the 4.1.0 kernel but It would go by so fast I could never make out what it was. After much searching I was able to find it in the syslog, I have updated to the new 4.1.1 kernel but it still shows up at boot. I have not noticed any difference in my system performance, but I thought it may be affecting something I don't normally use, so I decided to report the problem to the team.
“I have not failed. I’ve just found 10,000 ways that won’t work.” - Thomas Edison
Posts: 8,937
Threads: 559
Joined: Feb 2014
Reputation:
5
After a bit of research, looks like a bug that hasn't been squashed yet.
Posts: 530
Threads: 26
Joined: Feb 2015
Reputation:
0
I read on one site that it was a kernel bug that had been fixed but has resurfaced in the newer kernels. I am sure one of the next few kernels will take care of it, from what I found it is on a lot of systems.
“I have not failed. I’ve just found 10,000 ways that won’t work.” - Thomas Edison
Posts: 8,937
Threads: 559
Joined: Feb 2014
Reputation:
5
Is there something in the newer kernels you require?
Posts: 530
Threads: 26
Joined: Feb 2015
Reputation:
0
Probably not, I just thought I would test them on this old netbook.
“I have not failed. I’ve just found 10,000 ways that won’t work.” - Thomas Edison
Posts: 530
Threads: 26
Joined: Feb 2015
Reputation:
0
Rolling back to the originally installed kernel fixed this issue.
“I have not failed. I’ve just found 10,000 ways that won’t work.” - Thomas Edison
![[Image: X5qGkCg.png]](https://imgur.com/X5qGkCg.png)
![[Image: 0op1GNe.png]](https://i.imgur.com/0op1GNe.png)
![[Image: LgJ2mtP.png]](https://i.imgur.com/LgJ2mtP.png)
![[Image: vLZcFUE.png]](https://imgur.com/vLZcFUE.png)
![[Image: lrUHro3.jpg]](https://i.imgur.com/lrUHro3.jpg)