Second that. Daily panics using a Tyan board w/ BCM5704. Unfortunately
unable to provide crash dump and I was forced to use a different NIC. But
for what its worth here is the relevant pciconf -lv output.
b...@pci0:2:9:0: class=0x02 card=0x164814e4 chip=0x164814e4 rev=0x03
hdr=0x00
vendor
Broadcom 5714 5715 - no problems.
2010/2/22 Denis Lamanov :
> Yes, PCIX BCM5704
> FreeBSD vpn2 8.0-STABLE FreeBSD 8.0-STABLE #1 r204028: Thu Feb 18 08:29:42
> EET 2010 ad...@vpn2:/usr/obj/usr/src/sys/GENERIC i386
>
> 2010/2/22 Pyun YongHyeon
>
>> On Mon, Feb 22, 2010 at 03:17:17PM +0200, Den
Hi Pyun,
On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
> Since I don't have BCM5704 hardware it's hard to find which
> revision may affect to this issue. Could you narrow down which
> revision number started showing the issue?
I have BCM5704 hardware (Tyan S2882 system board). I
Yes, PCIX BCM5704
FreeBSD vpn2 8.0-STABLE FreeBSD 8.0-STABLE #1 r204028: Thu Feb 18 08:29:42
EET 2010 ad...@vpn2:/usr/obj/usr/src/sys/GENERIC i386
2010/2/22 Pyun YongHyeon
> On Mon, Feb 22, 2010 at 03:17:17PM +0200, Denis Lamanov wrote:
> > I see same trouble (lost packets after 4 day uptim
On Mon, Feb 22, 2010 at 03:17:17PM +0200, Denis Lamanov wrote:
> I see same trouble (lost packets after 4 day uptime and reboot) :(
>
> dev.bge.0.stats.rx.FCSErrors: 18
>
You also have PCIX BCM5704 controller? What FreeBSD version do you
use?
> 2010/2/19 Slawa Olhovchenkov
>
> > On Fri, Feb 1
On Mon, Feb 22, 2010 at 10:18:47AM +0300, Slawa Olhovchenkov wrote:
> On Sun, Feb 21, 2010 at 03:41:53PM -0800, Pyun YongHyeon wrote:
>
> > On Sun, Feb 21, 2010 at 12:44:50AM +0300, Slawa Olhovchenkov wrote:
> > > On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
> > >
> > > > Norm
vpn2# sysctl dev.bge.0.stats
dev.bge.0.stats.FramesDroppedDueToFilters: 0
dev.bge.0.stats.DmaWriteQueueFull: 0
dev.bge.0.stats.DmaWriteHighPriQueueFull: 0
dev.bge.0.stats.NoMoreRxBDs: 0
dev.bge.0.stats.InputDiscards: 0
dev.bge.0.stats.InputErrors: 0
dev.bge.0.stats.RecvThresholdHit: 36622
dev.bge.0
I see same trouble (lost packets after 4 day uptime and reboot) :(
dev.bge.0.stats.rx.FCSErrors: 18
2010/2/19 Slawa Olhovchenkov
> On Fri, Feb 19, 2010 at 12:06:47PM -0800, Pyun YongHyeon wrote:
>
> >
> > > dev.bge.1.stats.rx.Fragments: 1
> >
> > You received a frame that is less than 64 bytes
On Sun, Feb 21, 2010 at 03:41:53PM -0800, Pyun YongHyeon wrote:
> On Sun, Feb 21, 2010 at 12:44:50AM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
> >
> > > Normally you should not have any FCS errors, it could be related
> > > with signal qu
On Sun, Feb 21, 2010 at 12:44:50AM +0300, Slawa Olhovchenkov wrote:
> On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
>
> > Normally you should not have any FCS errors, it could be related
> > with signal quality and these errors might not be correctly
> > counted.
>
> I can't che
On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
> Normally you should not have any FCS errors, it could be related
> with signal quality and these errors might not be correctly
> counted.
I can't check cable and switch counters on bge1 before Feb 24.
> > 3. packets don't lost on
On Fri, Feb 19, 2010 at 11:13:59PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Feb 19, 2010 at 12:06:47PM -0800, Pyun YongHyeon wrote:
>
> >
> > > dev.bge.1.stats.rx.Fragments: 1
> >
> > You received a frame that is less than 64 bytes with a bad FCS.
> >
> > > dev.bge.1.stats.rx.UcastPkts: 29565
On Fri, Feb 19, 2010 at 12:06:47PM -0800, Pyun YongHyeon wrote:
>
> > dev.bge.1.stats.rx.Fragments: 1
>
> You received a frame that is less than 64 bytes with a bad FCS.
>
> > dev.bge.1.stats.rx.UcastPkts: 2956515
> > dev.bge.1.stats.rx.MulticastPkts: 0
> > dev.bge.1.stats.rx.FCSErrors: 18
>
>
On Fri, Feb 19, 2010 at 10:11:03PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Feb 19, 2010 at 11:03:59AM -0800, Pyun YongHyeon wrote:
>
> > On Fri, Feb 19, 2010 at 03:24:15PM +0300, Slawa Olhovchenkov wrote:
> > > On Fri, Feb 19, 2010 at 08:51:29AM +0300, Slawa Olhovchenkov wrote:
> > >
> > > > O
On Fri, Feb 19, 2010 at 11:03:59AM -0800, Pyun YongHyeon wrote:
> On Fri, Feb 19, 2010 at 03:24:15PM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Feb 19, 2010 at 08:51:29AM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Thu, Feb 18, 2010 at 04:19:13PM -0800, Pyun YongHyeon wrote:
> > >
> > > >
>
On Fri, Feb 19, 2010 at 03:24:15PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Feb 19, 2010 at 08:51:29AM +0300, Slawa Olhovchenkov wrote:
>
> > On Thu, Feb 18, 2010 at 04:19:13PM -0800, Pyun YongHyeon wrote:
> >
> > >
> > > I'm still not sure whether the panic is related with bge(4) but
> > > th
On Fri, Feb 19, 2010 at 08:51:29AM +0300, Slawa Olhovchenkov wrote:
> On Thu, Feb 18, 2010 at 04:19:13PM -0800, Pyun YongHyeon wrote:
>
> >
> > I'm still not sure whether the panic is related with bge(4) but
> > there are a couple of missing workaround for PCIX BCM5704 silicon
> > bug in bge(4).
On Thu, Feb 18, 2010 at 04:19:13PM -0800, Pyun YongHyeon wrote:
>
> I'm still not sure whether the panic is related with bge(4) but
> there are a couple of missing workaround for PCIX BCM5704 silicon
> bug in bge(4). Did you also see the panic before updating to
> stable/8?
Before updating to st
On Thu, Feb 18, 2010 at 03:32:54PM -0800, Jeremy Chadwick wrote:
> On Fri, Feb 19, 2010 at 12:50:39AM +0300, Slawa Olhovchenkov wrote:
> > On Thu, Feb 18, 2010 at 01:32:13PM -0800, Pyun YongHyeon wrote:
> >
> > > > > dmesg output(only bge(4) related one).
> > > >
> > > > dmesg from boot:
> > > >
On Fri, Feb 19, 2010 at 12:50:39AM +0300, Slawa Olhovchenkov wrote:
> On Thu, Feb 18, 2010 at 01:32:13PM -0800, Pyun YongHyeon wrote:
>
> > > > dmesg output(only bge(4) related one).
> > >
> > > dmesg from boot:
> > >
> > > bge0: mem
> > > 0xfdf7-0xfdf7 irq 25 at device 2.0 on pci2
> >
On Fri, Feb 19, 2010 at 12:50:39AM +0300, Slawa Olhovchenkov wrote:
> On Thu, Feb 18, 2010 at 01:32:13PM -0800, Pyun YongHyeon wrote:
>
> > > > dmesg output(only bge(4) related one).
> > >
> > > dmesg from boot:
> > >
> > > bge0: mem
> > > 0xfdf7-0xfdf7 irq 25 at device 2.0 on pci2
> >
On Thu, Feb 18, 2010 at 01:32:13PM -0800, Pyun YongHyeon wrote:
> > > dmesg output(only bge(4) related one).
> >
> > dmesg from boot:
> >
> > bge0: mem
> > 0xfdf7-0xfdf7 irq 25 at device 2.0 on pci2
> > miibus0: on bge0
> > brgphy0: PHY 1 on miibus0
> > brgphy0: 10baseT, 10baseT-FDX
On Fri, Feb 19, 2010 at 12:24:28AM +0300, Slawa Olhovchenkov wrote:
> On Thu, Feb 18, 2010 at 11:36:12AM -0800, Pyun YongHyeon wrote:
>
> > On Thu, Feb 18, 2010 at 05:38:22PM +0300, Slawa Olhovchenkov wrote:
> > > On Tue, Feb 16, 2010 at 09:57:19AM -0800, Pyun YongHyeon wrote:
> > >
> > > > On Su
On Thu, Feb 18, 2010 at 11:36:12AM -0800, Pyun YongHyeon wrote:
> On Thu, Feb 18, 2010 at 05:38:22PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Feb 16, 2010 at 09:57:19AM -0800, Pyun YongHyeon wrote:
> >
> > > On Sun, Feb 14, 2010 at 10:04:58AM -0800, Nick Rogers wrote:
> > > > I'm having repea
On Thu, Feb 18, 2010 at 05:38:22PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Feb 16, 2010 at 09:57:19AM -0800, Pyun YongHyeon wrote:
>
> > On Sun, Feb 14, 2010 at 10:04:58AM -0800, Nick Rogers wrote:
> > > I'm having repeated kernel panic issues on 8.0-RELEASE/amd64. Can anyone
> > > shed light o
On Tue, Feb 16, 2010 at 09:57:19AM -0800, Pyun YongHyeon wrote:
> On Sun, Feb 14, 2010 at 10:04:58AM -0800, Nick Rogers wrote:
> > I'm having repeated kernel panic issues on 8.0-RELEASE/amd64. Can anyone
> > shed light on the below error? I unfortunately cannot provide a proper crash
> > dump. The
On Sun, Feb 14, 2010 at 10:04:58AM -0800, Nick Rogers wrote:
> I'm having repeated kernel panic issues on 8.0-RELEASE/amd64. Can anyone
> shed light on the below error? I unfortunately cannot provide a proper crash
> dump. The pointer addresses are always the same. The only other thing I've
> notic
hw.bge.allow_asf: 0
On Mon, Feb 15, 2010 at 2:23 AM, Giacomo Olgeni wrote:
>
> Hello,
>
> Are you running with hw.bge.allow_asf enabled?
>
>
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
I'm having repeated kernel panic issues on 8.0-RELEASE/amd64. Can anyone
shed light on the below error? I unfortunately cannot provide a proper crash
dump. The pointer addresses are always the same. The only other thing I've
noticed that may be related is a watchdog timeout on bge0 error before the
29 matches
Mail list logo
