search for: 33820

...EG 1643202022,2213797598   148320   223 /libexec/ld-elf.so.1 usbhid-up 4929 root  txt   VREG 1643202022,2213797598    93672 13486 /usr/lib/libusb.so.3 usbhid-up 4929 root  txt   VREG 1643202022,2213797598   131824   200 /lib/libthr.so.3 usbhid-up 4929 root  txt   VREG 1643202022,2213797598  1949672 33820 /lib/libc.so.7 usbhid-up 4929 root    0u  VCHR                  0,16      0t0    16 /dev/null usbhid-up 4929 root    1u  VCHR                  0,16      0t0    16 /dev/null usbhid-up 4929 root    2u  VCHR                  0,16      0t0    16 /dev/null usbhid-up 4929 root    3u  unix    0xfffff8023f...

...1950 FC-HBA is a 7104 from LSI 2GB RAM DualCore Xeon Kernel: 2.6.16.29-xen And here the output from lsmod in DomU: [root@samba3-1 modules]# lsmod Module Size Used by ipv6 254048 12 i2c_dev 11908 0 i2c_core 23808 1 i2c_dev binfmt_misc 12808 1 dm_mirror 23120 0 dm_mod 52248 1 dm_mirror snd_intel8x0 33820 0 snd_ac97_codec 93728 1 snd_intel8x0 snd_ac97_bus 6144 1 snd_ac97_codec snd_pcm_oss 51616 0 snd_mixer_oss 20352 1 snd_pcm_oss snd_pcm 88580 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 25860 1 snd_pcm snd 53348 6 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer sound...

http://bugs.freedesktop.org/show_bug.cgi?id=25258 Summary: [9400M] KMS and X do not use monitor's native resolution Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

Hi! On my FreeBSD 12.0-RELEASE-p7 server I was unable to retrieve the correct information from my two UPS. Every time only the first UPS will returned when I entering "upsc apc900" or "upsc apc901". I don't know why (Bug or configuration issue on my side?!). I have downloaded the latest source code and with my "patch" I was able to get the right information

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

...tigate the log as much as I can but i'm not getting any usefull pieces of information. The only entries I have in the log files are the following: /*log: /var/log/messages:*/ /Dec 5 09:53:35 hostname kernel: pid 33815 (imap), uid 0: exited on signal 11 Dec 5 09:53:39 hostname kernel: pid 33820 (imap), uid 0: exited on signal 11 Dec 5 09:54:22 hostname kernel: pid 33910 (pop3), uid 0: exited on signal 11 Dec 5 09:55:22 hostname kernel: pid 34071 (pop3), uid 0: exited on signal 11 Dec 5 09:55:47 hostname kernel: pid 34103 (imap), uid 0: exited on signal 11 Dec 5 09:56:13 hostname k...

...IN= OUT=eth2 SRC=192.168.16.1 DST=216.165.191.52 LE N=72 TOS=0x00 PREC=0x00 TTL=64 ID=9582 DF PROTO=TCP SPT=56528 DPT=6667 WINDOW=18824 RES= 0x00 ACK PSH URGP=0 Jul 4 16:01:29 thecrow WRONG IFACE: IN= OUT=eth1 SRC=192.168.17.1 DST=130.206.1.5 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=66 DF PROTO=TCP SPT=33820 DPT=21 WINDOW=0 RES=0x00 RST URGP=0 Even though, when I use ''tcpdump'' for catching the wrong packets (that is: tcpdump -i eth1 host 192.168.17.1 _or_ tcpdump -i eth2 host 192.168.16.1 ) results that _A LOT MORE PACKETS_ are BADLY ROUTED, than sent to the LOG target. My conclusi...