Re: [PATCH] arm: Blacklist gcc 4.8.[012] and 4.9.0 with CONFIG_FRAME_POINTER

Peter Hurley writes: On 10/10/2014 12:36 PM, Russell King - ARM Linux wrote: On Fri, Oct 10, 2014 at 12:26:14PM -0400, Peter Hurley wrote: gcc versions 4.8.[012] and 4.9.0 generates code that prematurely adjusts the stack pointer such that still-to-be-referenced locals are below the

Re: [PATCH] arm: Blacklist gcc 4.8.[012] and 4.9.0 with CONFIG_FRAME_POINTER

Peter Hurley writes: On 10/11/2014 12:33 PM, Mikael Pettersson wrote: Peter Hurley writes: On 10/10/2014 12:36 PM, Russell King - ARM Linux wrote: On Fri, Oct 10, 2014 at 12:26:14PM -0400, Peter Hurley wrote: gcc versions 4.8.[012] and 4.9.0 generates code that prematurely

Re: status of ia64 / hpsim

Tony Luck writes: On Tue, Dec 30, 2014 at 7:50 AM, Christoph Hellwig h...@infradead.org wrote: IS the ia64 hpsim architecture still in use? I noticed it because it has a fairly rudimentary SCSI driver under arch/ia64, which doesn't look very maintained. Mikael was doing

Re: [PATCH] Don't allow blocking of signals using sigreturn.

Jann Horn writes: Or should I throw this patch away and write a patch for the prctl() manpage instead that documents that being able to call sigreturn() implies being able to effectively call sigprocmask(), at least on some architectures like X86? Well, that is the semantics of

Re: [PATCH] seccomp.2: Add note about alarm(2) not being sufficient to limit runtime

Jann Horn writes: On Wed, Mar 11, 2015 at 10:43:50PM +0100, Mikael Pettersson wrote: Jann Horn writes: Or should I throw this patch away and write a patch for the prctl() manpage instead that documents that being able to call sigreturn() implies being able to effectively

Re: [PATCH] Don't allow blocking of signals using sigreturn.

Andy Lutomirski writes: On Wed, Mar 11, 2015 at 2:43 PM, Mikael Pettersson mikpeli...@gmail.com wrote: Jann Horn writes: Or should I throw this patch away and write a patch for the prctl() manpage instead that documents that being able to call sigreturn() implies being able

[REGRESSION,BISECTED] 4.1-rc2 radeon audio changes oops the kernel hard

On my Ivy Bridge i7 mobo w/ Radeon graphics, the 4.1-rc2 kernel oopses hard, requiring a hard reset: BUG: unable to handle kernel NULL pointer dereference at 0010 IP: [a03d0e1b] radeon_audio_detect+0x5b/0x150 [radeon] PGD 0 Oops: [#1] SMP Modules linked in: af_packet

RE: [REGRESSION,BISECTED] 4.1-rc2 radeon audio changes oops the kernel hard

Deucher, Alexander writes: -Original Message- From: Mikael Pettersson [mailto:mikpeli...@gmail.com] Sent: Monday, May 04, 2015 11:53 AM To: linux-kernel@vger.kernel.org Cc: Deucher, Alexander Subject: [REGRESSION,BISECTED] 4.1-rc2 radeon audio changes oops the kernel

[4.3-rc1 regression] modular 8250 doesn't load

I have CONFIG_SERIAL_8250=m. With 4.2 '/sbin/modprobe 8250' worked and resulted in: [ 41.354550] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 41.375156] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A With 4.3-rc1 however the command fails and logs

Re: [4.3-rc1 regression] modular 8250 doesn't load

Greg Kroah-Hartman writes: > On Mon, Sep 14, 2015 at 08:06:21PM +0200, Mikael Pettersson wrote: > > Greg Kroah-Hartman writes: > > > On Mon, Sep 14, 2015 at 07:08:10PM +0200, Mikael Pettersson wrote: > > > > I have CONFIG_SERIAL_8250=m. With 4.

