Ok, that wasn't it either! Log files don't seem to be showing me anything! Here is messages about that time: May 8 21:13:06 localhost dhclient: bound to 192.168.2.37 -- renewal in 1670 seconds. May 8 21:40:56 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67 May 8 21:40:56 localhost dhclient: DHCPACK from 192.168.2.10 May 8 21:40:56 localhost dhclient: bound to 192.168.2.37 -- renewal in 1577 seconds. May 8 22:07:13 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67 May 8 22:07:13 localhost dhclient: DHCPACK from 192.168.2.10 May 8 22:07:13 localhost dhclient: bound to 192.168.2.37 -- renewal in 1684 seconds. May 8 22:35:17 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67 May 8 22:35:17 localhost dhclient: DHCPACK from 192.168.2.10 May 8 22:35:17 localhost dhclient: bound to 192.168.2.37 -- renewal in 1547 seconds. May 8 23:01:04 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67 May 8 23:01:04 localhost dhclient: DHCPACK from 192.168.2.10 May 8 23:01:04 localhost dhclient: bound to 192.168.2.37 -- renewal in 1541 seconds. May 8 23:08:28 localhost ntpd[1889]: synchronized to 209.193.103.214, stratum 2 May 8 23:26:45 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67 May 8 23:26:45 localhost dhclient: DHCPACK from 192.168.2.10 May 8 23:26:45 localhost dhclient: bound to 192.168.2.37 -- renewal in 1398 seconds. May 9 06:26:29 localhost kernel: imklog 3.14.1, log source = /proc/kmsg started. On Thu, May 8, 2008 at 7:23 PM, Dr. Diesel <dr.diesel@xxxxxxxxx> wrote: > On Thu, May 8, 2008 at 7:25 PM, Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > On Thu, May 8, 2008 at 4:58 PM, Dr. Diesel <dr.diesel@xxxxxxxxx> wrote: > >> Still happens without the vboxdrv kernel module.... > >> > > > > was it a rmmod or a reboot of the system without the module? Sometimes > > loading a module will much with the kernel enough that removing it is > > not enough to make a problem not occur. You might also want to run sar > > at 1 minute intervals and see if something like 100% CPU usage etc is > > occuring? > > > > Ok, vboxdrv now disabled at boot, not just rmmod. > > I don't think it was a 100% CPU issue, I was not able to loggin via > SSH either. The number lock and caps lock keys were also > non-responsive also. > > > > > -- > > > projecthuh.com > All of my bits are free, are yours? Fedoraproject.org > -- projecthuh.com All of my bits are free, are yours? Fedoraproject.org -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
