[lkml]   [2007]   [Feb]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.20-mm2
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.

> > 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.)

- Dave
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-02-22 04:59    [W:0.116 / U:6.624 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site