hwclock can break the RTC
Bug #274402 reported by
Tim Gardner
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Netbook Remix |
Triaged
|
High
|
Debbie Beliveau | ||
util-linux (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
Hardy |
Fix Released
|
High
|
Tim Gardner | ||
Intrepid |
Fix Released
|
High
|
Tim Gardner |
Bug Description
Binary package hint: util-linux
If multiple copies of hwclock are run simultaneously the RTC can become non-functional.
TESTCASE:
$ sudo bash -c 'for ((i = 0; i < 10; i++)) ; do ( hwclock &) ; done'
Related branches
Changed in belmont: | |
assignee: | nobody → smagoun |
importance: | Undecided → High |
milestone: | none → rc2 |
status: | New → Confirmed |
Changed in netbook-remix: | |
milestone: | 1.0.1 → 1.2.0 |
Changed in belmont: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
During startup hwclock.sh is run more then once. In rare cases they overlap causing the PC RTC to become non-functional. This is because the second copy of hwclock falls back to using IOPL and direct I/O instructions after it fails to open /dev/rtc (already owned by the first copy of hwclock). The RTC hardware is not designed for such uncontrolled access.