![]() 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 │ │ ├── │ ├── │ ├── │ ├── │ ├── eo.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 I can take a picture of this error if this is useful. but I am afraid that it will mess up my existing setup even more overwriting GRUB. I had to change the path accordingly since they seem to be different in Windows 10, but the new menu entry does not work: I get an error saying that I should use the Windows disk and fix problems. ![]() I tried to do what is suggested here: … menu_entry Therefore I assume the problem is caused by having two drives.Īs you can see from the output above, I *do not* have an EFI system partition on the HDD, only on the SSD. ![]() I did the same thing on another PC except everything was on the same disk, and it worked, meaning os-prober was able to detect Windows. ![]() Sector size (logical/physical): 512 bytes / 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes ![]()
0 Comments
Leave a Reply. |