I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting. Regards, Nick.
On Thursday 21 Oct 2004 16:45 pm, Nicholas Moir wrote:
I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting.
It might help if you could tell us whatthe panic actually is Dylan
Regards,
Nick.
-- "I see your Schwartz is as big as mine" -Dark Helmet
On Thursday 21 October 2004 11:45, Nicholas Moir wrote:
I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting.
Are you sure that is really the problem? Sounds more like something is missing from your initrd or some other boot type of problem. <arm-chair quarterback mode>
On Thursday, 21 October 2004 17.45, Nicholas Moir wrote:
I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting.
I agree with the other two replies; however, if you really want to go through the (therapeutic?) labour of stripping out suse patches, have a look at the src.rpm for the kernel you're using. It has the patches that have been applied to it, which you can patch -R at your leisure But as has been said, I suspect there will be a simpler way of solving it by examining the actual error you get
On Thursday 21 October 2004 16:45, Nicholas Moir wrote:
I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. imo it's a result of an incomplete kernel installation. usually, a "make install" does everything for you (builds the kernel image, modules, and takes care of the initrd stuff). However, try (from Suse's kernel) to have a look at the inird image (or try to run initrd yourself and see which modules does it add...)
Another thing might be that SuSE's .config includes the kernel tag/label and make may think the modules are already compiled. You should try edit "Build options" and pick up a different config name/release number combination. Then run make clean and rebuild.
Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting. I don't think there's an easy way to do that. you can do a diff between the two kernels though (but may result in a rather large file...)
Cheers, L
Nicholas Moir wrote:
I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting.
Regards,
Nick.
Which kernel? 2.6.9 is up running here on 9.1 x86 and x86_64. You could try acpi=off, apm=off, pci=noacpi, lnoapic as boot options. I thought of mkinitrd, but that is likely to cause a different problem, like modules not loaded. If you have another box handy + serial port, crossover cable and kermit/gtkterm/cutecom or hyperterminal on windows, you can capture the full panic with boot option "console=ttyS?" and mail it to the kernel mailing list. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
On Thu, 2004-10-21 at 16:45, Nicholas Moir wrote:
I have a host which will only boot with the patched SUSE kernel, a vanilla kernel using the SUSE .config results in a kernel panic. Is there a way of stripping out the SUSE patches individually, so I can find out which patch is responsible for the machine booting.
Thanks for the replies. Here is the panic text from kernel 2.4.24, using the same .config as the SUSE kernel: reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ataraid(114,2))... for (ataraid(114,2)) is_tree_node: node level 10799 does not match to the expected one 4 ataraid(114,2):vs-5150:search_by_key: invalid format found in block 521998. Fsck? ataraid(114,2):vs-13070:reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1 2 0x0 SD] ataraid(114,2):Using r5 hash to sort names VFS:Cannot open root device "ataraid/d0p2" or 72:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 72:02 Thanks.
participants (6)
-
Anders Johansson -
Bruce Marshall -
Dylan -
Laur Ivan -
Nicholas Moir -
Sid Boyce