Adko Branil writes:
> >Right near the end there's a lockdep warning about a deadlock
>
> >between sata_promise's hardreset thing and the machine getting a
> >ata_bmdma_interrupt.
>
> >But since I don't know this code, it would be nice if you could take a
> >look at it.
>
> I picked up 3
Doug Kehn writes:
> Hi All,
>
> I am observing kernel soft lockups when running
> network throughput tests with NUTTCP. The kernel is a
> stock 2.6.23 kernel with patches from uClinux.org. I
> have applied the incremental 2.6.23 patches to produce
> the resulting 2.6.23.14-uc0 kernel. Th
Ard Biesheuvel writes:
> This patch adds support for the PROT_FINAL flag to
> the mmap() and mprotect() syscalls.
>
> The PROT_FINAL flag indicates that the requested set
> of protection bits should be final, i.e., it shall
> not be allowed for a subsequent mprotect call to
> set protection
Adrian Bunk writes:
> The issue described in [1] is still present and unfixed (and even the
> fix there wasn't complete since it didn't cover SMP).
>
> Thanks to Riku Voipio for noting that it is still unfixed.
>
> cu
> Adrian
>
> [1] http://lkml.org/lkml/2007/8/1/474
I think calling
Andi Kleen writes:
> Pavel Emelyanov <[EMAIL PROTECTED]> writes:
> >this subdir;
> > 3. sysctl inodes are now smaller than the procfs ones.
>
> That's always a good thing.
>
> > Note: update your initscripts to mount sysctl filesystem
> > right after the proc is mounted in order not
Vineet Gupta writes:
> On 07/09/2013 09:21 AM, Wedson Almeida Filho wrote:
> > On Sat, Jul 6, 2013 at 9:59 PM, Joe Perches wrote:
> >>
> >> Not correct.
> >>
> >>> while (start < end) {
> >>> - size_t mid = start + (end - start) / 2;
> >>> + size_t mid = (star
Dell Latitude E6510, CONFIG_DRM_NOUVEAU, 64-bit Fedora 17 user-space, Xorg
drivers, and
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev
a2).
With 3.11 X starts fine, with 3.12-rc1 it fails with the following in
Xorg.0.log:
...
[56.819] (II) Loading /usr/lib64/
I wrote:
> Dell Latitude E6510, CONFIG_DRM_NOUVEAU, 64-bit Fedora 17 user-space, Xorg
> drivers, and
>
> 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev
> a2).
>
> With 3.11 X starts fine, with 3.12-rc1 it fails with the following in
> Xorg.0.log:
>
> ..
Vince Weaver writes:
> On Fri, 30 Aug 2013, Stephane Eranian wrote:
> > >
> > You mean that the high cost in your first example comes from the fact
> > that you are averaging over all the iterations and not n-1 (where 1 is
> > the first). I don't see a flag in mmap() to fault it in immediately
mpty and the 'other' pty
> > has been closed) and, only then, wait for buffer work to complete
> > before re-testing if the read buffer is still empty.
> >
> > As before, subsequent pty master reads return any available data
> > until no more data is available,
With 3.12-rc[12] I see unexpected failures in gcc's Ada acats testsuite, e.g.
=== acats tests ===
FAIL: a83009b
FAIL: c37209a
FAIL: c45531e
FAIL: c45614a
FAIL: c67005d
FAIL: c730a01
FAIL: c74302b
FAIL: cc3004a
FAIL: cd2a24j
FAIL: cd2a53a
FAIL: cxa3001
FAIL:
Adko Branil writes:
> After updating bios no more crashes happened, i tested it many times
> on heavy HDD IO loads, with many kernels (including CONFIG_PREEMPT
> kernels). But now if enable "Cool'n' Quiet" option in bios,
> CONFIG_PREEMPT_VOLUNTARY kernel with passed "nosmp" at boot time,
> c
Alexander Kartashov writes:
> --- a/arch/arm/kernel/calls.S
> +++ b/arch/arm/kernel/calls.S
> @@ -387,7 +387,7 @@
> /* 375 */ CALL(sys_setns)
> CALL(sys_process_vm_readv)
> CALL(sys_process_vm_writev)
> -CALL(sys_ni_syscall)/* reserved for sys_kcm
mplayer worked fine on my Dell Latitude E6510 (nVidia GT218 [NVS 3100M]
graphics)
up to and including kernel 3.7-rc4. However, with 3.7-rc5 or -rc6, any attempt
to
run mplayer just blanks the screen, shows some stray white pixels in the upper
left
corner, kills the X server, and spews the follow
Marcin Slusarz writes:
> On Sat, Nov 17, 2012 at 08:35:18PM +0100, Mikael Pettersson wrote:
> > mplayer worked fine on my Dell Latitude E6510 (nVidia GT218 [NVS 3100M]
> > graphics)
> > up to and including kernel 3.7-rc4. However, with 3.7-rc5 or -rc6, any
> >
with
3.10-rc5), and with the patch I no longer see the bug.
Tested-by: Mikael Pettersson
> ---
> drivers/tty/pty.c | 13 +
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/tty/pty.c b/drivers/tty/pty.c
> index 9c2f1bc..dd0
> This commit restores the old behavior.
>
> Signed-off-by: Ross Lagerwall
This solves the VT blanking regression I've seen with the 3.10-rc
kernels.
Tested-by: Mikael Pettersson
> ---
> On 06/14/2013 05:35 PM, Greg KH wrote:
> > p.s. In the future,
Markus Trippelsdorf writes:
> Since v3.8.0 several people reported intermittent IO errors that happen
> during high system load while using "emerge" under Gentoo:
> ...
> File "/usr/lib64/portage/pym/portage/util/_eventloop/EventLoop.py", line
> 260, in iteration
> if not x.callback(f,
Randy Dunlap writes:
> On 06/02/13 01:45, Linus Torvalds wrote:
> >
> > Another week, another -rc. But this time (at least for now) only as a git
> > tree - for people actually using the tar-balls and patches, I apologize,
> > but I'm a complete moron, and didn't install kup, its perl depen
Peter Hurley writes:
> Based on the other reports from Mikael and David, I suspect this problem
> may have to do with my commit 699390354da6c258b65bf8fa79cfd5feaede50b6:
>
>pty: Ignore slave pty close() if never successfully opened
>
> This commit poisons the pty under certain error con
Kernels up to an including 3.8.0 work Ok on my old dual-CPU G5, but
3.9-rc3 refuses to boot. After selecting it in yaboot's menu I see
Please wait, loading kernel
Elf64 kernel loaded
Loading ramdisk
ramdisk loaded
Invalid memory access at SRR0: .0380 SRR1: 9000.00081000
and
My Latitude E6510 has the following graphics HW:
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev
a2) (prog-if 00 [VGA controller])
Subsystem: Dell Latitude E6510
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e200 (32-bit, non-
I keep getting the following warning with 3.11-rc1 on sparc64:
[ cut here ]
WARNING: CPU: 1 PID: 8174 at fs/ext4/inode.c:230 ext4_evict_inode+0x1f0/0x448()
Modules linked in: sunrpc af_packet ipv6 hid_generic snd_ali5451 snd_ac97_codec
snd_seq snd_seq_device snd_pcm tg3 sn
Theodore Ts'o writes:
> On Fri, Jul 19, 2013 at 07:29:25PM +0200, Mikael Pettersson wrote:
> > I keep getting the following warning with 3.11-rc1 on sparc64:
> >
> > [ cut here ]
> > WARNING: CPU: 1 PID: 8174 at fs/ext4/inode.c:230
3.11-rc1 and -rc2 refuse to boot on my Dell Latitude E6510
(Intel Core i7-740QM processor) due to __rdmsr_on_cpu throwing
a #GP fault.
Being a laptop it doesn't have a good way to log early boot
messages, so the following was typed in by hand:
serio...
mousedev...
rtc_cmos...
general protection
Ortwin Glück writes:
> Hi,
>
> I think the bug is already fixed in this commit:
>
> f3ed0a17f0292300b3caca32d823ecd32554a667
>
> Thermal: x86 package temp thermal crash
Thanks. Although I can see that patch in git, it's NOT present in either
the linux-3.11-rc2.tar.xz or the patch-3.11-r
Warlich, Christof writes:
> Andi Kleen writes:
> > The FP registers are restored lazily, but the state for this is kept in
> > the kernel.
>
> I'm not sure if I understand "lazily" in this context: Do you mean that FP
> registers _are_ restored within the kernel, but _not_ from a (possibly
Warlich, Christof writes:
> Mikael Pettersson writes:
> > Write to the fpstate ->mxcsr and ->swd fields in the sigaction handler's
> > uc_mcontext.
>
> To me, "sigaction handler's uc_mcontext" sounds like userspace, which really
&
Warlich, Christof writes:
> richard -rw- weinberger writes:
> > Are you telling us that Ubuntu shipped the wrong header file?
>
> Hmm - at least I still don't know how to get the right definition
> of uc_mcontext (with eglibc-2.13 on Ubuntu 11.10) ...
>
> If I include both signal.h and as
Wang, Yalin writes:
> Hi
>
> I have download the latest linux kernel code 3.9.4
> And Compare with 3.4.0 kernel .
>
> It seems there is no change for this part ,
> So it will still happen .
> Does anyone know who is responsible for arm arch part kernel code ?
A quick look in MAINTAI
My Kirkwood-based QNAP TS-119P+ boots fine with the 3.5 kernel. With
3.6-rc2 and 3.6-rc3 however sata_mv complains:
sata_mv sata_mv.0: cannot get optional clkdev
sata_mv sata_mv.0: slots 32 ports 2
and then the kernel grinds to a halt with no further messages.
Full boot log from 3.6-rc3 appende
Andrew Lunn writes:
> On Sat, Aug 25, 2012 at 03:01:33PM +0200, Mikael Pettersson wrote:
> > My Kirkwood-based QNAP TS-119P+ boots fine with the 3.5 kernel. With
> > 3.6-rc2 and 3.6-rc3 however sata_mv complains:
> >
> > sata_mv sata_mv.0: cannot get optional cl
inal reporter's machine.
Signed-off-by: Mikael Pettersson
Tested-by: Adko Branil
Cc: sta...@vger.kernel.org
---
This bug affects 2.6.32 and newer kernels.
drivers/ata/sata_promise.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff -rupN linux-3.6-rc5/drivers/ata/s
Al Viro writes:
> On Fri, Feb 15, 2008 at 12:35:23PM +0100, Mikael Pettersson wrote:
> > Andi Kleen writes:
> > > Pavel Emelyanov <[EMAIL PROTECTED]> writes:
> > > >this subdir;
> > > > 3. sysctl inodes are now smaller than the procfs o
Russell King - ARM Linux writes:
> On Thu, Feb 14, 2013 at 02:49:18PM +0100, Arnd Bergmann wrote:
> > Recent assembler versions complain about extraneous
> > whitespace inside [] brackets. This fixes all of
> > these instances for the samsung platforms. We should
> > backport this to all kerne
Yangfei (Felix) writes:
> Hi all,
>
> I found that hardcoded instruction in inline asm can cause certains
> certain features fail to work on ARM platform due to endianness.
> As an example, consider the following code snippet of
> platform_do_lowpower function from arch/arm/mach-re
Schrober writes:
> Hi,
>
> I wondered why the container_of implementation is so complicated.
>
> #define container_of(ptr, type, member) ({ \
> const typeof( ((type *)0)->member ) *__mptr = (ptr);\
> (type *)( (char *)__mptr - offsetof(type,member) );})
>
I just updated an old 1st gen AMD64 laptop from kernel 3.6.0 to 3.7.0,
Fedora 15 user-space, and was greeted by the following kernel warning:
WARNING: at net/wireless/core.c:389 wiphy_register+0x5c3/0x600 [cfg80211]()
Hardware name: SAM#451B
Modules linked in: rt2500pci(+) snd_mpu401_uart rt2x00pc
devendra.aaru writes:
> On Mon, Dec 17, 2012 at 5:51 AM, Mikael Pettersson wrote:
> > I just updated an old 1st gen AMD64 laptop from kernel 3.6.0 to 3.7.0,
> > Fedora 15 user-space, and was greeted by the following kernel warning:
> >
> > WARNING: at net/wireles
Gertjan van Wingerde writes:
> Mikael, Devendra,
>
> On Mon, Dec 17, 2012 at 1:59 PM, devendra.aaru
> wrote:
> > On Mon, Dec 17, 2012 at 7:22 AM, Mikael Pettersson wrote:
> >> devendra.aaru writes:
> >> > On Mon, Dec 17, 2012 at 5:51 AM, Mikael
Tim Shepard writes:
> This weekend I finally figured out why the keyboard in my MacBook Pro
> stopped working between 3.4 and 3.5.
>
> When I turned on CONFIG_EXPERT it turned off CONFIG_HID_APPLE. There
> was no warning that selecting "Configure standard kernel features" will
> invisibly t
The kernel for this 486 has CONFIG_M486=y and CONFIG_M586TSC=n,
but the 2.6.25 kernels still try to access the TSC. Here's the
oops from 2.6.25-rc2-git8:
Pid: 0, comm: swapper Not tainted (2.6.25-rc2-git8 #1)
EIP: 0060:[] EFLAGS: 00010002 CPU: 0
EIP is at native_read_tsc+0x6/0x10
EAX: 8ce6 EBX
Ingo Molnar writes:
>
> * Mikael Pettersson <[EMAIL PROTECTED]> wrote:
>
> > The kernel for this 486 has CONFIG_M486=y and CONFIG_M586TSC=n, but
> > the 2.6.25 kernels still try to access the TSC. Here's the oops from
> > 2.6.25-rc2-git8:
>
>
Mikael Pettersson writes:
> Ingo Molnar writes:
> >
> > * Mikael Pettersson <[EMAIL PROTECTED]> wrote:
> >
> > > The kernel for this 486 has CONFIG_M486=y and CONFIG_M586TSC=n, but
> > > the 2.6.25 kernels still try to access the TSC.
Ingo Molnar writes:
>
> * H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
> > Please fix it in both places. Using XOR instead of AND-NOT is a bug,
> > plain and simple.
>
> yes, i already fixed that when i added Mikael's patch and it's all
> queued up.
Ok. For reference and for LKML view
Booting 2.6.25-rc3 on my Ultra5 causes a hang before or as
the console is switched over to the framebuffer. The console
output is (extrapolated from dmesg in -rc2 and handwritten
notes, as I don't have a serial cable to my U5):
PROMLIB: Sun IEEE Boot Prom 'OBP 3.25.3 2000/06/29 14:12'
PROMLIB: Roo
Mikael Pettersson writes:
> Booting 2.6.25-rc3 on my Ultra5 causes a hang before or as
> the console is switched over to the framebuffer. The console
> output is (extrapolated from dmesg in -rc2 and handwritten
> notes, as I don't have a serial cable to my U5):
>
>
Catalin Marinas writes:
> Compilation requires a new aarch64-none-linux-gnu-
> toolchain (http://gcc.gnu.org/ml/gcc-patches/2012-05/msg01694.html).
Where are the corresponding binutils patches? Without those it's
impossible for people outside ARM to build the toolchain and kernel.
/Mikael
--
T
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 th
On Wed, 4 Apr 2001 13:09:11 +0200 (MET DST), Mikael Petterson wrote:
> 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() o
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 situation
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 @@
iput(inode);
Alan,
I think I've finally eliminated the X screen corruption my laptop
has been seeing at resume from suspend events.
The fix in -ac3 eliminated the corruption but left the console
blank if I exited X. The fix in -ac4 didn't actually work --
the corruptions resurfaced later. (Sorry about that.)
s 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':
drivers/parport/driver.o(.text.ini
these extensively.
* Maciej W. Rozycki : Various updates and fixes.
+ * Mikael Pettersson : Power Management for UP-APIC.
*/
#include
@@ -379,14 +380,169 @@
setup_apic_nmi_watchdog();
}
+#ifdef CONFIG_PM
+
+#include
+#include
+
+static struct {
+
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" in
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.
Sho
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 `cs
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
David Woodhouse wrote:
>[EMAIL PROTECTED] said:
>> i prefer clear oopses and bug reports instead of ignoring them. A
>> failed MSR write is not something to be taken easily. MSR writes if
>> fail mean that there is a serious kernel bug - we want to stop the
>> kernel and complain ASAP. And corre
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: m
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 p
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
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 20
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/cpu
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 th
ead 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
exhi
g code has been rewritten and should
be faster and more robust. (It fixed a sampling problem one user had
on a 4-way MP box.)
/ 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
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
ide-tap
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
/lib/modules/2.4
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 work:
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 be
> 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 A
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",
>cp
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 wit
Linus,
The patch below (for 2.4.0-test11pre2) makes include/asm-i386/elf.h's
ELF_PLATFORM be an alias for system_utsname.machine. bugs.h (which
initialises system_utsname.machine) and elf.h use the same algorithm
to map boot_cpu_data.x86 to a name, so it makes sense to share the
name between them
Alan,
2.2.18pre's include/asm-i386/elf.h is currently broken for the
Pentium IV (out of bounds array indexing error).
Since ELF_PLATFORM is identical to system_utsname.machine, the
patch below simply tosses ELF_PLATFORM's broken name generation
code and uses system_utsname.machine instead.
There
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. R
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. Pat
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-API
rocessors\n");
return -1;
@@ -242,11 +248,82 @@
}
/*
+ * Initialize a P6's local APIC for UP operation (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
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 las
t behaves, reports,
>suggestions 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
>
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.
>> pu
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 m
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 w
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) {
+
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 eff
On Wed, 14 Mar 2001 12:34:06 -0700 (MST), Andreas Dilger wrote in LKML:
>Lars writes:
>> > Put LABEL= 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 mount
>> a sw
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
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 s
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 imp
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
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 al
1 - 100 of 447 matches
Mail list logo