Re: [4.3-rc1 regression] modular 8250 doesn't load

Greg Kroah-Hartman writes: > On Mon, Sep 14, 2015 at 02:12:43PM -0700, Greg Kroah-Hartman wrote: > > On Mon, Sep 14, 2015 at 10:42:24PM +0200, Mikael Pettersson wrote: > > > Greg Kroah-Hartman writes: > > > > On Mon, Sep 14, 2015 at 08:06:21PM +0200, Mikael Pett

Re: [4.3-rc1 regression] modular 8250 doesn't load

Greg Kroah-Hartman writes: > On Mon, Sep 14, 2015 at 07:08:10PM +0200, Mikael Pettersson wrote: > > I have CONFIG_SERIAL_8250=m. With 4.2 '/sbin/modprobe 8250' worked > > and resulted in: > > > > [ 41.354550] Serial: 8250/16550 driver, 4 ports, IRQ sharing

Re: SIGSYS annoyance

Andy Lutomirski writes: > On Mon, Jun 6, 2016 at 9:03 AM, Kees Cook wrote: > > On Fri, Jun 3, 2016 at 10:16 PM, Andy Lutomirski > > wrote: > >> https://bugzilla.mozilla.org/show_bug.cgi?id=1176099 > >> > >> Should SIGSYS be delivered to the

Re: fork on processes with lots of memory

Felix von Leitner writes: > > Dear Linux kernel devs, > > > I talked to someone who uses large Linux based hardware to run a > > process with huge memory requirements (think 4 GB), and he told me that > > if they do a fork() syscall on that process, the whole system comes to > > standstill.

Re: 4.7-rc6, ext4, sparc64: Unable to handle kernel paging request at ...

Meelis Roos writes: > > > Just got this on bootup of my Sun T2000: > > >... > > > I have not seen it before, this includes 4.6.0 4.6.0-08907-g7639dad > > > 4.7.0-rc1-00094-g6b15d66 4.7.0-rc4-00014-g67016f6. > > > > > > It is not reproducible, did not appear on next reboot of the same > > >

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Anatoly Pugachev writes: > On Fri, Jul 28, 2017 at 11:45 AM, Mikael Pettersson > <mikpeli...@gmail.com> wrote: > > It's an rpmbuild --rebuild of Fedora's strace-4.18-1.fc24.src.rpm, but > > according to the > > build log the following should do it: > > &

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Mikael Pettersson writes: > Anatoly Pugachev writes: > > On Fri, Jul 28, 2017 at 11:45 AM, Mikael Pettersson > > <mikpeli...@gmail.com> wrote: > > > It's an rpmbuild --rebuild of Fedora's strace-4.18-1.fc24.src.rpm, but > according to the > &

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

David Miller writes: > From: Anatoly Pugachev > Date: Tue, 1 Aug 2017 01:01:47 +0300 > > > I don't know how to run on a running kernel , but as I understood: > > > > root@v215:strace# gzip -dc /boot/vmlinuz-4.12.0 > vmlinux > > root@v215:strace# gdb -q vmlinux > >

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Sam Ravnborg writes: > On Tue, Aug 01, 2017 at 10:58:29PM +0200, Sam Ravnborg wrote: > > Hi Mikael. > > > > I think this translates to the following code > > from linux/uaccess.h > > > > first part is the inlined _copy_from_user() > > > > > > > > (gdb) x/10i do_sys_poll+0x80-16 > >

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

