Beelink BTC Pro: crashes under Ubuntu 18.04

elboertjie

As can be seen from the syslog crash log, this error caused my Ubuntu system to shutdown.  Thankfully gracefully, but still stopped it completely.

The system is running 24/7 with no human interaction that could trigger this.  


Any ideas on how to fix this?

Is it a matter of finding a specific updated driver for Ubuntu for this hardware?

1. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.328870] CPU: 3 PID: 432 Comm: systemd-journal Tainted: G        W         4.18.0-18-generic #19~18.04.1-Ubuntu
   
2. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.328876] Hardware name: Beelink BT3 PRO/BT3 PRO, BIOS 5.11 02/23/2019
   
3. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.328892] RIP: 0010:baytrail_i2c_acquire+0x179/0x230
   
4. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.328896] Code: 4d c8 44 89 ea be 10 00 00 00 bf 04 00 00 00 e8 9d 54 8a ff 85 c0 75 54 8b 55 c8 48 8b 3b 48 c7 c6 67 bd 19 94 e8 d7 14 ea ff <0f> 0b 41 b8 92 ff ff ff 48 8b 5d d0 65 48 33 1c 25 28 00 00 00 44
   
5. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329116] RSP: 0018:ffffb36e80a43970 EFLAGS: 00010282
   
6. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329128] RAX: 0000000000000000 RBX: ffff9d1aae8a4018 RCX: 0000000000000006
   
7. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329134] RDX: 0000000000000000 RSI: 0000000000000092 RDI: ffff9d1abfd964b0
   
8. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329141] RBP: ffffb36e80a439b0 R08: 00000000000011ca R09: 0000000000000004
   
9. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329148] R10: 0000000000000000 R11: ffffffff9498a80f R12: 000000011c3b1a43
   
10. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329155] R13: 000000000000010e R14: ffffffff9419bc78 R15: 000000011c3b19c6
    
11. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329165] FS:  00007fcf2b9c7940(0000) GS:ffff9d1abfd80000(0000) knlGS:0000000000000000
    
12. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329172] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    
13. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329179] CR2: 00007f8e7eda8000 CR3: 000000016d806000 CR4: 00000000001006e0
    
14. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329185] Call Trace:
    
15. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329210]  i2c_dw_acquire_lock+0x22/0x50
    
16. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329224]  i2c_dw_xfer+0x82/0x260
    
17. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329236]  __i2c_transfer+0x119/0x420
    
18. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329248]  ? _cond_resched+0x19/0x40
    
19. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329259]  i2c_transfer+0x5e/0xf0
    
20. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329271]  regmap_i2c_read+0x6d/0xa0
    
21. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329286]  _regmap_raw_read+0xac/0x1f0
    
22. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329296]  ? regmap_i2c_smbus_i2c_write+0x30/0x30
    
23. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329307]  ? _regmap_raw_read+0xac/0x1f0
    
24. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329319]  _regmap_bus_read+0x37/0x70
    
25. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329331]  _regmap_read+0x6a/0x130
    
26. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329340]  ? _cond_resched+0x19/0x40
    
27. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329352]  regmap_read+0x3f/0x70
    
28. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329372]  fuel_gauge_reg_readb.isra.3+0x40/0x90 [axp288_fuel_gauge]
    
29. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329388]  fuel_gauge_get_property+0x10b/0x3b3 [axp288_fuel_gauge]
    
30. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329401]  power_supply_get_property+0x1f/0x40
    
31. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329412]  power_supply_show_property+0xa3/0x2f0
    
32. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329425]  power_supply_uevent+0x116/0x240
    
33. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329438]  dev_uevent+0xba/0x2e0
    
34. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329455]  ? kmem_cache_alloc_trace+0x1b0/0x1c0
    
35. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329468]  ? uevent_show+0x88/0x100
    
36. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329481]  uevent_show+0xa8/0x100
    
37. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329494]  dev_attr_show+0x21/0x50
    
38. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329507]  sysfs_kf_seq_show+0x9f/0x130
    
39. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329517]  kernfs_seq_show+0x27/0x30
    
40. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329528]  seq_read+0xe5/0x430
    
41. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329541]  kernfs_fop_read+0x137/0x180
    
42. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329554]  ? security_file_permission+0xa0/0xb0
    
43. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329569]  __vfs_read+0x1b/0x40
    
44. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329581]  vfs_read+0x8e/0x130
    
45. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329591]  ksys_read+0x55/0xc0
    
46. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329602]  __x64_sys_read+0x1a/0x20
    
47. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329616]  do_syscall_64+0x5a/0x120
    
48. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329629]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
    
49. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329640] RIP: 0033:0x7fcf2b4e20b4
    
50. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329643] Code: c3 0f 1f 44 00 00 41 54 55 49 89 d4 53 48 89 f5 89 fb 48 83 ec 10 e8 3b 06 02 00 4c 89 e2 41 89 c0 48 89 ee 89 df 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 77 06 02 00 48
    
51. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329862] RSP: 002b:00007ffc552dc860 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
    
52. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329874] RAX: ffffffffffffffda RBX: 00000000000000a6 RCX: 00007fcf2b4e20b4
    
53. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329881] RDX: 0000000000001000 RSI: 000055c907173c40 RDI: 00000000000000a6
    
54. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329887] RBP: 000055c907173c40 R08: 0000000000000000 R09: 0000000000000000
    
55. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329894] R10: 000055c90701e010 R11: 0000000000000246 R12: 0000000000001000
    
56. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329900] R13: 0000000000001001 R14: 0000000000000d68 R15: 0000000000001001
    
57. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329913] ---[ end trace 7de48589e1416166 ]---
    
58. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329927] i2c_designware 808622C1:06: couldn't acquire bus ownership
    
59. Jun 22 19:23:04 mypc-BT3-PRO kernel: [1894839.329953] axp288_fuel_gauge axp288_fuel_gauge: axp288 reg read err:-110
    
60. 
    

Copy the Code

beelink

Ubuntu 18.04 version driver, you can try to install

https://beelink-my.sharepoint.co ... 4fw0iD4HHQ?e=lHEOTg