public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Witbrodt <dawitbro@sbcglobal.net>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression
Date: Sun, 24 Aug 2008 06:05:04 -0700 (PDT)	[thread overview]
Message-ID: <751256.282.qm@web82108.mail.mud.yahoo.com> (raw)



> > - Is there any chance I can get it into the stable 2.6.26.X updates?
> > (Who should I ask, or are only developers allowed to lobby for this
> > sort of thing?)
> 
> after the patch get into linus tree. Greg will put the patch into 2.6.26.X

OK, thanks a bunch.


> > - Are you worried about the potential problems of a quirk-based approach?
> > What if many more people experience a similar regression once 2.6.26 or
> > later appears in their distribution?  I'm sure you don't want to have to
> > write a different quirk for each individual's hardware, and this problem
> > did not arise with the approach used for resource management in 2.6.25.
> 
> this patch should be safe.
> 
> 2.6.26 is fixing one bug about reserving local apic address and that
> in e820 table.
> and it reveals one bios bug.

Correction -- it revealed at least two.  See the link I posted earlier in
this thread:

http://www.uwsg.indiana.edu/hypermail/linux/kernel/0808.2/1807.html

Scroll down to the line that starts with "[blog]" for the link. You can see
the discussion I had encouraging him to come here to help us troubleshoot 
if you go to that blog and click "Comments".

I only mention this as a warning, in case it could lead to a lot of extra 
problems for you later.  If you're quite sure that everything is OK, then 
all I can do is thank you again and keep my fingers crossed for you and the
kernel team that nothing bad happens when 2.6.2[67] hit the major distros.

Thanks Yinghai and Ingo (and Peter, Paul, Bill, Mike, Ilpo, Frans, Jesse...
and Andrew, for being the only one to tell me my ISP webmail client was 
breaking threading in everyone's inbox!)


Now leaving LKML...
Dave Witbrodt

             reply	other threads:[~2008-08-24 13:05 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 13:05 David Witbrodt [this message]
2008-08-24 19:29 ` HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression Yinghai Lu
2008-08-24 22:48   ` Yinghai Lu
  -- strict thread matches above, loose matches on Subject: below --
2008-08-26 15:25 David Witbrodt
2008-08-26 12:58 David Witbrodt
2008-08-26 13:28 ` Ingo Molnar
2008-08-25 13:39 David Witbrodt
2008-08-25 17:24 ` Yinghai Lu
2008-08-25 17:28 ` Yinghai Lu
2008-08-25  3:06 David Witbrodt
2008-08-25  2:00 David Witbrodt
2008-08-25  2:37 ` Yinghai Lu
2008-08-25  4:41 ` Yinghai Lu
2008-08-25  6:27   ` Ingo Molnar
2008-08-25  6:40     ` Yinghai Lu
2008-08-25  7:31   ` Ingo Molnar
2008-08-25  8:00     ` Yinghai Lu
2008-08-27 22:41       ` Jesse Barnes
2008-08-27 23:23         ` Yinghai Lu
2008-08-27 23:42           ` Jesse Barnes
2008-08-24  2:39 David Witbrodt
2008-08-24  3:44 ` Yinghai Lu
2008-08-23 23:42 David Witbrodt
2008-08-24  2:05 ` Yinghai Lu
2008-08-23 19:47 David Witbrodt
2008-08-23 20:12 ` Yinghai Lu
2008-08-23 20:51 ` Yinghai Lu
2008-08-23 19:29 David Witbrodt
2008-08-23 18:26 Rufus & Azrael
2008-08-23 19:17 ` Yinghai Lu
2008-08-23 19:40   ` Rufus & Azrael
2008-08-23 20:10     ` Yinghai Lu
2008-08-23 20:15       ` Rufus & Azrael
2008-08-23 20:28         ` Yinghai Lu
2008-08-23 20:33           ` Rufus & Azrael
2008-08-23 20:35             ` Yinghai Lu
2008-08-23 20:36               ` Rufus & Azrael
2008-08-23 20:45                 ` Yinghai Lu
2008-08-23 21:05                   ` Yinghai Lu
2008-08-28 22:52                     ` Jordan Crouse
2008-09-12 17:39                     ` Andreas Herrmann
2008-09-12 17:45                       ` Jordan Crouse
2008-09-14 16:25                         ` Ingo Molnar
2008-08-23 16:44 David Witbrodt
2008-08-23 16:32 David Witbrodt
2008-08-23 15:42 David Witbrodt
2008-08-23 15:55 ` Ingo Molnar
2008-08-23 11:58 David Witbrodt
2008-08-23 13:36 ` Ingo Molnar
2008-08-23 15:03   ` Ingo Molnar
2008-08-23 17:51 ` Yinghai Lu
2008-08-23 11:42 David Witbrodt
2008-08-23  2:25 David Witbrodt
2008-08-23  5:41 ` Yinghai Lu
2008-08-23  6:56   ` Yinghai Lu
2008-08-22  1:24 David Witbrodt
2008-08-21 16:53 David Witbrodt
2008-08-21 17:57 ` Yinghai Lu
2008-08-21 14:09 David Witbrodt
2008-08-21 15:33 ` Yinghai Lu
2008-08-21 13:33 David Witbrodt
2008-08-21  4:07 David Witbrodt
2008-08-21  6:42 ` Yinghai Lu
2008-08-21  7:04 ` Ilpo Järvinen
2008-08-21  2:48 David Witbrodt
2008-08-20 17:42 David Witbrodt
2008-08-20 17:58 ` Yinghai Lu
2008-08-21  2:02   ` Yinghai Lu
2008-08-20 16:44 David Witbrodt
2008-08-20 14:32 David Witbrodt
2008-08-20 14:49 ` Ingo Molnar
2008-08-20 14:08 David Witbrodt
2008-08-20  4:51 David Witbrodt
2008-08-20  5:21 ` Yinghai Lu
2008-08-20  7:51   ` Bill Fink
2008-08-20  8:02     ` Yinghai Lu
2008-08-20  9:15       ` Ingo Molnar
2008-08-20  9:31         ` Yinghai Lu
2008-08-20  9:36           ` Ingo Molnar

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=751256.282.qm@web82108.mail.mud.yahoo.com \
    --to=dawitbro@sbcglobal.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yhlu.kernel@gmail.com \
    /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