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] [day] [month] [year] [list]
Message-ID: <86802c440808211057j41e2b0c8jcd0817ca047962d0@mail.gmail.com>
Date:	Thu, 21 Aug 2008 10:57:40 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"David Witbrodt" <dawitbro@...global.net>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Vivek Goyal" <vgoyal@...hat.com>,
	"Bill Fink" <billfink@...dspring.com>,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	"Peter Zijlstra" <peterz@...radead.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, netdev <netdev@...r.kernel.org>
Subject: Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression

On Thu, Aug 21, 2008 at 9:53 AM, David Witbrodt <dawitbro@...global.net> wrote:
>
>
>> > I will try to provide the entire output tonight or tomorrow.  It will be
>> > difficult, though:  it looks like I have to try to fit the info from about
>> > 60 of the printk's in your patch onto the 80x25 VGA screen, and still
>> > make it understandable enough to be useful.
>> >
>>
>> with hpet=disable?
>
> Oh, well that's easy.  (See below.)  I assumed you needed the data for a
> hanging kernel, not one with the workaround enabled.
>
> I can still try to provide the output of the printk's in your patch later,
> in that would have any value.  Here is 'dmesg' for a recent kernel with
> "hpet=disable":

insert_resource/request_resource works well

can you verify if hpet work on old kernel?

cat /proc/timers*

YH
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