Bug 150911 - i2c_designware 808622C1:06: punit semaphore timed out, resetting
Summary: i2c_designware 808622C1:06: punit semaphore timed out, resetting
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: I2C (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Drivers/I2C virtual user
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-01 21:47 UTC by Filipp Andjelo
Modified: 2016-09-01 14:57 UTC (History)
4 users (show)

See Also:
Kernel Version: 4.6.4
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg, see from 8.684792 (107.15 KB, text/x-log)
2016-08-01 21:47 UTC, Filipp Andjelo 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Filipp Andjelo 2016-08-01 21:47:35 UTC 
Created attachment 227211 [details]
dmesg, see from 8.684792

Chuwi HiBook Tablet (Model CWI514) Cherry Trail

i2c_designware 808622C1:06: couldn't acquire bus ownership
i2c_designware: probe of 808622C1:06 failed with error -110
Comment 1 [account disabled by the administrator] 2016-08-18 07:00:31 UTC 
First thing is try a newer kernel but also if those other warnings are still open, please open bug reports for them. I will fix those after this if it still occurs on a newer kernel release like 4.8 rc2.
Comment 4 Filipp Andjelo 2016-08-31 19:45:11 UTC 
Was not even able to boot with 4.8 rc3 (and rc2), getting "task ... blocked for more than 120 sec" all the time. System is very unresponsive and in dmesg I have a lot of stacktraces. When going back to 4.7.x everything is fine. I'm not sure what to do now. I am new to it, but is there any IRC channel I could get some sort of help? Any advice?
Comment 5 tagorereddy 2016-09-01 14:50:37 UTC 
I have same problem with my laptop. The bug is #155241. I think I'll mark the bug as duplicate to yours. I've tried and tested the bug all the way from 4.6 to 4.8-rc3 kernels. All produce the same result as this. This problem has been around for quite some time going back to 2014. The issue exists in baytrail based SOCs too. There were few patches pushed upstream to fix the issue in 2015, but none seem to work.
Comment 6 tagorereddy 2016-09-01 14:57:26 UTC 
There's the bug #150481 reporting the same issue.
Note You need to log in before you can comment on or make changes to this bug.