Re: PCI SIO devices hog interrupts, cause lock order problems

From: Drew Derbyshire (ahd_at_kew.com)
Date: 08/30/04

  • Next message: bettan: "Re: 5.3 beta2 bridging" 
    To: freebsd-current@freebsd.org
Date: Mon, 30 Aug 2004 15:23:16 -0400 (EDT)

    > From imp@bsdimp.com Mon Aug 30 14:50:50 2004
    > : Basically, any PCI SIO device hogs its interrupt if the PUC device is not
    > : also in the kernel, and this causes real problems for any environment like
    > : mine where pulling the modem is not trivial. Does the distributed GENERIC
    > : kernel have room for the PUC device? Are there side effects that PUC should
    > : be excluded from GENERIC?
    >
    > puc should be in GENERIC, imho.

    Who makes the call (or the commit)? The cost is ~ 55K on disk
    (which seems excessive) with current build, I assume that's bloated
    by the current kernel options.

    > : As a bonus, there appears to be a bug with kernel locking exposed by the
    > : problem. With the stock generic kernel, the XL device reports it couldn't
    > : map the interrupt, and then a lock order reversal is reported. (See the
    > : attached log for the gory details).
    >
    > This is a known problem.

    Well, it at least it didn't panic on me, which previous experiments
    (months ago) were prone to do.

    -ahd-

    p.s. Sorry about the original mail being ugly MS HTML. I needed the MIME, not the HTML.
    _______________________________________________
    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: bettan: "Re: 5.3 beta2 bridging"

    Relevant Pages