Enabling AHCI on ICH7M

2010-04-05 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My laptop manufacturer decided not to have AHCI included in the BIOS for this device, so I've been looking at what needs to happen in order to make this work. On this device, the BIOS doesn't even initialize BAR(5), so I need to start at that point ..

Re: [head tinderbox] failure on ia64/ia64

2010-04-05 Thread Robert Watson
On Mon, 5 Apr 2010, Robert Watson wrote: In file included from /src/sys/fs/coda/coda_fbsd.c:49: /src/sys/fs/coda/cnode.h:97: error: expected specifier-qualifier-list before 'CodaFid' /src/sys/fs/coda/cnode.h:199: error: expected ')' before '*' token Sorry all -- I'll commit a fix for this s

Re: [head tinderbox] failure on ia64/ia64

2010-04-05 Thread Robert Watson
On Mon, 5 Apr 2010, FreeBSD Tinderbox wrote: cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src

[head tinderbox] failure on ia64/ia64

2010-04-05 Thread FreeBSD Tinderbox
TB --- 2010-04-05 20:44:45 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-04-05 20:44:45 - starting HEAD tinderbox run for ia64/ia64 TB --- 2010-04-05 20:44:45 - cleaning the object tree TB --- 2010-04-05 20:45:08 - cvsupping the source tree TB --- 2010-04-05 20:45:08 - /usr/bin/c

Re: Call for testers: fxp(4) Rx buffer use after free

2010-04-05 Thread Pyun YongHyeon
On Sun, Apr 04, 2010 at 06:00:54PM -0700, Pyun YongHyeon wrote: > Hi, > > It seems that fxp(4) has a long standing races between controller > and driver. The exotic RFD handling of controller is race prone as > we had seen old ethernet controllers. I could easily reproduce this > by rebooting syst

Re: ipv6_enable

2010-04-05 Thread Bjoern A. Zeeb
On Mon, 5 Apr 2010, jhell wrote: Hi, reading the thread in thread view I had wondered why your reply had been ignored until I realized that it was the last to come in. So I'll use it to reply to, especially as I like it. I have no idea (unless I'll read them) about the guts of various shell fu

Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32

2010-04-05 Thread pluknet
Hi, the interesting part for me is how to properly assert now a value of e.g. KINFO_PROC_SIZE varying on err.. different COMPAT_FREEBSD32 arches (say, FreeBSD would have _kern_proc FreeBSD32 compat layer for top/ps/). -- wbr, pluknet ___ freebsd-curren

Re: ipv6_enable

2010-04-05 Thread Hiroki Sato
John Hay wrote in <20100405083056.ga8...@zibbi.meraka.csir.co.za>: jh> These questions actually start more questions for me. :-) Maybe we should jh> also think from the user perspective and list a few use cases and what a jh> user need to put in rc.conf to make that work? jh> jh> Your normal de

Re: ipv6_enable

2010-04-05 Thread jhell
On 04/05/2010 00:21, Kevin Oberman wrote: >> Date: Sun, 04 Apr 2010 20:13:40 -0700 >> From: Doug Barton >> >> On 04/04/10 02:41, Hiroki Sato wrote: >>> "Kevin Oberman" wrote >>> in <20100404053352.e6f751c...@ptavv.es.net>: > > Gentlemen, > > I think this is converging on a good, functional s

Re: ipv6_enable

2010-04-05 Thread Hiroki Sato
Doug Barton wrote in <4bb95564.1070...@freebsd.org>: do> On 04/04/10 02:41, Hiroki Sato wrote: do> > "Kevin Oberman" wrote do> > in <20100404053352.e6f751c...@ptavv.es.net>: do> > do> > ob> The use of FACILITY_enable in rc.conf predates /etc/rc.d scripts and I do> > ob> see no reason not to

Re: ipv6_enable

2010-04-05 Thread Doug Barton
On 04/04/10 22:42, Hiroki Sato wrote: > Doug Barton wrote > in <4bb7e224.6020...@freebsd.org>: > > If people want to disable IPv6 GUA assignment in per-AF manner, it > should be done by per-AF global knobs for $ifconfig_* because the GUA > assignment involves $ifconfig_* knobs only for the u

Re: Ports breakage since r205471

2010-04-05 Thread Garrett Cooper
On Mon, Apr 5, 2010 at 2:12 AM, Erwin Lansing wrote: > On Mon, Apr 05, 2010 at 02:02:46AM -0700, Xin LI wrote: >> On 2010/04/05 01:50, Erwin Lansing wrote: >> > On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote: >> >> Hi all, >> >>     I realize that this is most suitable for current@

Re: Ports breakage since r205471

2010-04-05 Thread Erwin Lansing
On Mon, Apr 05, 2010 at 02:02:46AM -0700, Xin LI wrote: > On 2010/04/05 01:50, Erwin Lansing wrote: > > On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote: > >> Hi all, > >> I realize that this is most suitable for current@ and I'm > >> cross-posting, but I wanted to jot down all of

Re: Ports breakage since r205471

2010-04-05 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010/04/05 01:50, Erwin Lansing wrote: > On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote: >> Hi all, >> I realize that this is most suitable for current@ and I'm >> cross-posting, but I wanted to jot down all of the ports broken s

Re: ipv6_enable

2010-04-05 Thread Doug Barton
I think it's clear at this point that you and I have some pretty serious disagreements about how this thing should look. I think that's unfortunate, since you have a lot of good ideas, I just think some of them are wrong. :) Seriously though, I hope we can find a way to come to agreement. I'm goin

Re: Ports breakage since r205471

2010-04-05 Thread Erwin Lansing
On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote: > Hi all, > I realize that this is most suitable for current@ and I'm > cross-posting, but I wanted to jot down all of the ports broken since > the zlib version bump so that we can keep track of what's going on and > what needs to

Re: ipv6_enable

2010-04-05 Thread John Hay
On Mon, Apr 05, 2010 at 02:42:52PM +0900, Hiroki Sato wrote: > Doug Barton wrote > in <4bb7e224.6020...@freebsd.org>: > > do> As we've discussed previously, you and I have a lot of disagreement on > do> some of these principles. I'm going to outline my responses in some > do> detail, however I'

Re: ipv6_enable

2010-04-05 Thread Hiroki Sato
Doug Barton wrote in <4bb95564.1070...@freebsd.org>: do> On 04/04/10 02:41, Hiroki Sato wrote: do> > "Kevin Oberman" wrote do> > in <20100404053352.e6f751c...@ptavv.es.net>: do> > do> > ob> The use of FACILITY_enable in rc.conf predates /etc/rc.d scripts and I do> > ob> see no reason not to