# [OmniOS-discuss] [discuss] Re: [networking] rge_intr troubles

Saso Kiselkov skiselkov.ml at gmail.com
Sat Oct 1 22:13:06 UTC 2016

- Previous message: [OmniOS-discuss] [discuss] Re: [networking] rge_intr troubles
- Next message: [OmniOS-discuss] [discuss] Re: [networking] rge_intr troubles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On 10/1/16 11:45 PM, Dale Ghent wrote:
    >
    >> On Oct 1, 2016, at 3:36 PM, Saso Kiselkov <skiselkov.ml at gmail.com> wrote:
    >>
    >> So I'm playing around with a box that has an on-board Realtek NIC and
    >> periodically, about once every 2-5 minutes, the network just goes out to
    >> lunch and stops responding to ping or attempts to send anything from
    >> the box. I noticed that while doing so, the box is getting floored by
    >> interrupts from the NIC, so I see tons of rge_intr activity and one CPU
    >> core receiving about 160000 interrupts per second (other cores are idle).
    >
    > One core getting all the interrupts is expected, as both these chips and the driver do not support RSS.
    >
    > The key thing here is to see what rge_intr() is actually doing. It has 2 outcomes: It identifies the interrupt type, processes it, then returns to the DDI that it was claimed. IF it doesn't identify the interrupt, rge_intr() returns and reports unclaimed to the DDI.
    >
    > Knowing this info would be a good first step in figuring out what's going on.

    It's a whole buttload of RT_93c46_COMMOND_REG (0x50) interrupts.

    --
    Saso

- Previous message: [OmniOS-discuss] [discuss] Re: [networking] rge_intr troubles
- Next message: [OmniOS-discuss] [discuss] Re: [networking] rge_intr troubles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list