linux-kernel - Re: 2.6.20-mm2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Feb 2007 14:17:31 -0800
From:	David Brownell <david-b@...bell.net>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-mm2

On Thursday 22 February 2007 12:33 am, Rafael J. Wysocki wrote:

> Unfortunately, the userland shipped with OpenSUSE refuses to talk to the new
> one (or I don't know how to make it do that).

Did your "udev" create a /dev/rtc0?  If not, /sys/class/rtc-dev/rtc0/dev
will give the right major/minor numbers.

Given a /dev/rtc0, there are two simple solutions:

  (a) ln -s /dev/rtc0 /dev/rtc
  (b) upgrade your "hwclock" to one supporting "hwclock --file /dev/rtc0",
      since that should also try rtc0 when rtc can't be opened.

I found a udev incantation "git whatchanged drivers/rtc/rtc-dev.c",
which can automate (a):

       KERNEL=="rtc0", SYMLINK+="rtc"

I'm not sure what the story is on hwclock updates, given the issue
with "util-linux" maintainership.  I sent a patch on 7-Aug-2006 to
Adrian Bunk, which appears to have been disregarded, then to Karel
Zak (for the new fork?) on 17-Nov-2006 ... but if there's been an
announcement about a new util-linux repository with that patch,
I missed it.  The busybox patch I submitted 26-Jan-2007 hasn't
yet been merged, but that's a lot more understandable.

Basically it looks like userspace is almost a year behind the kernel
support for this RTC framework.  The problematic part is that it
seems that the "util-linux" maintainership issues are preventing
that issue from getting resolved ... so for now, I usually use
workaround (a).

> > Shoot.  OK, I'll see if I can reproduce it myself.  Is this system
> > using a generic CMOS RTC?  Or is HPET somehow involved?  (That old
> > RTC driver has HPET voodoo as well as normal RTC stuff.)
> 
> How can I check that?

If your boot messages say things about HPET, that's a start.  :)
I don't really know HPET; it hasn't ever come up on any system
that I've used.  ISTR that for various reasons BIOS would hide
it on most systems, but that Linux has been working on un-hiding
that hardware so it could be used.  I'll read up on it.  (As I
implied, the source code comments leave a lot to be desired.)

- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/