Re: PROBLEM: kernel panic

2007-10-14 Thread Scott Petler

Ok, I'll do that
Thanks

Sent from my iPhone

On Oct 14, 2007, at 2:32 PM, Trond Myklebust  
<[EMAIL PROTECTED]> wrote:




On Sun, 2007-10-14 at 14:00 -0700, Scott Petler wrote:

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,
 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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: PROBLEM: kernel panic

2007-10-14 Thread Scott Petler

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,
 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

Doug Whitesell (LKML) wrote:

On Oct 14, 2007, at 1:44 PM, Scott Petler wrote:


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.


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



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: PROBLEM: kernel panic

2007-10-14 Thread Scott Petler

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



Trond Myklebust wrote:

On Sat, 2007-10-13 at 15:48 -0700, Scott Petler wrote:
  

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



Are you able to repeat this Oops _without_ the nvidia driver?

Also, please provide the output from /proc/mounts

Cheers
  Trond


  

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 Library3.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 [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Oops: 0002 [#1]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: CPU:0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP:0060:[]Tainted: PVLI

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EFLAGS: 00010206   (2.6.23-rc9 #3)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP is at 0xe1168fde

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: esi: f8f34700   edi:    ebp: 0001   esp: e7cf3e00

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: ds: 007b   es: 007b   fs:   gs: 0033  ss: 0068

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Process firefox-bin (pid: 8397, ti=e7cf2000 task=f258ca90 
task.ti=e

7cf2000)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Stack: f8f18eb7 c01367f6 e7cf3e48 03e8 03e8 
ed3e97c0 f1f6db

9c f1f6db9c

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:e7cf3f54 f8f60ec2 0004257b   
f1f037dc e7cf3f

54 c01563d0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:019cc780 e7cf3eb0 c0155a63 dfff38c0 c014e001 
019cc780 f1f037

dc dfe0ecf4

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Call Trace:

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] rpcauth_lookupcred+0x63/0x87 [sunrpc]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] pagevec_lookup+0x1c/0x22

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] nfs_permission+0xab/0x183 [nfs]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] __d_lookup+0x8b/0xbf

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] dput+0x15/0xcb

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] nfs_permission+0x0/

Re: PROBLEM: kernel panic

2007-10-14 Thread Scott Petler

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



Trond Myklebust wrote:

On Sat, 2007-10-13 at 15:48 -0700, Scott Petler wrote:
  

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



Are you able to repeat this Oops _without_ the nvidia driver?

Also, please provide the output from /proc/mounts

Cheers
  Trond


  

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 Library3.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 [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Oops: 0002 [#1]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: CPU:0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP:0060:[e1168fde]Tainted: PVLI

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EFLAGS: 00010206   (2.6.23-rc9 #3)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP is at 0xe1168fde

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: esi: f8f34700   edi:    ebp: 0001   esp: e7cf3e00

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: ds: 007b   es: 007b   fs:   gs: 0033  ss: 0068

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Process firefox-bin (pid: 8397, ti=e7cf2000 task=f258ca90 
task.ti=e

7cf2000)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Stack: f8f18eb7 c01367f6 e7cf3e48 03e8 03e8 
ed3e97c0 f1f6db

9c f1f6db9c

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:e7cf3f54 f8f60ec2 0004257b   
f1f037dc e7cf3f

54 c01563d0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:019cc780 e7cf3eb0 c0155a63 dfff38c0 c014e001 
019cc780 f1f037

dc dfe0ecf4

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Call Trace:

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [f8f18eb7] rpcauth_lookupcred+0x63/0x87 [sunrpc]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c01367f6] pagevec_lookup+0x1c/0x22

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [f8f60ec2] nfs_permission+0xab/0x183 [nfs]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c01563d0] __d_lookup+0x8b/0xbf

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c0155a63] dput+0x15/0xcb

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion

Re: PROBLEM: kernel panic

2007-10-14 Thread Scott Petler

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,
altctrl 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

Doug Whitesell (LKML) wrote:

On Oct 14, 2007, at 1:44 PM, Scott Petler wrote:


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.


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



-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: PROBLEM: kernel panic

