Fedora kernel list - Nov 2007 - help! My re-compiled kernel always got crashed in a machine with scsi/sata disk

Thanks for all your help. I ran into another problem.

My 16-core machine has a scsi/sata disk. I have enabled all important
features related with scsi and sata.  I built 2.6.23 kernel on this machine.
But the kernel always got crashed randomly. Sometimes it couldnot even boot,
reporting some random errors,  like "segment violation, sleep for 40
seconds", or "Group volume VolGroup00 uses lvm2 metadata:
read-only", then
jump to a strange login window that I cannot log in using my root password.

 Another thing is that Linux works perfect if I installed Fecore Core 7 on
this multi-core machine with scsi/sata disk. Why it didnt work if I used
re-compiled kernel. I guess it is because I didnt config kernel right
(although I enabled all important features related with scsi/sata) in "make
menuconfig". If you happen to know how to enable scsi/sata features
correctly, please let me know. Thanks!

Below is my grub.conf related to 2.6.23 kernel.


# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.20)
        root (hd0,0)
        kernel /vmlinuz-2.6.20 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.20.img

Sorry, I posted 2.6.20 parameters in grub.conf. Parameters if 2.6.23 are
shown below:

title Fedora (2.6.23)
        root (hd0,0)
        kernel /vmlinuz-2.6.23 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.23.img

Feng

On 11/12/07, Feng Xian <feng.xian@gmail.com>
wrote:
>
> Thanks for all your help. I ran into another problem.
>
> My 16-core machine has a scsi/sata disk. I have enabled all important
> features related with scsi and sata.  I built 2.6.23 kernel on this
> machine. But the kernel always got crashed randomly. Sometimes it couldnot
> even boot, reporting some random errors,  like "segment violation,
sleep for
> 40 seconds", or "Group volume VolGroup00 uses lvm2 metadata:
read-only",
> then jump to a strange login window that I cannot log in using my root
> password.
>
>  Another thing is that Linux works perfect if I installed Fecore Core 7 on
> this multi-core machine with scsi/sata disk. Why it didnt work if I used
> re-compiled kernel. I guess it is because I didnt config kernel right
> (although I enabled all important features related with scsi/sata) in
"make
> menuconfig". If you happen to know how to enable scsi/sata features
> correctly, please let me know. Thanks!
>
> Below is my grub.conf related to 2.6.23 kernel.
>
>
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this
> file
> # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg.
> #          root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
> #          initrd /initrd-version.img
> #boot=/dev/sda
> default=1
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora (2.6.20)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.20 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
>         initrd /initrd-2.6.20.img
>
>


-- 
Addr: 1025N, 23rd str, APT 33,
         Lincoln, NE, 68503
Phone: (402)310-9826
WWW: cse.unl.edu/~fxian

Feng Xian wrote:
> Thanks for all your help. I ran into another problem.
>  
> My 16-core machine has a scsi/sata disk. I have enabled all important
> features related with scsi and sata.  I built 2.6.23 kernel on this
> machine. But the kernel always got crashed randomly. Sometimes it
> couldnot even boot, reporting some random errors,  like "segment
> violation, sleep for 40 seconds", or "Group volume VolGroup00
uses lvm2
> metadata: read-only", then jump to a strange login window that I
cannot
> log in using my root password.
>  
>  Another thing is that Linux works perfect if I installed Fecore Core 7
> on this multi-core machine with scsi/sata disk. Why it didnt work if I
> used re-compiled kernel. I guess it is because I didnt config kernel
> right (although I enabled all important features related with scsi/sata)
> in "make menuconfig". If you happen to know how to enable
scsi/sata
> features correctly, please let me know. Thanks!
I don''t think this is the correct forum for this question. This list is
targeted at issues surrounding the Fedora kernel, and you''re building
your own kernel. Once you start building your own, with a config that
obviously differs significantly from the Fedora config, we can''t
realistically provide support here.

Furthermore, I''m not quite sure I understand why you think you need to
build your own kernel either. To be bluntly honest, if you can''t figure
out what''s going wrong there on your own, you probably
shouldn''t be
building your own.

-- 
Jarod Wilson
jwilson@redhat.com

I downloaded a clean version of 2.6.23 and didnt do any modification on it
(athough I am about to modify it in the future). By default, the clean
version doesnt enable sata features, so I enabled these features and
compiled this clean version. But I couldn''t boot linux with the
compiled
kernel like I mentioned in my previous posts.

On 11/12/07, Jarod Wilson <jwilson@redhat.com>
wrote:
>
> Feng Xian wrote:
> > Thanks for all your help. I ran into another problem.
> >
> > My 16-core machine has a scsi/sata disk. I have enabled all important
> > features related with scsi and sata.  I built 2.6.23 kernel on this
> > machine. But the kernel always got crashed randomly. Sometimes it
> > couldnot even boot, reporting some random errors,  like "segment
> > violation, sleep for 40 seconds", or "Group volume
VolGroup00 uses lvm2
> > metadata: read-only", then jump to a strange login window that I
cannot
> > log in using my root password.
> >
> >  Another thing is that Linux works perfect if I installed Fecore Core
7
> > on this multi-core machine with scsi/sata disk. Why it didnt work if I
> > used re-compiled kernel. I guess it is because I didnt config kernel
> > right (although I enabled all important features related with
scsi/sata)
> > in "make menuconfig". If you happen to know how to enable
scsi/sata
> > features correctly, please let me know. Thanks!
>
> I don''t think this is the correct forum for this question. This
list is
> targeted at issues surrounding the Fedora kernel, and you''re
building
> your own kernel. Once you start building your own, with a config that
> obviously differs significantly from the Fedora config, we can''t
> realistically provide support here.
>
> Furthermore, I''m not quite sure I understand why you think you
need to
> build your own kernel either. To be bluntly honest, if you can''t
figure
> out what''s going wrong there on your own, you probably
shouldn''t be
> building your own.
>
> --
> Jarod Wilson
> jwilson@redhat.com
>
>
>
>

