search for: ioctls

Hi all, I'm a new user trying to get a Proline UPS I1000 UPS to work with freenas 9.3 over USB. When running upsdrvctl I get a permission denied error. Required debug info: OS name and version, # uname -a FreeBSD freenas.local 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #2 r275790+f84e770: Tue Dec 23 23:35:33 PST 2014 root at

Hello, I have a Salicru UPS connected by USB using nutdrv_qx driver. As I see that it was using too much CPU time (or at least, too much for what I think it should be normal), I used strace to see what is was using, and got a lot of lines like these: %<------------%<------------%<------------%<------------ ioctl(4, USBDEVFS_REAPURBNDELAY, 0x7ffdca143278) = -1 EAGAIN (Resource

I've got a Powercom Imperial UPS, with an internal USB<=>serial converter. It implements the same protocol as other powercom devices implements, but only when talking over serial port (there's no such port on the device). Someone wrote a draft version of usbserial driver for it, and the UPS works with this kernel-level driver and with powercom driver from nut (using /dev/ttyUSBx

I was in the process of doing a large zfs send | zfs receive when I decided that I wanted to terminate the the zfs send process. I killed it, but the zfs receive doesn''t want to die... In the meantime my zfs list command just hangs. Here is the tail end of the truss output from a "truss zfs list": ioctl(3, ZFS_IOC_OBJSET_STATS, 0x08043484) = 0 ioctl(3,

Hey all -- First post, so first off thanks for creating this wonderful software and helping out new users like me adapt to the wine-way :) Has anyone managed to get Windows/Mac only data analysis and vis suite Tableau Public (http://www.tableausoftware.com/public/download) running with any version Wine yet? It goes through the motions of installing, but then won't run. I'd welcome any

Hello Dmitry On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote: > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton <hdanton at sina.com> wrote: > > > > Hello Jason > > > > On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote: > > > > > > This is basically a kfree(ubuf) after the second vhost_net_flush() in > > > vhost_net_release(). >

Hello Dmitry On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote: > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton <hdanton at sina.com> wrote: > > > > Hello Jason > > > > On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote: > > > > > > This is basically a kfree(ubuf) after the second vhost_net_flush() in > > > vhost_net_release(). >

I am using the srpm from http://xenbits.xensource.com/kernels/rhel3x/kernel-2.4.21-47.0.1.EL.xs0.3.5. 15.src.rpm (I get the same issue using the binary RPM) the dom0 is running 3.0.3_0 Upon booting the DomU, (the DomU has been passed phy:/dev/sda6, which has been partitioned using qemu) I get the following ioctl errors. ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported

Returns a file''s size on disk. Had been posted by Chris Ball over a year ago (http://article.gmane.org/gmane.comp.file-systems.btrfs/2873). Chris Mason suggested a couple of improvements back then, which I have implemented in this version: - use u64 to return the result - replaced the loop while (1) { struct btrfs_ordered_extent *ordered;

...your host kernel, and your userspace launcher are in a +consistent state. + +This Documentation describes the unique ioctl calls to /dev/kvm, the resulting +kvm-vm file descriptors, and the kvm-vcpu file descriptors that differ from x86. + +1. ioctl calls to /dev/kvm +KVM does support the following ioctls on s390 that are common with other +architectures and do behave the same: +KVM_GET_API_VERSION +KVM_CREATE_VM (*) see note +KVM_CHECK_EXTENSION +KVM_GET_VCPU_MMAP_SIZE + +Notes: +* KVM_CREATE_VM may fail on s390, if the calling process has multiple +threads and has not called KVM_S390_ENABLE_SIE b...

...your host kernel, and your userspace launcher are in a +consistent state. + +This Documentation describes the unique ioctl calls to /dev/kvm, the resulting +kvm-vm file descriptors, and the kvm-vcpu file descriptors that differ from x86. + +1. ioctl calls to /dev/kvm +KVM does support the following ioctls on s390 that are common with other +architectures and do behave the same: +KVM_GET_API_VERSION +KVM_CREATE_VM (*) see note +KVM_CHECK_EXTENSION +KVM_GET_VCPU_MMAP_SIZE + +Notes: +* KVM_CREATE_VM may fail on s390, if the calling process has multiple +threads and has not called KVM_S390_ENABLE_SIE b...

Hi everyone, This patchset is the latest approach I''m using for the Ceph storage daemon to keep track of which data has safely committed to disk. The basic idea is to not use the (problematic) user transaction ioctls at all. Instead, the daemon quiesces its own write requests, initiates an async snapshot, and then continues. The snapshot approach is nice because it provides rollback. If something goes wrong, we can cleanly go back to the most recent consistent commit. The performance is also very similar to...

I've just updated today to 0.9.58 from wine 0.9.57 using the official ubuntu repositories reported in the main page and i've found a regression regarding quicktime (7.4). At a first look the application seems to load fine but when i do file=>open file... and choose a quicktime movie (it was exported from keynote and has points where the animation locks automatically waiting for the user

...vhost's ioctl on VFIO device fd directly, > > > > or introducing another mdev driver (i.e. vhost_mdev instead of > > > > using the existing vfio_mdev) for mdev device? > > > Can we simply add them into ioctl of mdev_parent_ops? > > Right, either way, these ioctls have to be and just need to be > > added in the ioctl of the mdev_parent_ops. But another thing we > > also need to consider is that which file descriptor the userspace > > will do the ioctl() on. So I'm wondering do you mean let the > > userspace do the ioctl() on the V...

...vhost's ioctl on VFIO device fd directly, > > > > or introducing another mdev driver (i.e. vhost_mdev instead of > > > > using the existing vfio_mdev) for mdev device? > > > Can we simply add them into ioctl of mdev_parent_ops? > > Right, either way, these ioctls have to be and just need to be > > added in the ioctl of the mdev_parent_ops. But another thing we > > also need to consider is that which file descriptor the userspace > > will do the ioctl() on. So I'm wondering do you mean let the > > userspace do the ioctl() on the V...

I recently purchased a Tripp Lite OmniSV1500XL and I've had no luck getting nut to work. # lsusb Bus 001 Device 001: ID 0000:0000 Bus 006 Device 002: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter Bus 006 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 004 Device 009: ID 09ae:0001 Tripp Lite Bus 004 Device

Hi Ben, Karol and Tom are seeing this on init with a nvif-enabled kernel + libdrm. What are we doing wrong? I think that route == NVIF_IOCTL_V0_ROUTE_NVIF (== 0), while owner is apparently 1, whatever that is. [362619.242238] nouveau: glxgears[6096]:00000000:00000000: ioctl: size 32 [362619.242240] nouveau: glxgears[6096]:00000000:00000000: ioctl: vers 0 type 00 object 0000000000000000 owner 00

...> or introducing another mdev driver (i.e. vhost_mdev instead of > > > > > > > > using the existing vfio_mdev) for mdev device? > > > > > > > Can we simply add them into ioctl of mdev_parent_ops? > > > > > > Right, either way, these ioctls have to be and just need to be > > > > > > added in the ioctl of the mdev_parent_ops. But another thing we > > > > > > also need to consider is that which file descriptor the userspace > > > > > > will do the ioctl() on. So I'm wondering do...

...> or introducing another mdev driver (i.e. vhost_mdev instead of > > > > > > > > using the existing vfio_mdev) for mdev device? > > > > > > > Can we simply add them into ioctl of mdev_parent_ops? > > > > > > Right, either way, these ioctls have to be and just need to be > > > > > > added in the ioctl of the mdev_parent_ops. But another thing we > > > > > > also need to consider is that which file descriptor the userspace > > > > > > will do the ioctl() on. So I'm wondering do...

Hi Seeing as we (Raspberry Pi) have just launched the Compute Module 4 with an exposed PCIe x1 lane, people are asking about adding graphics cards. Seeing as you are the people who have the knowledge with regard to NVidia and nouveau, what are your immediate thoughts of nouveau working on ARM/ARM64? Is there a chance of this working? I'm no PCIe expert, although I can call on some expertise