linux-traipu team mailing list archive

[Edward Donovan <855199@xxxxxxxxxxxxxxxxxx>]

** No longer affects: mythbuntu

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/855199

Title:
  "irqfixup" and "irqpoll" broken since 2.6.39

Status in The Linux Kernel:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Oneiric:
  Fix Released
Status in “linux” source package in Precise:
  Fix Released

Bug description:
  In all kernels since 2.6.39, the "irqfixup" and "irqpoll" options are
  no longer taking effect.

  The interrupts now generate the same errors seen without these kernel
  options, e.g.:

    irq 19: nobody cared (try booting with the "irqpoll" option)

  even though irqpoll, or irqfixup, is used.

  The Linux irq code was reworked during the 2.6.39 cycle.  I have gone
  through the patches, isolated two regressions, and submitted patches
  for each.

  The first bug effectively disabled the bad-irq handling routines, by a
  test condition be accidentally reversed.  This is the commit where the
  regression arrives:

    commit d05c65fff0 , genirq: spurious: Run only one poller at a time

  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=d05c65fff0ef672be75429266751f0e015b54d94

  The maintainer has accepted my patch for that, and it's on its way
  into releases: it will be in Linux 3.2, and upcoming stable releases,
  likely 3.0.11 and 3.1.3.  And it's marked as committed to Oneirc now.
  It's attached here, and is in Linus' tree at:

  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=c75d720fca8a91ce99196d33adea383621027bf2

  That bug disabled irqfixup & irqpoll for everybody.  But with that
  fixed, I had some machines where those kernel options still failed.  I
  bisected that problem to here:

    commit fa27271bc , genirq: Fixup poll handling

  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=fa27271bc8d230355c1f24ddea103824fdc12de6

  I've submitted another patch, for that regression, and Linus merged
  it.  Yay.  So 3.2 should be good, and 3.0/3.1 updates in a bit -- it
  took a month, last time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/855199/+subscriptions