kernel test robot xiaolong.ye@intel.com writes:
FYI, we noticed the following commit:
commit: f04f7e3e041aab12abbf3ed7b854446af5a624a9 ("drm: bochs: Don't remove uninitialized fbdev framebuffer") url: https://github.com/0day-ci/linux/commits/Gabriel-Krisman-Bertazi/drm-bochs-D... base: git://git.kraxel.org/linux drm-qemu
in testcase: trinity with following parameters:
runtime: 300s
test-description: Trinity is a linux system call fuzz tester. test-url: http://codemonkey.org.uk/projects/trinity/
on test machine: qemu-system-x86_64 -enable-kvm -m 512M
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
Problem is: register_framebuffer() fails with this config because of reasons, as show by this line:
[ 9.937917] bochsdrmfb: enable CONFIG_FB_LITTLE_ENDIAN to support this framebuffer
which causes drm_fb_helper_initial_config() to error out and call drm_fb_helper_fini(0 in the bochs_fbdev_init() error path. Also, since the kernel has CONFIG_DEBUG_TEST_DRIVER_REMOVE, it tries to remove the device in sequence, making a second call to drm_fb_helper_fini, because we didn't unset the initialized flag. I'll get a patch for this first thing tomorrow morning.