This patch (against 2.4.0-ac8) _may_ enable the NMI watchdog on
some K7 systems. It won't help if you have an old K7 without a
local APIC, or if your BIOS disables it.
This is a quick hack to test the mechanism -- I'll submit a
cleaner patch later if this one works.
If you try this, please cc:
On Mon, 15 Jan 2001 04:00:29 +0100, Petr Vandrovec wrote:
(1) You missed some zeros in MSR_K7_ definitions
Oops :-(
(2) AMD's MSR are real 64bit (well, 47bit) values, so high
MSR dword must be set to -1, not to 0
Correct. That was a copy-paste error from the P6 code.
When writing to a
On Mon, 22 Jan 2001 23:23:36 -0600 (CST), Thomas Molina wrote:
[1.] One line summary of the problem: seek= parameter for dd under 2.4.0
gives permission denied error
[2.] Full description of the problem/report:I was creating a new
root+boot disk for 2.4.0 this evening. I issued the command:
dd
to restart the counters.
The next version will support buffering and automatic restart.
/ Mikael Pettersson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Before people get too exited about the x86 Page Attribute Table ...
Does Linux use mode B (CR4.PSE=1) or mode C (CR4.PAE=1) paging?
If so, known P6 errata must be taken into account.
In particular, Pentium III errata E27 and Pentium II errata A56
imply that only the low four PAT entries are
Jeff Hartmann wrote:
Before people get too exited about the x86 Page Attribute Table ...
Does Linux use mode B (CR4.PSE=1) or mode C (CR4.PAE=1) paging?
If so, known P6 errata must be taken into account.
In particular, Pentium III errata E27 and Pentium II errata A56
imply that only the
On Sun, 28 Jan 2001 12:27:46 -0600 (CST), Thomas Molina wrote:
I seem to recall a discussion on faster processors causing timing
problems during a kernel make, but I'm unable to find it in the kernel
archives. I've now upgraded to an Athlon 900 MHz processor and an ASUS
A7V motherboard and have
On Tue, 30 Jan 2001 23:25:22 -0500, Adam Schrotenboer wrote:
2.4.1 detects 64 MB, but 2.4.0 detects 192 (Maybe 191, not sure).
...
Linux version 2.4.1 (root@tabriel) (gcc version egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release)) #9 Tue Jan 30 15:35:21 EST 2001
BIOS-provided physical RAM map:
Simon Richter writes:
I just switched my brother's computer to a 2.2 kernel, and now the CPU
overheats under Linux after about half an hour (reproducible). It works
fine under Windows 95b and worked under Linux 2.0.38.
CPU is a Pentium 166 MMX on an Asus TX97 mainboard, ISA cards are a
On 21 May 2001 14:49:55 -0400, Camm Maguire [EMAIL PROTECTED] wrote:
Greetings! 2.2.19+ide, applied the patch because this box has a new
Promise PDC20267 ide controller. 14GB HP Colorado tape drive. Before
we installed the new ide controller and patched the kernel, i.e. with
unpatched 2.2.19
On Tue, 29 May 2001 18:22:57 -0500 (CDT), Paul Walmsley wrote:
I have an 700Mhz Pentium III HP Omnibook 6000 that has been locking up
...
In the hopes of getting an oops from the NMI watchdog, I attempted to
enable the NMI watchdog with both 'nmi_watchdog=1' and 'nmi_watchdog=2'.
Neither seems
On Sun, 3 Jun 2001 00:23:10 +0100, Alan Cox wrote:
2.4.5-ac6
...
o Resync with Eric's master Configure.help(Eric Raymond)
ac5-ac6 accidentally(?) dropped the help text for CONFIG_X86_UP_APIC.
Patch below (vs -ac7) adds it back. Please apply.
/Mikael
---
Summary: ide-tape in 2.4.0-test8 seems to be unable to read the
last block of data in a stream, if the written data wasn't an
exact multiple of the tape unit's block size. 2.2.17 doesn't have
this problem.
Boot kernel 2.4.0-test8.
[root /tmp]# insmod ide-tape
[root /tmp]# dmesg | tail -2
2.4.0-test9-pre6 breaks building NFS as a module. pre6 changed lockd
to use two new functions locks_init_lock() and locks_copy_lock().
However, these functions aren't exported, resulting in:
/lib/modules/2.4.0-test9-pre6/kernel/fs/lockd/lockd.o: unresolved symbol
locks_init_lock
n (through-local).
+ * Assumes that init_apic_mappings() has mapped the local APIC.
+ * TODO: check how to do this for K7 and P4.
+ * Original code written by Mikael Pettersson.
+ */
+void __init init_local_APIC(void)
+{
+ unsigned int msr_orig_low, msr_orig_high;
+ unsigned int spiv_orig;
+
On Wed, 4 Oct 2000, Jeff Nguyen wrote:
Hi Alan.
I hope you will consider to integrate Andre IDE patche into the 2.2.18 or
2.2.19 kernel.
Be advised that the big IDE patch for 2.2 (at least as of a month ago)
contains a backport of the 2.4 ide-tape driver. That driver is BROKEN --
if the last
welcome. If any change didnt make it into this patch then
please resubmit, there were major changes.
...
- reworked the APIC-enabling code and boot order along the suggestion of
Mikael Pettersson, APICs should now be enabled early enough on all
systems. This should also fix the boot problems
On Wed, 04 Oct 2000, Brian Gerst wrote:
Mikulas Patocka wrote:
Hi.
arch/i386/kernel/entry.S
xchgl %eax, ORIG_EAX(%esp) # orig_eax (get the error code. )
movl %esp,%edx
xchgl %ecx, ES(%esp)# get the address and save es.
pushl %eax
On Wed, 11 Oct 2000, Frank de Lange wrote:
Solved the problem with Winchip not booting. It turns out they do not like the
code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
like it should.
That
On Tue, 10 Oct 2000, Jamie Lokier wrote:
1. Move the error_code block from divide_error to page_fault;
this removes one jump from the page_fault path.
It is not clear that it is worth it. You want to align error_code and
page_fault to 16 or 32 bytes bytes at least, and it would need
On Fri, 13 Oct 2000, Linus Torvalds wrote:
- pre3:
...
- Dave Jones: x86 setup fixes (recognize Pentium IV etc).
And then in test10-pre3 we find the following code added to
arch/i386/kernel/setup.c:
+ /* Pentium IV. */
+ if (c-x86 == 15) {
+
Here's a patch which should improve Pentium IV support in test10-pre.
The test10-pre3 patch detects Pentium IV (family code 15) but resets
boot_cpu_data.x86 to 6 in this case.
The advantage of doing this is that the places in the kernel which
construct cpu family names (i386 .. i686) still
This patch should fix the Pentium IV and other CPU detection
glitches which remain in test10-pre4.
The necessary fixes are:
* arch/i386/kernel/setup.c:
- (Pentium IV) don't goto name_decoded, return instead; otherwise
x86_model_id which was grabbed from the extended cpuid levels
will
i've had problems compiling pcmcia support in the last 2 pre releases of
the test10 kernel, pre4 and pre5. i'm using pcmcia-cs-3.1.21, which last
time i checked was the latest version of the pcmcia package source.
I'm using this patch.
/Mikael
--- pcmcia-cs-3.1.21/Configure.~1~ Thu Aug
On Sat, 3 Mar 2001 23:35:34 + (GMT), Alan Cox wrote:
Well, from reading the source, I don't see how this can break APM... What=
am I
missing?
If you've stopped kapm-idled from using cpu then you've stopped it from going
into the bios suspend one presumes.
Maybe, maybe not.
Short
Alan et al,
This patch (against 2.4.2-ac14) fixes a buglet in the UP-APIC support.
As a side-effect of hpa's CPU detection rewrite in 2.4.0-test, the
X86_FEATURE constants where changed from bit masks to bit numbers.
Unfortunately one spot in apic.c:detect_init_APIC() wasn't updated,
with the
On Wed, 14 Mar 2001 12:34:06 -0700 (MST), Andreas Dilger wrote in LKML:
Lars writes:
Put LABEL=label set with e2label in you fstab in place of the device name.
Which is great, for filesystems that support labels. Unfortunately,
this isn't universally available -- for instance, you cannot
Andreas Dilger writes:
Andries writes:
I've implemented a patch for util-linux-2.11a
which adds LABEL support to mkswap(8) and swapon/swapoff(8).
But I would prefer a somewhat more ambitious approach.
My first thought was: why label individual swap partitions?
I almost
of the recently removed "remote control" facility.
- WinChip documentation updates and corrections.
/ Mikael Pettersson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Fri, 24 Nov 2000, Jakub Jelinek wrote:
so the reason why it did not show up in the gcc you picked up from
ftp.gnu.org is that you have compiled it so that it defaults to -mcpu=i686
where the bug does not show up.
Indeed. I just ran some tests, and I can confirm that gcc 2.95.2 vanilla
An updated version of the UP-APIC patch for Intel P6 processors
is now available at:
http://www.csd.uu.se/~mikpe/linux/upapic/
The current version is intended for 2.4.0-test12 final.
This version is based on Ingo Molnar's upapic-2.4.0-test9-F8 patch,
with add-on patches from Maciej W.
Alan,
2.2.18 broke the emu10k1 driver when compiled into the kernel.
The problem is that 2.2.18 now implements 2.4-style module_init,
so emu10k1 ended up being initialised twice when built non-modular,
which rendered it dysfunctional. The fix is to remove the now
obsolete explicit init calls.
Francis Pieraut wrote:
I try to activate APIC interrruption on a single processor(PIII) with
kernel2.4.0-test11.
I activate APIC interruption with the configuration of linux kernel
2.4.0test-11. In the linux kernel configuration under processor type and
features I activate "APIC and IO-APIC
On Thu, 4 Jan 2001, Linus Torvalds wrote:
Changes since the prerelease:
...
Matti Aarnio:
- teach tulip driver about media types 5 and 6
This part of the patch introduces a bug in 2.4.0, as noticed by gcc:
media.c: In function `tulip_select_media':
media.c:268: warning: unused variable
Memory sizing for old machines whose BIOSen don't speak E820
got broken in 2.4.0-test13-pre4:
--- v2.4.0-test12/linux/arch/i386/kernel/setup.cMon Dec 11 17:59:43 2000
+++ linux/arch/i386/kernel/setup.c Thu Dec 21 14:01:19 2000
@@ -518,7 +518,7 @@
e820.nr_map = 0;
On Mon, 8 Jan 2001, Taner Halicioglu wrote:
I probably missed a message or note or something about this, but when I went
from 2.2.17 to 2.2.18, my sound card (SB Live!) stopped working. It seems
that in 2.2.18, it gets detected TWICE:
kernel: Linux version
On Tue, 9 Jan 2001, Tony Sumner wrote:
I have a problem with ftape. What happened was that I had a backup on
QIC80 tape that I made from Red Hat 5.2 and I (foolishly?) installed
SuSE 7.0. I then found I could not read the tape with the newer version
of ftape.
...
Kernel version: was 2.0.36, now
Is there any known bug in 2.2.18pre15 that could cause the
following oops in fs/buffer.c:find_buffer() ?
=== snip ===
ksymoops 0.7c on i586 2.2.18pre15. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.18pre15/ (default)
On Wed, 1 Nov 2000, Tigran Aivazian wrote:
But it contains an erroneous part in microcode.c:
- if (c-x86_vendor != X86_VENDOR_INTEL || c-x86 6){
+ if (c-x86_vendor != X86_VENDOR_INTEL || c-x86 != 6){
printk(KERN_ERR "microcode: CPU%d not an Intel P6\n",
cpu_num);
arch/i386/kernel/apm.c and pci-pc.c use the lcall instruction
(call far indirect) for invoking BIOS services.
The following syntax is used:
(apm) lcall %cs:apm_bios_entry
(pci-pc)lcall (%edi)
This works ok with binutils 2.9.5, but binutils 2.10.0.18
(gas 2.10.90) as shipped
On 15 Nov 2000, H. Peter Anvin wrote:
This implements support for MCE on chips which don't support MCA (in
addition to enabling MCA for non-Intel chips, like Athlon, which
supports MCA.)
I would appreciate it if people who have chips with MCE but no MCA --
this includes older AMD chips and some
2.4.0-test10 broke `dd' for block devices, due to the following
change to do_sys_truncate do_sys_ftruncate:
diff -u --recursive --new-file v2.4.0-test9/linux/fs/open.c linux/fs/open.c
--- v2.4.0-test9/linux/fs/open.cSun Oct 8 10:50:33 2000
+++ linux/fs/open.c Thu Oct 26 08:11:21
On Thu, 16 Nov 2000, Alexander Viro wrote:
And what kind of meaning would you assign to truncate on floppy?
On a block or char device, truncate == lseek seems reasonable.
My guess is that dd uses ftruncate because that's correct for
regular files and has happened to also work (as an alias for
Jordan writes:
I have been running a plug in for xmms for some time that uses the
aviplay program and avifile library...then when upgrading to test5/6 I
start getting this error message when running xmms:
ERROR: no time-stamp counter found! Quitting.
...
contents of /proc/cpuinfo:
Hmm, my CPUID vs /proc/cpuinfo comment seemed somewhat controversial.
Tigran Aivazian wrote:
Arguably, it is always better to parse /proc/cpuinfo instead of executing
CPUID directly (think PCI -- drivers should _NOT_ get their irq/io/etc
values from config space directly but only what the
On Mon, 7 May 2001 21:47:33 -0400 (EDT), Adam [EMAIL PROTECTED] wrote:
So I'm wondering, is there a way, kind of like relink system call which
coule take existing file descriptor (they are still so the fd is there,
just unlinked) and link it back to file name?
POSIX' fattach(int fd, const char
On Sat, 16 Jun 2001 11:27:53 +0900, [EMAIL PROTECTED] wrote:
The message on the screen
calibrating APIC timer .
CPU clock speed is 1395.7390MHz
... host bus clock speed is 0. MHz
cpu: 0, clocks: 0, slic: 0
Then nothing. I had to push the reset button at this point.
On Wed, 27 Jun 2001 17:42:01 +0800, Frank Zhu wrote:
I use a PIII machine as the server and cyrixIII machine as the client.The
kernel is 2.4.5.The distribute is red hat 7.1
when i mount the nfs file system at the client it failed.The core file is
created.using the gdb it report :
Program
@@ -82,25 +82,35 @@
/*
* Activate the NMI watchdog via the local APIC.
* Original code written by Keith Owens.
+ * AMD K7 code by Mikael Pettersson.
*/
+static unsigned int nmi_perfctr_msr; /* the MSR to reset in NMI handler */
#define MSR_K7_EVNTSEL0 0xC001
#define MSR_K7_PERFCTR0
On Fri, 2 Feb 2001 01:37:28 +0100, Ingo Molnar wrote:
On Thu, 1 Feb 2001, Mikael Pettersson wrote:
This patch (against 2.4.1-ac1) contains the following fixes:
* UP-APIC linkage fix: nr_ioapics must be moved from io_apic.c to
mpparse.c to permit linking the kernel in pure UP-APIC
Maciej W. Rozycki writes:
I've forgotten to cc you when sending Ingo my patch-2.4.0-ac12-upapic-19
fixes a few days ago, my apologies. Since the two patches conflict with
each other, I've merged them together and provide the result below.
Please check if it is fine for you.
Looks
H. Peter Anvin writes:
if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL) {
printk("No APIC support for non-Intel processors.\n");
return -1;
}
Why is the test there in the first place? If the machine has an APIC, it
should be
H. Peter Anvin wrote:
"Maciej W. Rozycki" wrote:
...
It might be viable just to delete the test altogether, though and just
trap #GP(0) on the MSR access. For the sake of simplicity. If a problem
with a system ever arizes, we may handle it then.
Note that we still have to choose
This patch contains two CPU detection bug fixes:
- arch/i386/kernel/apic.c:detect_init_APIC():
This is being run before identify_cpu(), so the x86_vendor
field wasn't properly defined. It only _seemed_ to work before
because uninitialised == 0 == X86_VENDOR_INTEL.
The basic CPU detection
On Thu, 8 Feb 2001 12:32:01 MET-1, Petr Vandrovec wrote:
I have another question for UP APIC NMI: As I reported some time ago,
if performance counters overflow when LVTPC has 'disabled' bit set,
NMI is lost forever. This causes problems with VMware - it has to
disable NMI deliveries during CR3
fixes and updated glue patches for new 2.2 kernels. New features
and hardware support will be implemented in the perfctr-2.x branch,
but it will only support 2.4/2.5 kernels. (Sorry, but maintaining
compatibility with 2.2 kernels is taking too much of my time.)
/ Mikael Pettersson
-
To unsubscribe
2.4.1-ac breaks parport_pc in PCI-less configs.
Attempting to 'make vmlinux' in 2.4.1-ac14 with
# CONFIG_MODULES is not set
# CONFIG_PCI is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
results in
drivers/parport/driver.o: In function `parport_pc_init_superio':
Maciej W. Rozycki : Various updates and fixes.
+ * Mikael Pettersson : Power Management for UP-APIC.
*/
#include linux/config.h
@@ -379,14 +380,169 @@
setup_apic_nmi_watchdog();
}
+#ifdef CONFIG_PM
+
+#include linux/slab.h
+#include linux/p
On Tue, 20 Feb 2001 16:00:53 -0500 (EST), Ingo Molnar wrote:
my major gripe right now is that we still have bug reports that say that
systems hang when using nmi_watchdog=1 and work if nmi_watchdog=0.
Changing the NMI watchdog to be 1 Hz will make these bugreports "Linux
hangs once a week"
On Thu, 22 Mar 2001 21:23:54 + (GMT), Alan Cox wrote:
Really the whole oom_kill process seems bass-ackwards to me. I can't in my mind
logically justify annihilating large-VM processes that have been running for
days or weeks instead of just returning ENOMEM to a process that just
On Thu, 22 Mar 2001 23:43:57 + (GMT), Alan Cox wrote:
How do you return an out of memory error to a C program that is out of memory
due to a stack growth fault. There is actually not a language construct for it
SIGSEGV.
Stack overflow for a language like C using standard
Andrew Morton writes:
Mikael Pettersson wrote:
[+] Speaking as a hacker on a runtime system for a concurrent
programming language (Erlang), I consider the current Unix/POSIX/Linux
default of having the kernel throw up[*] at the user's current stack
pointer to be unbelievably
Simon Garner wrote:
I've compiled kernel 2.4.3 on the following RH7 system, and I'm now getting
random crashes at boot, during IO-APIC initialisation. Random meaning that
sometimes it boots fine, other times it doesn't, and it hangs in different
places (but always around IO-APIC stuff). It
On Sun, 25 Mar 2001 18:40:03 +0200, Benjamin Herrenschmidt wrote:
There is a problem with the power management code for console.c
The current code calls do_blank_screen(0); on PM_SUSPEND, and
unblank_screen() on PM_RESUME.
The problem happens when X is the current display while putting the
Does the kernel's module loader (kernel/module.c, not kmod)
protect adequately against concurrent load/load or load/unload
requests? The question applies to both 2.2 and 2.4 kernels.
I'm trying to track down a problem where a user using a
RedHat 2.2.17-14 SMP kernel managed to trigger a
Bug fix for 2.4.3-ac7 nfsd changes: set_bit() needs a pointer
to the lvalue to modify, not the lvalue itself.
/Mikael
--- linux-2.4.3-ac7/fs/nfsd/nfsfh.c.~1~ Mon Apr 16 15:23:54 2001
+++ linux-2.4.3-ac7/fs/nfsd/nfsfh.c Mon Apr 16 15:57:24 2001
@@ -167,7 +167,7 @@
The machine is an old Athlon64 laptop (Targa Visionary 811,
OEMd as the Arima W720-K8, also sold as the eMachines m6805)
with a VIA K8T800 chipset. ACPI is enabled.
Up to kernel 2.6.20, time-keeping worked fine. In the
x86-64 kernel, the clock source is listed as jiffies.
With current
Valerie Henson writes:
From: Guido Classen [EMAIL PROTECTED]
This small patch fixes two issues with the Lite-On 82c168 PNIC adapters.
I've tested it with two cards in different machines both chip rev 17
The first is the wrong register address CSR6 for writing the MII register
which
On Mon, 19 Mar 2007 12:46:16 +, Alan Cox wrote:
This duplicates the IDE core LED trigger in the libata core.
I plan to use this by allowing PMU LED control on G5 towers. My test
platform
is a PowerMac 7,3 (Dual G5 2.0GHz, June 2004) with a K2 (sata_svw)
controller.
I
On Mon, 19 Mar 2007 18:42:22 +0100, Jesper Juhl wrote:
--- a/drivers/block/floppy.c
+++ b/drivers/block/floppy.c
@@ -4302,7 +4302,12 @@ static int __init floppy_init(void)
if (err)
goto out_flush_work;
-
On Tue, 20 Mar 2007 12:29:49 +0100 (CET), Andreas Kleen [EMAIL PROTECTED]
wrote:
The floppy driver's sysfs file just provides some auxiliary
information to user-space, none of which matters for most of
its users. It is IMO totally inappropriate to fail floppy
driver init in this case.
On Mon, 26 Mar 2007 13:29:37 +0200, Jean Delvare wrote:
* * * * * Updated patch * * * * *
From: Rudolf Marek [EMAIL PROTECTED]
Add safe (exception handled) variants of rdmsr_on_cpu and wrmsr_on_cpu.
You should use these when the target MSR may not actually exist, as
doing so could trigger
When I merged my 20619 new EH conversion with #libata-upstream
I had to manually resolve a conflict, and inadvertently lost
pdc_pata_ops' -post_internal_cmd binding. Corrected by this patch.
Signed-off-by: Mikael Pettersson [EMAIL PROTECTED]
---
drivers/ata/sata_promise.c |1 +
1 files
number both on the stack
and in EAX
Also, the x86-64 kernel's ia32_setup_rt_frame() has duplicated code
for setting up -mregparm=3 parameters: it looks like the same patch
hunk was merged twice at some point.
Fixed by the following patch.
Signed-off-by: Mikael Pettersson [EMAIL PROTECTED
Update my email address in CREDITS to one that works.
Signed-off-by: Mikael Pettersson [EMAIL PROTECTED]
---
Should CREDITS have a specific maintainer?
diff -rupN linux-2.6.21-rc1/CREDITS linux-2.6.21-rc1.mikpe-email-address/CREDITS
--- linux-2.6.21-rc1/CREDITS2007-02-24 22:32:42.0
of the PATA-only 20619 redundantly set
up scr_addr for the ports. Remove this.
Tested on 20619, 20575, and 20775 chips.
Signed-off-by: Mikael Pettersson [EMAIL PROTECTED]
---
drivers/ata/sata_promise.c | 29 ++---
1 files changed, 10 insertions(+), 19 deletions(-)
diff
On Sun, 25 Feb 2007 23:39:48 +0100, Andi Kleen wrote:
On Sunday 25 February 2007 12:47, Mikael Pettersson wrote:
The invokation of signal handlers on x86 has several bugs
in its treatment of the signal number parameter:
- the i386 kernel passes the raw not the translated signal number
] Error 1
make: *** [arch/sparc64/kernel] Error 2
Most other MSI stuff in irq.c is #ifdef CONFIG_PCI_MSI.
So do the same for virt_irq_free() to fix this problem.
Signed-off-by: Mikael Pettersson [EMAIL PROTECTED]
--- linux-2.6.21-rc1/arch/sparc64/kernel/irq.c.~1~ 2007-02-26
17:47:54.0
On Wed, 4 Apr 2007 12:06:44 +0200, Ingo Molnar wrote:
btw., how about pushing utrace to v2.6.22, is anything big holding that
up?
IMO, until regressions in the ptrace userspace API like
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229112
are eliminated, utrace must not replace ptrace
Robin Holt writes:
I have been experiencing hangs on a newly setup machine. Unfortunately,
it appears to be hanging inside the interrupt handler as sysrq and
caps-lock led seem to stop working when the event occurs. I am guessing
it is related to the sata_promise driver, but that is
Francis Moreau writes:
On 9/17/07, Ulrich Drepper [EMAIL PROTECTED] wrote:
On 9/17/07, Francis Moreau [EMAIL PROTECTED] wrote:
I think signal trampolines will still need them too. So making
vsyscalls configurable doesn't seem to work, does it ?
vsyscalls aren't used for that.
On Wed, 19 Sep 2007 14:35:29 +0100, James Pearson wrote:
/proc/PID/environ currently truncates at 4096 characters, patch based on
the /proc/PID/mem code.
Does /proc/PID/mem even work? If I do `strace cat /proc/PID/mem /dev/null'
for a known good PID, the first read() from /proc/PID/mem fails
H. Peter Anvin writes:
Mikael Pettersson wrote:
On Wed, 19 Sep 2007 14:35:29 +0100, James Pearson wrote:
/proc/PID/environ currently truncates at 4096 characters, patch based on
the /proc/PID/mem code.
Does /proc/PID/mem even work? If I do `strace cat /proc/PID/mem
/dev
On Fri, 16 Nov 2007 18:11:00 -0600, Timur Tabi wrote:
A private data pointer in struct device_attribute allows the 'show' and
'store'
functions to access instance data. This handy in situations where the
driver_data and platform_data pointers of 'struct device' are already used
for other
On Thu, 6 Dec 2007 21:20:41 -0500, Erez Zadok wrote:
I get a permission denied when trying to mount a localhost nfsv2/3
exported volume, on v2.6.24-rc4-124-gf194d13. It works w/ nfsv4 mounting.
It worked fine in 2.6.24-rc3. Here's a sequence of ops I tried:
# mount -t ext2 /dev/hdb1
On Sun, 25 Nov 2007 15:02:15 -0700, Josh Goldsmith wrote:
I have a Linksys NSLU2 running 2.6.21 (I can replicate the problem on
2.6.23 but it isn't fully supported on SlugOS). It is a armv5teb device
with 32MB of RAM, 400+ MB swap on its 160GB USB2 root disk. The machine is
used as a
On Sun, 25 Nov 2007 22:28:03 -0700, Josh Goldsmith wrote:
Is your 486 running a IDE disk on a normal interface or via USB? I wonder
if the NSLU2 only having I/O via USB might be significant.
My 486 has neither PCI nor USB, the disk is attached to a
plain ancient IDE port.
Also, this is a
William Lee Irwin III writes:
The -cap fields of struct acpi_video_device and struct acpi_video_bus
are 1B each, not 4B. The oversized memset()'s corrupted the subsequent
list_head fields. This resulted in silent corruption without
CONFIG_DEBUG_LIST and BUG's with it. This patch uses
William Lee Irwin III writes:
On Wed, Dec 12, 2007 at 12:48:09PM +0100, Mikael Pettersson wrote:
IMO the memset(ptr, 0, sizeof(*ptr)) idiom is both safer
and avoids having to write an uninteresting type name.
How about this, then?
Looks good.
Acked-by: Mikael Pettersson [EMAIL
sym2_remove(), which is marked __devexit.
Fixed by removing the __devexit from sym2_remove().
Signed-off-by: Mikael Pettersson [EMAIL PROTECTED]
--- linux-2.6.24-rc5/drivers/scsi/sym53c8xx_2/sym_glue.c.~1~2007-12-15
15:37:04.0 +0100
+++ linux-2.6.24-rc5/drivers/scsi/sym53c8xx_2/sym_glue.c
Linda Walsh writes:
Robert Hancock wrote:
Linda Walsh wrote:
Alan Cox wrote:
rate began falling; at 128k block-reads-at-a-time or larger, it
drops below
20MB/s (only on buffered SATA).
Try disabling NCQ - see if you've got a drive with the 'NCQ = no
readahead' flaw.
Linda Walsh writes:
Mikael Pettersson wrote:
Linda Walsh writes:
Robert Hancock wrote:
Linda Walsh wrote:
read rate began falling; at 128k block-reads-at-a-time or larger,
it
drops below 20MB/s (only on buffered SATA).
But more importantly -- I notice
Alexander Shaduri writes:
On Sat, 5 Jan 2008 09:10:12 +
Al Viro [EMAIL PROTECTED] wrote:
and we have q-page == 0x48464443. Seeing how we assign that sucker, that
smells like we've got a page on quicklist with {0x43, 0x44, 0x46, 0x48}
in its first 4 bytes. Instead of having
Booting 2.6.24-rc1 on my PowerMac the kernel now spits
out a sysctl warning early in the boot sequence:
--- dmesg-2.6.23
+++ dmesg-2.6.24-rc1
...
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash
On Sat, 27 Oct 2007 22:34:53 +0400, Alexey Dobriyan wrote:
On Sat, Oct 27, 2007 at 07:57:38PM +0200, Mikael Pettersson wrote:
Booting 2.6.24-rc1 on my PowerMac the kernel now spits
out a sysctl warning early in the boot sequence:
--- dmesg-2.6.23
+++ dmesg-2.6.24-rc1
...
IP route
My old 486 fails to boot with the 2.6.24-rc1 kernel.
Grub loads it, 4 lines of text appear but not the kernel's
Linux version blah greet, and the machine reboots.
Double-checked with a serial console: nothing appears
before it reboots.
All 2.6 kernels up to 2.6.23 worked fine on this machine.
On Sun, 28 Oct 2007 21:33:02 -0700, H. Peter Anvin wrote:
Mikael Pettersson wrote:
My old 486 fails to boot with the 2.6.24-rc1 kernel.
Grub loads it, 4 lines of text appear but not the kernel's
Linux version blah greet, and the machine reboots.
Double-checked with a serial console
On Sun, 28 Oct 2007 21:34:58 -0700, H. Peter Anvin wrote:
Mikael Pettersson wrote:
My old 486 fails to boot with the 2.6.24-rc1 kernel.
Grub loads it, 4 lines of text appear but not the kernel's
Linux version blah greet, and the machine reboots.
Double-checked with a serial console
On Mon, 29 Oct 2007 14:47:49 +0100 (CET), Thomas Gleixner wrote:
On Mon, 29 Oct 2007, Mikael Pettersson wrote:
On Sun, 28 Oct 2007 21:33:02 -0700, H. Peter Anvin wrote:
Mikael Pettersson wrote:
My old 486 fails to boot with the 2.6.24-rc1 kernel.
Grub loads it, 4 lines of text
On Tue, 30 Oct 2007 11:54:01 -0700 (PDT), Linus Torvalds wrote:
On Tue, 30 Oct 2007, Jeff Garzik wrote:
Mikael Pettersson (2):
sata_promise: ASIC PRD table bug workaround, take 2
sata_promise: cleanups
You and Mikael need to sort out the way you send/accept patches
1 - 100 of 874 matches
Mail list logo
