I'm running FreeBSD 10.2 with all latest updates in core and ports. I'm using the stock kernel.
I connected two USB 3 external HDDs (to USB 2 ports) and used a rsync to sync the data from one drive (UFS) to the other (NTFS). I let it run the whole night.
When I woke up I couldn't ssh (connection refused) so I went to the machine itself and saw a message being repeated:
I couldn't switch from one virtual console to the next (ctrl-alt-f2) and I couldn't restart (ctrl-alt-del). Normally, when I press the power button, the machine shuts down, but in this case it wouldn't.
I pressed the Num Lock key and the led on the keyboard didn't turn off. So I disconnected the USB mouse and the USB keyboard and connected just the keyboard. The message stopped popping on the screen and I saw a message about a keyboard being connected.
I was able to press Scroll Lock and run up-down in the framebuffer but nothing more than that. I had to pull the power plug. When I powered it back, the machine booted (I don't remember if it normally does that). I went away from the machine after I plugged in (didn't expect to just boot) so I don't know if there was any message that I should pay attention to something.
After that the OS booted normally and runs as we speak.
So, what was that? Am I looking at a hardware issue? A motherboard problem? A mouse problem? And why did SSHd stopped? I must say I'm a bit worried about the data in the two drives that synced, but that belongs to another topic.
I don't have any lines related to moused in /etc/rc.conf.
I use sc as my framebuffer.
I have kept connected this particular mouse in this FreeBSD machine in the past two months, and I have used it a bit inside Xorg. It's the first time this thing happens.
Lets check my /var/log/messages.
You'll notice this entry:
That's because I've set this machine to update the core OS and the ports automatically every few hours. There was an update and then a machine restart.
There is a skip of a few hours after that:
That's all I can notice in /var/log/messages.
I connected two USB 3 external HDDs (to USB 2 ports) and used a rsync to sync the data from one drive (UFS) to the other (NTFS). I let it run the whole night.
When I woke up I couldn't ssh (connection refused) so I went to the machine itself and saw a message being repeated:
Code:
ums0: 3 buttons and [XYZ] coordinates ID=0
ugen4.2: <PixArt> at usbus4
ums0: <PixArt Microsoft USB Optical Mouse, class 0/0, rev 1.10/1.00, addr 2> on usbus4
I couldn't switch from one virtual console to the next (ctrl-alt-f2) and I couldn't restart (ctrl-alt-del). Normally, when I press the power button, the machine shuts down, but in this case it wouldn't.
I pressed the Num Lock key and the led on the keyboard didn't turn off. So I disconnected the USB mouse and the USB keyboard and connected just the keyboard. The message stopped popping on the screen and I saw a message about a keyboard being connected.
I was able to press Scroll Lock and run up-down in the framebuffer but nothing more than that. I had to pull the power plug. When I powered it back, the machine booted (I don't remember if it normally does that). I went away from the machine after I plugged in (didn't expect to just boot) so I don't know if there was any message that I should pay attention to something.
After that the OS booted normally and runs as we speak.
So, what was that? Am I looking at a hardware issue? A motherboard problem? A mouse problem? And why did SSHd stopped? I must say I'm a bit worried about the data in the two drives that synced, but that belongs to another topic.
I don't have any lines related to moused in /etc/rc.conf.
I use sc as my framebuffer.
I have kept connected this particular mouse in this FreeBSD machine in the past two months, and I have used it a bit inside Xorg. It's the first time this thing happens.
Lets check my /var/log/messages.
You'll notice this entry:
Code:
Nov 18 08:02:32 freebsd pkg: png upgraded: 1.6.18 -> 1.6.19
Nov 18 08:02:32 freebsd pkg: libvpx upgraded: 1.4.0.488 -> 1.4.0.488_1
Nov 18 08:02:32 freebsd shutdown: reboot by root:
That's because I've set this machine to update the core OS and the ports automatically every few hours. There was an update and then a machine restart.
There is a skip of a few hours after that:
Code:
Nov 18 08:02:42 freebsd syslogd: exiting on signal 15
Nov 18 15:09:46 freebsd syslogd: kernel boot file is /boot/kernel/kernel
That's all I can notice in /var/log/messages.