PDA

View Full Version : kernel-PAE-2.6.33.1-21 nv regression



SlowJet
25th March 2010, 04:34 AM
kernel-PAE-2.6.33.1-21 now thinks my nv11 card is an nv10 and does not boot pass the F-bubble
rebooting with -19 works.

kernel-PAE-2.6.33.1-21 on intel boots fine.

This is with all the main koji updates thru the 24th.

SJ
An nv10 is
NVIDIA NV10-based Boards
NVIDIA GeForce256 32MiB
NVIDIA GeForce256 32MiB
I have an NV11
mx2

AdamW
25th March 2010, 06:43 PM
can you please file a bug, with some logs? Thanks.

edit: this is a bit odd, as there's no nvidia-related change at all logged between -19 and -21:

http://koji.fedoraproject.org/koji/buildinfo?buildID=163495

SlowJet
25th March 2010, 08:04 PM
"this is a bit odd, as there's no nvidia-related change at all logged between -19 and -21:"

You are right. Looks like that may have happen at 33-4.

So I started downgrading, starting with plymouth 8.0.1-1 back to 8.0.0
Installed the 21 kernel again and guess what?
It booted and it is called an NV10.

thanks for the clue.

SJ

AdamW
25th March 2010, 08:14 PM
where is it you're seeing this NV10/NV11 difference?

SlowJet
25th March 2010, 08:38 PM
In dmesg

I put a comment in fedora testing for plymouth

I can't do bugs due to e-mail and machine configuration.

SJ

GoinEasy9
26th March 2010, 05:04 AM
I seem to have a similar problem, with similar hardware, except my kernel went from 2.6.33-1 to 2.6.33.1-19

My Hardware: (I also have an NV11 on an old P4 Asus P4PE-X motherboard)
System: Host fedora13irc Kernel 2.6.33-1.fc13.i686.PAE i686 (32 bit) Distro Fedora release 13 (Goddard)
CPU: Single core Intel Pentium 4 (UP) cache 512 KB flags (sse sse2) bmips 4009.23 clocked at 2666.600 MHz
Graphics: Card nVidia NV11 [GeForce2 MX/MX 400] Fedora 1.7999.1 Res: 1440x900@59.9hz
GLX Renderer Software Rasterizer GLX Version 2.1 Mesa 7.8-devel Direct Rendering Yes

The newer kernel 2.6.33.1-19 that came in tonight stops during boot after Setting hostname fedora13irc, it never gets to Setting up Logical Volume Management.

Setting hostname fedora13irc: [ OK ] (Then boot locks up).

Readout from messages:

