From: Shane <gnome42@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: WTF does -rc mean? was [PATCH] x86, tsc: fix section mismatch warning
Date: Sun, 17 Aug 2008 23:03:23 -0400 [thread overview]
Message-ID: <fa4052ef0808172003r48863a4fu90c0647eef736571@mail.gmail.com> (raw)
Adrian Bunk wrote ....
|On Sun, Aug 10, 2008 at 10:07:31PM -0700, H. Peter Anvin wrote:
|> Thanks!
|>
|> I have pulled these four patches into tip:x86/cleanups.
|
|Section fixes are not cleanups but bugfixes.
|
|E.g. this patch by Marcin fixes the following 2.6.27 regression
|(that was found 4 days after you applied his patch):
|http://bugzilla.kernel.org/show_bug.cgi?id=11330
|
|Can you make sure that Marcin's bugfixes makes it into 2.6.27?
|
|> -hpa
|
|TIA
|Adrian
------------------------------------------------------------------------------------------------------
This bug was causing my system to hang during boot at "Setting the
system Clock".
This was completely stopping me from testing the -rc3 kernel. I only tried this
patch on a hunch (tsc == clock :), I'm on intel hardware.
[ To: Adrian Bunk, Mark Lord (and other people with similar attitudes/ethics)
thanks for fixing and tracking everyone elses bugs for us lusers. And
the following
hopefully scorching flame is not meant for you guys. ]
This is the third** -rc cycle where I have composed what is meant to
be a scorching
email to the kernel list about the mind blowing decline in -rc kernel
developer attitude.
I didn't send the other two but I just spent another two flippin'
hours booting and
fsck'in. And I am very cranky (to put it politely) because the
bleep'n problem is known
and the fix has been available for at least 7 days!!
I of course understand that there will be bugs in the -rc kernels,
that is why I bother putting
the time and energy into testing them. It is mainly the lackadaisical
attitude about getting
the fixes in that is a mind blower.
I am a (fairly long time) tester/luser of the kernel. I do it for fun
and to learn.
It isn't fun anymore.
** A couple examples of what I'm talking about:
http://www.gossamer-threads.com/lists/linux/kernel/852762#852762
http://www.gossamer-threads.com/lists/linux/kernel/853094#853094
This one is my least favourite. That r8169 bug required me to unplug
my box overnight
just to get back on the network. I foolishly thought that a bug like
that on such a popular
piece of hardware would not be allowed to persist in mainline for
long, so I foolishly
updated my kernel a few times (waiting days in between) and my box was basically
bricked overnight each time!! :((
The maintainer's attitude makes me want to chisel that chip right off my board.
Thanks again to Mark Lord!
http://www.gossamer-threads.com/lists/linux/kernel/841017#841017
Andrew was my hero on this one. Thanks Andrew!
http://www.gossamer-threads.com/lists/linux/kernel/852734#852734
( I doubt I have anything else useful to say about this so I likely
won't be posting
again to this thread )
Shane
next reply other threads:[~2008-08-18 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 3:03 Shane [this message]
2008-08-18 5:30 ` Nick Piggin
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=fa4052ef0808172003r48863a4fu90c0647eef736571@mail.gmail.com \
--to=gnome42@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®