Re: Kernel Panic Help
bsquared wrote: Hello, Can anyone recommend some resources for troubleshooting a kernel panic. I have been built LFS 6.8 on a USB stick, and moved it to a disk partition using 'dd'. I modified the grub.cfg file and rebooted. Then got a kernel panic. Doh! I forgot that I changed the root parameter in grub.cfg to use UUID. Thanks for the quick replies. -Brian -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: 2.6.39 - mount /dev/fd0 no longer works
Hello All, IMPORTANT UPDATE (very good news!!) As of 06/03/2011 12:34:00 AM (German time), my issue was removed by the new 2.6.39.1 release. As soon as I reached line 3502 (of 4164 overall) in reading the ChangeLog-2.6.39.1: block: always allocate genhd-ev if check_events is implemented, I knew my dear floppies would start whirring again like in the old times. I thank and acknowledge all the tireless and dedicated people who kept my problem (oops, issue) under wraps until working unfailingly again (as it did for the past 25 years or so). It comforts one beyond words to see the code of omerta still respected in certain circles, in these hectic and uncertain times. Hopefully, this attitude to extract the foot from our mouth as delicately and as quietly as it was inserted therein should always remain the basic principle in our lives. The enemy must NEVER find out about our little, _private_ indiscretions. Use (if you have to) only our secret code-words like genhd-ev above when dealing with them. Thank you very much for the total silence you met this thread with. It warms the cockles of my heart to see there are still people of character around in this wild and crazy world of ours. Thanks again, -- Alex PS 1. I attached the full ChangeLog-2.6.39.1 section covering this. 2. I've been wondering who the enemy is after all. Micro$oft? We're really in trouble then. 3. I was much afraid my OP would trigger yet another side show about who still uses floppies at this day and age. Luckily for me, like I said, omerta is still omerta. -- commit 9206053d7efb79adb564ccf7055342318b22475c Author: Tejun Heo t...@kernel.org Date: Thu May 26 21:06:50 2011 +0200 block: always allocate genhd-ev if check_events is implemented commit 75e3f3ee3c64968d42f4843ec49e579f84b5aa0c upstream. 9fd097b149 (block: unexport DISK_EVENT_MEDIA_CHANGE for legacy/fringe drivers) removed DISK_EVENT_MEDIA_CHANGE from legacy/fringe block drivers which have inadequate -check_events(). Combined with earlier change 7c88a168da (block: don't propagate unlisted DISK_EVENTs to userland), this enables using -check_events() for internal processing while avoiding enabling in-kernel block event polling which can lead to infinite event loop. Unfortunately, this made many drivers including floppy without any bit set in disk-events and -async_events in which case disk_add_events() simply skipped allocation of disk-ev, which disables whole event handling. As -check_events() is still used during open processing for revalidation, this can lead to open failure. This patch always allocates disk-ev if -check_events is implemented. In the long term, it would make sense to simply include the event structure inline into genhd as it's now used by virtually all block devices. Signed-off-by: Tejun Heo t...@kernel.org Reported-by: Ondrej Zary li...@rainbow-software.org Reported-by: Alex Villacis Lasso avill...@ceibo.fiec.espol.edu.ec Signed-off-by: Jens Axboe jax...@fusionio.com Signed-off-by: Greg Kroah-Hartman gre...@suse.de -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Kernel Panic Help
On Fri, Jun 3, 2011 at 10:34 AM, bsquared bwcod...@gmail.com wrote: bsquared wrote: Hello, Can anyone recommend some resources for troubleshooting a kernel panic. I have been built LFS 6.8 on a USB stick, and moved it to a disk partition using 'dd'. I modified the grub.cfg file and rebooted. Then got a kernel panic. Doh! I forgot that I changed the root parameter in grub.cfg to use UUID. Thanks for the quick replies. -Brian -- grub may understand uuid, but the root= line does not. (at least without building a initrd with a bash script inside that does some magic) -- Nathan Coulson (conathan) -- Location: British Columbia, Canada Timezone: PST (-8) Webpage: http://www.nathancoulson.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: setclock Question (lfs-bootscripts-21010424)
On 04/28/2011 03:04 PM, bsquared wrote: Your message reminded me to look into it and here's what I found... excerpt from http://www.linuxfromscratch.org/hints/downloads/files/time.txt; ~ Next are the symlinks. The symlink to run the setclock script is already ~ present in /etc/rc.d/rc.sysinit.d, so the only symlinks we have to create are ~ the ones to run setclock when the system shuts down: ~ ~ # ln -s ../init.d/setclock /etc/rc.d/rc0.d/K45setclock ~ # ln -s ../init.d/setclock /etc/rc.d/rc6.d/K45setclock ~ ~ At this point, the boot scripts are correctly set up and the only thing ~ that's left to configure is the TZ environment variable. However, I do not find /etc/rc.d/rc.sysinit.d. I do find /etc/rc.d/rcsysinit.d, but there is no link to setclock. What is the value/run level for start? Apparently this script was in LFS at some time, I wonder what happened. The script is no longer symlinked in /etc/rc.d/rcsysinit.d/. It is now ran by udevd. There are two rules in /etc/udev/rules.d/55-lfs.rules that run the setclock script during the time of 'udevadm settle'. SUBSYSTEM==rtc, ACTION==add, MODE=0644, RUN+=/etc/init.d/setclock start and KERNEL==rtc, ACTION==add, MODE=0644, RUN+=/etc/init.d/setclock start Nothing is ever displayed on the screen as this script is run by udevd, which has its own display level, not by init, but be assured that if the /dev/rtc file exists, be it a symlink to a device node, or a device node itself, the setclock script has already been run (unless the setclock script is missing or not executable) during the time of the udev script's run in rcsysinit.d. This does not mean that you cannot create the symlinks in RL0 and RL6 to run the script at shutdown. Hope that helps rather than confuses. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: 2.6.39 - mount /dev/fd0 no longer works
On 06/03/2011 09:28 PM, al...@verizon.net wrote: Thank you very much for the total silence you met this thread with. It warms the cockles of my heart to see there are still people of character around in this wild and crazy world of ours. On a related note, it is actually nice to see that someone still cares enough to take the time to write a sarcastic message with some flavor in this day and age! :-) It sure beats the old Thanks for nothing, grumble and leave routine. Due to your choice of writing style, I was unable to tell whether your sarcasm in the above quoted text was directed *at* lfs-support, or simply posted for the enjoyment of the readers. If not, you should understand that this is a volunteer community and that the reasons for silence are many, the most likely being that very few people use floppy drives any longer, making this community, at least, *unable* to assist. Fortunately, there are people upstream working on the kernel that do still use floppies and it was fixed. If your message was not directed *at* this list, only posted for entertainment, please ignore my comment above and know that I did enjoy reading your response right up until I read that last paragraph. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
