Brice Goglin a écrit :
Thanks a lot for this investigation. Would you mind reporting the
problem and fix upstream at https://bugs.freedesktop.org/index.cgi ?
The bug is reported upstream. The URL is
https://bugs.freedesktop.org/show_bug.cgi?id=10276
Fred
forwarded 413640 https://bugs.freedesktop.org/show_bug.cgi?id=10276
thank you
Frédéric Giquel wrote:
Brice Goglin a écrit :
Thanks a lot for this investigation. Would you mind reporting the
problem and fix upstream at https://bugs.freedesktop.org/index.cgi ?
The bug is reported
tags 413640 +upstream
thank you
Frédéric Giquel wrote:
I've found the reason of the crash. It's not related to nv or nvidia
driver but the AMD64 architecture.
The explanation :
- line 648 of v4l.c : ioctl(V4L_FD,VIDIOCGFREQ,value);
- line 612 of v4l.c : we know that value is INT32 *
- in
I've found the reason of the crash. It's not related to nv or nvidia
driver but the AMD64 architecture.
The explanation :
- line 648 of v4l.c : ioctl(V4L_FD,VIDIOCGFREQ,value);
- line 612 of v4l.c : we know that value is INT32 *
- in videodev.h of kernel headers (from debian package
Package: xserver-xorg-video-v4l
Version: 0.1.1-3
Severity: important
Using xvinfo makes xorg crashes when v4l module is loaded. It's reproducible.
Informations found in /var/log/Xorg.0.log.old after the crash :
(II) NV(0): v4l: memPhysBase=0xd000
Backtrace:
0:
Frédéric Giquel wrote:
Package: xserver-xorg-video-v4l
Version: 0.1.1-3
Severity: important
Using xvinfo makes xorg crashes when v4l module is loaded. It's reproducible.
Informations found in /var/log/Xorg.0.log.old after the crash :
(II) NV(0): v4l: memPhysBase=0xd000
Backtrace:
0:
6 matches
Mail list logo