Date:	Tue, 2 Dec 2008 15:20:25 +0000
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	Alejandro Riveira Fernández 
	<ariveira@...il.com>
Cc:	pazke <pazke@...ts.donpac.ru>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.28-rc7

On Tuesday 02 December 2008 14:48:15 Alejandro Riveira Fernández wrote:
> El Tue, 2 Dec 2008 16:11:58 +0300
>
> pazke <pazke@...ts.donpac.ru> escribió:
> > On 337, 12 02, 2008 at 01:14:42PM +0100, Alejandro Riveira Fern??ndez 
wrote:
> > > El Mon, 1 Dec 2008 20:11:55 -0800 (PST)
> > >
> > > Linus Torvalds <torvalds@...ux-foundation.org> escribi??:
> > > > I was gone for a week, and it wasn't quite as quiet as I was hoping
> > > > for, but there's a new -rc out there now with the merges of the
> > > > fallout.
> > > >
> > > > Almost all of it is various driver fixes, at least if you ignore the
> > > > (bulky) powerpc defconfig updates. The bulk being ACPI, DRM, input
> > > > and V4L, but with a smattering of usb, networking, infiniband and
> > > > firewire.
> > > >
> > > > Oh, and a number of section warning fixes.
> > > >
> > > > The shortlog is about as informative as it gets - it's all about a
> > > > lot of small details.
> > > >
> > > > 		Linus
> > >
> > >  Just tried it on my Ubuntu 8.10 install.
> > >  Booted fine and the distro got to its safe graphics mode because i'm
> > >  evil and use the nvidia kernel module. i switch to VT1 and the fun
> > >  begins something weird happens with the terminal...
> > >  I can not see the login: not the password: promts
> > >  I log in blindly
> > >  When i type a command nothing appears on screen i have to hit enter
> > > twice one make the command appear the second actually executes
> > >  After that i have to hit enter once more to get the shell promt again
> > >  Also I couldn't use sudo the password promt did not get my password
> > >
> > >  All of this happens without the nvidia module loaded (not even
> > > compiled)
> >
> > Realy ?
> >
> > > [  101.744347] nvidia: module license 'NVIDIA' taints kernel.
> > > [  102.003828] nvidia 0000:01:00.0: PCI INT A -> GSI 25 (level, low) ->
> > > IRQ 25 [  102.003838] nvidia 0000:01:00.0: setting latency timer to 64
> > > [  102.004747] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  180.06 
> > > Sat Nov  8 17:50:38 PST 2008
> >
> > 		^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Where do these messages come from then ?
>
>  I took the sanpshot of the dmesg after loading the module if my word is
> not enough i can reboot with the module disabled but i do not see the
> point... The truth is that the bug prevented me from loading/installing the
> nvidia module becouse i could not use sudo. Only when i rebooted into
> single mode where the problems went away i could build and install the
> module...

One thing I would point out is that your distro kernel (presumably 2.6.27 or 
older) would probably have had the NVIDIA module to hand and would not drop 
into safe mode, right? In this case, VT switching behaviour may be entirely 
different.

Could you please find out what framebuffer driver your distro is loading 
(probably nvidiafb, I'd guess) before starting X, and what Xorg driver Ubuntu 
use in this "safe graphics mode" (nv, vesa)? Also, could you try removing the 
nvidia module in the older kernel and confirm that the same VT corruption does 
not occur, so Rafael can identify this as a regression?

(Maybe things have changed over the years, but my understanding was that for 
the majority of Xorg drivers, mode setting was still done by the Xorg driver, 
not the kernel, and the X server is responsible for restoring the VT 
correctly, not the kernel's framebuffer driver. So this may possibly not be a 
kernel bug at all.)

-- 
Cheers,
Alistair.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists