search for: initalize

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:584: warning: Function parameter or member 'init' not described in 'init_reserved' drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:611: warning: expecting prototype for INIT_DONE(). Prototype was for init_done() instead [Snipped ~140 lines for brevity] Cc: Ben Skeggs <bskeggs at

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:584: warning: Function parameter or member 'init' not described in 'init_reserved' drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c:611: warning: expecting prototype for INIT_DONE(). Prototype was for init_done() instead [Snipped ~140 lines for brevity] Signed-off-by: Lee Jones

I have a high volume asterisk 1.40 installation and I ran a SIP SHOW CHANNELS. (see partial output below). My questions are: 1. "wc-l" of the output shows 4000 lines. Does this mean 2000 active calls? (2 channels per call) 2. The latter part of the output shows "unkn" for Form column. Why does it not know the codec? Could it be UDPTL? Or are these calls messed up? 3.

Is there a reason that Reduce() doesn't take a "..." argument that would allow arbitrary extra arguments to be passed through to the function? Here is a little example of how this would be convenient: z <- list( data.frame(state=c("California"), cases=0), data.frame(state=c("California","Massachusetts"),

Hi, for quite some time now I would like to switch from the proprietary driver to nouveau, using a GK107 (Quadro) in a thinkpad. Unfortunately the monitors connected to the lenovo "ultra dock" are not properly recognized when using nouveau. The laptop contains a multiplexer: so in the bios it can be selected, whether the docking station's DP/HDMI/VGA-Ports are "directly"

Hello, I've just been hit by this old bug which is still present in 4.14: https://bugs.freedesktop.org/show_bug.cgi?id=80675 On MCP79 (ION), when stolen memory is set to 32MB in BIOS, console is blank but X11 works. When the stolen memory is increased to 64MB, console works fine. Bisected it to this: 4f6029da58ba9204c98e33f4f3737fe085c87a6f is the first bad commit commit

Hi Jasmin, On Sun, Mar 1, 2020 at 11:32 AM Jasmin <jasmin.pm at protonmail.com> wrote: > > Hi, > > for quite some time now I would like to switch from the proprietary driver to nouveau, using a GK107 (Quadro) in a thinkpad. > Unfortunately the monitors connected to the lenovo "ultra dock" are not properly recognized when using nouveau. DP-MST support was first

Building on the work in ff0a614bd724f6c4c6a5014a9955dc1bc028f336, this moves the capability code down into the run-init library, so that run-init can use it as well, via the new "-d" flag. Signed-off-by: Kees Cook <kees at outflux.net> --- usr/kinit/Kbuild | 3 +-- usr/kinit/capabilities.h | 10 ++++++++++ usr/kinit/kinit.c | 6 +++---

Hi, I''m trying to run Xen 3.0 with a file-backed VBD on a opteron system. Here''s my Xen config file (xenconf): # -*- mode: python; -*- kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" memory = 1024 name = "Dom2" vif = [ '''' ] disk = [ ''file:/xendisk/vm3disk,sda1,w'' ] root = "/dev/sda1

On Friday 17 November 2017 15:43:33 Ilia Mirkin wrote: > With a new kernel, mind grabbing a dmesg with drm.debug=0x1e > nouveau.debug=debug (or maybe even =trace)? Maybe also see if > fbcon/fbdev have any debug things that can be turned on? Here's diff of the 32MB and 64MB debug logs: --- nouveau-debug-32mb.txt- 2017-11-17 18:12:06.290108330 +0100 +++ nouveau-debug-64mb.txt-

I just updated my Redhat EL systems to R-2.7.2, and tried to update my packages as well. Lattice is one that failed. What do I need to do? R version 2.7.2 (2008-08-25) > install.packages("lattice", repos = "http://cran.fhcrc.org/") Warning in install.packages("lattice", repos = "http://cran.fhcrc.org/") : argument 'lib' is missing: using

Hi Folks, I create a file backed vbd to boot a guest VM as described in the Xen''s user manual in section ''Using File-backed VBDs". The Dom0 and the VBD contain Suse Linux Enterprise Server 10 (X86_64). I am not able to boot the guest VM. During the boot process the INIT process generates an error saying <snip> Loading jbd Loading ext3 Waiting for device /dev/sda1 to

initramfs-tools wants to validate the real init program before running it, as there is no way out once it has exec'd run-init. This is complicated by the increasing use of symlinks for /sbin/init and for /sbin itself. We can't simply resolve them with 'readlink -f' because any absolute symlinks will be resolved using the wrong root. Add a dry-run mode (-n option) to run-init

Commit-ID: 10059fddba9f8bec6aeb0d37d217df6d65e64c3b Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=10059fddba9f8bec6aeb0d37d217df6d65e64c3b Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 17 Jan 2016 19:50:28 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] run-init: Add dry-run mode

systemd supports switching back to the initramfs during shutdown in order to make it easier to clean up the root file system. This is desirable in order to allow us to remove keys from RAM before rebooting, making it harder to obtain confidential information by rebooting into an environment that scrapes RAM contents. --- debian/changelog | 4 +

This set is part of a larger effort attempting to clean-up W=1 kernel builds, which are currently overwhelmingly riddled with niggly little warnings. Lee Jones (15): drm/xlnx/zynqmp_disp: Use correct kerneldoc formatting in zynqmp_disp drm/xlnx/zynqmp_dp: Fix function name zynqmp_dp_link_train() -> zynqmp_dp_train() drm/vkms/vkms_composer: Fix a few different kerneldoc formatting

test/trace/Makefile.am | 11 +++++ test/trace/text-field-init-native-5.swf |binary test/trace/text-field-init-native-5.swf.trace | 2 + test/trace/text-field-init-native-6.swf |binary test/trace/text-field-init-native-6.swf.trace | 2 + test/trace/text-field-init-native-7.swf |binary test/trace/text-field-init-native-7.swf.trace | 2 +

Hi, Trying a new kernel on old [NV04] system I get tons of nouveau 0000:01:00.0: gr: intr 00000001 [NOTIFY] nsource 00000040 [ILLEGAL_MTHD] nstatus 00004000 [PROTECTION_FAULT] ch 0 [DRM] subc 3 class 004a mthd 02fc data 00000003 errors when operating on console. As I updated from 4.3 kernel, a bisect does not feel like the best start. What is that 02fc method which fbcon is probably

This set is part of a larger effort attempting to clean-up W=1 kernel builds, which are currently overwhelmingly riddled with niggly little warnings. Cc: Alex Deucher <alexander.deucher at amd.com> Cc: amd-gfx at lists.freedesktop.org Cc: Ben Skeggs <bskeggs at redhat.com> Cc: "Christian K?nig" <christian.koenig at amd.com> Cc: Daniel Vetter <daniel at ffwll.ch>

Commit-ID: 603f1bb024a03d9c50a89e7256ae7814292baf06 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=603f1bb024a03d9c50a89e7256ae7814292baf06 Author: Matthew Garrett <matthewgarrett at google.com> AuthorDate: Thu, 18 Apr 2019 12:12:27 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 20 Apr 2019 17:11:34 +0100 [klibc] run-init: Allow