linux-kernel - Re: Early hang with 2.6.21-rc4-rt1

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 25 Mar 2007 10:01:58 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Early hang with 2.6.21-rc4-rt1

 > I finally got curious enough to want to debug why starting kvm with
 > tun/tap networking produces a bunch of
 > 
 >     rtc: lost some interrupts at 1024Hz.
 > 
 > messages.  So I'm assuming it's a ~millisecond irqs-off section
 > somewhere.

And after everything, it's a heisenbug -- I repeatably get that lost
interrupts message on stock 2.6.21-rc4 but never on -rt1 with
CONFIG_LATENCY_TRACE.

Any suggestion of where to look?  My /proc/latency_trace stays
stubbornly empty -- are there any sysctls I need to change from their
default to get latency tracing?  I'm a complete noob when it comes to
the -rt patch, so I'm not sure what the right way to use the tracing
infrastructure to track down this lost rtc interrupts issue is.

Thanks, 
  Roland
-
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/