(RESTART HERE - TO BOOT INTO 2.6.33.1-19 Kernel)

Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): GdmSignalHandler: handling signal 15
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x804bf50
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): Got callback for signal 15
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): Caught signal 15, shutting down normally.
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): GdmSignalHandler: Caught termination signal - calling fatal func
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSignalHandler: handling signal 15
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x804d570
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): Got callback for signal 15
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): Caught signal 15, shutting down normally.
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmSignalHandler: handling signal 15
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x804c6d0
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): Got callback for signal 15
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): Caught signal 15, shutting down normally.
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmSignalHandler: Caught termination signal - calling fatal func
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GDM finished, cleaning up...
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmDisplayStore: Clearing display store
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmDisplayStore: Unreffing display: 0x9054810
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSignalHandler: Caught termination signal - calling fatal func
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmDisplay: Disposing display
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmSlaveProxy: Disposing slave proxy
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmSlaveProxy: Killing slave
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSimpleSlave: Stopping simple_slave
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSlave: Stopping slave
Mar 25 22:56:23 localhost gdm-binary[1191]: DEBUG(+): GdmCommon: sending signal 15 to process 1226
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
Mar 25 22:56:23 localhost pam: gdm-password[1377]: DEBUG(+): Worker finished
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSlave: Disconnected from display
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionDirect: Closing session
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): Writing logout record
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): using ut_type DEAD_PROCESS
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): using ut_tv time 1269572183
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): using ut_pid 1407
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): using ut_id :0
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): using ut_host :0
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): using ut_line tty7
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): Writing wtmp logout record to /var/log/wtmp
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): Removing utmp record
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionDirect: Stopping all conversations
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionWorkerJob: Stopping job pid:1377
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmCommon: sending signal 9 to process 1377
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionWorkerJob: Waiting on process 1377
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmCommon: process (pid:1377) done (status:0)
Mar 25 22:56:23 localhost init: system-setup-keyboard main process (749) killed by TERM signal
Mar 25 22:56:23 localhost init: tty (/dev/tty2) main process (1198) killed by TERM signal
Mar 25 22:56:23 localhost init: tty (/dev/tty3) main process (1201) killed by TERM signal
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionWorkerJob: SessionWorkerJob died
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionDirect: Emitting conversation-stopped signal
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSimpleSlave: conversation stopped
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionDirect: Disposing session
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionDirect: Closing session
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSessionDirect: Stopping all conversations
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmServer: Stopping server
Mar 25 22:56:23 localhost init: tty (/dev/tty4) main process (1204) killed by TERM signal
Mar 25 22:56:23 localhost init: tty (/dev/tty5) main process (1210) killed by TERM signal
Mar 25 22:56:23 localhost init: tty (/dev/tty6) main process (1215) killed by TERM signal
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmCommon: sending signal 15 to process 1229
Mar 25 22:56:23 localhost gdm-simple-slave[1226]: DEBUG(+): GdmServer: Waiting on process 1229
Mar 25 22:56:24 localhost kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 1
Mar 25 22:56:24 localhost avahi-daemon[889]: Got SIGTERM, quitting.
Mar 25 22:56:24 localhost avahi-daemon[889]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.104.
Mar 25 22:56:24 localhost kernel: Xorg used greatest stack depth: 4820 bytes left
Mar 25 22:56:24 localhost gdm-simple-slave[1226]: DEBUG(+): GdmCommon: process (pid:1229) done (status:0)
Mar 25 22:56:24 localhost gdm-simple-slave[1226]: DEBUG(+): GdmServer: Server died
Mar 25 22:56:24 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSignalHandler: Removing handler 10: signum=11 0x80545c0
Mar 25 22:56:24 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSlave: Stopping slave
Mar 25 22:56:24 localhost gdm-simple-slave[1226]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
Mar 25 22:56:24 localhost gdm-simple-slave[1226]: DEBUG(+): Slave finished
Mar 25 22:56:24 localhost gdm-binary[1191]: DEBUG(+): GdmCommon: process (pid:1226) done (status:0)
Mar 25 22:56:24 localhost gdm-binary[1191]: DEBUG(+): GdmLocalDisplayFactory: Display 0x9054810 disposed
Mar 25 22:56:24 localhost gdm-binary[1191]: DEBUG(+): GdmDisplay: Finalizing display: /org/gnome/DisplayManager/Display1
Mar 25 22:56:24 localhost gdm-binary[1191]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
Mar 25 22:56:25 localhost console-kit-daemon[1243]: WARNING: Couldn't read /proc/1531/environ: Failed to open file '/proc/1531/environ': No such file or directory
Mar 25 22:56:25 localhost abrtd: UnRegistered Reporter plugin Bugzilla
Mar 25 22:56:25 localhost abrtd: UnRegistered Analyzer plugin CCpp
Mar 25 22:56:25 localhost abrtd: UnRegistered Analyzer plugin Kerneloops
Mar 25 22:56:25 localhost abrtd: UnRegistered Reporter plugin KerneloopsReporter
Mar 25 22:56:25 localhost abrtd: UnRegistered Action plugin KerneloopsScanner
Mar 25 22:56:25 localhost abrtd: UnRegistered Reporter plugin Logger
Mar 25 22:56:25 localhost abrtd: UnRegistered Analyzer plugin Python
Mar 25 22:56:25 localhost abrtd: Got signal 15, exiting
Mar 25 22:56:30 localhost acpid: exiting
Mar 25 22:56:31 localhost rpc.statd[904]: Caught signal 15, un-registering and exiting
Mar 25 22:56:31 localhost NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Mar 25 22:56:31 localhost NetworkManager: <info> exiting (success)
Mar 25 22:56:32 localhost init: Disconnected from system bus
Mar 25 22:56:32 localhost rtkit-daemon[1367]: Demoting known real-time threads.
Mar 25 22:56:32 localhost rtkit-daemon[1367]: Successfully demoted thread 1520 of process 1516 (/usr/bin/pulseaudio).
Mar 25 22:56:32 localhost rtkit-daemon[1367]: Successfully demoted thread 1518 of process 1516 (/usr/bin/pulseaudio).

