search for: sbio

This series adds an initial implementation for scrub. It works quite straightforward. The usermode issues an ioctl for each device in the fs. For each device, it enumerates the allocated device chunks. For each chunk, the contained extents are enumerated and the data checksums fetched. The extents are read sequentially and the checksums verified. If an error occurs (checksum or EIO), a good copy

While testing raid-auto-repair patches I''m going to send out later, I just found the very last bug in my current scrub patch series: Changelog v4->v5: - fixed a deadlock when fixup is taking longer while scrub is about to end Original message follows: ------------------------ This patch set introduces two new features for scrub. They share the backref iteration code which is the

The goal is to detect when drives start to get an increased error rate, when drives should be replaced soon. Therefore statistic counters are added that count IO errors (read, write and flush). Additionally, the software detected errors like checksum errors and corrupted blocks are counted. An ioctl interface is added to get the device statistic counters. A second ioctl is added to atomically get

...mes, but what is the difference > with the nvac (Ion)? > > Would the nvac have some reserved memory for its usage by the bios which > would then be used as "VRAM"? PFB on the dGPU IGPs has facilities to fake VRAM from an area of "stolen" system memory reserved by the SBIOS. GK20A/GM20B do not do this, and require direct (or, via a mmu, whatever) access to system memory. Ben. > > In any case, the patchseries sounds simple-enough to be maintainable. > > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freed...

...raight TLS, SMTP over TLS, or a handful other protocols over TLS. The demonstration here focuses on SMTP over TLS only.) The demonstration with SMTP over TLS involves a one-line change in the OpenSSL s_client source code (with OpenSSL 1.0.0, at line 1129 of file apps/s_client.c). Old: BIO_printf(sbio,"STARTTLS\r\n"); New: BIO_printf(sbio,"STARTTLS\r\nRSET\r\n"); With this change, the s_client command sends the plaintext STARTTLS command ("let's turn on TLS") immediately followed by an RSET command (a relatively harmless protocol "reset"). Both comma...

...ying to find out what else I can do to confirm that, and rule out pxelinux/. I'd like to get a confirmation that the use of pxelinux isn't a factor, as I'm not using 'keeppxe'. I'm rolling out a couple hundred workstations, and using a pxelinux menu-driven update of the SBIOS and to do the OS install (SuSE 9.3). Hardware is HP xw9300 workstations,dual opteron, NVidia chipset and NIC. The entire pxelinux-involved process works properly 100% of the time, DHCP, kernel loading, memdisk... etc. The systems are showing one very improper behaviour: Some significant p...

It's my megabyte, I want to use it! At this point in init vbios is copied over already, so there's no reason it cannot used to hold other data now. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c b/drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c index cf97c4d..507d35d 100644 ---

http://bugs.freedesktop.org/show_bug.cgi?id=25777 Summary: Blank Screen on Gt230M Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

Hi The setup, as in the subject, is supposed to boot a Winpe to install xp to a clean PC. I use the Ramdisk method (ie PXELinux pases the setup on to the M$ pxe loader and and boots WinPE) It works perfectly with evry other chipset, but Nvidias NForce 4. (tested 15 different) With NF4 it loads up well but the M$ PnP routine detects the Network management bus wrong (nvidia specific approach to

New revision of this patchset that prevents VRAM objects from being allocated on VRAM-less systems like Tegra. This is required for Mesa to work on such systems. Changes since v2: - Use vram_size to detect systems without VRAM and set the correct domain instead of expecting each chip to set its domain explicitly. Alexandre Courbot (2): nouveau: support for custom VRAM domains nvc0: use