Re: [head tinderbox] failure on i386/i386

2011-05-06 Thread YongHyeon PYUN
On Sat, May 07, 2011 at 04:18:08AM +, FreeBSD Tinderbox wrote: > TB --- 2011-05-07 02:10:00 - tinderbox 2.7 running on > freebsd-current.sentex.ca > TB --- 2011-05-07 02:10:00 - starting HEAD tinderbox run for i386/i386 > TB --- 2011-05-07 02:10:00 - cleaning the object tree > TB --- 2011-05-0

[head tinderbox] failure on amd64/amd64

2011-05-06 Thread FreeBSD Tinderbox
TB --- 2011-05-07 02:10:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-05-07 02:10:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2011-05-07 02:10:00 - cleaning the object tree TB --- 2011-05-07 02:10:28 - cvsupping the source tree TB --- 2011-05-07 02:10:28 - /usr/bin

[head tinderbox] failure on i386/i386

2011-05-06 Thread FreeBSD Tinderbox
TB --- 2011-05-07 02:10:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-05-07 02:10:00 - starting HEAD tinderbox run for i386/i386 TB --- 2011-05-07 02:10:00 - cleaning the object tree TB --- 2011-05-07 02:10:28 - cvsupping the source tree TB --- 2011-05-07 02:10:28 - /usr/bin/c

[head tinderbox] failure on i386/pc98

2011-05-06 Thread FreeBSD Tinderbox
TB --- 2011-05-07 02:10:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-05-07 02:10:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2011-05-07 02:10:00 - cleaning the object tree TB --- 2011-05-07 02:10:24 - cvsupping the source tree TB --- 2011-05-07 02:10:24 - /usr/bin/c

[CFT] Early Retransmit for TCP (rfc5827) patch

2011-05-06 Thread Weongyo Jeong
Hello all, I'd like to send another patch to support RFC5827 in TCP stack which could be found at: http://people.freebsd.org/~weongyo/patch_20110506_rfc5827.diff This patch supports all Early Retransmit logics (Byte-Based Early Retransmit and Segment-Based Early Retransmit) when net.inet

Heads Up: after r221543 you need a fresh make depend

2011-05-06 Thread Rick Macklem
Since r221543 moves nfs_kdtrace.h, you'll need to do a fresh make cleandepend; make depend to update your kernel dependencies. rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, sen

Re: firewire debugging

2011-05-06 Thread Chris Ruiz
On Tue, May 3, 2011 at 4:35 PM, Julian Elischer wrote: > does anyone know if there is a limitation on firewire debugging on a machine > with > 4GB or memory? I've successfully used firewire dcons on amd64 with 8GB of RAM. > I have 1394 {a,b} cards.  does it make a difference? Shouldn't make a d

Re: dsp mmap change

2011-05-06 Thread John Baldwin
On Friday, May 06, 2011 10:04:28 am Kostik Belousov wrote: > On Fri, May 06, 2011 at 04:38:00PM +0300, Andriy Gapon wrote: > > on 06/05/2011 16:32 Kostik Belousov said the following: > > > On Fri, May 06, 2011 at 11:55:00AM +0300, Andriy Gapon wrote: > > >> > > >> I would like to ask for a review a

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread John Baldwin
On Friday, May 06, 2011 11:36:52 am Jack Vogel wrote: > I don't see why you are blaming em, you can see its on MSIX vectors > that are NOT storming, its something with USB as noted. Trying to > disable em from using MSIX is in exactly the wrong direction IMHO. In the past Intel host bridges have e

Re: dsp mmap change

2011-05-06 Thread Juergen Lock
On Fri, May 06, 2011 at 11:55:00AM +0300, Andriy Gapon wrote: > > I would like to ask for a review and/or testing of the following patch: > http://people.freebsd.org/~avg/dev_dsp_mmap.diff > > It's supposed to fix an issue described here: > http://lists.freebsd.org/pipermail/freebsd-multimedia/20

Re: dsp mmap change

2011-05-06 Thread Andriy Gapon
on 06/05/2011 16:00 John Baldwin said the following: > On Friday, May 06, 2011 4:55:00 am Andriy Gapon wrote: >> >> I would like to ask for a review and/or testing of the following patch: >> http://people.freebsd.org/~avg/dev_dsp_mmap.diff >> >> It's supposed to fix an issue described here: >> http

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread Daan Vreeken
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" > > > > > > > # vmstat -i > > > > interrupt total

Re: atkbdc broken on current ?

2011-05-06 Thread John Baldwin
On Thursday, May 05, 2011 5:04:54 pm Damjan Marion wrote: > > On May 5, 2011, at 7:43 PM, John Baldwin wrote: > > > On Thursday, May 05, 2011 9:21:04 am Damjan Marion wrote: > >> > >> Hi, > >> > >> I have issue with old HP DL380G3 server. When I use ILO virtual console to > > manage server. Se

Re: dsp mmap change

