Ok, this also confirms that the board had issues *before* any changes
were made to the RTC core. I'd push the board vendor to update the BIOS
to avoid this issue.
Even so, I'm curious as to what exactly trips it up. Maybe we can
provide a module option for the rtc-cmos driver to disable the
Using an older known-good kernel, could you build and run the test
case at the end of Documentation/rtc.txt a few times and see if it
triggers the same problem?
I'm suspicious that the setting the alarm is whats tripping the BIOS
into enabling the HT bit. Because with older kernels, we used
Hi all,
Result of bisecting: v2.6.38-rc1 exhibits the problem. v2.6.37 and
many of the topic branches merged in the 2.6.38 merge window work ok.
Some other topic branches do not boot at all.
Jiri: if you have gitk installed, then git bisect visualize can help
get a sense of what's in the
Hi all,
Hi Jiri,
Jiri Polach wrote:
On Ben's advice I am trying to locate the commit that causes the problem to
appear more precisely using 'git bisect'. However, too many of generated
revisions are unbootable so I have to use 'bisect skip' frequently.
Ok, so I've looked over the log
On 10/30/2011 4:25 PM, Ben Hutchings wrote:
On Sun, 2011-10-30 at 07:05 -0400, Jiri Polach wrote:
Package: linux-2.6
Version: 2.6.39-3~bpo60+1
Severity: normal
When the computer is turned off using shutdown -h or halt command,
the hypertherading BIOS setting is changed - even if
5 matches
Mail list logo
