Most recent kernel where this bug did not occur: 2.6.20 Distribution: Gentoo 2007 Hardware Environment: lspci output: 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] (rev 36) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) Software Environment: kernel: Linux tux 2.6.22 #2 Sun Aug 5 02:10:48 HKT 2007 i686 Intel(R) Pentium(R) 4 CPU 2.93GHz GenuineIntel GNU/Linux and lsmod: Module Size Used by parport_pc 36516 0 parport 36296 1 parport_pc nvidia 7242420 18 ata_generic 8068 0 sis5513 13320 0 [permanent] generic 5380 0 [permanent] psmouse 39568 0 serio_raw 7556 0 sr_mod 16932 0 cdrom 37280 1 sr_mod sd_mod 29968 4 ext3 131080 0 mbcache 8836 1 ext3 jbd 54056 1 ext3 scsi_wait_scan 1792 0 sata_sis 9476 0 pata_sis 14596 4 sata_sis libata 126772 3 ata_generic,sata_sis,pata_sis usbhid 28768 0 ohci_hcd 22276 0 uhci_hcd 25872 0 usb_storage 72128 0 scsi_mod 145288 5 sr_mod,sd_mod,scsi_wait_scan,libata,usb_storage hid 27776 1 usbhid Problem Description:the sis5513 and generic modules are permanent, I just want to builtin them in the kernel image, but if I rebuild it with all these modules options builtin, the new vmlinuz will panic, that it cannot find the block device. Indeed I have the IDE disk, but pata_sis saw it as a SCSI disk, thus it can work well with these modules, why it cannot work when they are in the vmlinuz? Steps to reproduce: a normal sis5513 system with modules work well, but that vmlinuz rebuilt with all these module builtin would eventually panic.
Is this still a prolem?
I'm closing this bug, please re-open if it still happens with the recent kernels.