David Miller writes: > From: Mikael Pettersson <mikpeli...@gmail.com> > Date: Thu, 3 Aug 2017 22:02:57 +0200 > > > With that in place the kernel booted fine. > > When I then ran the `poll' strace test binary, the OOPS was replaced by: > > &

Re: v4.13-rc2: usb mouse stopped working?

Jiri Kosina writes: > On Mon, 24 Jul 2017, Pavel Machek wrote: > > > On thinkpad x220, USB mouse stopped working in v4.13-rc2. v4.12 was > > ok, iirc. > > > > Now, USB mouse is so common hw that I may have something wrong in my > > config...? But I did not change anything there. > >

strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Attempting to build strace-4.18 as sparcv9 code and run its test suite on a sparc64 machine (Sun Blade 2500 w/ 2 x USIIIi in my case) fails reliably in three test cases (sched.gen, sched_xetattr.gen, and poll) because two test binaries (sched_xetattr and poll) OOPS the kernel and get killed.

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

David Miller writes: > From: Mikael Pettersson <mikpeli...@gmail.com> > Date: Thu, 27 Jul 2017 21:45:25 +0200 > > > Attempting to build strace-4.18 as sparcv9 code and run its test suite > > on a sparc64 machine (Sun Blade 2500 w/ 2 x USIIIi in my case) fails

Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro

Jia He writes: > I tried to build kernel 4.14-rc1 on a arm64 server in distro centos 7.3. > The gcc version is 4.8.5 I have no input on the specifics of the issue, but please note that gcc-4.8 is no longer supported or maintained by upstream. Even gcc-4.9 is EOL, and gcc-5 will be EOL:d inn a

Re: [PATCH] mm: disable `vm.max_map_count' sysctl limit

On Mon, Nov 27, 2017 at 6:25 PM, Andi Kleen wrote: > It's an arbitrary scaling limit on the how many mappings the process > has. The more memory you have the bigger a problem it is. We've > ran into this problem too on larger systems. > > The reason the limit was there

Re: [PATCH] mm: disable `vm.max_map_count' sysctl limit

On Mon, Nov 27, 2017 at 5:22 PM, Matthew Wilcox wrote: >> Could you be more explicit about _why_ we need to remove this tunable? >> I am not saying I disagree, the removal simplifies the code but I do not >> really see any justification here. > > I imagine he started seeing

[PATCH] mm: disable `vm.max_map_count' sysctl limit

Also built an ARM NOMMU kernel to make sure NOMMU compiles and links cleanly. Signed-off-by: Mikael Pettersson <mikpeli...@gmail.com> --- Documentation/sysctl/vm.txt | 17 +- Documentation/vm/ksm.txt | 4 Documentation/vm/remap_file_pages.txt | 4

