similar to: CentOS-announce Digest, Vol 137, Issue 3

CentOS Errata and Enhancement Advisory 2016:1390 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1390.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 89b552cce1a54801c5d8f77a296885a6f2be44bc2e2b8b2e0421902d4d47d9f3 kmod-rtsx_usb_sdmmc-0.1_rh1-1.el7_2.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2016:1390 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1390.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3ca04e56e7e50aaaca87c41de77cafd8ce7cf263a5c5ac90b748b40697d508ff kmod-rtsx_usb-0.1_rh1-1.el7_2.x86_64.rpm Source:

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Enhancement Advisory 2015:1227 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-1227.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 346f40963d7aba73efb26e0dd547e1e667a733ee4d6b16274ff62e949c49deac kmod-rtsx_usb_sdmmc-0.1_rh1-1.el6_6.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2015:1227 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-1227.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0ce989f6bf54c41855e92e75988072bd398df25cddf24992fe9fa512a86f87e0 kmod-rtsx_usb-0.1_rh1-1.el6_6.i686.rpm x86_64:

On 21.03.19 18:12, Jerome Glisse wrote: > On Thu, Mar 21, 2019 at 04:59:14PM +0100, Tobias Klausmann wrote: >> Hi, >> >> just for your information and maybe for some help: with 5.1rc1 and SVM >> enabled i see the following backtrace [1] when the nouveau card (reverse >> prime) goes to sleep, for now i have papered over with [2] which leaves me >> with

mimic the behavior of vblank_disable_fn(), another caller of drm_vblank_disable_and_save(). This avoids oopsing, while trying to disable vblank on a not connected display: [ 12.768079] WARNING: CPU: 0 PID: 274 at drivers/gpu/drm/drm_vblank.c:609 drm_calc_vbltimestamp_from_scanoutpos+0x296/0x320 [drm] [ 12.768080] Modules linked in: bnep snd_hda_codec_hdmi rtsx_usb_sdmmc uvcvideo rtsx_usb_ms

On Wed, Jul 19, 2017 at 04:10:50PM -0400, Ilia Mirkin wrote: > I believe the solution is to not call drm_crtc_vblank_off for atomic > modesetting in nouveau_display_fini. I think Ben's working on it. Yes, the goal of vblank_on/off was very much to not paper over driver bugs with clever tricks like these. If the driver cant keep track of its vblank, something has gone wrong, and the core

I believe the solution is to not call drm_crtc_vblank_off for atomic modesetting in nouveau_display_fini. I think Ben's working on it. On Wed, Jul 19, 2017 at 1:25 PM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > mimic the behavior of vblank_disable_fn(), another caller of > drm_vblank_disable_and_save(). > > This avoids oopsing, while trying to

On Thu, Jul 20, 2017 at 11:58 PM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > Mh ok, > > paper over in nouveau_display_fini until Ben comes up with a better idea > then?! No paper needed, just don't call drm_vblank_off for the atomic case. Not sure why that patch isn't landed yet, it should be simple. -Daniel > > Greetings, > > Tobias

Mh ok, paper over in nouveau_display_fini until Ben comes up with a better idea then?! Greetings, Tobias On 7/20/17 10:13 AM, Daniel Vetter wrote: > On Wed, Jul 19, 2017 at 04:10:50PM -0400, Ilia Mirkin wrote: >> I believe the solution is to not call drm_crtc_vblank_off for atomic >> modesetting in nouveau_display_fini. I think Ben's working on it. > Yes, the goal of

On Tue, Jul 12, 2016 at 06:49:34PM +0200, Peter Wu wrote: > The FBIOPUT_CON2FBMAP ioctl takes a console_lock(). When this is called > while nouveau was runtime suspended, a deadlock would occur due to > nouveau_fbcon_set_suspend also trying to obtain console_lock(). > > Fix this by delaying the drm_fb_helper_set_suspend call. Based on the > i915 code (which was done for

Hi, just for your information and maybe for some help: with 5.1rc1 and SVM enabled i see the following backtrace [1] when the nouveau card (reverse prime) goes to sleep, for now i have papered over with [2] which leaves me with userspace hangs. Any pointers where to look for the actual culprit? PS: Card is: nouveau 0000:01:00.0: NVIDIA GP106 (136000a1) Greetings, Tobias [1]: BUG: unable

https://bugs.freedesktop.org/show_bug.cgi?id=83443 Priority: medium Bug ID: 83443 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau cras QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter: openoliv at mailoo.org Hardware: x86-64

On Wed, Jul 13, 2016 at 06:17:47PM +0100, Chris Wilson wrote: > On Tue, Jul 12, 2016 at 06:49:34PM +0200, Peter Wu wrote: > > The FBIOPUT_CON2FBMAP ioctl takes a console_lock(). When this is called > > while nouveau was runtime suspended, a deadlock would occur due to > > nouveau_fbcon_set_suspend also trying to obtain console_lock(). > > > > Fix this by delaying

On Sat, 2017-07-15 at 14:52 -0400, Ilia Mirkin wrote: > > OK, so this issue appears to be that we're calling > drm_crtc_vblank_off() on a crtc for which vblank is already disabled. > My guess is that this happens because the crtc is disabled. > > Not sure what the proper check is to see if vblanks are already disabled... Seems so, the below shut up suspend for both 8600 GT

https://bugs.freedesktop.org/show_bug.cgi?id=93267 Bug ID: 93267 Summary: BUG: unable to handle kernel paging request in reservation_object_wait_timeout_rcu Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority:

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Enhancement Advisory 2014:1111 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-1111.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1c67b2e255a183d54b3eb43f39a9e5f2263aa4d4ce1a7cfac61f45d323de74a4 kmod-memstick_dup-0.1_rh1-1.el6_5.i686.rpm

On Sat, Oct 15, 2022 at 12:21:41PM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: a1b6b102df03 Merge branch 'phylink_set_mac_pm' > git tree: net > console output: https://syzkaller.appspot.com/x/log.txt?x=179af0c2880000 > kernel config: https://syzkaller.appspot.com/x/.config?x=85495c44a2c25446 > dashboard