Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-05 Thread Andi Kleen
On Sun, Jan 05, 2014 at 05:45:47AM +0100, Mike Galbraith wrote: > On Sat, 2014-01-04 at 19:18 +0100, Andi Kleen wrote: > > On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote: > > > where do I start. Let me explain what is going on here. The code > >

Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-04 Thread Andi Kleen
On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote: > where do I start. Let me explain what is going on here. The code > sequence Yes the IST stacks are needed for correctness, even in more cases than the example below. You cannot just disable them, just because you don't li

Bug#684569: microcode module loaded on Celeron CPU

2012-08-13 Thread Andi Kleen
> At least when updates come through the BIOS the OS distributor does > not have to be involved. The non-free packages also allow users to > use the updates from Intel without too much fuss when they want them. One alternative would be to offer a downloader. Just hiding them from the user is not

Bug#684569: linux-image-3.5-trunk-686-pae: microcode module loaded on Celeron CPU

2012-08-13 Thread Andi Kleen
On Mon, Aug 13, 2012 at 09:44:48AM +0200, Paul Menzel wrote: > Looking into this some more, this seems unlikely in Debian because the > microcode packages are in non-free [1] and therefore not available for > Debian users not having enabled non-free repositories > > Because of that the microcode p

Bug#684569: linux-image-3.5-trunk-686-pae: microcode module loaded on Celeron CPU

2012-08-12 Thread Andi Kleen
On Sat, Aug 11, 2012 at 03:17:19PM +0200, Paul Menzel wrote: > > This really depends on what operations you want to do, and how buggy the > > CPU microcode installed by the BIOS is. If you care that much about it, > > you can blacklist it. > > Understood. Although I do not understand from where t

Bug#589187: mcelog: problem reading memory diagnosis

2010-07-17 Thread Andi Kleen
On Sat, Jul 17, 2010 at 11:30:19AM +0200, Julien BLACHE wrote: > > standard does not have a standardized way to do the matching mcelog > > wants to do, but my test boxes allowed it through the non standard > > parsing so I implemented it this way. > > Is there anything you'd need beside the dmidec

Bug#589187: mcelog: problem reading memory diagnosis

2010-07-17 Thread Andi Kleen
On Sat, Jul 17, 2010 at 10:48:19AM +0200, Julien BLACHE wrote: > Toni Mueller wrote: > > Hi Toni, Andi, > > Andi: We're trying to diagnose a DMI table parsing failure in > memdb.c. The output below is a patched mcelog that outputs the DMI > string it's failing to parse. > > Looks like the DMI t

Bug#587365: mcelog decodes "timeout" flag backwards

2010-06-28 Thread Andi Kleen
On Mon, Jun 28, 2010 at 06:22:03PM +0200, Julien BLACHE wrote: > Andi Kleen wrote: > > Hi, > > > Fix added to git, thanks everyone. > > Err, Andi, you changed the text strings but did not actually swap them > in commit adc8d7441d8d774cb6efb6aff748fb70ed41d51f,

Bug#587365: mcelog decodes "timeout" flag backwards

2010-06-28 Thread Andi Kleen
On Mon, Jun 28, 2010 at 12:18:30PM +0200, Julien BLACHE wrote: > forwarded 587365 a...@firstfloor.org > thanks > > "Patrick J. LoPresti" wrote: > > Hi Andi, Patrick, > > > (I apologize for submitting this via Debian, but I have been > > completely unable to locate contact information for the up

Bug#404148: disabling hw iommu on nvidia

2007-04-02 Thread Andi Kleen
On Tuesday 03 April 2007 00:29:16 dann frazier wrote: > hey Andi, > Debian is looking at patching our kernel to disable the hw iommu on > nvidia chipsets for the data corruption bug that's been discussed on > lkml[1]. It would be better if you waited until the official solution. The hardware deb

Bug#253588: this bug / #253588: tcp(7) contains incorrect/biased information about syncookies

2007-01-24 Thread Andi Kleen
> tcp.7 contains bad FUD about syncookies, I don't see any FUD in there -Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#341801: skge error; hangs w/ hardware memory hole

2006-07-07 Thread Andi Kleen
On Friday 07 July 2006 23:18, Stephen Hemminger wrote: > On Mon, 3 Jul 2006 22:52:38 +0200 > Martin Michlmayr <[EMAIL PROTECTED]> wrote: > > > We received the following bug report at http://bugs.debian.org/341801 > > > > | I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory > >