keyboard driver problem?
Hello, have problem with A4Tech G7100 wireless combo mouse+keyboard. Mouse works fine, but keyboard not. It's loading: ugen4.2: A4TECH at usbus4 ukbd1: A4TECH USB Device, class 0/0, rev 1.10/1.02, addr 2 on usbus4 but pressing any key doesn't have effect. It works only in one way - if i pressing one (any) key and don't releasing it and preessing another key at the same time. For example to make work key a i should press b (and don't releasing it, use like shift) and after that pressing key a. And it works. This problem is only in 8.x branch. At Freebsd 7.3, 7.4 it works ok. I think the problem is in new ukbd-driver, when i press 'q' key, debug says: ukbd_intr_callback:547: actlen=8 bytes ukbd_intr_callback:590: apple_eject=0 apple_fn=0 ukbd_intr_callback:597: [0] = 20 ukbd_put_key:312: 0x14 (20) pressed ukbd_intr_callback:547: actlen=8 bytes ukbd_intr_callback:590: apple_eject=0 apple_fn=0 ukbd_put_key:312: 0x414 (1044) released (this is for usb wire-keyboard that works fine) ukbd_intr_callback:547: actlen=12 bytes ukbd_intr_callback:590: apple_eject=0 apple_fn=0 (and this is for my ATech G7100 keyboard) Could you tell me where the problem is? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On Saturday 01 January 2011 19:47:21 you wrote: On Mon, Dec 27, 2010 at 02:05:25AM +0100, Bernhard Schmidt wrote: On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: [ .. ] If you can get debug output while the UPs/DOWNs happen, that would help a lot. Sorry about the delay. The laptop has been in Windows land for the last week. I finally have a log where the interface is going UP/DOWN and have wlandebug in effect. It's 220KB. You can find it at Thanks http://troutmask.apl.washington.edu/~kargl/wlan0.msg wlan0: AMRR decreasing rate 48 (txcnt=35 retrycnt=14) wlan0: recv deauthenticate (reason 2) wlan0: ieee80211_new_state_locked: RUN - AUTH (nrunning 0 nscanning 0) I've seen those before, though, I never figured out if there is a way to bypass that. What's happening here is that the AP detects that you've ben idle (as in not sending frames) for quite a while (the rate decrease does indicate that) and kicks you with a 'auth no longer valid' message. This seems to be a 'feature' of your AP and not an issue with the driver, at least I do not see any connection. As a workaround try to ping something behind the AP. -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: keyboard driver problem?
On Sunday 02 January 2011 09:36:06 too.much.du...@gmail.com wrote: Hello, have problem with A4Tech G7100 wireless combo mouse+keyboard. Mouse works fine, but keyboard not. It's loading: ugen4.2: A4TECH at usbus4 ukbd1: A4TECH USB Device, class 0/0, rev 1.10/1.02, addr 2 on usbus4 but pressing any key doesn't have effect. It works only in one way - if i pressing one (any) key and don't releasing it and preessing another key at the same time. For example to make work key a i should press b (and don't releasing it, use like shift) and after that pressing key a. And it works. This problem is only in 8.x branch. At Freebsd 7.3, 7.4 it works ok. I think the problem is in new ukbd-driver, when i press 'q' key, debug says: ukbd_intr_callback:547: actlen=8 bytes ukbd_intr_callback:590: apple_eject=0 apple_fn=0 ukbd_intr_callback:597: [0] = 20 ukbd_put_key:312: 0x14 (20) pressed ukbd_intr_callback:547: actlen=8 bytes ukbd_intr_callback:590: apple_eject=0 apple_fn=0 ukbd_put_key:312: 0x414 (1044) released (this is for usb wire-keyboard that works fine) ukbd_intr_callback:547: actlen=12 bytes ukbd_intr_callback:590: apple_eject=0 apple_fn=0 (and this is for my ATech G7100 keyboard) Could you dump the device and configuration descriptors of your keyboard using the usbconfig utility. usbconfig -d X.Y dump_device_desc dump_curr_config_desc It looks like your keyboard is sending 12 bytes instead of 8, which is expected from UKBD. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: keyboard driver problem?
On Sunday 02 January 2011 09:36:06 too.much.du...@gmail.com wrote: Hello, have problem with A4Tech G7100 wireless combo mouse+keyboard. Mouse works fine, but keyboard not. It's loading: ugen4.2: A4TECH at usbus4 ukbd1: A4TECH USB Device, class 0/0, rev 1.10/1.02, addr 2 on usbus4 but pressing any key doesn't have effect. It works only in one way - if i pressing one (any) key and don't releasing it and preessing another key at the same time. For example to make work key a i should press b (and don't releasing it, use like shift) and after that pressing key a. And it works. This problem is only in 8.x branch. At Freebsd 7.3, 7.4 it works ok. I think the problem is in new ukbd-driver, when i press 'q' key, debug In sys/dev/usb/input/ukbd.c, you could try to redefine this variable to 8. #define UKBD_NKEYCODE 6 /* units */ --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Suddenly slow lstat syscalls on CURRENT from Juli
On 01.01.2011 18:26, Kostik Belousov wrote: On Sat, Jan 01, 2011 at 05:59:10PM +0100, Beat G?tzi wrote: On 01.01.2011 17:46, Kostik Belousov wrote: On Sat, Jan 01, 2011 at 05:42:58PM +0100, Beat G?tzi wrote: On 01.01.2011 17:12, Kostik Belousov wrote: On Sat, Jan 01, 2011 at 05:00:56PM +0100, Beat G?tzi wrote: On 01.01.2011 16:45, Kostik Belousov wrote: Check the output of sysctl kern.maxvnodes and vfs.numvnodes. I suspect they are quite close or equial. If yes, consider increasing maxvnodes. Another workaround, if you have huge nested directories hierarhy, is to set vfs.vlru_allow_cache_src to 1. Thanks for the hint. kern.maxvnodes and vfs.numvnodes were equal: # sysctl kern.maxvnodes vfs.numvnodes kern.maxvnodes: 10 vfs.numvnodes: 100765 I've increased kern.maxvnodes and the problem was gone until vfs.numvnodes reached the value of kern.maxvnodes again: # sysctl kern.maxvnodes vfs.numvnodes kern.maxvnodes: 15 vfs.numvnodes: 150109 The processes should be stuck in vlruwk state, that can be checked with ps or '^T' on the terminal. Yes, there are various processes in vlruwk state, As the directory structure is quite huge on this server I've set vfs.vlru_allow_cache_src to one now. Did it helped ? No, it doesn't looks like setting vfs.vlru_allow_cache_src helped. The problem was gone when I increased kern.maxvnodes until vfs.numvnodes reached that level. I've stopped all running deamons but numvnodes doesn't decrease. Stopping the daemons would not decrease the count of cached vnodes. What you can do is to call unmount on the filesystems. Supposedly, the filesystems are busy and unmount shall fail, but it will force freed the vnodes that are unused by any process. That freed around 1500 vnodes. At the moment the vfs.numvnodes doesn't increase rapidly and the server is usable. I will keep an eye it to see if I run into the same problem again. This is too small amount of vnodes to be freed for the typical system, and it feels like a real vnode leak. It would be helpful if you tried to identify the load that causes the situation to occur. From the data I collect from the server it doesn't look like a constant leak: 2010-12-21/18/00: vfs.numvnodes: 84089 2010-12-22/18/00: vfs.numvnodes: 76599 2010-12-23/18/00: vfs.numvnodes: 22854 2010-12-24/18/00: vfs.numvnodes: 17940 2010-12-25/18/00: vfs.numvnodes: 84999 2010-12-26/18/00: vfs.numvnodes: 84601 2010-12-27/18/00: vfs.numvnodes: 32724 2010-12-28/18/00: vfs.numvnodes: 141104 I checked for the exact point in time when vfs.numvnodes hit the limit: 2010-12-28/01/30: vfs.numvnodes: 71566 2010-12-28/01/35: vfs.numvnodes: 82448 2010-12-28/01/40: vfs.numvnodes: 89826 2010-12-28/01/45: vfs.numvnodes: 79625 2010-12-28/01/50: vfs.numvnodes: 24678 2010-12-28/01/55: vfs.numvnodes: 100045 2010-12-28/02/00: vfs.numvnodes: 100351 2010-12-28/02/05: vfs.numvnodes: 100685 2010-12-28/02/10: vfs.numvnodes: 100989 Every night at 1:02 there is a script running that checks out SVN trunk of VirtualBox and tries to build that in the tinderbox. From the tinderbox logs I see that the build of virtualbox-ose-devel-4.0.1.r35314 on FreeBSD 7 Jail was finished at 2010-12-28 01:47:05. At 01:48:55 the build for FreeBSD 8 started but it looks like something went wrong there as this build never finished. Unfortunately I'm not able to reproduce what of that build caused this problem. There were no changes in the VBox SVN between the 27th and the 28th so on the 27th an identical tinderbox run was successful. You are on the UFS, right ? Yes, UFS with Softupdates except on /: # mount /dev/da0s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/da0s1d on /tmp (ufs, local, soft-updates) /dev/da0s1f on /usr (ufs, local, soft-updates) /dev/da0s1e on /var (ufs, local, noexec, nosuid, soft-updates) Beat ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
keyboard driver problem?
I've tried already to change both UKBD_NMOD and UKBD_NKEYCODE, but where is no result. #define UKBD_NKEYCODE 8 // doesn't work too usbconfig -u 4 -a 2 dump_device_desc dump_curr_config_desc ugen4.2: USB Device A4TECH at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x09da idProduct = 0x054f bcdDevice = 0x0102 iManufacturer = 0x0001 A4TECH iProduct = 0x0002 USB Device iSerialNumber = 0x no string bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x003b bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x no string Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x84, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x000c bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x no string Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x57, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x // sorry if i missed the thread, dunno how to reply via gmail correctly ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: keyboard driver problem?
On Sunday 02 January 2011 15:22:32 I Think wrote:
I've tried already to change both UKBD_NMOD and UKBD_NKEYCODE, but where is
no result.
#define UKBD_NKEYCODE 8 // doesn't work too
usbconfig -u 4 -a 2 dump_device_desc dump_curr_config_desc
ugen4.2: USB Device A4TECH at usbus4, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0110
bDeviceClass = 0x
bDeviceSubClass = 0x
bDeviceProtocol = 0x
bMaxPacketSize0 = 0x0008
idVendor = 0x09da
idProduct = 0x054f
bcdDevice = 0x0102
iManufacturer = 0x0001 A4TECH
iProduct = 0x0002 USB Device
iSerialNumber = 0x no string
bNumConfigurations = 0x0001
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x003b
bNumInterfaces = 0x0002
bConfigurationValue = 0x0001
iConfiguration = 0x no string
bmAttributes = 0x00a0
bMaxPower = 0x0032
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x
bAlternateSetting = 0x
bNumEndpoints = 0x0001
bInterfaceClass = 0x0003
bInterfaceSubClass = 0x0001
bInterfaceProtocol = 0x0001
iInterface = 0x no string
Additional Descriptor
bLength = 0x09
bDescriptorType = 0x21
bDescriptorSubType = 0x11
RAW dump:
0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x84,
0x08 | 0x00
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081
bmAttributes = 0x0003
wMaxPacketSize = 0x000c
bInterval = 0x0001
bRefresh = 0x
bSynchAddress = 0x
Interface 1
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x0001
bAlternateSetting = 0x
bNumEndpoints = 0x0001
bInterfaceClass = 0x0003
bInterfaceSubClass = 0x0001
bInterfaceProtocol = 0x0002
iInterface = 0x no string
Additional Descriptor
bLength = 0x09
bDescriptorType = 0x21
bDescriptorSubType = 0x11
RAW dump:
0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x57,
0x08 | 0x00
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0082
bmAttributes = 0x0003
wMaxPacketSize = 0x0008
bInterval = 0x0001
bRefresh = 0x
bSynchAddress = 0x
You could maybe try this. Lookup the following code in ukbd.c. Add the lines
marked with +
if (sc-sc_kbd_id != 0) {
/* check and remove HID ID byte */
usbd_copy_out(pc, 0, id, 1);
if (id != sc-sc_kbd_id) {
DPRINTF(wrong HID ID\n);
goto tr_setup;
}
offset = 1;
len--;
} else {
offset = 0;
}
+ if (len == 12) {
+ offset += 2;
+ len -= 2;
+ }
+ if (len == 11) {
+ offset += 1;
+ len -= 1;
+ }
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: userland weirdness between r216351 and r216738
Op 31-12-2010 23:43, Alexander Kabaev schreef: On Fri, 31 Dec 2010 22:35:05 +0100 René Ladan r...@freebsd.org wrote: Hi, somewhere between 9.0-amd64 r216351 and r216738, I've noticed some userland weirdness. Symptoms are: - pseudo-random number generator not starting, preventing ssh(d) from working - fonts in X.org (xfce4) missing or replaced - mouse only working when hald is running I don't know if the above symptoms are somehow related, or what causes them. The kernel is GENERIC without (u)lpt and umass and with these modules loaded: fdescfs.ko if_iwn.ko snd_hda.ko sound.ko umass.ko iwn5000fw.ko nvidia.ko (256.53) linux.ko cuse4bsd.ko atapicam.ko linprocfs.ko Kernel and world are compiled with FreeBSD clang version 2.8 (tags/RELEASE_28 115870) 20101007 Reverting to r216351 (kernel, world, mergemaster) brought things back to normal. I can do a binary search if desired. Did someone else also see this? Happy 2011, Rene Try backing out rtld down to version prior to this commit http://svn.freebsd.org/changeset/base/216695 . There is an issue with rtld's use of SSE on amd64 which will be fixed soon. Backing out src/libexec/rtld-elf to r216694 solved it for now :) Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
keyboard driver problem?
already tried variants : offset+=4 len-=4 offset+=0 len-=4 and yours, but they doesn't have correct effect (yours variant gives some addition lags: for example pressing o presses Scroll Lock, h - WIN_L and etc) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Suddenly slow lstat syscalls on CURRENT from Juli
On 02.01.2011 01:36, Julian Elischer wrote: On 1/1/11 9:26 AM, Kostik Belousov wrote: On Sat, Jan 01, 2011 at 05:59:10PM +0100, Beat G?tzi wrote: On 01.01.2011 17:46, Kostik Belousov wrote: On Sat, Jan 01, 2011 at 05:42:58PM +0100, Beat G?tzi wrote: On 01.01.2011 17:12, Kostik Belousov wrote: On Sat, Jan 01, 2011 at 05:00:56PM +0100, Beat G?tzi wrote: On 01.01.2011 16:45, Kostik Belousov wrote: Check the output of sysctl kern.maxvnodes and vfs.numvnodes. I suspect they are quite close or equial. If yes, consider increasing maxvnodes. Another workaround, if you have huge nested directories hierarhy, is to set vfs.vlru_allow_cache_src to 1. Thanks for the hint. kern.maxvnodes and vfs.numvnodes were equal: # sysctl kern.maxvnodes vfs.numvnodes kern.maxvnodes: 10 vfs.numvnodes: 100765 I've increased kern.maxvnodes and the problem was gone until vfs.numvnodes reached the value of kern.maxvnodes again: # sysctl kern.maxvnodes vfs.numvnodes kern.maxvnodes: 15 vfs.numvnodes: 150109 The processes should be stuck in vlruwk state, that can be checked with ps or '^T' on the terminal. Yes, there are various processes in vlruwk state, As the directory structure is quite huge on this server I've set vfs.vlru_allow_cache_src to one now. Did it helped ? No, it doesn't looks like setting vfs.vlru_allow_cache_src helped. The problem was gone when I increased kern.maxvnodes until vfs.numvnodes reached that level. I've stopped all running deamons but numvnodes doesn't decrease. Stopping the daemons would not decrease the count of cached vnodes. What you can do is to call unmount on the filesystems. Supposedly, the filesystems are busy and unmount shall fail, but it will force freed the vnodes that are unused by any process. That freed around 1500 vnodes. At the moment the vfs.numvnodes doesn't increase rapidly and the server is usable. I will keep an eye it to see if I run into the same problem again. This is too small amount of vnodes to be freed for the typical system, and it feels like a real vnode leak. It would be helpful if you tried to identify the load that causes the situation to occur. You are on the UFS, right ? try running sockstat to a file and looking to see what is open.. it could just be a normal leak. The sockstat output looks normal at least to me: http://tmp.chruetertee.ch/tinderbox-sockstat Thanks, Beat ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: keyboard driver problem?
On Sunday 02 January 2011 15:42:42 too.much.du...@gmail.com wrote:
already tried variants :
offset+=4 len-=4
offset+=0 len-=4
and yours, but they doesn't have correct effect
(yours variant gives some addition lags:
for example pressing o presses Scroll Lock, h - WIN_L and etc)
Hi,
Maybe you can add a printout, to dump the len bytes:
uint32_t yy;
printf(UKBD data: );
for (yy = 0; yy != len; yy++)
{
uint8_t temp;
usbd_copy_out(pc, offset + yy, temp, 1);
printf(0x%02x , (int)temp);
}
printf(\n);
I guess the reason your keyboard doesn't work is that we don't parse any HID
descriptors in UKBD.
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
jailing MYSQL error
Hi. I'm using ezjail standard config file, with a modified fstab file (mount_nullfs ports to jail). Cat /usr/local/etc/ezjail/j009_mysql2 export jail_j009_mysql2_hostname=j009_mysql2 export jail_j009_mysql2_ip=xx.xx.xx.xx export jail_j009_mysql2_rootdir=/ezjail/j009_mysql2 export jail_j009_mysql2_exec_start=/bin/sh /etc/rc export jail_j009_mysql2_exec_stop= export jail_j009_mysql2_mount_enable=YES export jail_j009_mysql2_devfs_enable=YES export jail_j009_mysql2_devfs_ruleset=devfsrules_jail export jail_j009_mysql2_procfs_enable=YES export jail_j009_mysql2_fdescfs_enable=YES export jail_j009_mysql2_image= export jail_j009_mysql2_imagetype= export jail_j009_mysql2_attachparams= export jail_j009_mysql2_attachblocking= export jail_j009_mysql2_forceblocking= export jail_j009_mysql2_zfs_datasets= export jail_j009_mysql2_cpuset= export jail_j009_mysql2_fib= My steps: 1. Ezjail-admin onestart j009_mysql2 2. Ezjail-admin console j009_mysql2 3. Cd /usr/ports/database/mysql55-server make install clean 4. cp /usr/local/share/mysql/my-innodb-heavy-4G.cnf /usr/local/etc/my.cnf (modified socket file path to /var/db/mysql/mysql.sock, in both client and server lines) 5. chown -R mysql:mysql ... for ... /tmp /var/tmp /var/db/mysql 6. mysql_enable=YES in jail rc.conf 7. /usr/local/etc/rc.d/mysql-server start 8. ...and NOTHING ... mysql-server scripts starts /usr/local/bin/mysql_install_db (creates mysql and test folders in /var/db/mysql ... but nothing else ... it's just running) I had to kill everything. After reading lots of webpages and trying all kind of stuff (including http://devel.reinikainen.net/15, but without ssl stuff), I decided to install MySQL on the host. I've made the same steps (3-5 and 7 with onestart instead start) and used the same my-innodb-heavy-4G.cnf file Everything went well. Mysqld started, creating socket file and pid file; mysql_install_db had no errors. The log file says: 110102 18:07:06 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql 110102 18:07:06 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.5 110102 18:07:06 InnoDB: Initializing buffer pool, size = 2.0G 110102 18:07:07 InnoDB: Completed initialization of buffer pool 110102 18:07:07 InnoDB: highest supported file format is Barracuda. 110102 18:07:07 InnoDB: 1.1.3 started; log sequence number 1595675 110102 18:07:07 [Note] Event Scheduler: Loaded 0 events 110102 18:07:07 [Note] /usr/local/libexec/mysqld: ready for connections. Version: '5.5.7-rc-log' socket: '/var/db/mysql/mysql.sock' port: 3306 FreeBSD port: mysql-server-5.5.7 I didn't give up ... so I did: 9. Rm -rf /var/db/mysql/* (in jail) 10. Cp /var/db/mysql/mysql/* /ezjail/j009_mysql2/var/db/mysql/mysql (from host to jail) 11. Cp /var/db/mysql/performance_schema/* /ezjail/j009_mysql2/var/db/mysql/performance_schema (from host to jail) 12. Starting and entering the jail again 13. usr/local/etc/rc.d/mysql-server start was started upon entering the jail (did not create pid and socket file) but generated this log: 110102 17:03:05 [Note] Plugin 'FEDERATED' is disabled. /usr/local/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 110102 17:03:05 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.5 110102 17:03:05 InnoDB: Initializing buffer pool, size = 2.0G 110102 17:03:06 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file /innodb/ibdata1 did not exist: InnoDB: a new database to be created! 110102 17:03:06 InnoDB: Setting file /innodb/ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 110102 17:03:06 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 256 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 110102 17:03:08 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 256 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 110102 17:03:10 InnoDB: Log file ./ib_logfile2 did not exist: new to be created InnoDB: Setting log file ./ib_logfile2 size to 256 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 14. usr/local/etc/rc.d/mysql-server stop ... doesn't work because of missing pid file (the same with mysql_upgrade suggested by the log file) 15. './mysql/plugin.frm' file exists 16. kill everything and run again usr/local/etc/rc.d/mysql-server start with this result: 110102 17:07:40 [Note] Plugin
Re: keyboard driver problem?
ukbd_intr_callback:547: actlen=12 bytes ukbd_intr_callback:568: UKBD data: ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x14 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:575: 0x00 ukbd_intr_callback:578: ukbd_intr_callback:603: apple_eject=0 apple_fn=0 i tried debug sc_odata.keycode[i] sc_ndata.keycode[i] at function ukbd_interrupt(), they are empty, but for another keyboard they are not. I guess the reason your keyboard doesn't work is that we don't parse any HID descriptors in UKBD. So why is it working in freebsd 7.x then? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: jailing MYSQL error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Just to be sure as the long detailed information that you laid before can lead to confusion, lets take this one step at a time. Assuming all your bases are covered and it sinks down to a permissions issue try this: chown root:wheel /path/to/jail/tmp /path/to/jail/var/tmp chmod 1777 /path/to/jail/tmp /path/to/jail/var/tmp rm -rf /path/to/jail/var/db/mysql - -Login to the jail here- make sure that rc.conf* only contains mysql_enable=YES service mysql-server start ls -ld /var/db/mysql should convey mode 700 or drwx-- and uid/88 gid/88 mysql/mysql At this point your mysql server should be running and fully working. Another thing to make sure you eliminate just in case... would be any my.cnf files in /etc or /usr/local/etc Good luck - -- Regards, jhell,v JJH48-ARIN -BEGIN PGP SIGNATURE- iQEcBAEBAgAGBQJNIPrkAAoJEJBXh4mJ2FR+fLEH/0N91782PKGna/DZNoRF4hWJ 8tTh9bPFaHGjRu2ITC08gFJBLaAK8hE5oh9Tg5k6eysyzjE1EEHXUAJaL6B8Rg+N w5m66OGtvunX8JQqwu8d6ulDLk4EHex7Aaf0G2wfpW2OBDP4oCbeXxaakDJp+dzB GGf4a4ezODgQsr8Hxva71bgesfQ6a1BEirf/pwGcaQs9y1lCgoRK6M+iKDKqruLM Vyp4oNCHX52GTKa/cpx2VveZG/F21RabYtCVrBhU3Xq0EbDeDkiP2JjZt0xNPJVA dnCfCtTRECeruqlFHekH7MayF7uZ5nZIjJ3SEA6xHTCyt3PVC7oxr1NCmaETWJQ= =HFv4 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Call for testers] FreeBSD VirtIO Network Driver
On Sun, Jan 2, 2011 at 5:02 PM, bv deboomer...@gmail.com wrote: Hi. I'd like to present the network VirtIO driver I've been working on for the last few months in my spare time. It is not based on the NetBSD code that is floating around. The attached patch should apply to both recent -current and -stable. Early development was done on VirtualBox, but most has been done on KVM/QEMU. snip I'm going to be away from my computer for the next couple of days, I'll get to any email after then. Thanks for this work, I'm sure it will be quite useful. I'm testing on a FreeBSD Virtualbox Host/Guest. Guest is CURRENT kern.osrevision: 199506 virtualbox-ose-3.2.10_2 My particular version of Virtualbox isn't optimized yet for virtio I believe, but I did see about 1/3 higher peak bandwidth and a definite reduction in CPU usage. -- Adam Vande More ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
