Re: Sparc release requalification
On Fri, Sep 11, 2009 at 05:18:18PM -0700, David Miller wrote: Could this consistency be of any significance, maybe the printk functions are somehow problematic... so I fiddled with them some more, but it looks more like they just waste time until something kicks in and somehow kills the kernel without a trace. That doesn't sound like perfctr_irq() and die_nmi(), but then I don't really any idea how exactly all that works :) You can't put debugging print statements in the NMI irq handlers like perfctr_irq(), that will almost always cause a lockup or crash. Nah, didn't even try that - I saw that the existing printk() in there doesn't even show up, despite obvious tries to make it so. In case it matters, this is a tlb_type=cheetah_plus machine. I see this %pcr handling has been in debugging code (oprofile, performance counters) for some time before it moved into the NMI handler, so I'm guessing it didn't get enough testing because fewer people have the debugging features enabled. I would recommend disabling it for now in the stable releases until this grave regression is resolved. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sparc release requalification
From: Josip Rodin j...@entuzijast.net Date: Sat, 12 Sep 2009 11:49:54 +0200 I see this %pcr handling has been in debugging code (oprofile, performance counters) for some time before it moved into the NMI handler, so I'm guessing it didn't get enough testing because fewer people have the debugging features enabled. I would recommend disabling it for now in the stable releases until this grave regression is resolved. Remind me what kernel you're trying now? -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sparc release requalification
On Sat, Sep 12, 2009 at 02:59:43AM -0700, David Miller wrote: From: Josip Rodin j...@entuzijast.net Date: Sat, 12 Sep 2009 11:49:54 +0200 I see this %pcr handling has been in debugging code (oprofile, performance counters) for some time before it moved into the NMI handler, so I'm guessing it didn't get enough testing because fewer people have the debugging features enabled. I would recommend disabling it for now in the stable releases until this grave regression is resolved. Remind me what kernel you're trying now? The 2.6.31 release. (Actually stable 2.6.31.y git but that's currently the same.) -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
