similar to: [Bug 23730] New: x11-base/nouveau-drm fails on drm_fb_helper.c with 'EINVAL' undeclared

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=497 ------- Additional Comments From netfilter@linuxace.com 2006-08-04 04:37 MET ------- Created an attachment (id=259) --> (https://bugzilla.netfilter.org/bugzilla/attachment.cgi?id=259&action=view) proposed patch -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving

https://bugs.freedesktop.org/show_bug.cgi?id=105319 Bug ID: 105319 Summary: DRM: EVO timeout with kernel 4.15.x Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau

Hi All, I'm experiencing a problem with some mails in deliver. Here the logged error message: deliver(stefan at roese.nl): 2009-05-06 11:57:36 Panic: file index-mail-headers.c: line 141 (index_mail_parse_header_finish): assertion failed: ((match[match_idx] & HEADER_MATCH_FLAG_FOUND) == 0) deliver(stefan at roese.nl): 2009-05-06 11:57:36 Error: Raw backtrace: /usr/lib/dovecot/deliver

Hi all, I've a simple program called empty.c :) $ cat empty.c int main(int argc, char* argv[]) { return 0; } $ cat empty410.s .file "empty.c" .text .p2align 4,,15 .globl main .type main, @function main: xorl %eax, %eax ret .size main, .-main .ident "GCC: (GNU) 4.1.0 20050922 (experimental)"

Package: blktap-utils Version: 2.0.90-2 Severity: important Tapdisk fails to start and exit's silently after failing to detect current kernel version. This happens only on newer kernel versions missing sublevel field. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP

On Thu, Dec 13, 2018 at 05:53:50PM +0300, Pavel Tikhomirov wrote: > We've failed to copy and process vhost_iotlb_msg so let userspace at > least know about it. For instance before these patch the code below runs > without any error: > > int main() > { > struct vhost_msg msg; > struct iovec iov; > int fd; > > fd = open("/dev/vhost-net",

From: Pavel Tikhomirov <ptikhomirov at virtuozzo.com> Date: Thu, 13 Dec 2018 17:53:50 +0300 > We've failed to copy and process vhost_iotlb_msg so let userspace at > least know about it. For instance before these patch the code below runs > without any error: ... > Signed-off-by: Pavel Tikhomirov <ptikhomirov at virtuozzo.com> Michael, will you be taking this in via

When guestfs_lvm_canonical_lv_name was called with a /dev/dm* or /dev/mapper* name which was not an LV then a noisy error would be printed. This would typically have happened with encrypted disks, and now happens very noticably when inspecting Windows BitLocker- encrypted guests. Using the modified error behaviour of this API from the previous commit we can now hide that error in that specific

This is the patch I tested which works (on top of the patch posted): diff --git a/lib/canonical-name.c b/lib/canonical-name.c index e0c7918b4..ae4def692 100644 --- a/lib/canonical-name.c +++ b/lib/canonical-name.c @@ -53,8 +53,16 @@ guestfs_impl_canonical_device_name (guestfs_h *g, const char *device) * BitLocker-encrypted volume, so simply return the original * name in that case.

On Fri, Oct 09, 2020 at 11:37:41AM +0100, Richard W.M. Jones wrote: > On Fri, Oct 09, 2020 at 11:33:43AM +0100, Richard W.M. Jones wrote: > > > > This is the patch I tested which works (on top of the > > patch posted): > > > > diff --git a/lib/canonical-name.c b/lib/canonical-name.c > > index e0c7918b4..ae4def692 100644 > > --- a/lib/canonical-name.c

Hi, When I run my app on IE, it crashes everytime. However, when running on Firefox, it is perfectly fine. I saw the following error on the my server. [2005-11-15 10:45:20] ERROR Errno::EINVAL: Invalid argument c:/ruby/lib/ruby/1.8/webrick/httprequest.rb:325:in `gets'' c:/ruby/lib/ruby/1.8/webrick/httprequest.rb:325:in `__send__''

Hi All, I'm about to clean and re-initialize a Maxtor 160GB disk that shows a weird problem but I think I've found a bug in RELENG_4_7 somewhere so if preserving my disk can help conquer one more bug I'm happy to wait a couple of days and help solve that bug. Here's the story: While upgrading from 4.3-STABLE to 4.7p4 and at the same time reorganizing my vinum volumes I copied

fixes bogus values userspace gets from hwmon while the GPU is powered down Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nouveau_hwmon.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drm/nouveau/nouveau_hwmon.c b/drm/nouveau/nouveau_hwmon.c index 618d8b780..d445c6f3f 100644 --- a/drm/nouveau/nouveau_hwmon.c +++ b/drm/nouveau/nouveau_hwmon.c @@ -426,6

Does samba 3.0.23c not support the use of O_DIRECT? When I try to open an smbmount'd file using O_DIRECT, I get EINVAL. I am able to use O_DIRECT with no problems on a block device and nfs mounts, so I know the kernel supports it. samba: 3.0.23c kernel: 2.6.9-42.0.3.EL (32-bit) I am using the below code for my test. smb fails on open(2). #include <fcntl.h> #include

When DP MST hubs get confused, they can occasionally stop responding for a good bit of time up until the point where the DRM driver manages to do the right DPCD accesses to get it to start responding again. In a worst case scenario however, this process can take upwards of 10+ seconds. Currently we use the default output_poll_changed handler drm_fb_helper_output_poll_changed() to handle output

On Fri, Oct 09, 2020 at 11:33:43AM +0100, Richard W.M. Jones wrote: > > This is the patch I tested which works (on top of the > patch posted): > > diff --git a/lib/canonical-name.c b/lib/canonical-name.c > index e0c7918b4..ae4def692 100644 > --- a/lib/canonical-name.c > +++ b/lib/canonical-name.c > @@ -53,8 +53,16 @@ guestfs_impl_canonical_device_name (guestfs_h *g,

On Thu, Sep 17, 2020 at 01:40:04PM +0100, Richard W.M. Jones wrote: >When guestfs_lvm_canonical_lv_name was called with a /dev/dm* or >/dev/mapper* name which was not an LV then a noisy error would be >printed. This would typically have happened with encrypted disks, and >now happens very noticably when inspecting Windows BitLocker- >encrypted guests. > >Using the modified

On Thu, 2018-07-19 at 09:49 +0200, Lukas Wunner wrote: > On Wed, Jul 18, 2018 at 04:56:39PM -0400, Lyude Paul wrote: > > When DP MST hubs get confused, they can occasionally stop responding for > > a good bit of time up until the point where the DRM driver manages to > > do the right DPCD accesses to get it to start responding again. In a > > worst case scenario however,

http://bugs.freedesktop.org/show_bug.cgi?id=20547 Summary: nouveau drm doesn't build Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: dliana at

On Wed, Jul 18, 2018 at 04:56:39PM -0400, Lyude Paul wrote: > When DP MST hubs get confused, they can occasionally stop responding for > a good bit of time up until the point where the DRM driver manages to > do the right DPCD accesses to get it to start responding again. In a > worst case scenario however, this process can take upwards of 10+ > seconds. > > Currently we use