lkml.org 
[lkml]   [2007]   [Feb]   [21]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
FromDavid Brownell <>
SubjectRe: 2.6.20-mm2
DateWed, 21 Feb 2007 19:57:00 -0800
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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-02-22 04:59    [from the cache]
©2003-2008