Re: INFO: task blocked for more than 120 seconds.
Good day, Someone in our local LUG recently posed about this, he was seeing Jul 21 07:39:04 linux kernel: INFO: task mount:5258 blocked for more than 120 seconds. Jul 21 07:39:04 linux kernel: echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jul 21 07:39:04 linux kernel: mount D 0002 0 / 5258 4842 0x0080 Jul 21 07:39:04 linux kernel: 880037b4fb28 0082 / 880037b4fa78 812d6ea0 Jul 21 07:39:04 linux kernel: 880037b4fad8 812ef2f9 / 880037b4ffd8 880037b4ffd8 He found a solution: Googling around suggests that it might be a recurrent kernel bug (as it appears to come and go between versions) and that it might be related to the method the kernel uses to idle the processor. The most power-efficient technique is to use the MWAIT instruction, which is the default on systems that support it. The least power-efficient (and most performant) is use a polling idle loop. In between is to use the HALT instruction. Since starting to boot my kernel with idle=halt (and pcie_aspm=off, FWIW, but I don't think my system was using it anyway), I haven't had any recurrance. Does that help?
Re: stopping dm-* modules and associated files from loading at boot
On Tue, Aug 31, 2010 at 10:54 PM, g gel...@bellsouth.net wrote: On 09/01/2010 05:10 AM, Akemi Yagi wrote: snip I understand mkinitrd would not honor the options if the system sees certain hardware. from where do you get this? to my knowledge, i have in/on/around this system box to give any indication of raid. I don't remember where I saw the description about the omit options. In any event, that approach apparently did not work for you. The unpacking/repacking method is a sure way to remove modules from the .img file. Your system might fail to boot but it is worth a try if you wish to experiment. Akemi
Re: stopping dm-* modules and associated files from loading at boot
On 09/01/2010 03:17 PM, Akemi Yagi wrote: snip I don't remember where I saw the description about the omit options. ok. In any event, that approach apparently did not work for you. very true. The unpacking/repacking method is a sure way to remove modules from the .img file. Your system might fail to boot but it is worth a try if you wish to experiment. have never done such, but that is what i like about computers and linux. always something new to learn. boot failure is not a problem. i have 3 kernels loaded to fall back to. this is a triple boot box, so i can also use 1 of other 2 to restore old init*.img. yes, i always backup a file before fiddling. learned that in early s100 days. if manual removal does not work, i will probably use yum to remove raid software. just might be that is what i should have done to start. again, thanks for your help. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature
