similar to: Linux F00F Patch [Forwarded e-mail from Aleph One]

these are both fixed in 2.0.32-pre4 and 2.1.63. The 2.0.32-pre4 stuff seems very solid, though the f00f bug fix is not proper for SMP machines yet. It looks like 2.0.32-pre5 fixes the f00f bug on SMP machines properly. All of these are available on ftp.kernel.org: ftp://ftp.kernel.org/pub/linux/kernel/testing/pre-patch-2.0.32-5.gz ftp://ftp.kernel.org/pub/linux/kernel/v2.1/linux-2.1.63.tgz

A follow up on https://lists.centos.org/pipermail/centos/2020-July/351009.html In addition to page size problems I just found out that page-ranges option is ignored. To reproduce I created a two page PDF file and printed it like lp -d printer_name -o page-ranges=1 twopage.pdf Two local printers, HP and Canon output two pages. Printers were configured using CUPS UI by selecting the appropriate

Hi, I've been trying to get the G.729a beta codec running with my remote Asterisk box that talks IAX2 to my local Asterisk box. Digium fixed the problem I was having in registering the beta codec, so that now works fine. I've removed the old codec_g729b.so from /usr/lib/asterisk/modules and put in place the codec_g729a.so beta from digium FTP. My CVS build of Asterisk is about a

With FreeBSD 4.8-20030731-STABLE #0, dmesg messages indicate: module_register: module miibus/ukphy already exists! linker_file_sysinit "miibus.ko" failed to register! 17 module_register: module pccard/ed already exists! linker_file_sysinit "if_ed.ko" failed to register! 17 This doesn't look dangerous but the rl0 ethernet card just stopped recieving packets suddenly and

Hi all.. I have found some problems on smbfs module in 2.4.18 kernel. I compiled it by myself (not the very first kernel compilation in my life ;-)) and then I have got it. Looks like it touch smbfs module as when I recompile 2.4.18 modules with smbfs sources changed to sources of smbfs from 2.4.17 problem disappears!! My mainboard is Abit BE6 with Pentium III 450 MHz. I am using SuSE 7.3 with

Hi All, I just had "an issue" with my Linux 2.6.1 kernel. While working, I tried to rf -rf a directory, and was told my filesystem was mounted readonly (which it wasn't). I then shut the machine down, and on shutdown, I got a "kernel BUG at fs/ext3/super.c: 411". Full report below: Mike [1.] One line summary of the problem: Filesystem became readonly, then

Okay, I've run through all of the tests in the DIAGNOSE, which my 1.9.18p1 SAMBA server (and NT4SP3/W95 clients) pass with flying colours. server box: Linux 2.0.33, gcc 2.7.2.2, libc 5.4.33, shadow, quota on (usr+grp), and my smb.conf is summarised (by testparm output) below: Problem is this: with respect to programs not long filename-aware/compliant, users cannot "double-click" on

I've finally been able to capture the panic, as now it occurs even with DDB configured. Of the six machines I have running 6.1-RC (CVSupped today), this is the only one that does this. /boot/kernel/kernel text=0x30c488 data=0x3b6a0+0x3170c syms=[0x4+0x46430+0x4+0x58da4] no such file or directory - Hit [Enter] to boot immediately, or any other key for command prompt. Booting

Hello, I''ve come across a strange problem when installing a particular software package in a domU. I''m trying to install DigiChat (http://www.digichat.com/downloads.html) and the process is immediately killed. I have installed the package with no problems in a VMware VM, UML and native. ...Even installed into a UML, then copied the entire filesystem over and created a domU

currently i'm trying to setup diskless client, which netboots 6.1-PRERELEASE kernel with help of etherboot. i've built custom kernel with `sudo make -j4 buildkernel KERNCONF=DISKLESS CPUTYPE=pentium-mmx -DNO_MODULES' and attached config. kernell loads off tftp server fine, detecting devices, but traps, when trying to mount root fs from nfs server. i've managed to get copy of

Use NOKPROBE_SYMBOL macro to protect functions from kprobes instead of __kprobes annotation in trap.c. This also applies __always_inline annotation for some cases, because NOKPROBE_SYMBOL() will inhibit inlining by referring the symbol address. Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> Cc: Thomas Gleixner <tglx at linutronix.de> Cc: Ingo Molnar <mingo at

Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic similar to smp_call_function_single()" has unified the way to handle single and multiple cross-CPU function calls. Now only one interrupt is needed for architecture specific code to support generic SMP function call interfaces, so kill the redundant single function call interrupt. Cc: Andrew Morton <akpm at

Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic similar to smp_call_function_single()" has unified the way to handle single and multiple cross-CPU function calls. Now only one interrupt is needed for architecture specific code to support generic SMP function call interfaces, so kill the redundant single function call interrupt. Cc: Andrew Morton <akpm at

Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic similar to smp_call_function_single()" has unified the way to handle single and multiple cross-CPU function calls. Now only one interrupt is needed for architecture specific code to support generic SMP function call interfaces, so kill the redundant single function call interrupt. Cc: Andrew Morton <akpm at

[ Asked on -questions on Friday; re-asking now on -stable without cross-post] I recently upgraded a 4.11-REL machine to 6.0-REL and have run into some snags. While the installation from CD went fine, after configuring and enabling my ed0 NIC, bad things start to happen. FWIW, this machine is an ancient (hardware circa 1991, BIOS circa 1994) dual-Pentium 133 MHz machine, with EISA/PCI and

Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic similar to smp_call_function_single()" has unified the way to handle single and multiple cross-CPU function calls. Now only one intterupt is needed for architecture specific code to support generic SMP function call interfaces, so kill the redundant single function call interrupt. Cc: Andrew Morton <akpm at

Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic similar to smp_call_function_single()" has unified the way to handle single and multiple cross-CPU function calls. Now only one intterupt is needed for architecture specific code to support generic SMP function call interfaces, so kill the redundant single function call interrupt. Cc: Andrew Morton <akpm at

Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic similar to smp_call_function_single()" has unified the way to handle single and multiple cross-CPU function calls. Now only one intterupt is needed for architecture specific code to support generic SMP function call interfaces, so kill the redundant single function call interrupt. Cc: Andrew Morton <akpm at

The 32-bit and 64-bit versions of copy_thread have functionally identical handling for copying the I/O bitmap, modulo differences in error handling. Clean up the error paths in both by moving the copy of the I/O bitmap to the end, to eliminate the need to free it if subsequent copy steps fail; move the resulting identical code to a static inline in a common header. Signed-off-by: Josh Triplett

From: Joerg Roedel <jroedel at suse.de> The #VC handler needs special entry code because: 1. It runs on an IST stack 2. It needs to be able to handle nested #VC exceptions To make this work the entry code is implemented to pretend it doesn't use an IST stack. When entered from user-mode or early SYSCALL entry path it switches to the task stack, if entered from kernel-mode it tries