kernel-2.6.11-1.1202 hangs

[Justin Conover]

SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts

Hangs right there, had similar problem with 1191, the original kernel
boots fine.

[Paul F. Johnson]

Hi,
> SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
>
> Hangs right there, had similar problem with 1191, the original kernel
> boots fine.

Yep. I'm getting slightly further, but it's dead after loading bttv.

TTFN

Paul

[Justin Conover]

Anyone else that has an aicxxx scis controller having an issuse?

On Fri, 25 Mar 2005 20:38:58 +0000, Paul  wrote:
> Hi,
> > SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
> >
> > Hangs right there, had similar problem with 1191, the original kernel
> > boots fine.
>
> Yep. I'm getting slightly further, but it's dead after loading bttv.
>
> TTFN
>
> Paul
>
> --
> "It is often said that something cannot be libel if it is the truth.
> This has had to be amended to 'something cannot be libel if it is the
> truth or if the bank balance says otherwise'" - US Today

[Michael Schwendt]

On Fri, 25 Mar 2005 20:38:58 +0000, Paul wrote:
> Hi,
> > SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
> >
> > Hangs right there, had similar problem with 1191, the original kernel
> > boots fine.
>
> Yep. I'm getting slightly further, but it's dead after loading bttv.

Here, booting into run-level 3 seems to work. But booting with rhgb or
running startx makes it lock up hard (with blank black screen) as soon
as it tries to switch video modes. Same with 1191.

[D. Stolte]

i had the same problem which went away after removing the nvidiafb
module. if you also have a nvidia card then it may also work for you.

/ds

Michael Schwendt wrote:
> On Fri, 25 Mar 2005 20:38:58 +0000, Paul wrote:
> > Hi,
> > > SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
> > >
> > > Hangs right there, had similar problem with 1191, the original kernel
> > > boots fine.
> >
> > Yep. I'm getting slightly further, but it's dead after loading bttv.
>
> Here, booting into run-level 3 seems to work. But booting with rhgb or
> running startx makes it lock up hard (with blank black screen) as soon
> as it tries to switch video modes. Same with 1191.

[Paul F. Johnson]

Hi,

Please don't top post - it's damned annoying and makes following a
thread even more problematic. Leave top posting to those who know no
better...
> > Here, booting into run-level 3 seems to work. But booting with rhgb or
> > running startx makes it lock up hard (with blank black screen) as soon
> > as it tries to switch video modes. Same with 1191.
> i had the same problem which went away after removing the nvidiafb
> module. if you also have a nvidia card then it may also work for you.

Makes no difference at this end. If I remove the rhgb and quiet options
from the boot commandline, I still get a lock up. I don't have the
nvidiafb module loaded, but do have a GF4.

1191 and 1201 both lock.

TTFN

Paul

[Arjan van de Ven]

> 1191 and 1201 both lock.

you're not using the binary nvidia kernel module I hope ?

(please anyone who reports kernel problems and is using that module,
please mention the fact that you use that module!!!)

[Justin Conover]

New kernel and just reboot to get into it, how could it have the
nvidia kernel module loaded?

On Sat, 26 Mar 2005 13:44:03 +0100, Arjan van de Ven  wrote:
> > 1191 and 1201 both lock.
>
> you're not using the binary nvidia kernel module I hope ?
>
> (please anyone who reports kernel problems and is using that module,
> please mention the fact that you use that module!!!)
>
> --
> fedora-test-list mailing list
> [e-mail]
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list

[Dave Jones]

On Sat, Mar 26, 2005 at 01:44:03PM +0100, Arjan van de Ven wrote:
> > 1191 and 1201 both lock.
>
> you're not using the binary nvidia kernel module I hope ?

He mentioned the new nvidiafb module thats part of the kernel tree.

Dave

[Arjan van de Ven]

On Sat, 2005-03-26 at 21:32 -0500, Dave Jones wrote:
> On Sat, Mar 26, 2005 at 01:44:03PM +0100, Arjan van de Ven wrote:
> > > 1191 and 1201 both lock.
> >
> > you're not using the binary nvidia kernel module I hope ?
>
> He mentioned the new nvidiafb module thats part of the kernel tree.

doesn't rule out using the binary thing..

in fact the binary thing is known to explode when the fb module is
used...

[dragoran]

Arjan van de Ven wrote:
> On Sat, 2005-03-26 at 21:32 -0500, Dave Jones wrote:
> > On Sat, Mar 26, 2005 at 01:44:03PM +0100, Arjan van de Ven wrote:
> > > > 1191 and 1201 both lock.
> > >
> > > you're not using the binary nvidia kernel module I hope ?
> >
> > He mentioned the new nvidiafb module thats part of the kernel tree.
>
> doesn't rule out using the binary thing..
>
> in fact the binary thing is known to explode when the fb module is
> used...

