Very Computer

by **Francisc** » Thu, 21 Feb 2002 03:05:04

Hi, I'm using RedHat 7.1 and I upgraded the kernel to 2.4.17 to add support
for ext3 filesystem.
Since then I can't copy anything to the machine (from samba or ftp) because
it hangs up, kernel panic I think. I'm not sure because it doesn't have a
monitor atached, and when I attach a monitor after it hangs up it's all
black screen, but one time there were a lot of numbers un the screen and it
said kernel panic.
I'm not sure what to do or what I'm doing wrong, if I go to the previous
kernel everything works fine.
Any Ideas?, If you need more info just tell me.
Thank you.

Francisco

by **Michael Lee Yoh** » Thu, 21 Feb 2002 03:10:41

Quote:> Hi, I'm using RedHat 7.1 and I upgraded the kernel to 2.4.17 to add support
> for ext3 filesystem.

Since you upgraded your kernel, did you attempt to use the old .config
file from your old kernel, or did you hand select the option for
yourself? Do you have experience in selecting kernel options for
builds? Could you please be more descriptive on the kernel panic - is
it because it couldn't find a root partition? You say there are a bunch
of numbers that spew on the screen - are they hexadecimal in nature?

All this information would be extremely handy in helping you out. :)

--

Software Developer, Engineering Services
Red Hat, Inc.

http://people.redhat.com/myohe/

QUIPd 1.02: (491 of 814)
-> At the same time that we are earnest to explore and learn all
-> things, we require that all things be mysterious and unexplorable,
-> that land and sea be infinitely wild, unsurveyed and unfathomed by
-> us because unfathomable.
-> - Henry David Thoreau

by **Francisc** » Thu, 21 Feb 2002 05:00:49

I didn't know the old .config file could be used, but I tried to copy the
same configuration of the old kernel.
The kernel panic happens only when I try to copy something to that machine
(from samba or ftp), everything else works fine and the machine can be up
for days if nobody tries to upload something. You can download from samba
or ftp and that doesn't happen.
The las two lines of the kernel panic were:

<0> Kernel Panic: aiee, killing interrupt handler:
in interrupt handler - not syncing

I don't know if there is a log file with this?, so I can show the entire
message. There where a lot of hex code in the screen. Something like this:
<hexhex> <hexhex> ....
<hexhex> <hexhex> ....
etc.

Now I'll try to recompile the kernel with the old .config and see what
happen.
Thank you.

Francisco

> > Hi, I'm using RedHat 7.1 and I upgraded the kernel to 2.4.17 to add
support
> > for ext3 filesystem.

> Since you upgraded your kernel, did you attempt to use the old .config
> file from your old kernel, or did you hand select the option for
> yourself? Do you have experience in selecting kernel options for
> builds? Could you please be more descriptive on the kernel panic - is
> it because it couldn't find a root partition? You say there are a bunch
> of numbers that spew on the screen - are they hexadecimal in nature?

> All this information would be extremely handy in helping you out. :)

> --

> Software Developer, Engineering Services
> Red Hat, Inc.

> http://people.redhat.com/myohe/

> QUIPd 1.02: (491 of 814)
> -> At the same time that we are earnest to explore and learn all
> -> things, we require that all things be mysterious and unexplorable,
> -> that land and sea be infinitely wild, unsurveyed and unfathomed by
> -> us because unfathomable.
> -> - Henry David Thoreau

by **Michael Lee Yoh** » Thu, 21 Feb 2002 05:52:15

Quote:> <0> Kernel Panic: aiee, killing interrupt handler:
> in interrupt handler - not syncing

> I don't know if there is a log file with this?, so I can show the entire

If the kernel was able to dump the panic message to the log, then it
would be in /var/log/messages. Often times, a panic is not captured due
to the way the kernel queues its instructions.

Quote:> message. There where a lot of hex code in the screen. Something like this:
> <hexhex> <hexhex> ....
> <hexhex> <hexhex> ....
> etc.

Here's my suggestion. Obviously a driver is not agreeing with your
computer.
If you want ext3 support, simply use "up2date" to upgrade your kernel.
You can do this by: "up2date kernel kernel-headers e2fsprogs
util-linux". This will install the latest errata kernel for Red Hat 7.1
which also includes ext3 support, and the utilities necessary to manage
your ext3 filesystems.

If you can find the existence of the entire panic message, then it would
be helpful in determining which module was the culprit and develop a
game plan to get rid of the problem.
--

Software Developer, Engineering Services
Red Hat, Inc.

http://people.redhat.com/myohe/

QUIPd 1.02: (275 of 814)
-> Life is very important to Americans.
-> - Bob Dole

by **Francisc** » Thu, 21 Feb 2002 13:35:54

Well, I looked the last time in messages but it wasn't recorded.
Now I used the .config of the redhat distribution in the new kernel (the one
for i586) and the only settings I changed were the cpu type (pentium mmx)
and I added suport for ext3.
Happens the same.
So I think I will do what you sugested, but I would really like to know what
could be happening.
Thank you.

Francisco

> > <0> Kernel Panic: aiee, killing interrupt handler:
> > in interrupt handler - not syncing

> > I don't know if there is a log file with this?, so I can show the entire

> If the kernel was able to dump the panic message to the log, then it
> would be in /var/log/messages. Often times, a panic is not captured due
> to the way the kernel queues its instructions.

> > message. There where a lot of hex code in the screen. Something like
this:
> > <hexhex> <hexhex> ....
> > <hexhex> <hexhex> ....
> > etc.

> Here's my suggestion. Obviously a driver is not agreeing with your
> computer.
> If you want ext3 support, simply use "up2date" to upgrade your kernel.
> You can do this by: "up2date kernel kernel-headers e2fsprogs
> util-linux". This will install the latest errata kernel for Red Hat 7.1
> which also includes ext3 support, and the utilities necessary to manage
> your ext3 filesystems.

> If you can find the existence of the entire panic message, then it would
> be helpful in determining which module was the culprit and develop a
> game plan to get rid of the problem.
> --

> Software Developer, Engineering Services
> Red Hat, Inc.

> http://people.redhat.com/myohe/

> QUIPd 1.02: (275 of 814)
> -> Life is very important to Americans.
> -> - Bob Dole

Very Computer

problem with new kernel.

problem with new kernel.

problem with new kernel.

problem with new kernel.

problem with new kernel.

problem with new kernel.