2011-05-06 Thread John Baldwin
On Friday, May 06, 2011 4:55:00 am Andriy Gapon wrote: > > I would like to ask for a review and/or testing of the following patch: > http://people.freebsd.org/~avg/dev_dsp_mmap.diff > > It's supposed to fix an issue described here: > http://lists.freebsd.org/pipermail/freebsd-multimedia/2011- Feb

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread Mike Tancsa
On 5/6/2011 11:02 AM, Daan Vreeken wrote: > One core is spending half it's time handling interrupts. > /var/log/messages doesn't show any new message since the storm > started. "vmstat -i" now shows : > > # vmstat -i > interrupt total rate > irq3:

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread Jack Vogel
I don't see why you are blaming em, you can see its on MSIX vectors that are NOT storming, its something with USB as noted. Trying to disable em from using MSIX is in exactly the wrong direction IMHO. Jack On Fri, May 6, 2011 at 8:32 AM, Daan Vreeken wrote: > Hi Steven, > > On Friday 06 May 20

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread 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 809547235 55608 > > Have you tried

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread Steven Hartland
- Original Message - From: "Daan Vreeken" # vmstat -i interrupt total rate irq3: uart1 917384 63 --> irq16: ehci0 809547235 55608 Have you tried removing USB from the kernel? USB seems to be a common

Re: Interrupt storm with MSI in combination with em1

2011-05-06 Thread Daan Vreeken
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. I'll reboot the machine later today when I h

Re: dsp mmap change

2011-05-06 Thread Kostik Belousov
On Fri, May 06, 2011 at 04:38:00PM +0300, Andriy Gapon wrote: > on 06/05/2011 16:32 Kostik Belousov said the following: > > On Fri, May 06, 2011 at 11:55:00AM +0300, Andriy Gapon wrote: > >> > >> I would like to ask for a review and/or testing of the following patch: > >> http://people.freebsd.org/

Re: Clang error make buildworld

2011-05-06 Thread Pan Tsu
Olivier Smedts writes: > 2011/5/5 Roman Divacky : >>> Because with clang, -march=native often breaks buildworld, while >>> -march=core2 is ok. >> >> Can you be more specific about this claim? On what CPU are seeing >> this breakage? > > Ok, with latest HEAD... > > %echo | gcc -march=native -E -v

Re: dsp mmap change

2011-05-06 Thread Andriy Gapon
on 06/05/2011 16:38 Andriy Gapon said the following: > on 06/05/2011 16:32 Kostik Belousov said the following: >> Your patch hardcodes an assumption that sndbufs are always >> contiguous. I was unable to convince myself that this is true. > > I think that this should be true for the case when DMA

Re: dsp mmap change

2011-05-06 Thread Andriy Gapon
on 06/05/2011 16:32 Kostik Belousov said the following: > On Fri, May 06, 2011 at 11:55:00AM +0300, Andriy Gapon wrote: >> >> I would like to ask for a review and/or testing of the following patch: >> http://people.freebsd.org/~avg/dev_dsp_mmap.diff >> >> It's supposed to fix an issue described her

Re: dsp mmap change

2011-05-06 Thread Kostik Belousov
On Fri, May 06, 2011 at 11:55:00AM +0300, Andriy Gapon wrote: > > I would like to ask for a review and/or testing of the following patch: > http://people.freebsd.org/~avg/dev_dsp_mmap.diff > > It's supposed to fix an issue described here: > http://lists.freebsd.org/pipermail/freebsd-multimedia/20

Re: Switch from legacy ata(4) to CAM-based ATA

2011-05-06 Thread Alexander Motin
Sergey Kandaurov wrote: > On 6 May 2011 12:33, Alexander Motin wrote: >> Sergey Kandaurov wrote: >>> XENHVM uses it's own naming scheme and can name disks as daN or adN, >>> depending on virtual block device id. atapci0/ata0/ata1 devices still >>> present >>> there (such as in Bruce Cran's dmesg)

Re: Switch from legacy ata(4) to CAM-based ATA

2011-05-06 Thread Sergey Kandaurov
On 6 May 2011 12:33, Alexander Motin wrote: > Sergey Kandaurov wrote: >> XENHVM uses it's own naming scheme and can name disks as daN or adN, >> depending on virtual block device id. atapci0/ata0/ata1 devices still present >> there (such as in Bruce Cran's dmesg), but no any disks attached from it

Re: Using Dtrace for Performance Evaluation

2011-05-06 Thread Alexander Leidinger
Quoting David Christensen (from Thu, 5 May 2011 13:08:56 -0700): I was looking at using dtrace to help characterize performance for the new bxe(4) driver but I'm having problems with the very simple task of capturing time spent in a function. The D script I'm using looks like the following:

dsp mmap change

2011-05-06 Thread Andriy Gapon
I would like to ask for a review and/or testing of the following patch: http://people.freebsd.org/~avg/dev_dsp_mmap.diff It's supposed to fix an issue described here: http://lists.freebsd.org/pipermail/freebsd-multimedia/2011-February/011691.html In short, the following pseudo-code should do the

Re: Switch from legacy ata(4) to CAM-based ATA

2011-05-06 Thread Alexander Motin
Sergey Kandaurov wrote: > XENHVM uses it's own naming scheme and can name disks as daN or adN, > depending on virtual block device id. atapci0/ata0/ata1 devices still present > there (such as in Bruce Cran's dmesg), but no any disks attached from it: > instead, all of them hung from device/vbd/N. >