On Mon, Jul 22, 2013 at 03:17:33PM -0700, John Stultz wrote:
> Thanks again for your interest in hunting this down.
Yeah, "interest" is a good euphemism for "it pisses the h*ll out of me"
:-)
Btw, the failing box runs a SLED11 kernel (3.0.x + a lot of patches)
while the good box will run latest u
On 07/22/2013 02:27 PM, Borislav Petkov wrote:
On Mon, Jul 22, 2013 at 02:15:57PM -0700, John Stultz wrote:
On 07/22/2013 02:12 PM, Borislav Petkov wrote:
On Mon, Jul 22, 2013 at 01:59:01PM -0700, John Stultz wrote:
So did this work some of the time, but not all? Or was the behavior
totally un
On Mon, Jul 22, 2013 at 02:15:57PM -0700, John Stultz wrote:
> On 07/22/2013 02:12 PM, Borislav Petkov wrote:
> >On Mon, Jul 22, 2013 at 01:59:01PM -0700, John Stultz wrote:
> >>So did this work some of the time, but not all? Or was the behavior
> >>totally unchanged with this?
> >Yep, some of the
On 07/22/2013 02:12 PM, Borislav Petkov wrote:
On Mon, Jul 22, 2013 at 01:59:01PM -0700, John Stultz wrote:
So did this work some of the time, but not all? Or was the behavior
totally unchanged with this?
Yep, some of the time. The first couple of runs it worked and I was
euphoric and then it r
On Mon, Jul 22, 2013 at 01:59:01PM -0700, John Stultz wrote:
> So did this work some of the time, but not all? Or was the behavior
> totally unchanged with this?
Yep, some of the time. The first couple of runs it worked and I was
euphoric and then it rebooted and I almost threw the box out the win
On 07/19/2013 08:13 AM, Borislav Petkov wrote:
On Fri, Jul 19, 2013 at 04:26:28PM +0200, Borislav Petkov wrote:
On Fri, Jul 19, 2013 at 12:53:49AM +0200, Borislav Petkov wrote:
I assumed it was some sort of BIOS issue where any modification of the
RTC_AIE bit caused the alarm irq line to be lef
On Fri, Jul 19, 2013 at 05:13:21PM +0200, Borislav Petkov wrote:
> Nope, this doesn't help - box just rebooted. :(
>
> So I'm back to the DMI quirk patch...
Ok, some more observations before I throw this box out the window:
So, we emulate RTC there with HPET:
$ cat /proc/driver/rtc
rtc_time
On Fri, Jul 19, 2013 at 04:26:28PM +0200, Borislav Petkov wrote:
> On Fri, Jul 19, 2013 at 12:53:49AM +0200, Borislav Petkov wrote:
> > > I assumed it was some sort of BIOS issue where any modification of the
> > > RTC_AIE bit caused the alarm irq line to be left high(or something
> > > like that)
On Fri, Jul 19, 2013 at 12:53:49AM +0200, Borislav Petkov wrote:
> > I assumed it was some sort of BIOS issue where any modification of the
> > RTC_AIE bit caused the alarm irq line to be left high(or something
> > like that) that triggered the immediate power-on on shutdown. But I've
> > not been
Hey John,
On Thu, Jul 18, 2013 at 09:35:26AM -0700, John Stultz wrote:
> So first of all, thanks for digging in and generating a patch here!
> This issue has been on my list, but I've not been able to reproduce
So you know about it! This is one nasty deal, I tell ya :)
> it and have just not had
On 07/18/2013 08:44 AM, Borislav Petkov wrote:
From: Borislav Petkov
41c7f7424259f ("rtc: Disable the alarm in the hardware (v2)") added the
functionality to disable the RTC wake alarm when shutting down the box.
However, there are at least two b0rked BIOSes we know about:
https://bugzilla.no
From: Borislav Petkov
41c7f7424259f ("rtc: Disable the alarm in the hardware (v2)") added the
functionality to disable the RTC wake alarm when shutting down the box.
However, there are at least two b0rked BIOSes we know about:
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.
12 matches
Mail list logo