the nvidia installer also gives a warning when the fb module is even 
included in the kernel.

[D. Stolte]

Arjan van de Ven wrote:
> On Sat, 2005-03-26 at 21:32 -0500, Dave Jones wrote:
> > On Sat, Mar 26, 2005 at 01:44:03PM +0100, Arjan van de Ven wrote:
> > > > 1191 and 1201 both lock.
> > >
> > > you're not using the binary nvidia kernel module I hope ?
> >
> > He mentioned the new nvidiafb module thats part of the kernel tree.
>
> doesn't rule out using the binary thing..
>
> in fact the binary thing is known to explode when the fb module is
> used...

I mentioned that i had to remove the nvidiafb module from the modulepath
because the initscripts try to modprobe this module during the hw
detection and the oops/hang happens.
After deleting this module everything is fine.

/ds

[dragoran]

D. Stolte wrote:
> Arjan van de Ven wrote:
> > On Sat, 2005-03-26 at 21:32 -0500, Dave Jones wrote:
> > > On Sat, Mar 26, 2005 at 01:44:03PM +0100, Arjan van de Ven wrote:
> > > > > 1191 and 1201 both lock.
> > > >
> > > > you're not using the binary nvidia kernel module I hope ?
> > >
> > > He mentioned the new nvidiafb module thats part of the kernel tree.
> >
> > doesn't rule out using the binary thing..
> >
> > in fact the binary thing is known to explode when the fb module is
> > used...
>
> I mentioned that i had to remove the nvidiafb module from the modulepath
> because the initscripts try to modprobe this module during the hw
> detection and the oops/hang happens.
> After deleting this module everything is fine.
>
> /ds

does the crash happen when NO nvidia binary module is used?
if yes its a bug, if not its a known issue

[Paul F. Johnson]

Hi,
> does the crash happen when NO nvidia binary module is used?
> if yes its a bug, if not its a known issue

Yes. It hangs without an nvidia module (my laptop has nothing from
nvidia on it and that dies at the same point)

TTFN

Paul

[D. Stolte]

Paul wrote:
> Hi,
> > does the crash happen when NO nvidia binary module is used?
> > if yes its a bug, if not its a known issue
>
> Yes. It hangs without an nvidia module (my laptop has nothing from
> nvidia on it and that dies at the same point)
>
> TTFN
>
> Paul

paul, please remove the nvidiafb module (i really mean rm -f
nvidiafb.ko!) and see what happens.

/ds

[Justin Conover]

