Hi Glebius,
On Tuesday 29 November 2011 15:28:42 Gleb Smirnoff wrote:
> Daan,
>
> On Tue, Nov 29, 2011 at 01:07:13AM +0100, Daan Vreeken wrote:
> D> Thanks for the looking into this and for your quick commit. I like your
> D> twist on the patch with the move from the unit
Hi Glebius,
On Friday 25 November 2011 15:32:58 Gleb Smirnoff wrote:
> On Fri, Nov 25, 2011 at 05:19:35PM +0400, Gleb Smirnoff wrote:
> T> On Thu, Nov 24, 2011 at 09:28:51AM +0100, Daan Vreeken wrote:
> T> D> Recently I've discovered a bug in if_clone.c and if.c where
http://www.freebsd.org/cgi/query-pr.cgi?pr=162789
Could anyone take a look at it?
Regards,
--
Daan Vreeken
Vitsch Electronics
http://Vitsch.nl
tel: +31-(0)40-7113051 / +31-(0)6-46210825
KvK nr: 17174380
___
freebsd-current@freebsd.org mailing
Hi all,
I have been experimenting with a VIMAGE kernel and noticed that it can be
panic()'d by opening and closing an if_tap device. I've submitted a PR with a
possible patch as kern/158686 .
Could anyone have a look at it?
Thanks,
--
Daan Vreeken
Vitsch Electronics
http://Vitsch.n
Hi Jack,
On Friday 06 May 2011 17:36:52 Jack Vogel wrote:
> On Fri, May 6, 2011 at 8:32 AM, Daan Vreeken wrote:
> > Hi Steven,
> >
> > On Friday 06 May 2011 17:20:15 Steven Hartland wrote:
> > > From: "Daan Vreeken"
> > >
> > > >
Hi Steven,
On Friday 06 May 2011 17:20:15 Steven Hartland wrote:
> From: "Daan Vreeken"
>
> > # vmstat -i
> > interrupt total rate
> > irq3: uart1 917384 63
> > --> irq16: ehci0
On Thursday 05 May 2011 22:22:15 Jack Vogel wrote:
> On Thu, May 5, 2011 at 1:17 PM, Daan Vreeken wrote:
> > Hi Peter,
> >
> > On Thursday 05 May 2011 21:28:02 Peter Jeremy wrote:
> > > On 2011-May-05 13:22:59 +0200, Daan Vreeken wrote:
> > > >Not yet.
Hi Peter,
On Thursday 05 May 2011 21:28:02 Peter Jeremy wrote:
> On 2011-May-05 13:22:59 +0200, Daan Vreeken wrote:
> >Not yet. I'll reboot the machine later today when I have physical access
> > to it to check the BIOS version. I'll keep you informed as soon as I ge
g like that on your motherboard?
Not yet. I'll reboot the machine later today when I have physical access to it
to check the BIOS version. I'll keep you informed as soon as I get another
storm going.
> On Wed, May 4, 2011 at 4:27 PM, Daan Vreeken wrote:
> > On Thursday 05
On Thursday 05 May 2011 00:15:43 you wrote:
> This all looks completely kosher, what IRQ is the storm on??
IRQ 16. Further down this email there is a list of devices that share the IRQ
according to 'dmesg'.
> On Wed, May 4, 2011 at 3:04 PM, Daan Vreeken wrote:
> > Hi,
&
27;t always start directly at boot. I
haven't been able (yet) to pinpoint what's triggering it to start.
> On Wed, May 4, 2011 at 11:19 AM, Daan Vreeken wrote:
> > Hi Jack,
> >
> > Wednesday 04 May 2011 19:46:05 Jack Vogel wrote:
> > > Who makes your moth
mstat -i"
> > output.
> >
> > As only 'em0' and 'em1' seem to be using MSI interrupts, my guess is that
> > the
> > e1000 driver is causing this problem. Could it be that the driver forgets
> > to
> > clear/mask legacy interrupt
interrupts perhaps?
Any tips on how to debug and/or fix this?
The full output of "dmesg" can be found here :
http://vehosting.nl/pub_diffs/dmesg_plantje2_2011_05_04.txt
And the full output of "pciconf -lv" is here :
http://vehosting.nl/pub_diffs/pciconf_p
On Thursday 27 November 2003 15:33, Jay Cornwall wrote:
> Daan Vreeken [PA4DAN] wrote:
> > If you have time left, could you perhaps also have a look at kern/51186?
> > I have filed it back in March and it's still open. (Fixes a memory
> > corruption bug in ugen).
&g
On Thursday 27 November 2003 01:08, Jay Cornwall wrote:
> > It looks like this:
> >
> > panic()
> > destroy_dev()
> > ugen_destroy_devnodes()
> > ugen_set_config()
>
> Yes, that's the one, and I think I can see why. The existing code fixed
> devfs problems for normal ugen_set_config calls, but does
15 matches
Mail list logo
