Displaying 4 results from an estimated 4 matches for "smarteyebox".
2005 Dec 15
0
Kernel panic in usbserial.
...Laptop) with a usb2serial interface plugged from the system boot, and
using that line as console line for a remote device, i had the following kernel
panic after few times performing the "reset" command in the gnome-terminal due
font corruption, i had this kernel panic:
Dec 14 23:58:10 smarteyebox kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000080
Dec 14 23:58:10 smarteyebox kernel: printing eip:
Dec 14 23:58:10 smarteyebox kernel: e0b598da
Dec 14 23:58:10 smarteyebox kernel: *pde = 00000000
Dec 14 23:58:10 smarteyebox kernel: Oops: 0000 [#1]
Dec 14 23:58:1...
2006 Jan 09
0
Kernel panic in usbserial - now in 2.6.9-22.0.1.106.unsupported, previous in 2.6.9-22.0.1.EL
...Laptop) with a usb2serial interface plugged from the system boot, and
using that line as console line for a remote device, i had the following kernel
panic after few times performing the "reset" command in the gnome-terminal due
font corruption, i had this kernel panic:
Dec 14 23:58:10 smarteyebox kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000080
Dec 14 23:58:10 smarteyebox kernel: printing eip:
Dec 14 23:58:10 smarteyebox kernel: e0b598da
Dec 14 23:58:10 smarteyebox kernel: *pde = 00000000
Dec 14 23:58:10 smarteyebox kernel: Oops: 0000 [#1]
Dec 14 23:58:1...
2006 Jul 03
2
new clamav update miss 'clamav' user/group creation/update
...tc/freshclam.conf?? (s/n) s
[root at sparkbox ~]# groupadd clamav
[root at sparkbox ~]# useradd -g clamav -s /sbin/nologin -c "Clam AntiVirus" clamav
[root at sparkbox ~]# service clamd start
Starting Clam AntiVirus Daemon: [
OK ]
[root at smarteyebox yum.repos.d]# freshclam -v
ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).
ERROR: Problem with internal logger.
[root at sparkbox ~]# l /var/log/clamav/
drwxr-xr-x 2 104 105 4,0K jul 3 10:32 clamav/
<...>
[root at sparkbox ~]# chown -R c...
2005 Dec 14
5
oom-killer.
...for this workstation? I think the oom-killer was called correctly to avoid the
system collapsed, but i think there was a problem in the swapping subsystem or a
memmory trashing situation to avoid.
Help and hints appreciated,
Attached you'll the oom-killer log,
TIA
J.J.
--
Linux smarteyebox.stigmatedbrain.net 2.6.9-22.0.1.EL i686 GNU/Linux
11:55:01 up 1 day, 12:06, 9 users, load average: 1.20, 1.30, 1.57
---------------------------------------------------------
"Rome wasn't burned in a day. "
-------------- next part --------------
An embedded and charset-unspecified tex...