mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: tglx@linutronix.de
Cc: Ingo Molnar <mingo@elte.hu>, teunis <teunis@wintersgift.com>,
	linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor@mail.ru>,
	john stultz <johnstul@us.ibm.com>, Len Brown <lenb@kernel.org>
Subject: Re: various laptop nagles - any suggestions?   (note: 2.6.19-rc2-mm1 but applies to multiple kernels)
Date: Tue, 7 Nov 2006 23:19:03 -0800	[thread overview]
Message-ID: <20061107231903.99156678.akpm@osdl.org> (raw)
In-Reply-To: <1161552160.22373.17.camel@localhost.localdomain>

On Sun, 22 Oct 2006 23:22:39 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:

> This LAPIC business is weird.

So I tested your latest set of patches on the Vaio.  Still not very good. 
It all _seems_ to work for a while.  But after a suspend-to-disk/resume
cycle (which may not be relevant) and five-odd minutes uptime the machine
shat itself.

See http://userweb.kernel.org/~akpm/1.txt for the whole log and
http://userweb.kernel.org/~akpm/config-sony.txt for the config.

It's presently sitting in an xterm echoing keyboard input and permitting
the mouse cursor to move, but it doesn't do anything else.



I have a bad feeling about the hrtimer+dynticks patches, frankly.  We had a
lot of discussion and review of the original patchset and it almost all
seemed OK apart from this tsc-goes-silly problem.  But then this lot:

highres-timer-core-fix-status-check.patch
highres-timer-core-fix-commandline-setup.patch
clockevents-smp-on-up-features.patch
highres-depend-on-clockevents.patch
i386-apic-cleanup.patch
pm-timer-allow-early-access.patch
i386-lapic-timer-calibration.patch
clockevents-add-broadcast-support.patch
clockevents-add-broadcast-support-fix.patch
acpi-include-apic-h.patch
acpi-include-apic-h-fix.patch
acpi-keep-track-of-timer-broadcast.patch
i386-apic-timer-use-clockevents-broadcast.patch
acpi-verify-lapic-timer.patch
acpi-verify-lapic-timer-exports.patch
acpi-verify-lapic-timer-fix.patch

got merged and I haven't looked at any of that and I don't know that anyone
else has and I don't even know if anyone knows what's in there.

But I do know that it fiddles with APICs, and they are quick to anger.  I
have little confidence in merging all of that material.

I'll retain it all for a while so that we can continue to try to fix this
APIC problem but if/when we get that done I think it's time to drop all of
it and start again, because APIC changes really do need a lot of careful
review and thought.

<cycles the power>

No, it's no good at all.  This time it just went back to its old ways of
taking a month to get through initscripts.

  reply	other threads:[~2006-11-08  7:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 16:05 teunis
2006-10-20  2:41 ` Andrew Morton
2006-10-20 16:30   ` teunis
2006-10-20 18:07     ` Andrew Morton
2006-10-20 18:13       ` Thomas Gleixner
2006-10-20 18:26         ` Andrew Morton
2006-10-20 18:37           ` Thomas Gleixner
2006-10-20 18:46           ` Thomas Gleixner
2006-10-20 19:15             ` Andrew Morton
2006-10-20 20:37               ` Ingo Molnar
2006-10-20 20:54                 ` Andrew Morton
2006-10-20 20:56                   ` Ingo Molnar
2006-10-21  1:25                     ` Andrew Morton
2006-10-21  9:49                       ` Thomas Gleixner
2006-10-22 21:22                         ` Thomas Gleixner
2006-11-08  7:19                           ` Andrew Morton [this message]
2006-11-08 22:28                             ` Thomas Gleixner
2006-10-21 14:52           ` Arjan van de Ven
2006-10-20 19:13       ` Dmitry Torokhov
2006-10-20 22:26         ` teunis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061107231903.99156678.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dtor@mail.ru \
    --cc=johnstul@us.ibm.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=teunis@wintersgift.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®