Loading ...
Sorry, an error occurred while loading the content.

9710Re: Help with OpenSlug-OpenDebian

Expand Messages
  • jack_2006b
    Oct 30, 2005
    • 0 Attachment
      Thanks for the info, but I new with OpenDebian, maybe is a simple
      answer, but where is the Kernel Command line where I need to write
      the noirqdebug? Sorry.

      Thanks with any help

      --- In nslu2-linux@yahoogroups.com, John Bowler <jbowler@a...> wrote:
      > From: jack_2006b
      > >Oct 29 09:56:49 localhost kernel: irq26: nobody cared
      > I can't remember how these things get output in the log but I
      think the
      > traceback corresponds to the kernel warning at the end (i.e. the
      > I quoted above.)
      > Try running without IRQ debugging (i.e. with noirqdebug on the
      > command line). IRQ debugging is useful when there are problems,
      but if
      > there aren't any you are likely to see spurious warnings. Here's
      > explanation from l-a-k:
      > From: linux-arm-kernel-bounces@l... On Behalf Of
      > Russell King - ARM Linux
      > Sent: Monday, October 24, 2005 3:30 PM
      > Subject: Re: ide0: unexpected interrupt (pxa255 and at91)
      > >On Mon, Oct 24, 2005 at 05:16:38PM -0500, Bill Gatliff wrote:
      > >> I have two different boards, one pxa255 and one at91rm9200,
      both of
      > >> which have nonremovable CF ATA cards. Same 2.6.12 kernel runs
      on each
      > >> (a few different config settings, obviously).
      > >
      > >At a guess, you're seeing the classic problems if hooking an
      > >output which is designed for level-based signalling to an edge-
      > >input.
      > >
      > >You have two options:
      > >1. Drop interrupts and risk devices stopping working afterwards.
      > >2. Gain extra spurious interrupts which the driver may ignore.
      > >
      > >We opt for (2) because that's the more reliable option - at the
      > >expense of occasionally creating unexpected interrupts. The IDE
      > >subsystem is unfortunately particularly noisy when it comes to
      > >these.
      > I don't know whether this applies to the USB on the NSLU2 PCI
      > controller, but that irq26 is the IRQ from the USB which is on
      > the PCI bus and it is a spurious interrupt so far as we have
      > ever been able to see.
      > John Bowler <jbowler@a...>
    • Show all 6 messages in this topic