linux-kernel - Re: [2/6] 2.6.21-rc2: known regressions

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]

Message-ID: <Pine.LNX.4.64.0703080954220.10832@woody.linux-foundation.org>
Date:	Thu, 8 Mar 2007 10:01:45 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Michael S. Tsirkin" <mst@...lanox.co.il>
cc:	Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Jeff Chua <jeff.chua.linux@...il.com>, pavel@...e.cz,
	linux-pm@...ts.osdl.org, lenb@...nel.org,
	linux-acpi@...r.kernel.org, luming.yu@...el.com,
	Arkadiusz Miskiewicz <arekm@...en.pl>,
	Konstantin Karasyov <konstantin.a.karasyov@...el.com>,
	Greg KH <greg@...ah.com>,
	linux-usb-devel@...ts.sourceforge.net,
	Thomas Meyer <thomas.mey@....de>, Meelis Roos <mroos@...ux.ee>,
	Alexey Starikovskiy <alexey.y.starikovskiy@...ux.intel.com>,
	Janosch Machowinski <jmachowinski@....de>,
	vladimir.p.lebedev@...el.com,
	Ash Milsted <thatistosayiseenem@...ab.com>,
	dmitry.torokhov@...il.com, linux-input@...ey.karlin.mff.cuni.cz,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [2/6] 2.6.21-rc2: known regressions

[ Eric, Ingo, can you double-check the timer initialization after resume? 
  We appear to have several reports of date not advancing, and while this 
  could be some SATA issue, it could easily be a timer tick issue too ]

On Thu, 8 Mar 2007, Michael S. Tsirkin wrote:
> 
> Here's the status with -rc3: better, but still does not work as well as 2.6.20.

Ok. I think we mostly solved the irq-related stuff, but you might want to 
check whether you have CONFIG_NOHZ on or off and whether that makes a 
difference.

> 2. First disk access after resume takes a couple of minutes
>    (seemed instant with 2.6.20) during this time no new messages show on console

Yeah, there is some problem with SATA resume. It would be beautiful if the 
people who actually see this could narrow it down with bisection. "It 
works for me" is clearly the case for many people, but not all.

But before blaming SATA, check if you have NO_HZ enabled and whether 
disabling that makes it work ok. If timeouts don't work right (or are 
*extremely* slow) things that should be instant won't be.

> 3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
>    after waiting for some 10 min, I rebooted.
>    no new messages showed up in /var/log/messages

I think this is likely just more of the disk being buggered, but it could 
again be related to NO_HZ (people report time not advancing, and that 
would make any X timeout taking forever, and you'd see exactly your 
behaviour).

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