2.5 kernel hangs system
Hello,
Ok, i've got a 2.5.68 kernel compilation that when i try to boot it it
hangs the system. It gives me hex codes after it loads the kernel or if i have it load an initrd, it loads that then gives hex codes and stops.
I've got output from lspci -v and my config file at the following url:
www.davemehler.net
Suggestions are desperately needed.
If there's missing information that i should post please let me know and i will post it.
Thanks.
Dave.
Quoted 8 lines · Dave Mehler
Ok, i've got a 2.5.68 kernel compilation that when i try to boot it it
hangs the system. It gives me hex codes after it loads the kernel or if i have it load an initrd, it loads that then gives hex codes and stops.
I've got output from lspci -v and my config file at the following url:
www.davemehler.net
Suggestions are desperately needed.
If there's missing information that i should post please let me know and i will post it.
please post all messages (The "hex-codes").
You may need to readDocumentation/serial-console.txtDocumentation/oops-tracing.txt
if you don't know how to catch them.
Signature · 5 lines
Regards Michael Buesch. http://www.8ung.at/tuxsoft $ cat /dev/zero > /dev/null /dev/null: That's *not* funny! :(
Quoted 12 lines · Dave Mehler
Hello,
Ok, i've got a 2.5.68 kernel compilation that when i try to boot it it
hangs the system. It gives me hex codes after it loads the kernel or if i have it load an initrd, it loads that then gives hex codes and stops.
I've got output from lspci -v and my config file at the following url:
www.davemehler.net
Suggestions are desperately needed.
If there's missing information that i should post please let me know and i will post it.
Thanks.
Dave.
First, I don't understand how as you say, "suggestions are desperately needed" on a developmental kernel. These things are not known to work on all configurations and some information like "It gives me hex codes..." is worthless. Please write down these "hex-codes" and, after booting a version the works, run them through ksymoops. If you don't know what that is:
The latest version can be found in ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops together with patches to other utilities in order to give more accurate Oops debugging.
FYI, after you run the text through ksymoops, you may find that it occurs in a module that you really don't need to load at boot time. Just remove that from initrd and try again.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips). Why is the government concerned about the lunatic fringe? Think about it.
Quoted 6 lines · Richard B. Johnson
First, I don't understand how as you say, "suggestions are desperately needed" on a developmental kernel. These things are not known to work on all configurations and some information like "It gives me hex codes..." is worthless. Please write down these "hex-codes" and, after booting a version the works, run them through ksymoops. If you don't know what that is:
ksymoops? I thought 2.5 kernels didn't need ksymoops anymore and that function names were automatically "guessed" in call stack traces.
Signature · 3 lines
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html Linux Registered User #287198
Quoted 11 lines · Felipe Alfaro Solana
Quoted 6 lines · Richard B. Johnson
First, I don't understand how as you say, "suggestions are desperately needed" on a developmental kernel. These things are not known to work on all configurations and some information like "It gives me hex codes..." is worthless. Please write down these "hex-codes" and, after booting a version the works, run them through ksymoops. If you don't know what that is:
ksymoops? I thought 2.5 kernels didn't need ksymoops anymore and that function names were automatically "guessed" in call stack traces.
IFF you use "include symbols" when building you shouldn't need ksymoops. IMO, if you're using 2.5.x you really should include the symbols - chances are you'll need em.
Signature · 1 line
Murray J. Root
Quoted 9 lines · Felipe Alfaro Solana
Quoted 8 lines · Richard B. Johnson
Quoted 6 lines
First, I don't understand how as you say, "suggestions are desperately needed" on a developmental kernel. These things are not known to work on all configurations and some information like "It gives me hex codes..." is worthless. Please write down these "hex-codes" and, after booting a version the works, run them through ksymoops. If you don't know what that is:
Quoted 7 lines
Quoted 3 lines
ksymoops? I thought 2.5 kernels didn't need ksymoops anymore and that function names were automatically "guessed" in call stack traces.
IFF you use "include symbols" when building you shouldn't need ksymoops. IMO, if you're using 2.5.x you really should include the symbols - chances are you'll need em.
Maybe we are reading this differently, but it sounded to me like the original system hang never reached the kernel | system log and that some hex codes were the only clues. In that case, pushing them thru ksymoops does still make some sense, doesn't it?
How else would you determine where the hang occurred?
~Randy
Quoted 17 lines · Randy.Dunlap
Quoted 9 lines · Felipe Alfaro Solana
Quoted 8 lines · Richard B. Johnson
Quoted 6 lines
First, I don't understand how as you say, "suggestions are desperately needed" on a developmental kernel. These things are not known to work on all configurations and some information like "It gives me hex codes..." is worthless. Please write down these "hex-codes" and, after booting a version the works, run them through ksymoops. If you don't know what that is:
Quoted 7 lines
Quoted 3 lines
ksymoops? I thought 2.5 kernels didn't need ksymoops anymore and that function names were automatically "guessed" in call stack traces.
IFF you use "include symbols" when building you shouldn't need ksymoops. IMO, if you're using 2.5.x you really should include the symbols - chances are you'll need em.
Quoted 6 lines
Maybe we are reading this differently, but it sounded to me like the original system hang never reached the kernel | system log and that some hex codes were the only clues. In that case, pushing them thru ksymoops does still make some sense, doesn't it?
How else would you determine where the hang occurred?
I read it that he was getting an oops with just hex values cause he didn't have the symbols included (note the reference to "it just gives hex codes"). I could be wrong, since I'm only looking at the quote of a quote of someone's interpretation. :) With symbols included an oops DOES print the actual call trace in readable form. (I've seen enough oops to be certain of that :)
Signature · 1 line
Murray J. Root
Quoted 24 lines · Murray J. Root
Quoted 17 lines · Randy.Dunlap
Quoted 9 lines · Felipe Alfaro Solana
Quoted 8 lines · Richard B. Johnson
Quoted 6 lines
First, I don't understand how as you say, "suggestions are desperately needed" on a developmental kernel. These things are not known to work on all configurations and some information like "It gives me hex codes..." is worthless. Please write down these "hex-codes" and, after booting a version the works, run them through ksymoops. If you don't know what that is:
Quoted 7 lines
Quoted 3 lines
ksymoops? I thought 2.5 kernels didn't need ksymoops anymore and that function names were automatically "guessed" in call stack traces.
IFF you use "include symbols" when building you shouldn't need ksymoops. IMO, if you're using 2.5.x you really should include the symbols - chances are you'll need em.
Quoted 6 lines
Maybe we are reading this differently, but it sounded to me like the original system hang never reached the kernel | system log and that some hex codes were the only clues. In that case, pushing them thru ksymoops does still make some sense, doesn't it?
How else would you determine where the hang occurred?
Quoted 8 lines
I read it that he was getting an oops with just hex values cause he didn't have the symbols included (note the reference to "it just gives hex codes"). I could be wrong, since I'm only looking at the quote of a quote of someone's interpretation. :) With symbols included an oops DOES print the actual call trace in readable form. (I've seen enough oops to be certain of that :)
I agree with > >
I'd say he's getting the same thing as me
<http://marc.theaimsgroup.com/?l=linux-kernel&m=105099066618652&w=2>
the 'hex codes' are the last line of grub loading the kernel
so where to from here ??
/ Brett