Hello,
From kernel 1432 and 1433 in rawhide my boot process has some serious
delays where my system doesn't seem to do anything and doesn't respond. This also happens when logining in and starting gnome. I made a bootchart from the 1426 kernel which runs fine and one form 1433 which suffers from those delays. http://files.zoeloelip.be/1426.png http://files.zoeloelip.be/1433.png
Bart
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
From kernel 1432 and 1433 in rawhide my boot process has some serious
delays where my system doesn't seem to do anything and doesn't respond. This also happens when logining in and starting gnome. I made a bootchart from the 1426 kernel which runs fine and one form 1433 which suffers from those delays. http://files.zoeloelip.be/1426.png http://files.zoeloelip.be/1433.png
Looks like there's a 30 second process of just insmod, unless it's grouping them. If you could track down what driver is being silly, that could help a lot.
Bill
Bill Nottingham wrote:
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
From kernel 1432 and 1433 in rawhide my boot process has some serious
delays where my system doesn't seem to do anything and doesn't respond. This also happens when logining in and starting gnome. I made a bootchart from the 1426 kernel which runs fine and one form 1433 which suffers from those delays. http://files.zoeloelip.be/1426.png http://files.zoeloelip.be/1433.png
Looks like there's a 30 second process of just insmod, unless it's grouping them. If you could track down what driver is being silly, that could help a lot.
Bill
Is there an easy way to do this? Or just trying? Maybe you see some drivers that has changed which causes this problem, here's me lsmod output: Module Size Used by parport_pc 28933 1 lp 13001 0 parport 40713 2 parport_pc,lp sunrpc 170756 1 powernow_k8 15945 0 dm_mod 58077 0 video 15941 0 button 6609 0 battery 9413 0 asus_acpi 11093 0 ac 4805 0 wacom 13505 0 ipv6 268033 10 ohci1394 41353 0 ieee1394 305209 1 ohci1394 yenta_socket 22989 0 rsrc_nonstatic 13249 1 yenta_socket pcmcia_core 42857 2 yenta_socket,rsrc_nonstatic ohci_hcd 26721 0 ehci_hcd 40653 0 i2c_nforce2 7233 0 i2c_core 21185 1 i2c_nforce2 snd_intel8x0m 18821 0 shpchp 94277 0 snd_intel8x0 34817 1 snd_ac97_codec 79165 2 snd_intel8x0m,snd_intel8x0 snd_seq_dummy 3653 0 snd_seq_oss 37057 0 snd_seq_midi_event 8256 1 snd_seq_oss snd_seq 62289 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 8781 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 51313 0 snd_mixer_oss 17857 1 snd_pcm_oss snd_pcm 99017 4 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pc m_oss snd_timer 33605 2 snd_seq,snd_pcm snd 56901 12 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_s eq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 10913 1 snd snd_page_alloc 10313 3 snd_intel8x0m,snd_intel8x0,snd_pcm sk98lin 176801 0 skge 38737 0 joydev 9601 0 xfs 592241 2 exportfs 8897 1 xfs sata_nv 9669 0 libata 47817 1 sata_nv sd_mod 20929 0 scsi_mod 147369 2 libata,sd_mod
Bart
Bill Nottingham wrote:
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
From kernel 1432 and 1433 in rawhide my boot process has some serious
delays where my system doesn't seem to do anything and doesn't respond. This also happens when logining in and starting gnome. I made a bootchart from the 1426 kernel which runs fine and one form 1433 which suffers from those delays. http://files.zoeloelip.be/1426.png http://files.zoeloelip.be/1433.png
Looks like there's a 30 second process of just insmod, unless it's grouping them. If you could track down what driver is being silly, that could help a lot.
Bill
Hello,
I finally found the problem. It's caused by the battery acpi module. I searched for insmod in rc.sysinit and there is only one part that uses insmod instead of modprobe. When I change this into modprobe my system boots normal and haldeamon starts. But the battery-applet doesn't work. I tried to do /sbin/insmod battery.ko and it takes a long time to finish. Hal crashes when I boot with a new kernel. I now move the battery.ko module out the acpi directory, this way I can boot in a normal way but the battery applet doesn't work of course.
What should I do now?
Cheers,
Bart
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
I finally found the problem. It's caused by the battery acpi module. I searched for insmod in rc.sysinit and there is only one part that uses insmod instead of modprobe. When I change this into modprobe my system boots normal and haldeamon starts. But the battery-applet doesn't work. I tried to do /sbin/insmod battery.ko and it takes a long time to finish. Hal crashes when I boot with a new kernel. I now move the battery.ko module out the acpi directory, this way I can boot in a normal way but the battery applet doesn't work of course.
What should I do now?
You can file a kernel bug about the battery driver, although it's probably related to something funky in your BIOS as well.
Bill
On Fri, Aug 05, 2005 at 10:46:03AM -0400, Bill Nottingham wrote:
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
I finally found the problem. It's caused by the battery acpi module. I searched for insmod in rc.sysinit and there is only one part that uses insmod instead of modprobe. When I change this into modprobe my system boots normal and haldeamon starts. But the battery-applet doesn't work. I tried to do /sbin/insmod battery.ko and it takes a long time to finish. Hal crashes when I boot with a new kernel. I now move the battery.ko module out the acpi directory, this way I can boot in a normal way but the battery applet doesn't work of course.
What should I do now?
You can file a kernel bug about the battery driver, although it's probably related to something funky in your BIOS as well.
There are a number of kernel bugs open on the acpi battery stuff already. https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=165150
Chances are this is a dupe of one of them.
Dave
Dave Jones wrote:
On Fri, Aug 05, 2005 at 10:46:03AM -0400, Bill Nottingham wrote:
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
I finally found the problem. It's caused by the battery acpi module. I searched for insmod in rc.sysinit and there is only one part that uses insmod instead of modprobe. When I change this into modprobe my system boots normal and haldeamon starts. But the battery-applet doesn't work. I tried to do /sbin/insmod battery.ko and it takes a long time to finish. Hal crashes when I boot with a new kernel. I now move the battery.ko module out the acpi directory, this way I can boot in a normal way but the battery applet doesn't work of course.
What should I do now?
You can file a kernel bug about the battery driver, although it's probably related to something funky in your BIOS as well.
There are a number of kernel bugs open on the acpi battery stuff already. https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=165150
Chances are this is a dupe of one of them.
Dave
Ok. But must of them are quite old. Mine only appeared after kernel 1426 which I think is post 2.6.13-rc2. I don't know how to search for changes in the kernel source. I'm not familiar with git. I search the kernel changelog but I can't find anything about the battery module. If you need more information, just let me know.
Bart
Bart Vanbrabant wrote:
Dave Jones wrote:
On Fri, Aug 05, 2005 at 10:46:03AM -0400, Bill Nottingham wrote:
Bart Vanbrabant (bart.vanbrabant@zoeloelip.be) said:
I finally found the problem. It's caused by the battery acpi module. I searched for insmod in rc.sysinit and there is only one part that uses insmod instead of modprobe. When I change this into modprobe my system boots normal and haldeamon starts. But the battery-applet doesn't work. I tried to do /sbin/insmod battery.ko and it takes a long time to finish. Hal crashes when I boot with a new kernel. I now move the battery.ko module out the acpi directory, this way I can boot in a normal way but the battery applet doesn't work of course.
What should I do now?
You can file a kernel bug about the battery driver, although it's probably related to something funky in your BIOS as well.
There are a number of kernel bugs open on the acpi battery stuff already. https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=165150
Chances are this is a dupe of one of them.
DaveOk. But must of them are quite old. Mine only appeared after kernel 1426 which I think is post 2.6.13-rc2. I don't know how to search for changes in the kernel source. I'm not familiar with git. I search the kernel changelog but I can't find anything about the battery module. If you need more information, just let me know.
Bart
rc5-git3 solved the problem. The 1451 version from rawhide fixed it. Thanks for the help
Bart
-
Bart Vanbrabant -
Bill Nottingham -
Dave Jones