2

Possible Duplicate:
Given a git patch id, how to find out which kernel release contains it?

I encountered a bug in one of the newer kernel versions. There is no workaround; if I want to have sound at my system at all, I have to boot an older kernel version. Since this is a home computer I use for video and music, I need the sound and haven't updated the kernel since 3.5.4-2, not wanting to overwrite the version which still works.

There already is a fix which repairs the problem. But I don't know when it will be included in a kernel update. How do I find out which kernel version will contain the fix? I don't want to update until this version comes out.

Community
  • 1
rumtscho
  • 249
  • 5
  • 18
  • As a general rule, it is not a particularly good idea to update your kernel _very_ often. 3.5.4-2 is a very recent kernel (less than two months old), unless there is a specific functionality in one of the new ones, I would stick with it until a major update comes out. – terdon Oct 09 '12 at 15:48
  • @terdon I have Fedora, it automatically pushes out the most recent kernels in the stable version. Right now, I have 3.5.5-2 sitting in yum, urging me to install it. – rumtscho Oct 09 '12 at 15:50
  • Ignore it. As I said, upgrading your kernel with no specific reason is a recipe for the kind of problems you are experiencing. Just add this to `/etc/yum.conf`: `exclude=kernel*`. Then, in a few months, if you feel you should update your kernel, do so manually. Just remember the golden rule: [IIABDFI](http://acronyms.thefreedictionary.com/IIABDFI). On my debian system I am perfectly happy with my 3.2.0-3 kernel and I don't think I'll update unless something really worthwhile comes around. – terdon Oct 09 '12 at 15:56
  • @terdon. Nothing wrong with your explanation, but the link to IIABDFI is terrible :). It took me time to find the relevant text inside all those ads –  Oct 09 '12 at 17:05
  • @FrancescoTurco, crap, you're quite right, sorry. I just took the 1st google hit. – terdon Oct 09 '12 at 17:07
  • @terdon: That is **incredibly** bad advice. The stable kernels address security and data-loss problems. See, for example, the [release announcement](https://lwn.net/Articles/518342/) for 3.5.5: "All users of the 3.5 kernel series must upgrade." Telling users to `exclude=kernel*` is like telling a Windows user to disable automatic updates. – Jim Paris Oct 09 '12 at 18:32
  • @terdon: Also, you say "On my debian system I am perfectly happy with my 3.2.0-3 kernel". Debian's 3.2.0-3 is based on upstream 3.2.21, which is outdated, but **still** only 3.5 months old. – Jim Paris Oct 09 '12 at 18:35
  • @terdon, @rumtscho: Finally, in this specific case: the patch in question **was** included in 3.5.5, so you should stop ignoring `yum` and just install it already. It will fix your problem. – Jim Paris Oct 09 '12 at 18:37
  • @JimParis, I am not saying one should never update the kernel. The OP specifically does not want to, so disabling yum's automatic notification is a perfectly good short-term solution. – terdon Oct 10 '12 at 09:35

1 Answers1

0

Duplicate of Given a git patch id, how to find out which kernel release contains it?

In short: from your "fix" link, click "commitdiff" at the top, click "raw", and look at the X-Git-Tag header.

Community
  • 1
Jim Paris
  • 14,137
  • 5
  • 36
  • 35