0
kissste

H6 after apt upgrade

Recommended Posts

My PineH64, as well as OrangePI one plus (H6) were working fine using 4.18.rc7-bionic till I have tried apt upgrade

 

I'm getting the following error on both.

 

Any ideas? Thank you vm

Starting kernel ...

[    2.104055] Internal error: Oops: 96000004 [#1] SMP
[    2.108938] Modules linked in:
[    2.111997] CPU: 1 PID: 33 Comm: kworker/1:1 Not tainted 4.19.11-sunxi64 #5.67.181221
[    2.119819] Hardware name: Pine H64 (DT)
[    2.123750] Workqueue: events deferred_probe_work_func
[    2.128887] pstate: 80000005 (Nzcv daif -PAN -UAO)
[    2.133679] pc : sun8i_dwmac_probe+0x16c/0x550
[    2.138121] lr : sun8i_dwmac_probe+0x21c/0x550
[    2.142560] sp : ffff00000924bb00
[    2.145871] x29: ffff00000924bb00 x28: 0000000000000000 
[    2.151181] x27: ffff000008d7e9a0 x26: ffff000008bf1b20 
[    2.156491] x25: ffff800077fe1b88 x24: ffff000008c45000 
[    2.161800] x23: ffff800075167c10 x22: ffff800075167c00 
[    2.167110] x21: ffff800009b88018 x20: ffff8000099ede18 
[    2.172419] x19: ffff000008d68000 x18: 0000000000008000 
[    2.177728] x17: 0000000000000001 x16: 0000000000000019 
[    2.183037] x15: 00000000fffffff0 x14: ffff000008c83000 
[    2.188347] x13: 6572206f74207265 x12: 0000000000000030 
[    2.193656] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f 
[    2.198965] x9 : feff727264626260 x8 : ffff00000924b7c8 
[    2.204275] x7 : 0000000000000000 x6 : 0000000000000003 
[    2.209584] x5 : 0000000000000002 x4 : 0000000000000003 
[    2.214893] x3 : 0000000000000000 x2 : ffff00000924bb70 
[    2.220203] x1 : ffff800009b88400 x0 : ffff800075167c10 
[    2.225516] Process kworker/1:1 (pid: 33, stack limit = 0x(____ptrval____))
[    2.232472] Call trace:
[    2.234921]  sun8i_dwmac_probe+0x16c/0x550
[    2.239019]  platform_drv_probe+0x50/0xa0
[    2.243029]  really_probe+0x1c4/0x298
[    2.246692]  driver_probe_device+0x58/0x100
[    2.250875]  __device_attach_driver+0x98/0xf0
[    2.255231]  bus_for_each_drv+0x64/0xc8
[    2.259067]  __device_attach+0xd8/0x130
[    2.262902]  device_initial_probe+0x10/0x18
[    2.267084]  bus_probe_device+0x90/0x98
[    2.270920]  deferred_probe_work_func+0x74/0xb0
[    2.275452]  process_one_work+0x1e4/0x360
[    2.279462]  worker_thread+0x268/0x4b0
[    2.283212]  kthread+0x128/0x130
[    2.286442]  ret_from_fork+0x10/0x1c
[    2.290019] Code: f9401283 9101c3a2 aa1703e0 f9400463 (a9401464) 
[    2.296109] ---[ end trace 5d7d5a8453aae6f4 ]---
[    2.301096] sunxi-mmc 4020000.mmc: Got CD GPIO
[    2.327072] sunxi-mmc 4022000.mmc: initialized, max. request size: 2048 KB
[    2.330897] sunxi-mmc 4020000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[    2.391260] mmc0: host does not support reading read-only switch, assuming write-enable
[    2.402549] mmc0: Problem switching card into high-speed mode!
[    2.408501] mmc0: new SDHC card at address 0001
[    2.413921] mmcblk0: mmc0:0001 SD 29.1 GiB 
[    2.419970]  mmcblk0: p1
[    2.488162] mmc1: new high speed MMC card at address 0001
[    2.494443] mmcblk1: mmc1:0001 NCard  14.5 GiB 
[    2.499686] mmcblk1boot0: mmc1:0001 NCard  partition 1 4.00 MiB
[    2.506308] mmcblk1boot1: mmc1:0001 NCard  partition 2 4.00 MiB
[    2.513295]  mmcblk1: p1

 

Share this post


Link to post
Share on other sites

Known issue.

 

Go back to 4.18.0-rc7 and freeze kernel until solved or build your own kernel with all the stuff needed and disable on board Ethernet and use USB-Ethernet adapter.

 

Interesting to know though that other boards are affected too.

 

Share this post


Link to post
Share on other sites
(edited)

And what would be the recommended way to go back to a previous version (without starting from scratch) (Quite sure this is somewhere in a FAQ, but I had no luck finding it)

Edited by johanvdw

Share this post


Link to post
Share on other sites
On 12/24/2018 at 12:52 PM, Werner said:

Known issue.

 

Go back to 4.18.0-rc7 and freeze kernel until solved or build your own kernel with all the stuff needed and disable on board Ethernet and use USB-Ethernet adapter.

 

Interesting to know though that other boards are affected too.

 

why do you update the kernel in an image if you know it causes errors? why are there 6 images on your site and they all don't work? how do you conduct testing?:wacko:

people spend days trying to compile the firmware, and as a result nothing works and it turns out that this is a "known problem" that is not solved. put on the site the last image 4.17 instead of 5.1, where there is no problem.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
0