GoinEasy9
26th March 2010, 05:05 AM
Previous post Continued:

Mar 25 22:56:32 localhost rtkit-daemon[1367]: Successfully demoted thread 1516 of process 1516 (/usr/bin/pulseaudio).
Mar 25 22:56:32 localhost rtkit-daemon[1367]: Demoted 3 threads.
Mar 25 22:56:32 localhost rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Mar 25 22:56:33 localhost kernel: Kernel logging (proc) stopped.
Mar 25 22:56:33 localhost rsyslogd: [origin software="rsyslogd" swVersion="4.4.2" x-pid="818" x-info="http://www.rsyslog.com"] exiting on signal 15.

(At this point boot is locked, requiring Power Off restart)
(RESET HERE)


Rebooting into the 2.6.33-1 kernel proceeds normally, I would like to file a bug, but I'm not sure how to categorize it, and, before I saw this thread, was experimenting to see if I could narrow it down. What would the headline be for bugzilla .. "Kernel 2.6.33.1-19 locks up during boot"? Is it nv regression like SlowJet explains?

Thanks in Advance

SlowJet
26th March 2010, 06:26 AM
It seems to be a series of little tweeks going on so use 33.1 until they all get sorted into updates-testing.
You can check the http://lists.fedoraproject.org/pipermail/test/2010-March/thread.html for
>plymouth-0.8.1-1 not compiled yet, last one failed.
gdm-2.29.92-6 in koji
goobject-introspection
libdrm-2.4.19-2
python-2.6.424
selinux-policy-3.7.16-1
kernel 21
btrfs-progs
NewtworkManager-0.8.0-4
Then you should be matched up good.
Otherwise download from koji and rpm -uvh (but there could be more fixes before they get to update-testing?)

SJ

---------- Post added at 09:26 PM CDT ---------- Previous post was at 09:09 PM CDT ----------

OK, I just booted the nv machine with all of those except the new not yet plymouth
and it booted ok and the mouse pointer come up on the f-bubble and stayed until it snapped to the logon screen, i.e. no black screen, smooth transition.
So things are looking good (with those updates).

SJ

Just t to follow thru
I tried plymouth-0.8.1-1 again after all the updates for the nv machine
and it worked for kernel--PAE-2.6.33.1-21

i think it may have been the gobject-introspection because I was getting a strange avc message in dmeg but didn't relate it to anything until I saw that gobject-introspection had be messed up and then re-called the avc message has a prefix of gob or such.

SJ

jff
26th March 2010, 07:09 AM
This is not for 2.6.33.1-21, but for 2.6.33.1-19 (the latest Fedora kernel update on Alpha). Boot freezes/hangs on T400. Kernel 2.6.33-1 works fine.

SlowJet
26th March 2010, 07:41 AM
There is two f13 branches + koji = F13 development
Yes 33.1 works fine, most of the kernels work fine by the time they get to f13brached alpha.
An most of the kernels work fine in f13 testing.
But sometimes they don't work straight from koji.

However, this problem sort of expanded due to several tweeks and a couple of packages getting some wrong settings.
Hence, if you wait for the corrections in f13 testing it my be next week or Saturday before you will see them in updates-testing.

Alpha won't see them at all unless it fixes something in he QA shakedown.

SJ