-- 
Addr: 1025N, 23rd str, APT 33,
         Lincoln, NE, 68503
Phone: (402)310-9826
WWW: cse.unl.edu/~fxian

Feng Xian wrote:
> I downloaded a clean version of 2.6.23 and didnt do any modification on
> it (athough I am about to modify it in the future). By default, the
> clean version doesnt enable sata features, so I enabled these features
> and compiled this clean version. But I couldn''t boot linux with
the
> compiled kernel like I mentioned in my previous posts.
Like I said, its not a Fedora kernel, and thus not something we can
reasonably support here. The only possible list-relevant bit of info
here would be knowing *why* you''re building your own, such that we can
make the Fedora kernel provide what you need so you don''t have to, if
possible and/or relevant.

That said, seeing as how a Fedora kernel does boot your system, you''ll
probably get a lot closer to a bootable system with your own kernel if
you start with the Fedora kernel config file instead of the upstream
kernel config file, and go from there.

> On 11/12/07, *Jarod Wilson* <jwilson@redhat.com
> <mailto:jwilson@redhat.com>> wrote:
> 
>     Feng Xian wrote:
>     > Thanks for all your help. I ran into another problem.
>     >
>     > My 16-core machine has a scsi/sata disk. I have enabled all
important
>     > features related with scsi and sata.  I built 2.6.23 kernel on
this
>     > machine. But the kernel always got crashed randomly. Sometimes it
>     > couldnot even boot, reporting some random errors,  like
"segment
>     > violation, sleep for 40 seconds", or "Group volume
VolGroup00 uses
>     lvm2
>     > metadata: read-only", then jump to a strange login window
that I
>     cannot
>     > log in using my root password.
>     >
>     >  Another thing is that Linux works perfect if I installed Fecore
>     Core 7
>     > on this multi-core machine with scsi/sata disk. Why it didnt work
if I
>     > used re-compiled kernel. I guess it is because I didnt config
kernel
>     > right (although I enabled all important features related with
>     scsi/sata)
>     > in "make menuconfig". If you happen to know how to
enable scsi/sata
>     > features correctly, please let me know. Thanks!
> 
>     I don''t think this is the correct forum for this question.
This list is
>     targeted at issues surrounding the Fedora kernel, and you''re
building
>     your own kernel. Once you start building your own, with a config that
>     obviously differs significantly from the Fedora config, we
can''t
>     realistically provide support here.
> 
>     Furthermore, I''m not quite sure I understand why you think you
need to
>     build your own kernel either. To be bluntly honest, if you
can''t figure
>     out what''s going wrong there on your own, you probably
shouldn''t be
>     building your own.

-- 
Jarod Wilson
jwilson@redhat.com

Dnia 2007-11-12, o godz. 15:30:45 "Feng Xian"
<feng.xian@gmail.com> napisał(a):
> By default, the clean
> version doesnt enable sata features, so I enabled these features and
> compiled this clean version.
By default, Fedora''s kernel works without the need to recompile. And
you''ve
already admitted that. Use Fedora when it works and you can come back and
report problems when it doesn''t.

If you plan on patching the kernel, Fedora provides SRPM-s with patches and
known-working configs in there. This is the thing you can seek help on on this
list, not the "vanilla" kernel with your own broken config.

Lam

Thanks! Now I know what confused me. What I downloaded was linux
kernel from "Linux Archive" website instead of fedora source from
redhat. I used to believe that these two sources are the same. From
your message, they are apparently different.

I compiled fedora source again this time and it is working now! Thanks
a lot! :-)

On Nov 13, 2007 12:38 AM, Leszek Matok <Lam@lam.pl>
wrote:
> Dnia 2007-11-12, o godz. 15:30:45 "Feng Xian"
<feng.xian@gmail.com> napisał(a):
>
> > By default, the clean
> > version doesnt enable sata features, so I enabled these features and
> > compiled this clean version.
> By default, Fedora''s kernel works without the need to recompile.
And you''ve
> already admitted that. Use Fedora when it works and you can come back and
> report problems when it doesn''t.
>
> If you plan on patching the kernel, Fedora provides SRPM-s with patches and
> known-working configs in there. This is the thing you can seek help on on
this
> list, not the "vanilla" kernel with your own broken config.
>
> Lam
>
> _______________________________________________
> Fedora-kernel-list mailing list
> Fedora-kernel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-kernel-list
>
>


-- 
Addr: 1025N, 23rd str, APT 33,
         Lincoln, NE, 68503
Phone: (402)310-9826
WWW: cse.unl.edu/~fxian

Feng Xian wrote:
> Thanks! Now I know what confused me. What I downloaded was linux
> kernel from "Linux Archive" website instead of fedora source from
> redhat. I used to believe that these two sources are the same. From
> your message, they are apparently different.
As far as the code itself goes, we try to stay as close to upstream as
possible. We start with the upstream kernel tarball and apply some
patches and our own kernel config from there.

Generally, if you take an upstream tarball and just use the Fedora
kernel config, you''ll get a booting system (usually works for me,
anyhow).

-- 
Jarod Wilson
jwilson@redhat.com