Re: __rtc_read_alarm missing month/year field bug?

2016-07-21 Thread Joe Lawrence
On 07/19/2016, Alexandre Belloni wrote: > > Well like said in my previous mail, I don't think the rollover is the > issue here but I'm interested in knowing what conditions are leading > to endless interrupts. Hi Alexandre, Unfortunately I've switched employers so I no longer have access to the

Re: __rtc_read_alarm missing month/year field bug?

2016-07-21 Thread Joe Lawrence
On 07/19/2016, Alexandre Belloni wrote: > > Well like said in my previous mail, I don't think the rollover is the > issue here but I'm interested in knowing what conditions are leading > to endless interrupts. Hi Alexandre, Unfortunately I've switched employers so I no longer have access to the

Re: __rtc_read_alarm missing month/year field bug?

2016-07-19 Thread Alexandre Belloni
On 27/06/2016 at 13:36:04 -0400, Joe Lawrence wrote : > Ping? This isn't a major problem, but can setup endless RTC interrupts > under certain conditions on said hardware. > Well like said in my previous mail, I don't think the rollover is the issue here but I'm interested in knowing what

Re: __rtc_read_alarm missing month/year field bug?

2016-07-19 Thread Alexandre Belloni
On 27/06/2016 at 13:36:04 -0400, Joe Lawrence wrote : > Ping? This isn't a major problem, but can setup endless RTC interrupts > under certain conditions on said hardware. > Well like said in my previous mail, I don't think the rollover is the issue here but I'm interested in knowing what

Re: __rtc_read_alarm missing month/year field bug?

2016-07-19 Thread Alexandre Belloni
Hi, On 20/06/2016 at 12:06:38 -0400, Joe Lawrence wrote : > Hello Alessandro and Alexandre, > > I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine > running the 4.6 kernel, with an expiration time that puts the alarm way > out into next year. This is easily reproducible on

Re: __rtc_read_alarm missing month/year field bug?

2016-07-19 Thread Alexandre Belloni
Hi, On 20/06/2016 at 12:06:38 -0400, Joe Lawrence wrote : > Hello Alessandro and Alexandre, > > I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine > running the 4.6 kernel, with an expiration time that puts the alarm way > out into next year. This is easily reproducible on

Re: __rtc_read_alarm missing month/year field bug?

2016-06-27 Thread Joe Lawrence
On 06/20/2016 12:06 PM, Joe Lawrence wrote: > Hello Alessandro and Alexandre, > > I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine > running the 4.6 kernel, with an expiration time that puts the alarm way > out into next year. This is easily reproducible on this machine by >

Re: __rtc_read_alarm missing month/year field bug?

2016-06-27 Thread Joe Lawrence
On 06/20/2016 12:06 PM, Joe Lawrence wrote: > Hello Alessandro and Alexandre, > > I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine > running the 4.6 kernel, with an expiration time that puts the alarm way > out into next year. This is easily reproducible on this machine by >

__rtc_read_alarm missing month/year field bug?

2016-06-20 Thread Joe Lawrence
Hello Alessandro and Alexandre, I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine running the 4.6 kernel, with an expiration time that puts the alarm way out into next year. This is easily reproducible on this machine by setting a wakealarm sometime in the near future, then

__rtc_read_alarm missing month/year field bug?

2016-06-20 Thread Joe Lawrence
Hello Alessandro and Alexandre, I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine running the 4.6 kernel, with an expiration time that puts the alarm way out into next year. This is easily reproducible on this machine by setting a wakealarm sometime in the near future, then