Re: [PATCH] mm: disable `vm.max_map_count' sysctl limit

On Mon, Nov 27, 2017 at 11:12 AM, Michal Hocko wrote: > > I've kept the kernel tunable to not break the API towards user-space, > > but it's a no-op now. Also the distinction between split_vma() and > > __split_vma() disappears, so they are merged. > > Could you be more

Re: CPU overheat with 2.2

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

Re: 2.2.19+ide: corrupts ide tape output

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

Re: Hard lockup debugging suggestions? APIC enabling suggestions?

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

Re: Linux 2.4.5-ac7

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 ---

Re: Oops in 2.4.0-ac5

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

[PATCH] enable K7 nmi watchdog

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:

Re: [PATCH] enable K7 nmi watchdog

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

Re: problem with dd for floppy under 2.4.0

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:

[Announce] Version 1.8 of x86 performance counters driver

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/

x86 PAT errata

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

Re: x86 PAT errata

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

Re: time in the future during make for 2.4.0

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

Re: [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB

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

Re: [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB

On Wed, 31 Jan 2001 10:01:08 -0500, Adam Schrotenboer wrote: > > 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

Re: 2.2.18 - failed to exec /sbin/modprobe -s -k binfmt-464c

On Wed, 31 Jan 2001 14:17:56 -0700, Josh Higham wrote: >I tried compiling a 2.2.18 kernel, and when I reboot I get > >failed to exec /sbin/modprobe -s -k binfmt-464c Reconfigure with CONFIG_BINFMT_ELF=y and your kernel will work again. /Mikael - To unsubscribe from this list: send the line

Re: [ot] named sockets

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,

Re: [PATCH] 2.4.2: cure the kapm-idled taking (100-epsilon)% CPU

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.

[PATCH] UP-APIC fix for Mobile P6

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

Re: magic device renumbering was -- Re: Linux 2.4.2ac20

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

Re: [util-linux] Re: magic device renumbering was -- Re: Linux 2.4.2ac20

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

Re: [PATCH] Prevent OOM from killing init

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

[Announce] Version 1.5 of x86 performance counters driver

e 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 FAQ a

ide-tape bug in 2.4.0-test8

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

[PATCH] missing EXPORT_SYMBOLs break NFS in 2.4.0-test9-pre6

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

Re: 2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

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

Re: PROBLEM:Illegal instruction when mount nfs file systems using cyr ixIII

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

Re: PROBLEM:Illegal instruction when mount nfs file systems using

On Thu, 28 Jun 2001 20:42:09 +0100 (BST), Alan Cox wrote: >> > Intel specifically state that you cannot use CMOV without checking >> > for it. Its actually a gcc/binutils tool bug. The CPU is right. >> >> How is that a gcc bug? You tell the compiler to generate cmov, you run >> it on a CPU

[Announce] Version 1.6 of x86 performance counters driver

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/

Re: gcc-2.95.2-51 is buggy

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

[PATCH] local APIC and NMI watchdog on UP P6 systems

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.

Re: [patch] enabling APIC and NMI watchdog on UP systems

rn -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. + */ +void __init init_local_APIC(void) +{

Re: Integrating Andre IDE patch into 2.2.18/19 kernel

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

Re: [patch] APIC, NMI watchdog support on UP systems

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

Re: {PATCH] Re: wasting time on page fault

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. >>

Re: 2.4.0-test9 + Winchip2/2A processor family == hang on boot

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

Re: {PATCH] Re: wasting time on page fault

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

Re: test10-pre3

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) {

[PATCH] fixes to Pentium IV detection in test10-pre3

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

[PATCH] cpu detection fixes for test10-pre4

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

Re: pcmcia compile errors - test10-pre5

> 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

[PATCH] fix emu10k1 init breakage in 2.2.18

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.

Re: Activating APIC on single processor

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

2.4.0 tulip bug (was: And oh, btw..)

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

2.4.0 memory sizing broken on old x86 machines

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;

Re: 2.2.18 and EMU10K1 problems...

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

Re: Ftape bug

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.2.18pre15 oops in find_buffer()

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)

Re: Linux-2.4.0-test10

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",

binutils/gas problem with 'lcall'

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

2.4.0-test11pre2: one more Pentium IV CPU naming fix

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

2.2.18pre Pentium IV bug fix

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

Re: New bluesmoke patch available, implements MCE-without-MCA support

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

2.4.0-test10 truncate() change broke `dd'

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

Re: 2.4.0-test10 truncate() change broke `dd'

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

Re: Error in x86 CPU capabilities starting with test5/6

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

Re: Error in x86 CPU capabilities starting with test5/6

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

[PATCH] 2.4.1-ac1 UP-APIC/NMI watchdog fixes

@@ -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

Re: [PATCH] 2.4.1-ac1 UP-APIC/NMI watchdog fixes

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 linki

Re: [PATCH] 2.4.1-ac1 UP-APIC/NMI watchdog fixes

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

Re: UP APIC reenabling vs. cpu type detection ordering

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 >

[PATCH] Re: UP APIC reenabling vs. cpu type detection ordering

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

[PATCH] 2.4.1-ac6 UP-APIC bug fix

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

Re: [PATCH] Re: UP APIC reenabling vs. cpu type detection o

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

[Announce] Version 1.9 of x86 performance counters driver

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 when CONFIG_PCI=n

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':

[PATCH] 2.4.1-ac UP-APIC updates

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 { + /* 'active' is tr

Re: [PATCH] 2.4.1-ac UP-APIC updates

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"

Re: [PATCH] Prevent OOM from killing init

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

Re: [PATCH] Prevent OOM from killing init

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

Re: Asus CUV4X-D, 2.4.3 crashes at boot

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

Re: console.c unblank_screen problem

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

Re: console.c unblank_screen problem

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()

<    1   2   3   4   5   6   7   8   9   >