2007-10-14 Thread Scott Petler

Ok, I'll do that
Thanks

Sent from my iPhone

On Oct 14, 2007, at 2:32 PM, Trond Myklebust  
[EMAIL PROTECTED] wrote:




On Sun, 2007-10-14 at 14:00 -0700, Scott Petler wrote:

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,
altctrl 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


-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


PROBLEM: kernel panic

2007-10-13 Thread Scott Petler

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 Library3.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 [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Oops: 0002 [#1]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: CPU:0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP:0060:[]Tainted: PVLI

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EFLAGS: 00010206   (2.6.23-rc9 #3)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP is at 0xe1168fde

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: esi: f8f34700   edi:    ebp: 0001   esp: e7cf3e00

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: ds: 007b   es: 007b   fs:   gs: 0033  ss: 0068

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Process firefox-bin (pid: 8397, ti=e7cf2000 task=f258ca90 
task.ti=e

7cf2000)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Stack: f8f18eb7 c01367f6 e7cf3e48 03e8 03e8 
ed3e97c0 f1f6db

9c f1f6db9c

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:e7cf3f54 f8f60ec2 0004257b   
f1f037dc e7cf3f

54 c01563d0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:019cc780 e7cf3eb0 c0155a63 dfff38c0 c014e001 
019cc780 f1f037

dc dfe0ecf4

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Call Trace:

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] rpcauth_lookupcred+0x63/0x87 [sunrpc]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] pagevec_lookup+0x1c/0x22

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] nfs_permission+0xab/0x183 [nfs]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] __d_lookup+0x8b/0xbf

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] dput+0x15/0xcb

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] nfs_permission+0x0/0x183 [nfs]
Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] __link_path_walk+0x11c/0xa79

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] setup_sigcontext+0x104/0x187

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] link_path_walk+0x42/0xaf
Read from remote host 192.168.1.175: Connection reset by peer
Connection to 192.168.1.175 closed.

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [] permission+0x9e/0xdb


/proc/cpuinfo

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 2
model name  : Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping: 7
cpu MHz : 2411.749
cache size  : 512 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags  

PROBLEM: kernel panic

2007-10-13 Thread Scott Petler

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 Library3.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 [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Oops: 0002 [#1]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: CPU:0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP:0060:[e1168fde]Tainted: PVLI

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EFLAGS: 00010206   (2.6.23-rc9 #3)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: EIP is at 0xe1168fde

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: esi: f8f34700   edi:    ebp: 0001   esp: e7cf3e00

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: ds: 007b   es: 007b   fs:   gs: 0033  ss: 0068

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Process firefox-bin (pid: 8397, ti=e7cf2000 task=f258ca90 
task.ti=e

7cf2000)

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Stack: f8f18eb7 c01367f6 e7cf3e48 03e8 03e8 
ed3e97c0 f1f6db

9c f1f6db9c

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:e7cf3f54 f8f60ec2 0004257b   
f1f037dc e7cf3f

54 c01563d0

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:019cc780 e7cf3eb0 c0155a63 dfff38c0 c014e001 
019cc780 f1f037

dc dfe0ecf4

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel: Call Trace:

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [f8f18eb7] rpcauth_lookupcred+0x63/0x87 [sunrpc]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c01367f6] pagevec_lookup+0x1c/0x22

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [f8f60ec2] nfs_permission+0xab/0x183 [nfs]

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c01563d0] __d_lookup+0x8b/0xbf

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c0155a63] dput+0x15/0xcb

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [f8f60e17] nfs_permission+0x0/0x183 [nfs]
Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c014f648] __link_path_walk+0x11c/0xa79

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c0102ff8] setup_sigcontext+0x104/0x187

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c014ffe7] link_path_walk+0x42/0xaf
Read from remote host 192.168.1.175: Connection reset by peer
Connection to 192.168.1.175 closed.

Message from [EMAIL PROTECTED] at Sat Oct 13 15:22:34 2007 ...
zion kernel:  [c014de5a] permission+0x9e/0xdb


/proc/cpuinfo

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 2
model name  : Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping: 7
cpu MHz : 2411.749
cache size  : 512 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu