gnawty: hangs at boot with experiment-4.4 |
||||||
Issue descriptionTesting FFU on 4.4, I stumble upon hang to boot, without FFU being triggered. I built my changes on top of b209e516a943a10860186598affe80fef992454e It does not happen at every boot: [ 6.456141] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6.588855] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 6.597523] asix 1-2.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 11.567316] init: failsafe-delay main process (1052) killed by TERM signal [ 11.575053] BUG: unable to handle kernel paging request at ffffc9007ca3700b
,
Apr 8 2016
Looking at samus? I know there are some known frecon issues, see issue 598853 . I'm not sure we should be getting a full-on "hang" though.
,
Apr 8 2016
Oh, of course you're not using samus. It's in the $subject. But this still may be simply due to missing DRM patches.
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 13 2018
Baytrail all switched to 4.4, so I bet it's working now ;) |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by gwendal@chromium.org
, Mar 31 201698.8 KB
98.8 KB Download