On Thursday, 22 February 2007 04:57, David Brownell wrote:
> On Tuesday 20 February 2007 2:07 pm, Rafael J. Wysocki wrote:
>
> > > Plus, I'd guess, the old rtc driver statically linked.
> >
> > Yes (mistakenly).
>
> Until someone merges the BSOD-for-Linux patch, I'll continue to
> assume that oopsing is the wrong response to "user" mistakes. ;)
>
> Legacy drivers can be such a PITA.
Unfortunately, the userland shipped with OpenSUSE refuses to talk to the new
one (or I don't know how to make it do that).
> > > What I see is a should-not-happen fault of some kind in a cleanup
> > > path that's been tested with non-PNP rtc drivers. A quick glance
> > > at the code left me puzzled. Would sleeping a second or two before
> > > calling rtc_device_unregister() change that behavior?
> >
> > [tries]
> >
> > No.
>
> 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?
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
