netdev - Re: sblk->status_tag on drivers/net/ethernet/broadcom/tg3.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1393992738.4632.15.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
Date:	Tue, 4 Mar 2014 20:12:18 -0800
From:	Michael Chan <mchan@...adcom.com>
To:	Jagan Teki <jagannadh.teki@...il.com>
CC:	<netdev@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Nithin Nayak Sujir <nsujir@...adcom.com>,
	Grant Likely <grant.likely@...aro.org>,
	Rob Herring <robh+dt@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: sblk->status_tag on drivers/net/ethernet/broadcom/tg3.c

On Wed, 2014-03-05 at 09:33 +0530, Jagan Teki wrote:
> The driver is not seeing the status block mean - tg3.c driver?

Yes, tg3 driver.  All IRQ events (link change, rx, tx) are in status
block.  If tg3 does not see the correct bits and indexes in the status
block, it won't know what to do.  In this case, it doesn't see the link
change bit in status block (I suspect), so it is not acknowledging and
clearing the link change event.  Status block is DMA'ed from the NIC to
memory.

> Does it relates to ISR or addressing of PCIe RC driver, I'm doing
> nothing on my PCIe RC driver just read the legacy INT# status and
> return.

RC stands for what?  Root Complex?  I don't know what an RC driver does.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html