HEADS UP: FreeBSD 6.3 EoL coming soon

[FreeBSD Security Officer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

On January 31st, FreeBSD 6.3 will reach its End of Life and will no longer be
supported by the FreeBSD Security Team.  Users of this release are strongly
encouraged to upgrade to a newer release before that date -- more conservative
users will probably wish to upgrade to FreeBSD 6.4 or FreeBSD 7.1 (which are
both extended-support branches), while others will probably wish to upgrade to
FreeBSD 7.2 or FreeBSD 8.0.

The freebsd-update(8) utility can be used to upgrade i386 and amd64 systems
from 6.3-RELEASE (or 6.3-RELEASE-pX for some X) to 6.4-RELEASE using binary
updates (i.e., without compiling from source) as described in the 6.4-RELEASE
announcement; given an adequate internet connection, this process usually takes
15 minutes or less.

The current supported branches and expected EoL dates are:

   +-+
   |  Branch   |  Release   |  Type  |   Release date  |  Estimated EoL  |
   |---+++-+-|
   |RELENG_6   |n/a |n/a |n/a  |November 30, 2010|
   |---+++-+-|
   |RELENG_6_3 |6.3-RELEASE |Extended|January 18, 2008 |January 31, 2010 |
   |-|
   |RELENG_6_4 |6.4-RELEASE |Extended|November 18, 2008|November 30, 2010|
   |-|
   |RELENG_7   |n/a |n/a |n/a  |last release + 2y|
   |---+++-+-|
   |RELENG_7_1 |7.1-RELEASE |Extended|January 4, 2009  |January 31, 2011 |
   |---+++-+-|
   |RELENG_7_2 |7.2-RELEASE |Normal  |May 4, 2009  |May 31, 2010 |
   |---+++-+-|
   |RELENG_8   |n/a |n/a |n/a  |last release + 2y|
   |---+++-+-|
   |RELENG_8_0 |8.0-RELEASE |Normal  |November 25, 2009|November 30, 2010|
   +-+

- --
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAks/E1cACgkQFdaIBMps37J56wCcDDGvadAV0JnZsUXIVPRMghmQ
9KwAn3TiFrI5cNLjGwu58gMXOtNNbPg2
=GOl4
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cannot list a particular directory through NFS with UDP

[Jeremie Le Hen]

Rick,

Thanks for your time on this.

On Thu, Dec 31, 2009 at 02:23:32PM -0500, Rick Macklem wrote:
> [stuff snipped]
> >> This appears to be the reply to the nfs readdir request, which is what
> >> would be expected. It could be a problem with the content or the reply
> >> or a NetBSD client issue.
> >>
> >> If you were to email me the raw tcpdump capture for the above, I could
> >> take a look at it in wireshark (which knows how to interpret nfs) and
> >> see if there is anything bogus looking in the reply.
> >> ("tcpdump -s 0 -w  host 192.168.1.1" and then email me  as an
> >> attachment, should do it)
> >
> > You will find the pcap file attached.
> >
> Well, I looked at it under wireshark and the readdir reply looks fine.
> (It is made up of two IP fragments, but wireshark reassembles them ok
> and says the checksums are ok. The contents look like a valid Readdir
> RPC reply.) Maybe NetBSD doesn't reassemble the IP fragments correctly
> or has an issue w.r.t. the checksum, but Wireshark thinks it's aok.

I will reduce the MTU and see if the problem arises with directories
that could be read correctly otherwise.  I will keep you informed.

Does NFS permit to fragment/reassemble at the application layer?

> ps: I vaguely recall that the problem went away when you used TCP
>  instead. Is that correct?

Yes this is correct.

Regards,
-- 
Jeremie Le Hen

Humans are born free and equal.  But some are more equal than the others.
Coluche
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: cvsweb: src/UPDATING on RELENG_7

[Henri Hennebert]

Le 1/01/2010 16:40, Ian Smith a écrit :

Hi,

Thought I had a clue on using cvsweb, but seem to have mislaid it ..

After updating 7.0-RELEASE to RELENG_7 sources on Dec 28, checking
UPDATING before and during buildworld, went hunting on cvsweb for the
very version of UPDATING I was reading, 1.507.2.34 of 2009/11/29.

I can't find it, as such.  1.507 shows on MAIN, RELENG_7_BP, RELENG_7.
Selecting only RELENG_7 just shows that single ver 1.507 of Oct'07.


It is a known bug of cvsweb:

http://www.freebsd.org/cgi/query-pr.cgi?prp=120185-1-txt&n=/patch.txt

Henri


On a punt I manually entered 1.507.2.34 for a diff against 1.507 and
that looks just right:

http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING.diff?r1=text&tr1=1.507&r2=text&tr2=1.507.2.34

But where would I look to find the log and view for 1.507.2.34 itself?

cheers, Ian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Hacked - FreeBSD 7.1-Release

[Ian Smith]

On Thu, 31 Dec 2009, Jeremy Chadwick wrote:
 > On Thu, Dec 31, 2009 at 04:16:07AM +1100, Ian Smith wrote:
 > > On Tue, 29 Dec 2009, David Wolfskill wrote:
 > >  > On Tue, Dec 29, 2009 at 03:20:37AM -0800, Jeremy Chadwick wrote:
 > >  > > ...
 > >  > > I've written my own script to do all of this.  It parses periodic
 > >  > > security mails (on a daily basis), and does WHOIS lookups + parses the
 > >  > > results to tell me what netblocks/CIDRs I should consider blocking.  
 > > For
 > >  > > example, for a security mail that contains this:
 > >  > > 
 > >  > > horus.sc1.parodius.com login failures:
 > >  > > Dec 28 15:54:49 horus sshd[74684]: Failed password for root from 
 > > 199.71.214.240 port 51197 ssh2
 > >  > > Dec 28 15:54:49 horus sshd[74686]: Invalid user test from 
 > > 199.71.214.240
 > >  > > Dec 28 18:39:24 horus sshd[84742]: Failed password for root from 
 > > 208.94.235.248 port 42979 ssh2
 > >  > > Dec 28 18:39:25 horus sshd[84744]: Failed password for root from 
 > > 208.94.235.248 port 43056 ssh2
 > >  > > Dec 28 18:39:25 horus sshd[84746]: Failed password for root from 
 > > 208.94.235.248 port 43156 ssh2
 > >  > > Dec 28 18:39:26 horus sshd[84749]: Failed password for root from 
 > > 208.94.235.248 port 43265 ssh2
 > >  > > Dec 28 18:39:27 horus sshd[84751]: Failed password for root from 
 > > 208.94.235.248 port 43356 ssh2
 > >  > > 
 > >  > > The script would output the following:
 > >  > > 
 > >  > > 199.71.214.240
 > >  > > 199.71.212.0/22Psychz Networks, Walnut, CA, US
 > >  > > 208.94.235.248
 > >  > > 208.94.232.0/22WZ Communications Inc., Madison, WI, US
 > >  > > 208.94.235.0/24Soft-Com.biz, Inc., Panama, NA, PA
 > > 
 > > Jeremy, care to share your whois lookup / parsing script for this?
 > 
 > Sure.  It's a combination of two scripts which I call "parse_ssh_deny"
 > (sh) and "lookup" (perl).  How I use them: I get "security run output"
 > mails from periodic every night, and use mutt to save them (one per
 > server) to a single file, which I pipe to "parse_ssh_deny", resulting in
 > the above output.
 > 
 > I read the output by hand and decide manually what to put into
 > pf.conf.ssh-deny.

Thanks for this, very helpful.  Perhaps for others too.

 > I'll note that some of the servers are multi-user, so users mistyping
 > their password is common -- I specifically exclude that error message
 > from the awk line in "parse_ssh_deny" because I don't want legitimate
 > users potentially blocked.  People should tune the script based on their
 > needs though.
 > 
 > The "lookup" perl script uses whois(1) with specific arguments to get
 > back results from ARIN, and then parses the results.  Sometimes WHOIS
 > records don't have certain details (country code, city, state, etc.),
 > and other times they do.  The script tries to handle all of those.

Many of my lookups, often done adhoc while browsing various logs, are as 
likely to be via APNIC and other RIRs, all of which have differences in 
format to some extent; I'll have to play with all this when there's a 
bit more time.

 > The reason I chose to parse whois(1) output rather than using something
 > like Net::Whois or Net::Whois::IP is because I prefer self-contained
 > scripts (unless there's sufficient justification for reliance on such
 > third-party code); plus I didn't particularly like either of these perl
 > modules.

Yes I prefer using the base tools too.  I often find lots of perl code 
close to unreadable, but yours couldn't be clearer.  David Wolfskill 
sent some more useful clues too.  Thanks again, guys.

cheers, Ian


 > parse_ssh_deny
 > 
 > #!/bin/sh
 > for i in `awk '/Failed password for root/ {print $11} /Failed password for 
 > invalid user .+ from/ {print $13} /Invalid user/ {print $NF}' | sort -u -n`
 > do
 >  lookup "$i"
 > done
 > 
 > 
 > lookup
 > 
 > #!/usr/local/bin/perl
 > use strict;
 > use warnings;
 > 
 > # $ whois -a "+ 67.205.112.200" | egrep '^CustName|OrgName|CIDR'
 > # OrgName:iWeb Technologies Inc.
 > # CIDR:   67.205.64.0/18
 > # CustName:   iWeb Dedicated CL2
 > # CIDR:   67.205.112.192/27
 > 
 > my $lookup = shift or die "Usage: $0 ip\n";
 > 
 > my ($name, $city, $state, $cc, $cidr) = undef;
 > 
 > print $lookup, "\n";
 > 
 > open(FH, "whois -a '+ $lookup' |") or die;
 > while()
 > {
 >   $name  = $2if (m#^(CustName|OrgName):\s+(.+)#);
 >   $city  = $1if (m#^City:\s+(.+)#);
 >   $state = $1if (m#^StateProv:\s+(.+)#);
 >   $cc= $1if (m#^Country:\s+(.+)#);
 >   $cidr  = $1if (m#^CIDR:\s+([\d\./]+)#);
 > 
 >   if ($name and $cidr)
 >   {
 >  $city  = $city  || '';
 >  $state = $state || '';
 >  $cc= $cc|| '';
 > 
 >  printf "\t%-23s", $cidr;
 >  print join(", ", $name, $city, $state, $cc);
 >  print "\n";
 >  ($name, $city, $state, $cc, $cidr) = undef;
 >  next;
 >   }
 > }
 > close(FH);
 > 
 > 
 > -- 
 > | Jeremy Chadwick

Re: problem with iwi driver in 8.0 and custom kernel (works on generic)

[Gavin Atkinson]

On Wed, 23 Dec 2009, ocean wrote:
> i've got some problems with iwi in Freebsd 8.0, using GENERIC kernel
> everything works just fine, compiling a custom kernel, just excluding some
> modules i don't need, cause an interrupt storm to happen on irq11:
> 
> Dec 22 22:35:18 legend kernel: iwi0:  mem
> 0xb0101000-0xb0101fff irq 10 at device 4.0 on pci6
> Dec 22 22:35:18 legend kernel: iwi0: [ITHREAD]
> Dec 22 22:35:22 legend kernel: wlan0: Ethernet address: xx:xx:xx:xx:xx:xx
> Dec 22 22:35:32 legend kernel: interrupt storm detected on "irq11:";
> throttling interrupt source
> Dec 22 22:35:33 legend kernel: iwi0: timeout waiting for iwi_bss firmware
> initialization to complete
> Dec 22 22:35:33 legend kernel: iwi0: could not load boot firmware iwi_bss

Before you recompiled, did the iwi0 device work?  Once booted, can you 
show the output of "vmstat -i"?  Also, can you post a verbose dmesg 
somewhere?

It might also be useful to re-add things back into the kernel, and figure 
out which device removal actually triggers this.

Gavin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

pkg_add thinks that -STABLE is -RELEASE (wrong __FreeBSD_version?)

[Paride Legovini]

Hi,

I'm running 8.0-STABLE and I noticed that by default pkg_add -r uses
packages-8.0-release/Latest/ as PACKAGESITE. I read in the handbook[1]
that pkg_add should use packages-5-stable/Latest/ as PACKAGESITE when
one is running -STABLE.

I took a look at the source code, and noticed that pkg_add considers
the system -STABLE if getosreldate() (i.e. __FreeBSD_version) is between
800500 and 899000 (see src/usr.sbin/pkg_install/add/main.c:92).
However, in RELENG_8, __FreeBSD_version is set to 800108. You can check
it via cvsweb[2].

Sounds like something is wrong. Am I missing something?
Do I just have to wait for the __FreeBSD_version to be bumped?

Regards,
Paride

[1] http://www.freebsd.org/doc/en/books/handbook/packages-using.html
[2] 
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/param.h?only_with_tag=RELENG_8

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Regression with Asus K8N7-E deluxe motherboard on 8-stable: ACPI or PCI drivers bug ?

[Olivier Cochard-Labbé]

Hi,

I've met 3 regressions on 8-stable on my Asus K8N7-E deluxe motherboard:
- PATA drivers  (kern/139143)
- USB 2.0 drivers (usb/139142)
- Ethernet (nfe) drivers

But, I don't think that the USB/PATA/nfe drivers are the problem: The
problem seems came from ACPI or PCI bus drivers bug with this
motherboard.
There are lot's of differences between the dmesg on 7.2 and 8.0
regarding the hardware ressources informations.

Full dmesg under FreeBSD 7.2 here:
http://pastebin.com/f7bbdcb3a

Full dmesg under FreeBSD 8.0 here:
http://pastebin.com/f52df9c4c

Here, are some examples of the diff between the 2 dmesg:

--

About ACPI, there is this error on 8.0:

ACPI Error: Package List length (6) larger than NumElements count (3), truncated
 20090521 dsobject-590
---

About PCI link18 (Initial Probe IRQ diff):

7.2:

pci_link18:   Index  IRQ  Rtd  Ref  IRQs
  Initial Probe   0  255   N 0  18
  Validation  0  255   N 0  18
  After Disable   0  255   N 0  18

8.0:

pci_link18:   Index  IRQ  Rtd  Ref  IRQs
  Initial Probe   05   N 0  18
  Validation  0  255   N 0  18
  After Disable   0  255   N 0  18
(Note the IRQ diff)

---

And lot's of devices have map size diff:

on 7.2:

found-> vendor=0x10de, dev=0x0052, revid=0xa2
map[10]: type I/O Port, range 32, base 0xdc00, size  5, enabled
map[20]: type I/O Port, range 32, base 0x4c00, size  6, enabled
map[24]: type I/O Port, range 32, base 0x4c40, size  6, enabled
found-> vendor=0x10de, dev=0x0053, revid=0xf2
map[20]: type I/O Port, range 32, base 0xf000, size  4, enabled
found-> vendor=0x10de, dev=0x0055, revid=0xf3
map[10]: type I/O Port, range 32, base 0x9e0, size  3, enabled
map[14]: type I/O Port, range 32, base 0xbe0, size  2, enabled
map[18]: type I/O Port, range 32, base 0x960, size  3, enabled
map[1c]: type I/O Port, range 32, base 0xb60, size  2, enabled
map[20]: type I/O Port, range 32, base 0xc400, size  4, enabled

on 8.0:

found-> vendor=0x10de, dev=0x0052, revid=0xa2
map[10]: type I/O Port, range 32, base 0xdc00, size 10, enabled
map[20]: type I/O Port, range 32, base 0x4c00, size 10, enabled
map[24]: type I/O Port, range 32, base 0x4c40, size  6, enabled
found-> vendor=0x10de, dev=0x0053, revid=0xf2
map[20]: type I/O Port, range 32, base 0xf000, size 12, enabled
found-> vendor=0x10de, dev=0x0055, revid=0xf3
map[10]: type I/O Port, range 32, base 0x9e0, size  5, enabled
map[14]: type I/O Port, range 32, base 0xbe0, size  5, enabled
map[18]: type I/O Port, range 32, base 0x960, size  5, enabled
map[1c]: type I/O Port, range 32, base 0xb60, size  5, enabled
map[20]: type I/O Port, range 32, base 0xc400, size 10, enabled
(Note the size diff)

---

An unknown and USB error on 8.0:

7.2:

pcib0: slot 2 INTA routed to irq 21 via \_SB_.PCI0.APCF

8.0:

pcib0: slot 2 INTA routed to irq 21 via \_SB_.PCI0.APCF
unknown: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x8000
unknown: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x8000
ohci early: SMM active, request owner change
ohci early: SMM does not respond, resetting

---

The memory addresses of devices or reserved addresse bytes are different:

7.2:

ohci0:  mem 0xd3003000-0xd3003fff irq
21 at device 2.0 on pci0
ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd3003000
ioapic0: routing intpin 21 (PCI IRQ 21) to vector 49

atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on
pci0
atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf000

atapci1:  port
0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem
0xd3002000-0xd3002fff irq 22 at device 7.0 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd800
ioapic0: routing intpin 22 (PCI IRQ 22) to vector 52

nfe0:  port
0xb000-0xb007 mem 0xd300-0xd3000fff irq 21 at device 10.0 on pci0
nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd300
miibus0:  on nfe0
e1000phy0:  PHY 15 on miibus0
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
nfe0: bpf attached
nfe0: Ethernet address: 00:13:d4:d6:3a:7b

8.0:

ohci0:  mem 0x8000-0x8fff irq
21 at device 2.0 on pci0
ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 49
(Note the mem diff)

atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376 at device 6.0 on pci0
atapci0: Lazy allocation of 0x1000 bytes rid 0x20 type 4 at 0x1000
atapci0: Reserved 0x1000 bytes for rid 0x20 type 4 at 0x1000
(Note the reserved bytes diff)

atapci2:  irq 23 at device 8.0 on pci0
atapci2: Lazy allocation of 0x400 bytes rid 0x20 type 4 at 0x2c00
atapci2: Reserved 0x400 bytes for rid 0x20 type 4 at 0x2c00
ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 52
(Note the  reserved bytes diff)

nfe0:  irq 21 at device
10.0 on pci0
nfe0: Lazy allocation of 0x1000

kernel build failed

[E. O.]

pls help me.. build kernel error..

I have to update their source code.. standart-supfile

# IMPORTANT: Change the next line to use one of the CVSup mirror sites
# listed at http://www.freebsd.org/doc/handbook/mirrors.html.
*default host=CHANGE_THIS.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_8_0
*default delete use-rel-suffix

src-all



GENERIC Kernel use..


FreeBSD fbsd 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Fri Jan  1 15:31:27 EET
2010 r...@fbsd:/usr/obj/usr/src/sys/GENERIC  amd64




error ;

make buildkernel and error..

./pci_if.h:226: error: stray '\335' in program
./pci_if.h:226: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '_MS'
./pci_if.h:226: error: stray '\335' in program
./pci_if.h:238: error: stray '\335' in program
./pci_if.h:238: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '_MS'
./pci_if.h:238: error: stray '\335' in program
cc1: warnings being treated as errors
In file included from /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h:72,
 from aic7xxx_reg_print.c:9:
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_subvendor':
/usr/src/sys/dev/pci/pcivar.h:244: warning: implicit declaration of function
'BUS_READ_IVAR'
/usr/src/sys/dev/pci/pcivar.h:244: warning: nested extern declaration of
'BUS_READ_IVAR'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_set_subvendor':
/usr/src/sys/dev/pci/pcivar.h:244: warning: implicit declaration of function
'BUS_WRITE_IVAR'
/usr/src/sys/dev/pci/pcivar.h:244: warning: nested extern declaration of
'BUS_WRITE_IVAR'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_read_config':
/usr/src/sys/dev/pci/pcivar.h:274: warning: implicit declaration of function
'PCI_READ_CONFIG'
/usr/src/sys/dev/pci/pcivar.h:274: warning: nested extern declaration of
'PCI_READ_CONFIG'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_write_config':
/usr/src/sys/dev/pci/pcivar.h:280: warning: implicit declaration of function
'PCI_WRITE_CONFIG'
/usr/src/sys/dev/pci/pcivar.h:280: warning: nested extern declaration of
'PCI_WRITE_CONFIG'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_enable_busmaster':
/usr/src/sys/dev/pci/pcivar.h:318: warning: implicit declaration of function
'PCI_ENABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h:318: warning: nested extern declaration of
'PCI_ENABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_disable_busmaster':
/usr/src/sys/dev/pci/pcivar.h:324: warning: implicit declaration of function
'PCI_DISABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h:324: warning: nested extern declaration of
'PCI_DISABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_enable_io':
/usr/src/sys/dev/pci/pcivar.h:330: warning: implicit declaration of function
'PCI_ENABLE_IO'
/usr/src/sys/dev/pci/pcivar.h:330: warning: nested extern declaration of
'PCI_ENABLE_IO'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_disable_io':
/usr/src/sys/dev/pci/pcivar.h:336: warning: implicit declaration of function
'PCI_DISABLE_IO'
/usr/src/sys/dev/pci/pcivar.h:336: warning: nested extern declaration of
'PCI_DISABLE_IO'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_vpd_ident':
/usr/src/sys/dev/pci/pcivar.h:342: warning: implicit declaration of function
'PCI_GET_VPD_IDENT'
/usr/src/sys/dev/pci/pcivar.h:342: warning: nested extern declaration of
'PCI_GET_VPD_IDENT'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_vpd_readonly':
/usr/src/sys/dev/pci/pcivar.h:348: warning: implicit declaration of function
'PCI_GET_VPD_READONLY'
/usr/src/sys/dev/pci/pcivar.h:348: warning: nested extern declaration of
'PCI_GET_VPD_READONLY'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_set_powerstate':
/usr/src/sys/dev/pci/pcivar.h:393: warning: implicit declaration of function
'PCI_SET_POWERSTATE'
/usr/src/sys/dev/pci/pcivar.h:393: warning: nested extern declaration of
'PCI_SET_POWERSTATE'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_powerstate':
/usr/src/sys/dev/pci/pcivar.h:399: warning: implicit declaration of function
'PCI_GET_POWERSTATE'
/usr/src/sys/dev/pci/pcivar.h:399: warning: nested extern declaration of
'PCI_GET_POWERSTATE'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_find_extcap':
/usr/src/sys/dev/pci/pcivar.h:405: warning: implicit declaration of function
'PCI_FIND_EXTCAP'
/usr/src/sys/dev/pci/pcivar.h:405: warning: nested extern declaration of
'PCI_FIND_EXTCAP'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_alloc_msi':
/usr/src/sys/dev/pci/pcivar.h:411: warning: implicit declaration of function
'PCI_ALLOC_MSI'
/usr/src/sys/dev/pci/pcivar.h:411: warning: nested extern declaration of
'PCI_ALLOC_MSI'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_alloc_msix':
/usr/src/sys/dev/pci/pcivar.h:417: warning: implicit declaration of function
'PCI_ALLOC_MSIX'
/usr/src/sys/dev/pci/pcivar.h:417: warning: nested extern declaration of
'PCI_ALLOC_MSIX'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_remap_msix':
/usr/src/sys/dev/pci/pcivar.h:423: warning: implicit declaration of function
'P

Re: kernel build failed

[Roland Smith]

On Sat, Jan 02, 2010 at 09:55:29PM +0200, E. O. wrote:
> pls help me.. build kernel error..
> 
> I have to update their source code.. standart-supfile
> 
> # IMPORTANT: Change the next line to use one of the CVSup mirror sites
> # listed at http://www.freebsd.org/doc/handbook/mirrors.html.
> *default host=CHANGE_THIS.FreeBSD.org

What host did you really use? CHANGE_THIS.FreeBSD.org doesn't exist.

> GENERIC Kernel use..
> 
> 
> FreeBSD fbsd 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Fri Jan  1 15:31:27 EET
> 2010 r...@fbsd:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> 
> 
> 
> error ;
> 
> make buildkernel and error..
> 
> ./pci_if.h:226: error: stray '\335' in program

I think pci_if.h is a generated file. Clean out /usr/obj and try again. If
that doesn't work, try updating your source again.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpHJnxYwUe8G.pgp
Description: PGP signature

kernel build failed

[E. O.]

pls help me , kernel always returns an error

/usr# ls -l /usr/
total 66
drwxrwxr-x   2 root  operator512  2 Oca 14:26 .snap
lrwxr-xr-x   1 root  wheel10  1 Oca 20:35 X11R6 -> /usr/local
drwxr-xr-x   2 root  wheel  7168  2 Oca 12:43 bin
drwxr-xr-x   3 root  wheel   512  1 Oca 20:42 compat
drwxr-xr-x   2 root  wheel   512  1 Oca 16:21 games
drwxr-xr-x   4 root  wheel   512  1 Oca 16:51 home
drwxr-xr-x  46 root  wheel  5120  1 Oca 16:18 include
drwxr-xr-x   6 root  wheel 11776  1 Oca 16:21 lib
drwxr-xr-x   3 root  wheel 12288 21 Kas 16:31 lib32
drwxr-xr-x   5 root  wheel   512 21 Kas 16:29 libdata
drwxr-xr-x   5 root  wheel  1536  1 Oca 16:21 libexec
drwxr-xr-x  18 root  wheel   512  1 Oca 20:55 local
drwxr-xr-x   3 root  wheel   512  2 Oca 22:47 obj
drwxr-xr-x  69 root  wheel  1536  2 Oca 18:01 ports
drwxr-xr-x   2 root  wheel  5120  1 Oca 16:18 sbin
drwxr-xr-x  25 root  wheel   512 21 Kas 17:03 share
drwxr-xr-x  22 root  wheel  1024  2 Oca 22:31 src

I have re-operations, but still get an error ..


# IMPORTANT: Change the next line to use one of the CVSup mirror sites
# listed at http://www.freebsd.org/doc/handbook/mirrors.html.
*default host=cvsup.FreeBSD.org 

*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_8_0
*default delete use-rel-suffix

src-all



source update and

cd /usr/src

make cleandir && make cleandir && rm -rf /usr/obj

make buildkernel

and error


./pci_if.h:214: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '_RELEASE_MS'
./pci_if.h:214: error: stray '\335' in program

./pci_if.h:226: error: stray '\335' in program
./pci_if.h:226: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '_MS'
./pci_if.h:226: error: stray '\335' in program
./pci_if.h:238: error: stray '\335' in program
./pci_if.h:238: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '_MS'
./pci_if.h:238: error: stray '\335' in program
cc1: warnings being treated as errors
In file included from /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h:72,
 from aic7xxx_reg_print.c:9:
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_subvendor':
/usr/src/sys/dev/pci/pcivar.h:244: warning: implicit declaration of function
'BUS_READ_IVAR'
/usr/src/sys/dev/pci/pcivar.h:244: warning: nested extern declaration of
'BUS_READ_IVAR'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_set_subvendor':
/usr/src/sys/dev/pci/pcivar.h:244: warning: implicit declaration of function
'BUS_WRITE_IVAR'
/usr/src/sys/dev/pci/pcivar.h:244: warning: nested extern declaration of
'BUS_WRITE_IVAR'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_read_config':
/usr/src/sys/dev/pci/pcivar.h:274: warning: implicit declaration of function
'PCI_READ_CONFIG'
/usr/src/sys/dev/pci/pcivar.h:274: warning: nested extern declaration of
'PCI_READ_CONFIG'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_write_config':
/usr/src/sys/dev/pci/pcivar.h:280: warning: implicit declaration of function
'PCI_WRITE_CONFIG'
/usr/src/sys/dev/pci/pcivar.h:280: warning: nested extern declaration of
'PCI_WRITE_CONFIG'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_enable_busmaster':
/usr/src/sys/dev/pci/pcivar.h:318: warning: implicit declaration of function
'PCI_ENABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h:318: warning: nested extern declaration of
'PCI_ENABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_disable_busmaster':
/usr/src/sys/dev/pci/pcivar.h:324: warning: implicit declaration of function
'PCI_DISABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h:324: warning: nested extern declaration of
'PCI_DISABLE_BUSMASTER'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_enable_io':
/usr/src/sys/dev/pci/pcivar.h:330: warning: implicit declaration of function
'PCI_ENABLE_IO'
/usr/src/sys/dev/pci/pcivar.h:330: warning: nested extern declaration of
'PCI_ENABLE_IO'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_disable_io':
/usr/src/sys/dev/pci/pcivar.h:336: warning: implicit declaration of function
'PCI_DISABLE_IO'
/usr/src/sys/dev/pci/pcivar.h:336: warning: nested extern declaration of
'PCI_DISABLE_IO'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_vpd_ident':
/usr/src/sys/dev/pci/pcivar.h:342: warning: implicit declaration of function
'PCI_GET_VPD_IDENT'
/usr/src/sys/dev/pci/pcivar.h:342: warning: nested extern declaration of
'PCI_GET_VPD_IDENT'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_vpd_readonly':
/usr/src/sys/dev/pci/pcivar.h:348: warning: implicit declaration of function
'PCI_GET_VPD_READONLY'
/usr/src/sys/dev/pci/pcivar.h:348: warning: nested extern declaration of
'PCI_GET_VPD_READONLY'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_set_powerstate':
/usr/src/sys/dev/pci/pcivar.h:393: warning: implicit declaration of function
'PCI_SET_POWERSTATE'
/usr/src/sys/dev/pci/pcivar.h:393: warning: nested extern declaration of
'PCI_SET_POWERSTATE'
/usr/src/sys/dev/pci/pcivar.h: In function 'pci_get_p

Re: pkg_add thinks that -STABLE is -RELEASE (wrong __FreeBSD_version?)

[pluknet]

2010/1/2 Paride Legovini :
> Hi,
>
> I'm running 8.0-STABLE and I noticed that by default pkg_add -r uses
> packages-8.0-release/Latest/ as PACKAGESITE. I read in the handbook[1]
> that pkg_add should use packages-5-stable/Latest/ as PACKAGESITE when
> one is running -STABLE.
>
> I took a look at the source code, and noticed that pkg_add considers
> the system -STABLE if getosreldate() (i.e. __FreeBSD_version) is between
> 800500 and 899000 (see src/usr.sbin/pkg_install/add/main.c:92).
> However, in RELENG_8, __FreeBSD_version is set to 800108. You can check
> it via cvsweb[2].
>
> Sounds like something is wrong. Am I missing something?
> Do I just have to wait for the __FreeBSD_version to be bumped?


Hi.

I'm afraid that's because __FreeBSD_version wasn't bumped
800107->800500 in RELENG_8 just after RELENG_8_0 created
(wrt changes in scheme for RELENG_8 timeframe where
current/stable border moved to 800500:
http://lists.freebsd.org/pipermail/svn-src-head/2009-June/007830.html

It continued then as is (still ok), and eventually was incremented
to 800108 (wrong here, though I hope it still can be safely corrected).

-- 
wbr,
pluknet
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: kernel build failed

[Warren Block]

On Sat, 2 Jan 2010, E. O. wrote:


source update and

cd /usr/src

make cleandir && make cleandir && rm -rf /usr/obj

make buildkernel

and error


After updating source, you should buildworld before trying to build the 
kernel.


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

-Warren Block * Rapid City, South Dakota USA
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: kernel build failed

[Doug Barton]

E. O. wrote:

> # IMPORTANT: Change the next line to use one of the CVSup mirror sites
> # listed at http://www.freebsd.org/doc/handbook/mirrors.html.
> *default host=cvsup.FreeBSD.org 

I don't think that's going to work properly for you. Try going to
http://www.freebsd.org/doc/handbook/cvsup.html#HANDBOOK-MIRRORS-CHAPTER-SGML-MIRRORS-PRIMARY-CVSUP
and picking a hostname from that list. You are going to want something
that looks like this:

*default host=cvsup1.FreeBSD.org

> *default base=/var/db
> *default prefix=/usr
> *default release=cvs tag=RELENG_8_0

Are you intending to download exactly the sources for 8.0-RELEASE? If
you want to have 8.0-STABLE you should use this instead:

*default release=cvs tag=RELENG_8

> *default delete use-rel-suffix
> 
> src-all
> 
> 
> 
> source update

How are you doing that exactly?

> and
> 
> cd /usr/src
> 
> make cleandir && make cleandir && rm -rf /usr/obj
> 
> make buildkernel

FreeBSD is not like Linux in the sense that you don't just want to
update the kernel independently of the rest of the base system. You
want to update the whole thing. Try this instead:

make buildworld &&
make buildkernel

You should also read
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
to get a better idea of the overall process.


hope this helps,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Regression with Asus K8N7-E deluxe motherboard on 8-stable: ACPI or PCI drivers bug ?

[Hans Petter Selasky]

On Saturday 02 January 2010 19:54:11 Olivier Cochard-Labbé wrote:
> ohci early: SMM active, request owner change
> ohci early: SMM does not respond, resetting

If the I/O address range changed, then the above can be explained by that we 
are reading/writing to an invalid range.

USB debug sysctls: /boot/loader.conf

hw.usb.ohci.debug=15
hw.usb.ehci.debug=15

--HPS
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cannot list a particular directory through NFS with UDP

[Rick Macklem]

On Sat, 2 Jan 2010, Jeremie Le Hen wrote:



I will reduce the MTU and see if the problem arises with directories
that could be read correctly otherwise.  I will keep you informed.



You can reduce rsize to 1024, so that it isn't happening, but that
will also change the size of the readdir reply. (ie. It might make
the problem go away, but doesn't prove that IP fragmentation is the
cause..)


Does NFS permit to fragment/reassemble at the application layer?



Nope. IP fragment reassembly should work fine and IP fragmentation
happens all the time when using NFS over UDP. (Some would say NFS over
UDP misused/abused IP fragmentation. In any case, it happens more
frequently there than anywhere else.)

ps: I vaguely recall that the problem went away when you used TCP
 instead. Is that correct?


Yes this is correct.


Thanks for poking at this, rick

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: gstat: geom_gettree = -1: No such file or directory

[Ulrich Spörlein]

On Fri, 01.01.2010 at 18:47:27 +0100, martinko wrote:
> Hi list,
> 
> gstat(8) does not work here on 8.0 (it worked happily on 6.x and 7.x) :
> 
> # gstat
> gstat: geom_gettree = -1: No such file or directory
> 
> Is this known ?  What can I do ?

I doubt that it is widely known, but I've seen these 2-3 times before
when fussing around with USB media and/or md(4) devices with gmirror on
top. Basically, if you get really creative with the geom layering, this
is likely to happen.

It sure is a bug, but without a good way to reproduce, noone's gonna fix
it.

Regards,
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UTF-8 problem in 8.0

[Ulrich Spörlein]

On Fri, 01.01.2010 at 15:47:36 -0800, Derek Kulinski wrote:
> Hello,
> 
> After installing FreeBSD 8.0 I noticed that some characters aren't
> displayed correctly (it worked fine for 7.2).
> 
> Mainly the dash character is most noticeable (though it's possible
> it's more of them).
> 
> Example:
> env LANG=C man sh
> env LANG=pl_PL.UTF-8 man sh
> env LANG=en_US.UTF-8 man sh
> 
> The first command shows everything fine, the later two seem to show
> some unprintable character in place of every dash (i.e. in the second
> paragraph word "built-in", or the dashes that break up the words at
> the end of the line)

me too, though I'm only setting LC_CTYPE to de_DE.UTF-8 and I don't
always see it. It must be some combination of xterm/ssh and/or putty
that breaks this.

On the other hand, I thought there was a commit done, that would render
- (the dash) always as - (0x2d) so you can copy&paste the examples from
the manpage into your shell.

But perhaps I was just dreaming this up?

Bye,
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UTF-8 problem in 8.0

[Jonathan Chen]

On Sun, Jan 03, 2010 at 02:38:32AM +0100, Ulrich Sp??rlein wrote:
> On Fri, 01.01.2010 at 15:47:36 -0800, Derek Kulinski wrote:
> > Hello,
> > 
> > After installing FreeBSD 8.0 I noticed that some characters aren't
> > displayed correctly (it worked fine for 7.2).
> > 
> > Mainly the dash character is most noticeable (though it's possible
> > it's more of them).
> > 
> > Example:
> > env LANG=C man sh
> > env LANG=pl_PL.UTF-8 man sh
> > env LANG=en_US.UTF-8 man sh
> > 
> > The first command shows everything fine, the later two seem to show
> > some unprintable character in place of every dash (i.e. in the second
> > paragraph word "built-in", or the dashes that break up the words at
> > the end of the line)
> 
> me too, though I'm only setting LC_CTYPE to de_DE.UTF-8 and I don't
> always see it. It must be some combination of xterm/ssh and/or putty
> that breaks this.

Actually, I've just got en_NZ.UTF8, and I see it on the console as
well.
-- 
Jonathan Chen 
--
"With sufficient thrust, pigs fly just fine. However, this is not necessarily
a good idea. It is hard to be sure where they are going to land, and it
could be dangerous sitting under them as they fly overhead." -- RFC 1925
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UTF-8 problem in 8.0

[Derek Kulinski]

Hello Jonathan,

Saturday, January 2, 2010, 7:28:07 PM, you wrote:

>> me too, though I'm only setting LC_CTYPE to de_DE.UTF-8 and I don't
>> always see it. It must be some combination of xterm/ssh and/or putty
>> that breaks this.

> Actually, I've just got en_NZ.UTF8, and I see it on the console as
> well.

Put en_NZ.UTF-8 (with the dash), if you set an invalid value it
switches to default.

-- 
Best regards,
 Derekmailto:tak...@takeda.tk

If you have a procedure with ten parameters, you probably missed some.
-- Alan J. Perlis

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UTF-8 problem in 8.0

[Jonathan Chen]

On Sat, Jan 02, 2010 at 07:37:15PM -0800, Derek Kulinski wrote:
> Hello Jonathan,
> 
> Saturday, January 2, 2010, 7:28:07 PM, you wrote:
> 
> >> me too, though I'm only setting LC_CTYPE to de_DE.UTF-8 and I don't
> >> always see it. It must be some combination of xterm/ssh and/or putty
> >> that breaks this.
> 
> > Actually, I've just got en_NZ.UTF8, and I see it on the console as
> > well.
> 
> Put en_NZ.UTF-8 (with the dash), if you set an invalid value it
> switches to default.

Sorry. I actually meant that if I had en_NZ.UTF-8 on the console, some
man pages' characters are mangled as well. If it uses the default of C,
everything is fine.

Cheers.
-- 
Jonathan Chen 
--
   "Lots of folks confuse bad management with destiny"
 - Kin Hubbard
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"