On Sat, May 10, 2008 at 8:50 PM, Mike Marion <[EMAIL PROTECTED]> wrote:
> Quoting Carl Lowenstein <[EMAIL PROTECTED]>:
>
>
> > One way to get an OS that does not have Linux kernel hang problems
> > with hp/Compaq hardware and 64-bit AMD processors is to use
> >
>
>  Some quick searches on my mailbox didn't get me much (and I'm woefully
> behind in this box), but if there's a thread on this I'd love to see it.
> I'm curious where this assumption of linux having a bug that makes it hang
> on HP 64bit hosts came from.  We've been running hundreds of such systems
> for several years now and rarely have issues.  Uptimes have been very good,
> mostly only limited by the below reasons or our reboots for patching & OS
> installs.
>

For what it's worth, this apparently only a laptop problem, and only
hp/Compaq laptops at that.  I can watch it happen by running "hwclock
--systohc ---verbose" or "hwclock --hctosys --verbose" and see a
message like "waiting for interrupt" after which the whole system is
hung.  No keyboard or mouse response, the only way to regain control
is to cycle the power.

Google with search terms   hp laptop hwclock   gives several hundred
hits, maybe half of the first ten are relevant.  A few more good ones
in the second ten.

I am not making this up.

    carl
-- 
 carl lowenstein marine physical lab u.c. san diego
 [EMAIL PROTECTED]


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to