# extra tests on tree/branch linus/master # extra tests on tree/branch drm-intel/topic/core-stuff Git bisect bad 7bf2844ed14de049a4ccec26eb3d8b4c3d5c1971 # 07:13 0- 12 drm/fb-helper: Propagate errors from initial config failure
# extra tests on HEAD of drm-intel/topic/core-stuff # first bad commit: drm/fb-helper: Propagate errors from initial config failure idr_remove called for id=20 which is not allocated. cirrus 0000:00:02.0: Fatal error during modeset init: -22 | backtrace:spi_register_driver | 0 | 1 | 1 | | backtrace:_gameport_register_driver | 0 | 1 | 1 | | backtrace:hanwang_driver_init | 0 | 2 | 2 | | backtrace:usb_register_driver | 0 | 2 | 2 | | backtrace:i2c_register_driver | 0 | 5 | 5 | | backtrace:kernel_init_freeable | 0 | 12 | 12 | | backtrace:_pci_register_driver | 0 | 12 | 12 | | Kernel_panic-not_syncing:softlockup:hung_tasks | 0 | 11 | 11 | Judging from the kernel boot hang timestamps, that looks like an noise. To propagate errors further rather than just ignore them.Īttached dmesg for the parent commit, too, to help confirm whether it is a noise error. That the error can be properly propagated. Make drm_fb_helper_initial_config() return an int rather than a bool so To: Thierry Reding +Cc: Daniel Vetter, LKP, dri-devel, linux-kernelĠday kernel testing robot got the below dmesg and the first bad commit is 2:04 ` BUG: unable to handle kernel paging request at 95d24c70 Fengguang WuĠ siblings, 1 reply 3+ messages in thread
#Cant boot from ahci cdrom drive using bochs in debian archive
WARNING: CPU: 1 PID: 1 at lib/idr.c:506 idr_remove() LKML Archive on help / color / mirror / Atom feed * WARNING: CPU: 1 PID: 1 at lib/idr.c:506 idr_remove() 17:03 Fengguang Wu
0 kommentar(er)