In further news, 1208 does the exact same thing for me........ :(

On Sun, 27 Mar 2005 16:18:37 +0200, D. Stolte  wrote:
> Paul wrote:
> > Hi,
> > > does the crash happen when NO nvidia binary module is used?
> > > if yes its a bug, if not its a known issue
> >
> > Yes. It hangs without an nvidia module (my laptop has nothing from
> > nvidia on it and that dies at the same point)
> >
> > TTFN
> >
> > Paul
>
> paul, please remove the nvidiafb module (i really mean rm -f
> nvidiafb.ko!) and see what happens.
>
> /ds
>
> --
> fedora-test-list mailing list
> [e-mail]
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list

[Paul F. Johnson]

Hi,
> paul, please remove the nvidiafb module (i really mean rm -f
> nvidiafb.ko!) and see what happens.

I'll give that a try.

TTFN

Paul

[Paul F. Johnson]

Hi,
> > paul, please remove the nvidiafb module (i really mean rm -f
> > nvidiafb.ko!) and see what happens.
>
> I'll give that a try.

It is the nvidiafb module which is causing the problems. I'm using the
1208 kernel happily.

TTFN

Paul

[Justin Conover]

SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts

Not me, i still get this and just hangs right there, I've sent a
e-mail to the selinux-fedora list too, to see what this might be.

On Sun, 27 Mar 2005 21:54:34 +0100, Paul  wrote:
> Hi,
> > > paul, please remove the nvidiafb module (i really mean rm -f
> > > nvidiafb.ko!) and see what happens.
> >
> > I'll give that a try.
>
> It is the nvidiafb module which is causing the problems. I'm using the
> 1208 kernel happily.
>
> TTFN
> Paul
>
> "It is often said that something cannot be libel if it is the truth.
> This has had to be amended to 'something cannot be libel if it is the
> truth or if the bank balance says otherwise'" - US Today
>
> --
> fedora-test-list mailing list
> [e-mail]
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list

[Justin Conover]

It seems that adding selinux=0 to the kernel line still hangs, but stops here

Enabling swap space:  Adding 2097144k swap on
/dev/VolGroup01/LogVol01. Priority:1 extents:1    [ ok ]

On Sun, 27 Mar 2005 15:22:26 -0600, Justin Conover
 wrote:
> SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
>
> Not me, i still get this and just hangs right there, I've sent a
> e-mail to the selinux-fedora list too, to see what this might be.
>
> On Sun, 27 Mar 2005 21:54:34 +0100, Paul  wrote:
> > Hi,
> > > > paul, please remove the nvidiafb module (i really mean rm -f
> > > > nvidiafb.ko!) and see what happens.
> > >
> > > I'll give that a try.
> >
> > It is the nvidiafb module which is causing the problems. I'm using the
> > 1208 kernel happily.
> >
> > TTFN
> > Paul
> >
> > "It is often said that something cannot be libel if it is the truth.
> > This has had to be amended to 'something cannot be libel if it is the
> > truth or if the bank balance says otherwise'" - US Today
> >
> > --
> > fedora-test-list mailing list
> > [e-mail]
> > To unsubscribe:
> > http://www.redhat.com/mailman/listinfo/fedora-test-list

[D. Stolte]

dragoran wrote:
> D. Stolte wrote:
> > Arjan van de Ven wrote:
> > > On Sat, 2005-03-26 at 21:32 -0500, Dave Jones wrote:
> > > > On Sat, Mar 26, 2005 at 01:44:03PM +0100, Arjan van de Ven wrote:
> > > > > > 1191 and 1201 both lock.
> > > > >
> > > > > you're not using the binary nvidia kernel module I hope ?
> > > >
> > > > He mentioned the new nvidiafb module thats part of the kernel tree.
> > >
> > > doesn't rule out using the binary thing..
> > >
> > > in fact the binary thing is known to explode when the fb module is
> > > used...
> >
> > I mentioned that i had to remove the nvidiafb module from the modulepath
> > because the initscripts try to modprobe this module during the hw
> > detection and the oops/hang happens.
> > After deleting this module everything is fine.
> >
> > /ds
>
> does the crash happen when NO nvidia binary module is used?
> if yes its a bug, if not its a known issue

yes, the binary nvidia driver is *not* installed. the probing of the
nvidiafb module is enough to make the box crash.

/ds

[Jef Spaleta]

On Sat, 26 Mar 2005 12:40:11 +0000, Paul  wrote:
> Makes no difference at this end. If I remove the rhgb and quiet options
> from the boot commandline, I still get a lock up. I don't have the
> nvidiafb module loaded, but do have a GF4.
>
> 1191 and 1201 both lock.

geforce2 here.. and i have absolutely no problem booting into either kernel.

you said it locks up after bttv is loaded... are you loading bttv from rc.local?

-jef

[Truls Gulbrandsen]

Justin Conover wrote:
> SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
>
> Hangs right there, had similar problem with 1191, the original kernel
> boots fine.

I have updated but still not rebooted. Before I do so, can some please 
tell how I get the machin up and running again if I encounter the same 
problem?

It seems like updating to a more resent kernel removes the previous one 
as I don't have the usual list of "old" kernels giving the option to 
boot a previous one if load fails.

Regards,
Truls

[Justin Conover]

Pretty much if it locks, you have to push your reset button.  When
grub loads, hit <ESC> to see your menu, or you can edit
/boot/grub/grub.conf and comment out the #hiddenmenu line to always
see your kernels.

On Sat, 26 Mar 2005 20:39:31 +0100, Truls Gulbrandsen
 wrote:
> Justin Conover wrote:
> > SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
> >
> > Hangs right there, had similar problem with 1191, the original kernel
> > boots fine.
>
> I have updated but still not rebooted. Before I do so, can some please
> tell how I get the machin up and running again if I encounter the same
> problem?
>
> It seems like updating to a more resent kernel removes the previous one
> as I don't have the usual list of "old" kernels giving the option to
> boot a previous one if load fails.
>
> Regards,
> Truls

[Dave Jones]

On Sat, Mar 26, 2005 at 08:39:31PM +0100, Truls Gulbrandsen wrote:
> It seems like updating to a more resent kernel removes the previous one 
> as I don't have the usual list of "old" kernels giving the option to 
> boot a previous one if load fails.

That should never happen unless you are upgrading using rpm -Uvh
(which you should never do, for exactly this reason).

Dave