Machine lockup with caps lock/num lock flashing or complete reboot/panic. I get various lockup issues with this kernel, (2.6.23 also similar problem). I had problems getting e1000 lan module to work (it was fine in 2.6.21.5). I disabled it and installed a different lan card that seems to work "better". Dual head machine 1GB RAM, nvidia driver x86-100.14.19 Here is output of ver_linux: --------------------------------------------------------------------------------------------------------------------------------------------- Linux zion 2.6.23-rc9 #3 Fri Oct 12 18:27:56 PDT 2007 i686 GNU/Linux Gnu C 4.1.2 Gnu make 3.81 binutils 2.17 util-linux 2.12r mount 2.12r module-init-tools 3.3-pre2 e2fsprogs 1.40-WIP Linux C Library 3.6 Dynamic linker (ldd) 2.3.6 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 udev 105 Modules Loaded nfs lockd sunrpc nvidia i2c_core af_packet ipv6 capability commoncap ppdev lp ac battery dm_mod e1000 loop snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer parport_pc button parport snd 8250_pnp 8250 serial_core soundcore shpchp pci_hotplug snd_page_alloc rng_core floppy intel_agp agpgart rtc sg evdev sr_mod usbhid sd_mod ata_piix 8139too ata_generic ehci_hcd uhci_hcd mii bitrev crc32 libata generic usbcore thermal processor fan unix ext3 jbd piix ide_disk ide_cd cdrom ide_scsi scsi_mod ide_core --------------------------------------------------------------------------------------------------------------------------------------------- Here is output from syslog as it went down: Message from syslogd@zion at Sat Oct 13 15:22:34 2007 ... zion kernel: Oops: 0002 [#1] Message from syslogd@zion at Sat Oct 13 15:22:34 2007 ... zion kernel: CPU: 0 Message from syslogd@zion at Sat Oct 13 15:22:34 2007 ... zion ...
Are you able to repeat this Oops _without_ the nvidia driver? Also, please provide the output from /proc/mounts Cheers -
Trond, I'm not exactly sure how to go back to not using the nvidia driver and select the xorg one. I do know that I wasn't able to use both monitors with the xorg driver, but I'm willing to try that to isolate the problem. Scott Output from /proc/mounts: rootfs / rootfs rw 0 0 none /sys sysfs rw 0 0 none /proc proc rw 0 0 udev /dev tmpfs rw 0 0 /dev/sda2 / ext3 rw,data=ordered 0 0 /dev/sda2 /dev/.static/dev ext3 rw,data=ordered 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid 0 0 usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec 0 0 twin:/home /home nfs rw,vers=3,rsize=32768,wsize=32768,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=twin 0 0 twin:/mp3 /mp3 nfs rw,vers=3,rsize=32768,wsize=32768,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=twin 0 0 -
If memory serves, you change your xorg.conf's "Device" section's "Driver" entry to read: "nv" instead of "nvidia", although I would consult the xorg documentation/your distribution's documentation (and back up your working xorg.conf) for specific details. (Your boot sequence may also automatically load the nvidia module, again, consult your distribution's documentation for details.) Cheers/hope this helps, dcw -
Doug, I thought that might do it, it does seem to work. I edited the driver line in my xorg.conf from nvidia to nv and then, <alt><ctrl> F1 login as root /etc/init.d/gdm stop /etc/init.d/gdm start It came back up with the same flashing crap on the second monitor, so I did it again with the 2nd monitor turned off altogether, and I'll see how long it will run on the single monitor without the nvidia driver without crashing (maybe forever...). Thanks, Scott -
Please don't forget to reboot, though. The kernel will remain tainted until you've rebooted without loading the nvidia module. Cheers Trond -
