Re: SIO Interrupt storms and unhandled interrupts

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 09/10/04

  • Next message: Stefan Eßer: "Re: PANIC: sym(4) didn't MODULE_DEPEND cam(4)." 
    To: "M. Warner Losh" <imp@bsdimp.com>
Date: Fri, 10 Sep 2004 14:07:11 -0400

    On Thursday 09 September 2004 05:41 pm, M. Warner Losh wrote:
    > In message: <6.1.2.0.0.20040909154407.08b1a9f8@64.7.153.2>
    >
    > Mike Tancsa <mike@sentex.net> writes:
    > : Thanks for the response! We found a different solution /
    > : approach which seems to work on both RELENG_4 and RELENG_5. The problem
    > : is that the modem is not being seen as a PCI / PUC device and instead is
    > : being seen as an ISA SIO device ?? The following RELENG_5 and RELENG_4
    > : patches seem to fix the problem. I wonder if the other modems listed in
    > : sio.c suffer the same fate ?
    > :
    > : Also fixed in this are those "cant re-use leafs" at bootup time. The
    > : modem is seen as a PUC device now.... At the bottom is a diff between
    > : the boot -v
    >
    > I like this fix! I'll see if I can find to commit it.

    Note that hacking sio to not use INTR_FAST would have had the same result.
    Note that in his dmesg diff, sio4 has to fall back to normal interrupt mode. 

    -- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Stefan Eßer: "Re: PANIC: sym(4) didn't MODULE_DEPEND cam(4)."

    Relevant Pages

    • [ANNOUNCE] Stacked GIT 0.13
      ... operations are performed using GIT commands and the patches are stored ... Safety checks for the 'rebase' command ... already modified by the current patch ... Fix bash completion to not garble the screen with an error message. ...
      (Linux-Kernel)
    • 2.6.21-mm2
      ... A handful of IDE patches were dropped due to compilation failures. ... See the `hot-fixes' directory for any important updates to this patchset. ... If you hit a bug in -mm and it is not obvious which patch caused it, ... sunrpc fix ...
      (Linux-Kernel)
    • 2.6.17-mm4
      ... The RAID patches have been dropped due to testing failures in -mm3. ... The SCSI Attached Storage tree has been restored. ... See the `hot-fixes' directory for any important updates to this patchset. ... Fix reject due to git-agpgart.patch. ...
      (Linux-Kernel)
    • Re: Q824143 -- how to get patch?!?
      ... There are 2 sorts of patches. ... client or clients that are have an issue. ... They are available from product support if the engineer while working with ... the client identifies that this fix will fix the specific problem the client ...
      (microsoft.public.security)
    • Re: [BUG] sched: big numa dynamic sched domain memory corruption
      ... fix group power for allnodes_domains ... Is the first of the above three patches the one needed to fix the "big ... This patch in turn seems to have some important fixes and followups ... Which of the following would you recommend I advise SUSE do for SLES10: ...
      (Linux-Kernel)