On 10/28/2010 9:42 AM, Brad du Plessis wrote:
Hi,
I've been seeing panics on a netbsd-4/i386 machine which appears to be
related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
I've narrowed down the problem here to a specific change.
Basically with netbsd-
Hi,
I've been seeing panics on a netbsd-4/i386 machine which appears to be
related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
I've narrowed down the problem here to a specific change.
Basically with netbsd-4 branch I see the failure, but if I revert
only
>> I've got 3 motherboards with re onboard that I've tested, 2 of the 3
>> have the problem. I checked the re hwrev and the one that works
>> fine is 0x2800. The 2 boards that don't work have hwrev
>> 0x3800 and 0x3C40.
> I'll have a look at the code and see if I can find the hwrev va
On 7/26/2010 8:50 AM, der Mouse wrote:
I don't see anything there that looks like the rev numbers you're
talking about. While now is not a good time, I'll have a look at the
code and see if I can find the hwrev value you're talking about and
print out its value for my hardware.
I manually pr
>> Actually, my main reason for writing is to mention that I have a
>> laptop, running 4.0.1, with an re onboard, and have never seen such
>> random crashes. I can give more details if they matter.
> I've got 3 motherboards with re onboard that I've tested, 2 of the 3
> have the problem. I checke
On 7/23/2010 12:54 PM, der Mouse wrote:
Well, use machines whose designers cut corners on hardware design and
guess what happens.
Actually, my main reason for writing is to mention that I have a
laptop, running 4.0.1, with an re onboard, and have never seen such
random crashes. I can give mor
On Fri, Jul 23, 2010 at 12:12:24PM +0200, Manuel Bouyer wrote:
> On Wed, Jul 21, 2010 at 02:06:11PM +0200, Brad du Plessis wrote:
> > I've managed to reproduce this now in netbsd-5 too (source is about
> > 3 months old, not sure if there have been any changes since):
> >
> > re0: discarding oversi
On 7/21/2010 3:17 PM, Izumi Tsutsui wrote:
I'm afraid it's memory corruption caused by hardware or PCI BIOS problem.
What happens if you change
>cfg = RE_CPLUSCMD_PCI_MRW;
to
>cfg = 0;
in re_init()? Or can you have newer BIOS for your hardware?
I've tried t
> is it possible that the re device is writting past its buffer (via
> DMA) and overwriting random memory ?
Isn't that one thing the iommu is for? Oh, wait
Well, use machines whose designers cut corners on hardware design and
guess what happens.
Actually, my main reason for writing is to me
On Wed, Jul 21, 2010 at 02:06:11PM +0200, Brad du Plessis wrote:
> I've managed to reproduce this now in netbsd-5 too (source is about
> 3 months old, not sure if there have been any changes since):
>
> re0: discarding oversize frame (len=9041)
> re0: discarding oversize frame (len=16158)
> panic:
On 7/21/2010 2:06 PM, Brad du Plessis wrote:
panic: kernel diagnostic assertion "pcg->pcg_avail == 0" failed: file
"../../../../kern_subr_pool.c", line 2580
Sorry, typo, should be:
panic: kernel diagnostic assertion "pcg->pcg_avail == 0" failed: file
"../../../../kern/subr_pool.c", line 2580
On 3/5/2010 12:39 PM, Brad du Plessis wrote:
On 3/5/2010 12:18 PM, Izumi Tsutsui wrote:
I've been seeing panics on a netbsd-4/i386 machine which appears to be
related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
:
Can anyone help me?
- options DIAGNOSTIC
> I've managed to reproduce this now in netbsd-5 too (source is about 3
> months old, not sure if there have been any changes since):
>
> re0: discarding oversize frame (len=9041)
> re0: discarding oversize frame (len=16158)
> panic: kernel diagnostic assertion "pcg->pcg_avail == 0" failed: file
On 3/6/2010 1:34 AM, David Young wrote:
On Wed, Mar 03, 2010 at 08:23:39AM +0200, Brad du Plessis wrote:
Hi all,
I've been seeing panics on a netbsd-4/i386 machine which appears to
be related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
re0: discarding
On 3/5/2010 12:18 PM, Izumi Tsutsui wrote:
I've been seeing panics on a netbsd-4/i386 machine which appears to be
related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
:
Can anyone help me?
- options DIAGNOSTIC might help debug
Had a kernel running with
On Wed, Mar 03, 2010 at 08:23:39AM +0200, Brad du Plessis wrote:
> Hi all,
>
> I've been seeing panics on a netbsd-4/i386 machine which appears to
> be related to the reception of oversized frames:
>
> re0: discarding oversize frame (len=8813)
> re0: discarding oversize frame (len=2191)
> re0: di
On 3/5/2010 12:18 PM, Izumi Tsutsui wrote:
I've been seeing panics on a netbsd-4/i386 machine which appears to be
related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
:
Can anyone help me?
- options DIAGNOSTIC might help debug
I'm busy trying to reproduc
> I've been seeing panics on a netbsd-4/i386 machine which appears to be
> related to the reception of oversized frames:
>
> re0: discarding oversize frame (len=8813)
:
> Can anyone help me?
- options DIAGNOSTIC might help debug
- does it happen on UP kernel (GENERIC, not GENERIC.MP), or netbsd
Hi all,
I've been seeing panics on a netbsd-4/i386 machine which appears to be
related to the reception of oversized frames:
re0: discarding oversize frame (len=8813)
re0: discarding oversize frame (len=2191)
re0: discarding oversize frame (len=10478)
uvm_fault(0xc0a44aa0, 0xe4ff7000, 1) -> 0x
19 matches
Mail list logo
