Re: atacontrol kernel crash (atausb?)

2007-01-28 Thread Ed Schouten
* M. Warner Losh [EMAIL PROTECTED] wrote:
 In message: [EMAIL PROTECTED]
 Hans Petter Selasky [EMAIL PROTECTED] writes:
 : Instead of having all these quirks, isn't it possible that the SCSI layer 
 can 
 : auto-probe this?
 
 The short answer is no.  There's no reliable way to tell if a device
 supports a given scsi command, and some devices freak out (lock up)
 when sent one.

Well, in one of the scenario's there is. USB UFI devices never support
synchronize.

-- 
 Ed Schouten [EMAIL PROTECTED]
 WWW: http://g-rave.nl/


pgp1WdiUG69vn.pgp
Description: PGP signature


Crash at sysctl -a

2007-01-28 Thread Lee Chung-Yeol
 Hi, I'm using freebsd-stable.

 From almost a year ago, my system crashes when I try to upgrade mysql because
of sysctl -a in its configure script.

 Immediately after the rebooting, there's no problem but as the uptime 
increases, 
 sysctl always crashes system.

 I'm using custom kernel following.
 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu Jan 18 08:41:09 KST 2007

 Thanks in advance.

 Here's the backtrace.
=
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x18264
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc0492d39
stack pointer   = 0x28:0xef6cfb18
frame pointer   = 0x28:0xef6cfb18
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 65874 (sysctl)
trap number = 12
panic: page fault
Uptime: 6d14h42m57s
Dumping 1023 MB (2 chunks)
  chunk 0: 1MB (159 pages) ... ok
  chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863
(CTRL-C to abort)  (CTRL-C to abort)  847 (CTRL-C to abort)  (CTRL-C to abort)
(CTRL-C to abort)  831 (CTRL-C to abort)  815 799 783 767 751 735 719 703 687
671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383
367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63
47 31 15

#0  doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0  doadump () at pcpu.h:165
#1  0xc04d072e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc04d09c4 in panic (fmt=0xc0660bde %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3  0xc063fecc in trap_fatal (frame=0xef6cfad8, eva=98916) at
/usr/src/sys/i386/i386/trap.c:837
#4  0xc063fc33 in trap_pfault (frame=0xef6cfad8, usermode=0, eva=98916) at
/usr/src/sys/i386/i386/trap.c:745
#5  0xc063f891 in trap (frame=
  {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -278070404, tf_esi =
-994135040, tf_ebp = -278070504, tf_isp = -278070524, tf_ebx = -994135040,
tf_edx = -987703296, tf_ecx = 0, tf_eax = 98724, tf_trapno = 12, tf_err = 0,
tf_eip = -1068946119, tf_cs = 32, tf_eflags = 66182, tf_esp = -278070336,
tf_ss = -1068492713}) at /usr/src/sys/i386/i386/trap.c:435
#6  0xc062ef0a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc0492d39 in dev2udev (x=0xc520d800) at
/usr/src/sys/fs/devfs/devfs_vnops.c:1308
#8  0xc0501857 in sysctl_kern_ttys (oidp=0xc069dda0, arg1=0x0, arg2=0,
req=0xef6cfc04) at /usr/src/sys/kern/tty.c:3052
#9  0xc04d8597 in sysctl_root (oidp=0x0, arg1=0x0, arg2=0, req=0xef6cfc04) at
/usr/src/sys/kern/kern_sysctl.c:1281
#10 0xc04d8794 in userland_sysctl (td=0x181a4, name=0xef6cfc74, namelen=2,
old=0xef6cfc04, oldlenp=0xbfbfd0fc, inkernel=0, new=0x0, 
newlen=98724, retval=0xef6cfc70, flags=98724) at
/usr/src/sys/kern/kern_sysctl.c:1380
#11 0xc04d8637 in __sysctl (td=0xc5206900, uap=0xef6cfd04) at
/usr/src/sys/kern/kern_sysctl.c:1315
#12 0xc06401e3 in syscall (frame=
  {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 2, tf_esi = -1077948164,
tf_ebp = -1077948248, tf_isp = -278069916, tf_ebx = 672472448, tf_edx = 0,
tf_ecx = -1077945952, tf_eax = 202, tf_trapno = 0, tf_err = 2, tf_eip =
672321659, tf_cs = 51, tf_eflags = 662, tf_esp = -1077948308, tf_ss = 59}) at
/usr/src/sys/i386/i386/trap.c:983
#13 0xc062ef5f in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:200
#14 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)


-- 
 Neural Networks and Machine Intelligence Lab. Dept. of EECS KAIST
 email: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Roland Smith
On Sun, Jan 28, 2007 at 04:39:29AM +0100, Lars Stokholm wrote:
 Hi,
 
 After updating to 6.2-STABLE Sun Jan 28 02:57:55 CET 2007 (GENERIC), I 
 get an error on startup from sysctl, because dev.cpu.0.cx_supported 
 doesn't exist. I think I tracked it down to this update:
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=1.9r2=1.10f=h
 
 I guess it's because I'm not running powerd, but if that's the case, 
 should powerd_enable=NO be changed to powerd_enable=YES in 
 /etc/defaults/rc.conf? Or is it some sort of mistake?

On my amd64 system, I've got powerd up and working, but
'dev.cpu.0.cx_supported' doesn't exist here either. Do you perhaps mean
'hw.acpi.cpu.cx_supported' because that does exists here.

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)


pgpA6nNoXjAfe.pgp
Description: PGP signature


Re: FreeBSD 6.2-STABLE and Flash 7 patch

2007-01-28 Thread Marc Fonvieille
On Thu, Jan 25, 2007 at 08:10:49AM +0900, Norikatsu Shigemura wrote:
 On Wed, 24 Jan 2007 22:51:07 +0100
 Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
  On Wed, 24 Jan 2007 13:11:16 -0600
  ejc [EMAIL PROTECTED] wrote:
   rtld.c has changed a bit over time so here's a patch against the new
   file.
  BTW, what is the reason this hack isn't included in the base kernel /
  code?
 
   I suggested new patch.  But no response:-(.
 
   SEE ALSO:
   
 http://lists.freebsd.org/pipermail/freebsd-hackers/2007-January/019360.html

Hello Norikatsu,

Is it possible to update
http://people.FreeBSD.org/~nork/rtld_dlsym_hack.diff to match 6-STABLE,
this would prevent thousand mails about the non-working flash7 plugin?

-- 
Marc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ath0: ath_reset: unable to reset hardware; hal status 3

2007-01-28 Thread Henrik Brix Andersen
Hi all,

I have noticed a problem when using ath(4) as an 802.11g access point
with hostapd(8) and WPA2-PSK CCMP.

The following problem seems to only occur when a Microsoft Windows XP
STA connects to the AP in 802.11g mode, my FreeeBSD STAs doesn't seem
to trigger this:

Jan 28 11:21:07 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jan 28 11:21:07 osgiliath kernel: ath0: ath_reset: unable to reset hardware; 
hal status 3
Jan 28 11:21:25 osgiliath kernel: ath0: device timeout
Jan 28 11:21:25 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jan 28 11:21:25 osgiliath kernel: ath0: ath_reset: unable to reset hardware; 
hal status 3
Jan 28 11:21:37 osgiliath kernel: ath0: device timeout
Jan 28 11:21:38 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jan 28 11:21:38 osgiliath kernel: ath0: ath_reset: unable to reset hardware; 
hal status 3
Jan 28 11:21:46 osgiliath kernel: ath0: device timeout

This is FreeBSD RELENG_6 (nanoBSD) as of yesterday with the new
ath_hal(4) running on a Soekris net4801-50:

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: Atheros 5212 mem 0xa001-0xa001 irq 11 at device 14.0 on pci0
ath0: Ethernet address: 00:05:4e:42:e8:7c
ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3

The same problem occured with version 0.9.17.2 of ath_hal(4).

I have increased the RX/TX buffers in ath(4) as shown in this snippet
from my kernel configuration:

device  ath
device  ath_hal
device  ath_rate_sample

options ATH_RXBUF=80
options ATH_TXBUF=200

The only way I can get the AP running again after the above messages
to syslog is to reboot it. The problem doesn't seem to occur in
802.11b mode nor in 802.11g mode with only FreeBSD STAs.

Any help in debugging this will be appreciated.

Regards,
Brix
-- 
Henrik Brix Andersen [EMAIL PROTECTED]


pgpaSfvVEpUzW.pgp
Description: PGP signature


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Lars Stokholm

Roland Smith wrote:

On Sun, Jan 28, 2007 at 04:39:29AM +0100, Lars Stokholm wrote:
After updating to 6.2-STABLE Sun Jan 28 02:57:55 CET 2007 (GENERIC), I 
get an error on startup from sysctl, because dev.cpu.0.cx_supported 
doesn't exist. I think I tracked it down to this update:


Also this error only shows up on startup, it's not in dmesg. Why?


http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=1.9r2=1.10f=h

I guess it's because I'm not running powerd, but if that's the case, 
should powerd_enable=NO be changed to powerd_enable=YES in 
/etc/defaults/rc.conf? Or is it some sort of mistake?


On my amd64 system, I've got powerd up and working, but
'dev.cpu.0.cx_supported' doesn't exist here either. Do you perhaps mean
'hw.acpi.cpu.cx_supported' because that does exists here.


I don't know why I came to that conclusion. I don't think it has 
anything to do with powerd. The only mention of cx_supported in the 
entire source tree is in power_profile (as linked above) and in acpi_cpu.c:


http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/acpica/acpi_cpu.c.diff?r1=1.57.2.1r2=1.57.2.2sortby=datef=h

I don't know if it has anything to do with that.

Anyway power_profile (called by devd afaik) seems to need it, but it 
doesn't exist.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Crash at sysctl -a

2007-01-28 Thread Gleb Kozyrev

On 28/01/07, Lee Chung-Yeol [EMAIL PROTECTED] wrote:

 Hi, I'm using freebsd-stable.

 From almost a year ago, my system crashes when I try to upgrade mysql because
of sysctl -a in its configure script.

 Immediately after the rebooting, there's no problem but as the uptime 
increases,
 sysctl always crashes system.


Just for the record, there is a PR on this:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89538

--
With best regards, Gleb Kozyrev.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Roland Smith
On Sun, Jan 28, 2007 at 12:14:40PM +0100, Lars Stokholm wrote:
 Roland Smith wrote:
 On Sun, Jan 28, 2007 at 04:39:29AM +0100, Lars Stokholm wrote:
 After updating to 6.2-STABLE Sun Jan 28 02:57:55 CET 2007 (GENERIC), I 
 get an error on startup from sysctl, because dev.cpu.0.cx_supported 
 doesn't exist. I think I tracked it down to this update:
 
 Also this error only shows up on startup, it's not in dmesg. Why?
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=1.9r2=1.10f=h

Is this the version you have on 6.2-STABLE? My 6.2-RELEASE box has
version 1.7.2.1, which uses hw.acpi.cpu.cx_supported.

Version 1.9 and 1.10 are in the MAIN branch.

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)


pgpF7DqLSDwHV.pgp
Description: PGP signature


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Bruce M. Simpson

Pete French wrote:

Am trying to solve a little problem with 'pf'. I have a ruleset which
has some firewall rules for the IPv6 interface stf0. This works fine,
except when I rreboot the machine, as the pf script is run before the
network_ipv6 script - so stf0 does not exist. but I cannot work out
how to arrange for stf0 to be created before the pf script is run - as
network_ipv6 requires 'routing', but the pf script says it must be run
before 'routing', if I am reading the 'REQUIRE' and 'BEFORE' lines
correctly.
  

Just chiming in to confirm that this problem definitely exists.
I don't have a solution, however, my IPv6 tunnels at home have all 
expired, so I may well get spare cycles to look at this the same time 
that I get spare cycles to revive the tunnels.


BMS
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Volker
On 12/23/-58 20:59, Pete French wrote:
 Am trying to solve a little problem with 'pf'. I have a ruleset which
 has some firewall rules for the IPv6 interface stf0. This works fine,
 except when I rreboot the machine, as the pf script is run before the
 network_ipv6 script - so stf0 does not exist. but I cannot work out
 how to arrange for stf0 to be created before the pf script is run - as
 network_ipv6 requires 'routing', but the pf script says it must be run
 before 'routing', if I am reading the 'REQUIRE' and 'BEFORE' lines
 correctly.

Pete,

I've played with that problems a few times. It's not a perfect
solution, but you may create your own pf loading script and place it
in /usr/local/etc/rc.d/. To make sure it's running late in startup,
use a proper # REQUIRE: line.

That way (and that what makes me saying it's not perfect) pf load
script /etc/rc.d/pf is being run but aborts loading pf rules in
first place and later (when rc is working though
/usr/local/etc/rc.d/) pf rules are loaded by your custom script.

HTH,

Volker

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Lars Stokholm

Roland Smith wrote:

On Sun, Jan 28, 2007 at 12:14:40PM +0100, Lars Stokholm wrote:

Roland Smith wrote:

On Sun, Jan 28, 2007 at 04:39:29AM +0100, Lars Stokholm wrote:
After updating to 6.2-STABLE Sun Jan 28 02:57:55 CET 2007 (GENERIC), I 
get an error on startup from sysctl, because dev.cpu.0.cx_supported 
doesn't exist. I think I tracked it down to this update:

Also this error only shows up on startup, it's not in dmesg. Why?


http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=1.9r2=1.10f=h


Is this the version you have on 6.2-STABLE? My 6.2-RELEASE box has
version 1.7.2.1, which uses hw.acpi.cpu.cx_supported.

Version 1.9 and 1.10 are in the MAIN branch.


Whoops. I'm using 1.7.2.2, but it's the same:
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?f=hr1=texttr1=1.7.2.1r2=texttr2=1.7.2.2
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Richard Coleman

Bruce M. Simpson wrote:

Pete French wrote:

Am trying to solve a little problem with 'pf'. I have a ruleset which
has some firewall rules for the IPv6 interface stf0. This works fine,
except when I rreboot the machine, as the pf script is run before the
network_ipv6 script - so stf0 does not exist. but I cannot work out
how to arrange for stf0 to be created before the pf script is run - as
network_ipv6 requires 'routing', but the pf script says it must be run
before 'routing', if I am reading the 'REQUIRE' and 'BEFORE' lines
correctly.
  

Just chiming in to confirm that this problem definitely exists.
I don't have a solution, however, my IPv6 tunnels at home have all 
expired, so I may well get spare cycles to look at this the same time 
that I get spare cycles to revive the tunnels.


BMS


Essentially the same problem exists with pf and ppp.  The tun device (on which most of my pf rules 
depend) does not yet exist when pf is started.


Apparently, someone has looked at this before, since there are commands to resync pf and ipf inside 
the rc.d script for ppp (in ppp_postcmd).  But this still doesn't work, since ppp is still 
negotiating the connection when this function is run, so pf fails a second time.  My solution was to 
jam a sleep 15 inside ppp_postcmd() right before the point the commands to reload pf and ipf are 
run.  It's major ugly, but it works.  Hopefully someone will find a better solution to these problems.


Richard Coleman
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Alexey Karagodov

or just make a symlink from /etc/rc.d/pf to /usr/local/etc/rc.d/pf
i solved this way problem with FQDN in pf rules


2007/1/28, Volker [EMAIL PROTECTED]:


On 12/23/-58 20:59, Pete French wrote:
 Am trying to solve a little problem with 'pf'. I have a ruleset which
 has some firewall rules for the IPv6 interface stf0. This works fine,
 except when I rreboot the machine, as the pf script is run before the
 network_ipv6 script - so stf0 does not exist. but I cannot work out
 how to arrange for stf0 to be created before the pf script is run - as
 network_ipv6 requires 'routing', but the pf script says it must be run
 before 'routing', if I am reading the 'REQUIRE' and 'BEFORE' lines
 correctly.

Pete,

I've played with that problems a few times. It's not a perfect
solution, but you may create your own pf loading script and place it
in /usr/local/etc/rc.d/. To make sure it's running late in startup,
use a proper # REQUIRE: line.

That way (and that what makes me saying it's not perfect) pf load
script /etc/rc.d/pf is being run but aborts loading pf rules in
first place and later (when rc is working though
/usr/local/etc/rc.d/) pf rules are loaded by your custom script.

HTH,

Volker

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Volker
On 01/28/07 16:40, Alexey Karagodov wrote:
 2007/1/28, Volker [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]:
 I've played with that problems a few times. It's not a perfect
 solution, but you may create your own pf loading script and place it
 in /usr/local/etc/rc.d/. To make sure it's running late in startup,
 use a proper # REQUIRE: line.
 
 That way (and that what makes me saying it's not perfect) pf load
 script /etc/rc.d/pf is being run but aborts loading pf rules in
 first place and later (when rc is working though
 /usr/local/etc/rc.d/) pf rules are loaded by your custom script.
 
 or just make a symlink from /etc/rc.d/pf to /usr/local/etc/rc.d/pf
 i solved this way problem with FQDN in pf rules


Alexey,

yes, I also did it using a simple symlink in the past but reading
stable@ (or has it been [EMAIL PROTECTED]) it is planned (or already
implemented?) to respect the rcorder for /etc/rc.d/ _and_
/usr/local/etc/rc.d/ in one go.

That means the rcorder is being calculated for both directories in
one step. I suspect when just symlinking an rc-script from
/etc/rc.d/ this might lead into the script being executed two times
in a row. I might be wrong on this but your suggestion is using a
side effect which might not work with all versions.

Greetings,

Volker
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Max Laier
On Sunday 28 January 2007 16:33, Richard Coleman wrote:
 Bruce M. Simpson wrote:
  Pete French wrote:
  Am trying to solve a little problem with 'pf'. I have a ruleset
  which has some firewall rules for the IPv6 interface stf0. This
  works fine, except when I rreboot the machine, as the pf script is
  run before the network_ipv6 script - so stf0 does not exist. but I
  cannot work out how to arrange for stf0 to be created before the pf
  script is run - as network_ipv6 requires 'routing', but the pf
  script says it must be run before 'routing', if I am reading the
  'REQUIRE' and 'BEFORE' lines correctly.
 
  Just chiming in to confirm that this problem definitely exists.
  I don't have a solution, however, my IPv6 tunnels at home have all
  expired, so I may well get spare cycles to look at this the same time
  that I get spare cycles to revive the tunnels.
 
  BMS

 Essentially the same problem exists with pf and ppp.  The tun device
 (on which most of my pf rules depend) does not yet exist when pf is
 started.

 Apparently, someone has looked at this before, since there are commands
 to resync pf and ipf inside the rc.d script for ppp (in ppp_postcmd). 
 But this still doesn't work, since ppp is still negotiating the
 connection when this function is run, so pf fails a second time.  My
 solution was to jam a sleep 15 inside ppp_postcmd() right before the
 point the commands to reload pf and ipf are run.  It's major ugly, but
 it works.  Hopefully someone will find a better solution to these
 problems.

In oder to solve these problems you have to understand why pf is failing.  
This can be for three reasons:

1) You use the interface name as address w/o dynamic lookup.  i.e. ... 
from stf0 ...
2) You use set loginterface sft0
3) You use the interface with ALTQ altq on stf0 ... (now this doesn't 
work and wouldn't be a good idea either, but for tun0 it makes slightly 
more sense).

To 1 and 2 there is a simple sollution: Don't do that then!  1 can easily 
be defused by adding parentheses. i.e. ... from (stf0)   If more 
control is required you have to write explicit addresses in your 
configuration anyway.  2 is obsolete by pfctl -vvsI -i stf0 which has 
all the counters for all the interfaces.  ALTQ is the only remaining 
problem.  I did do some initial patches to tear down altq on interface 
removal, which could be extended to work the other way 'round on 
interface arrival - if only I had more time :-\

-- 
/\  Best regards,  | [EMAIL PROTECTED]
\ /  Max Laier  | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | [EMAIL PROTECTED]
/ \  ASCII Ribbon Campaign  | Against HTML Mail and News


pgppmlwFyq2eY.pgp
Description: PGP signature


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Roland Smith
On Sun, Jan 28, 2007 at 04:54:12PM +0100, Lars Stokholm wrote:
 Whoops. I'm using 1.7.2.2, but it's the same:
 http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?f=hr1=texttr1=1.7.2.1r2=texttr2=1.7.2.2

Looks like this is related to the following CVS commit:
http://lists.freebsd.org/pipermail/cvs-src/2007-January/073402.html 

It looks like these changes are being MFC'd, but maybe your last update hasn't
yet caught all the updated files. Check the files mentioned in the
above commit in RELENG_6. Maybe a renewed csup followed by a
world/kernel build will solve the problem.

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)


pgpAD5ZWFdVa2.pgp
Description: PGP signature


Re: impossible rc.d ordering problem with stf and pf ?

2007-01-28 Thread Richard Coleman

Max Laier wrote:

On Sunday 28 January 2007 16:33, Richard Coleman wrote:

Bruce M. Simpson wrote:

Pete French wrote:

Am trying to solve a little problem with 'pf'. I have a ruleset
which has some firewall rules for the IPv6 interface stf0. This
works fine, except when I rreboot the machine, as the pf script is
run before the network_ipv6 script - so stf0 does not exist. but I
cannot work out how to arrange for stf0 to be created before the pf
script is run - as network_ipv6 requires 'routing', but the pf
script says it must be run before 'routing', if I am reading the
'REQUIRE' and 'BEFORE' lines correctly.

Just chiming in to confirm that this problem definitely exists.
I don't have a solution, however, my IPv6 tunnels at home have all
expired, so I may well get spare cycles to look at this the same time
that I get spare cycles to revive the tunnels.

BMS

Essentially the same problem exists with pf and ppp.  The tun device
(on which most of my pf rules depend) does not yet exist when pf is
started.

Apparently, someone has looked at this before, since there are commands
to resync pf and ipf inside the rc.d script for ppp (in ppp_postcmd). 
But this still doesn't work, since ppp is still negotiating the

connection when this function is run, so pf fails a second time.  My
solution was to jam a sleep 15 inside ppp_postcmd() right before the
point the commands to reload pf and ipf are run.  It's major ugly, but
it works.  Hopefully someone will find a better solution to these
problems.


In oder to solve these problems you have to understand why pf is failing.  
This can be for three reasons:


1) You use the interface name as address w/o dynamic lookup.  i.e. ... 
from stf0 ...

2) You use set loginterface sft0
3) You use the interface with ALTQ altq on stf0 ... (now this doesn't 
work and wouldn't be a good idea either, but for tun0 it makes slightly 
more sense).


To 1 and 2 there is a simple sollution: Don't do that then!  1 can easily 
be defused by adding parentheses. i.e. ... from (stf0)   If more 
control is required you have to write explicit addresses in your 
configuration anyway.  2 is obsolete by pfctl -vvsI -i stf0 which has 
all the counters for all the interfaces.  ALTQ is the only remaining 
problem.  I did do some initial patches to tear down altq on interface 
removal, which could be extended to work the other way 'round on 
interface arrival - if only I had more time :-\


I remember trying a dynamic interface for tun before, and it failed.  But I now see that it was 
because I also use set logininterface.  I didn't think to remove that.  Thanks for the help.  I'll 
give it a try.


Richard Coleman
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Lars Stokholm

Roland Smith wrote:

On Sun, Jan 28, 2007 at 04:54:12PM +0100, Lars Stokholm wrote:

Whoops. I'm using 1.7.2.2, but it's the same:
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?f=hr1=texttr1=1.7.2.1r2=texttr2=1.7.2.2


Looks like this is related to the following CVS commit:
http://lists.freebsd.org/pipermail/cvs-src/2007-January/073402.html 


It looks like these changes are being MFC'd, but maybe your last update hasn't
yet caught all the updated files. Check the files mentioned in the
above commit in RELENG_6. Maybe a renewed csup followed by a
world/kernel build will solve the problem.


Judging from the files updated since the last time, I don't think so:

# csup stable-supfile
Cannot connect to 2001:6c8:0:6::abcd: No route to host
Connected to 193.162.154.98
Updating collection src-all/cvs
 Edit src/sbin/ifconfig/ifieee80211.c
 Edit src/sbin/mount/getmntopts.c
 Edit src/sbin/mount/mntopts.h
 Edit src/sbin/mount/mount.c
 Edit src/sbin/mount_ext2fs/mount_ext2fs.c
 Edit src/share/man/man4/Makefile
 Edit src/share/man/man4/ng_ppp.4
 Edit src/sys/boot/pc98/btx/btx/btx.S
 Edit src/sys/conf/NOTES
 Edit src/sys/conf/files
 Edit src/sys/conf/options
 Edit src/sys/dev/ath/if_ath.c
 Edit src/sys/dev/ath/if_athvar.h
 Edit src/sys/kern/vfs_mount.c
 Edit src/sys/modules/netgraph/Makefile
 Checkout src/sys/modules/netgraph/deflate/Makefile
 Checkout src/sys/modules/netgraph/pred1/Makefile
 Edit src/sys/net80211/_ieee80211.h
 Edit src/sys/net80211/ieee80211.c
 Edit src/sys/net80211/ieee80211_node.c
 Edit src/sys/net80211/ieee80211_output.c
 Edit src/sys/net80211/ieee80211_proto.c
 Edit src/sys/net80211/ieee80211_var.h
 Checkout src/sys/netgraph/ng_deflate.c
 Checkout src/sys/netgraph/ng_deflate.h
 Edit src/sys/netgraph/ng_ppp.c
 Edit src/sys/netgraph/ng_ppp.h
 Checkout src/sys/netgraph/ng_pred1.c
 Checkout src/sys/netgraph/ng_pred1.h
 Edit src/sys/pc98/pc98/machdep.c
 Edit src/sys/sys/param.h
Finished successfully
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Lars Stokholm

Lars Stokholm wrote:

Roland Smith wrote:

On Sun, Jan 28, 2007 at 04:54:12PM +0100, Lars Stokholm wrote:

Whoops. I'm using 1.7.2.2, but it's the same:
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?f=hr1=texttr1=1.7.2.1r2=texttr2=1.7.2.2 


Looks like this is related to the following CVS commit:
http://lists.freebsd.org/pipermail/cvs-src/2007-January/073402.html
It looks like these changes are being MFC'd, but maybe your last 
update hasn't

yet caught all the updated files. Check the files mentioned in the
above commit in RELENG_6. Maybe a renewed csup followed by a
world/kernel build will solve the problem.


Judging from the files updated since the last time, I don't think so:


Damnit, I seem to be making one mistake after another, with no end to 
it. I'm truely sorry for wasting your time. Let's step back to where I 
started; dev.cpu.0.cx_supported *does* exist:


# sysctl dev.cpu.0.cx_supported
dev.cpu.0.cx_supported: C1/0

And here's the problem; this is what I get when I fire up FreeBSD:

...
Starting ums0 moused:.
hw.acpi.cpu.cx_lowest: C1
sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
Mounting NFS file systems:.
...

Taking the power_profile into account, I guess it comes something 
similar to:


# sysctl hw.acpi.cpu.cx_lowest=C1/0
hw.acpi.cpu.cx_lowest: C1
sysctl: hw.acpi.cpu.cx_lowest: Invalid argument

So, finally, the question now is why I get the invalid argument.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ath0: ath_reset: unable to reset hardware; hal status 3

2007-01-28 Thread Sam Leffler
Henrik Brix Andersen wrote:
 Hi all,
 
 I have noticed a problem when using ath(4) as an 802.11g access point
 with hostapd(8) and WPA2-PSK CCMP.
 
 The following problem seems to only occur when a Microsoft Windows XP
 STA connects to the AP in 802.11g mode, my FreeeBSD STAs doesn't seem
 to trigger this:
 
 Jan 28 11:21:07 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 
 4)
 Jan 28 11:21:07 osgiliath kernel: ath0: ath_reset: unable to reset hardware; 
 hal status 3
 Jan 28 11:21:25 osgiliath kernel: ath0: device timeout
 Jan 28 11:21:25 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 
 4)
 Jan 28 11:21:25 osgiliath kernel: ath0: ath_reset: unable to reset hardware; 
 hal status 3
 Jan 28 11:21:37 osgiliath kernel: ath0: device timeout
 Jan 28 11:21:38 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 
 4)
 Jan 28 11:21:38 osgiliath kernel: ath0: ath_reset: unable to reset hardware; 
 hal status 3
 Jan 28 11:21:46 osgiliath kernel: ath0: device timeout
 
 This is FreeBSD RELENG_6 (nanoBSD) as of yesterday with the new
 ath_hal(4) running on a Soekris net4801-50:
 
 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
 ath0: Atheros 5212 mem 0xa001-0xa001 irq 11 at device 14.0 on pci0
 ath0: Ethernet address: 00:05:4e:42:e8:7c
 ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3
 
 The same problem occured with version 0.9.17.2 of ath_hal(4).
 
 I have increased the RX/TX buffers in ath(4) as shown in this snippet
 from my kernel configuration:
 
 deviceath
 deviceath_hal
 deviceath_rate_sample
 
 options   ATH_RXBUF=80
 options   ATH_TXBUF=200
 
 The only way I can get the AP running again after the above messages
 to syslog is to reboot it. The problem doesn't seem to occur in
 802.11b mode nor in 802.11g mode with only FreeBSD STAs.
 
 Any help in debugging this will be appreciated.

I take it you tried ifconfig'ing the interface down and up?

The output of athstats at the point where things are wedged might be
useful.  Also verify if only tx is wedged (e.g. athstats 1 will show you
if you're receiving frames).

The fact that the card cannot be reset seems to imply the mac is somehow
locked up.  I vaguely recall some h/w issues like this on older cards
(and you are using a rather old card) but nothing that wasn't handled by
doing a reset operation.  Best suggestion I can make is to use a
different model card.

Sam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SPARC64: Can't upgrade from 6.1 to 6.2 due to binutils

2007-01-28 Thread Oliver Fromme
Matthew Herzog wrote:
  I have never been able to upgrade Sparc64 from source.

Then you must be doing something wrong.

  I suspect it is nearly impossible.

Certainly not.  Works perfectly fine for me, just the same
as FreeBSD/i386.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH  Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783
Any opinions expressed in this message are personal to the author and may
not necessarily reflect the opinions of secnetix GmbH  Co KG in any way.
FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

'Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.'
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Roland Smith
On Sun, Jan 28, 2007 at 07:26:00PM +0100, Lars Stokholm wrote:
 
 Damnit, I seem to be making one mistake after another, with no end to 
 it. I'm truely sorry for wasting your time. 

Been there, done that. A lot of times when I had a problem with the base
system (from 5.3-RELEASE uptil now) it turned out to be pilot error.

 Let's step back to where I 
 started; dev.cpu.0.cx_supported *does* exist:
 
 # sysctl dev.cpu.0.cx_supported
 dev.cpu.0.cx_supported: C1/0
 
 And here's the problem; this is what I get when I fire up FreeBSD:
 
 ...
 Starting ums0 moused:.
 hw.acpi.cpu.cx_lowest: C1
 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
 Mounting NFS file systems:.
 ...
 
 Taking the power_profile into account, I guess it comes something 
 similar to:
 
 # sysctl hw.acpi.cpu.cx_lowest=C1/0

I'm not sure that this is what is being called. The '/0' is removed by awk:

$ sysctl -n hw.acpi.cpu.cx_supported
C1/0
$ sysctl -n hw.acpi.cpu.cx_supported |awk '{ print C split($0, a) }' - 
2/dev/null
C1

 hw.acpi.cpu.cx_lowest: C1
 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument

Works fine here:

# sysctl hw.acpi.cpu.cx_lowest=C1/0
hw.acpi.cpu.cx_lowest: C1 - C1

 So, finally, the question now is why I get the invalid argument.

The only thing I can think of is that you've defined
performance_cx_lowest or economy_cx_lowest to some bogus value in rc.conf.

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)


pgpg0hSDD2GZF.pgp
Description: PGP signature


Re: rd.d/power_profile: dev.cpu.0.cx_supported doesn't exist

2007-01-28 Thread Lars Stokholm

Roland Smith wrote:

On Sun, Jan 28, 2007 at 07:26:00PM +0100, Lars Stokholm wrote:

hw.acpi.cpu.cx_lowest: C1
sysctl: hw.acpi.cpu.cx_lowest: Invalid argument


Works fine here:

# sysctl hw.acpi.cpu.cx_lowest=C1/0
hw.acpi.cpu.cx_lowest: C1 - C1


# sysctl hw.acpi.cpu.cx_lowest=C1/0
hw.acpi.cpu.cx_lowest: C1
sysctl: hw.acpi.cpu.cx_lowest: Invalid argument

# sysctl hw.acpi.cpu.cx_lowest=C1
hw.acpi.cpu.cx_lowest: C1
sysctl: hw.acpi.cpu.cx_lowest: Invalid argument


So, finally, the question now is why I get the invalid argument.


The only thing I can think of is that you've defined
performance_cx_lowest or economy_cx_lowest to some bogus value in rc.conf.


Nope, I haven't touched anything like that. In fact this is a fairly 
clean install of FreeBSD. I haven't messed a lot around with anything. 
In /etc/defaults/rc.conf they're:


performance_cx_lowest=HIGH# Online CPU idle state
economy_cx_lowest=HIGH# Offline CPU idle state
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


buildkernel (zlib module) broken?

2007-01-28 Thread Harald Schmalzbauer
Hello,

I don't understand this error:
=== zlib (all)
cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -Werror -D_KERNEL 
-DKLD_MODULE -nostdinc -I-   -DHAVE_KERNEL_OPTION_HEADERS -include 
/FlashBSD/obj/i686/FlashBSD/src/sys/i686.intern-korso/opt_global.h -I. -I@ 
-I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g 
-I/FlashBSD/obj/i686/FlashBSD/src/sys/i686.intern-korso -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -c /FlashBSD/src/sys/modules/zlib/../../net/zlib.c
ld  -d -warn-common -r -d -o zlib.kld zlib.o
: export_syms
awk -f /FlashBSD/src/sys/modules/zlib/../../conf/kmod_syms.awk zlib.kld  
export_syms | xargs -J% objcopy % zlib.kld
ld -Bshareable  -d -warn-common -o zlib.ko.debug zlib.kld
objcopy --strip-debug zlib.ko.debug zlib.ko
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2

Any hints?

Thanks,

-Harry
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildkernel (zlib module) broken?

2007-01-28 Thread Kris Kennaway
On Sun, Jan 28, 2007 at 10:12:26PM +0100, Harald Schmalzbauer wrote:
 Hello,
 
 I don't understand this error:
 === zlib (all)
 cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -Werror -D_KERNEL 
 -DKLD_MODULE -nostdinc -I-   -DHAVE_KERNEL_OPTION_HEADERS -include 
 /FlashBSD/obj/i686/FlashBSD/src/sys/i686.intern-korso/opt_global.h -I. -I@ 
 -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g 
 -I/FlashBSD/obj/i686/FlashBSD/src/sys/i686.intern-korso 
 -mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow 
 -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs 
 -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
 -Wcast-qual  -fformat-extensions -std=c99 -c 
 /FlashBSD/src/sys/modules/zlib/../../net/zlib.c
 ld  -d -warn-common -r -d -o zlib.kld zlib.o
 : export_syms
 awk -f /FlashBSD/src/sys/modules/zlib/../../conf/kmod_syms.awk zlib.kld  
 export_syms | xargs -J% objcopy % zlib.kld
 ld -Bshareable  -d -warn-common -o zlib.ko.debug zlib.kld
 objcopy --strip-debug zlib.ko.debug zlib.ko
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 
 Any hints?

Rerun make without -j and discover the real error which was some
distance back in the interleaved output from your parallel make
command.

kris


pgpo0Y8U1EiRg.pgp
Description: PGP signature


buildworld: make: don't know how to make ng_deflate.4

2007-01-28 Thread Lars Stokholm

Result of 'make buildworld':

gzip -cn /usr/src/share/man/man4/ng_cisco.4  ng_cisco.4.gz
make: don't know how to make ng_deflate.4. Stop
*** Error code 2

My guess is, that it's caused by this commit:
http://lists.freebsd.org/pipermail/cvs-all/2007-January/205804.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Rejected posting to [EMAIL PROTECTED]

2007-01-28 Thread L-Soft list server at LISTS.WAYNE.EDU (1.8d)
You are  not authorized to send  mail to the SOCIAL_WORK_ALUMNI  list from your
freebsd-stable@FREEBSD.ORG account. You might be authorized to send to the list
from another of your accounts, or perhaps when using another mail program which
generates slightly  different addresses, but  LISTSERV has no way  to associate
this other account or address with yours. If you need assistance or if you have
any  question  regarding the  policy  of  the SOCIAL_WORK_ALUMNI  list,  please
contact the list owners: [EMAIL PROTECTED]

 Rejected message (79 lines) --
Received: from mirapointmr3.wayne.edu (IDENT:[EMAIL PROTECTED] [141.217.1.113])
by lists.wayne.edu (8.13.8+Sun/8.13.8) with ESMTP id l0SNCg91005745
for [EMAIL PROTECTED]; Sun, 28 Jan 2007 18:12:42 -0500 (EST)
Received: from omta03ps.mx.bigpond.com (omta03ps.mx.bigpond.com 
[144.140.82.155])
by mirapointmr3.wayne.edu (MOS 3.7.5-GA)
with ESMTP id DEE31974;
Sun, 28 Jan 2007 18:12:40 -0500 (EST)
Received: from oaamta03ps.mx.bigpond.com ([124.178.38.141])
  by omta03ps.mx.bigpond.com with ESMTP
  id [EMAIL PROTECTED]
  for [EMAIL PROTECTED];
  Sun, 28 Jan 2007 23:12:39 +
Received: from freebsd.org ([124.178.38.141]) by oaamta03ps.mx.bigpond.com
  with ESMTP
  id [EMAIL PROTECTED]
  for [EMAIL PROTECTED];
  Sun, 28 Jan 2007 23:12:27 +
From: freebsd-stable@freebsd.org
To: [EMAIL PROTECTED]
Subject: Mail System Error - Returned Mail
Date: Mon, 29 Jan 2007 10:10:58 +1100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.
Message-Id: [EMAIL PROTECTED]
Content-Type: multipart/mixed; boundary=MIRAPOINT_PART1_45bd2dea
X-Mirapoint-Virus: VIRUSDELETED;
host=mirapointmr3.wayne.edu;
attachment=[2.2];
virus=W32/MyDoom-O
X-Junkmail-Status: score=10/60, host=mirapointmr3.wayne.edu
X-Junkmail-SD-Raw: score=unknown,
refid=str=0001.0A090208.45BD2DE9.006E,ss=1,fgs=0,
ip=144.140.82.155,
so=2006-03-30 10:46:40,
dmn=5.2.125/2006-10-10

This is a multi-part message in MIME format.

--MIRAPOINT_PART1_45bd2dea
Content-Type: text/plain

WARNING!!! (from mirapointmr3.wayne.edu)

The following message attachments were flagged by the antivirus scanner:

Attachment [2.2] file.zip, virus infected: W32/MyDoom-O.  Action taken: deleted

--MIRAPOINT_PART1_45bd2dea
Content-Type: multipart/mixed;
boundary==_NextPart_000_0014_3CA2273D.CE1A9DA7

--=_NextPart_000_0014_3CA2273D.CE1A9DA7
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit

The original message was received at Mon, 29 Jan 2007 10:10:58 +1100
from freebsd.org [219.243.90.59]

- The following addresses had permanent fatal errors -
[EMAIL PROTECTED]




--=_NextPart_000_0014_3CA2273D.CE1A9DA7
Content-Type: text/plain

VIRUS WARNING Message (from mirapointmr3.wayne.edu)

The virus W32/MyDoom-O was detected in email attachment [2.2] file.zip.  The 
infected attachment has been deleted.

--=_NextPart_000_0014_3CA2273D.CE1A9DA7--

--MIRAPOINT_PART1_45bd2dea--

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ath buildkernel problem with recent RELENG_6 [Was: Re: buildkernel (zlib module) broken?]

2007-01-28 Thread Harald Schmalzbauer
Am Sonntag, 28. Januar 2007 23:17 schrieb Kris Kennaway:
 On Sun, Jan 28, 2007 at 10:12:26PM +0100, Harald Schmalzbauer wrote:
  Hello,
 
  I don't understand this error:
  === zlib (all)
[...]
  1 error
  *** Error code 2
 
  Any hints?

 Rerun make without -j and discover the real error which was some
 distance back in the interleaved output from your parallel make
 command.

Ahh, ok, sorry, it's my first SMP system so I'm not used to this parallel 
build stuff...

ath seems to be the problem:
MAKE=/FlashBSD/obj/i686/FlashBSD/src/make.i386/make 
sh /FlashBSD/src/sys/conf/newvers.sh CUV-LV
cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. -I/FlashBSD/src/sys 
-I/FlashBSD/src/sys/contrib/altq -I/FlashBSD/src/sys/contrib/ipfilter 
-I/FlashBSD/src/sys/contrib/pf -I/FlashBSD/src/sys/dev/ath 
-I/FlashBSD/src/sys/contrib/ngatm -I/FlashBSD/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=8000 --param 
inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  
vers.c
linking kernel.debug
sample.o(.text+0x1a3a): In function `ath_rate_newstate':
/FlashBSD/src/sys/dev/ath/ath_rate/sample/sample.c:803: undefined reference to 
`ieee80211_iterate_nodes'
if_ath.o(.text+0x53c): In function `ath_attach':
/FlashBSD/src/sys/dev/ath/if_ath.c:417: undefined reference to 
`ieee80211_wme_acnames'
if_ath.o(.text+0xb92):/FlashBSD/src/sys/dev/ath/if_ath.c:599: undefined 
reference to `ieee80211_ifattach'
if_ath.o(.text+0xc3e):/FlashBSD/src/sys/dev/ath/if_ath.c:617: undefined 
reference to `ieee80211_media_status'
if_ath.o(.text+0xc4e):/FlashBSD/src/sys/dev/ath/if_ath.c:617: undefined 
reference to `ieee80211_media_init'
if_ath.o(.text+0xc72):/FlashBSD/src/sys/dev/ath/if_ath.c:627: undefined 
reference to `ieee80211_announce'
if_ath.o(.text+0xcf7): In function `ath_detach':
/FlashBSD/src/sys/dev/ath/if_ath.c:664: undefined reference to 
`ieee80211_ifdetach'
if_ath.o(.text+0x11af): In function `ath_bmiss_proc':
/FlashBSD/src/sys/dev/ath/if_ath.c:877: undefined reference to 
`ieee80211_beacon_miss'
if_ath.o(.text+0x1239): In function `ath_mapchan':
/FlashBSD/src/sys/dev/ath/if_ath.c:903: undefined reference to 
`ieee80211_chan2mode'
if_ath.o(.text+0x1fef): In function `ath_start':
/FlashBSD/src/sys/dev/ath/if_ath.c:1205: undefined reference to 
`ieee80211_find_txnode'
if_ath.o(.text+0x2025):/FlashBSD/src/sys/dev/ath/if_ath.c:1218: undefined 
reference to `ieee80211_pwrsave'
if_ath.o(.text+0x2042):/FlashBSD/src/sys/dev/ath/if_ath.c:1222: undefined 
reference to `ieee80211_classify'
if_ath.o(.text+0x2092):/FlashBSD/src/sys/dev/ath/if_ath.c:1234: undefined 
reference to `ieee80211_encap'
if_ath.o(.text+0x21d1):/FlashBSD/src/sys/dev/ath/if_ath.c:1280: undefined 
reference to `ieee80211_free_node'
if_ath.o(.text+0x220e): In function `ath_media_change':
/FlashBSD/src/sys/dev/ath/if_ath.c:1296: undefined reference to 
`ieee80211_media_change'
if_ath.o(.text+0x3016): In function `ath_beacon_alloc':
/FlashBSD/src/sys/dev/ath/if_ath.c:1987: undefined reference to 
`ieee80211_beacon_alloc'
if_ath.o(.text+0x336e): In function `ath_beacon_proc':
/FlashBSD/src/sys/dev/ath/if_ath.c:2155: undefined reference to 
`ieee80211_beacon_update'
if_ath.o(.text+0x374f): In function `ath_beacon_free':
/FlashBSD/src/sys/dev/ath/if_ath.c:2289: undefined reference to 
`ieee80211_free_node'
if_ath.o(.text+0x3ef2): In function `ath_descdma_cleanup':
/FlashBSD/src/sys/dev/ath/if_ath.c:2624: undefined reference to 
`ieee80211_free_node'
if_ath.o(.text+0x412b): In function `ath_node_alloc':
/FlashBSD/src/sys/dev/ath/if_ath.c:2680: undefined reference to `M_80211_NODE'
if_ath.o(.text+0x44bc): In function `ath_recv_mgmt':
/FlashBSD/src/sys/dev/ath/if_ath.c:2858: undefined reference to 
`ieee80211_ibss_merge'
if_ath.o(.text+0x48ea): In function `ath_rx_proc':
/FlashBSD/src/sys/dev/ath/if_ath.c:3036: undefined reference to 
`ieee80211_notify_michael_failure'
if_ath.o(.text+0x4a87):/FlashBSD/src/sys/dev/ath/if_ath.c:3100: undefined 
reference to `ieee80211_dump_pkt'
if_ath.o(.text+0x4ac7):/FlashBSD/src/sys/dev/ath/if_ath.c:3112: undefined 
reference to `ieee80211_find_rxnode_withkey'
if_ath.o(.text+0x4b82):/FlashBSD/src/sys/dev/ath/if_ath.c:3125: undefined 
reference to `ieee80211_input'
if_ath.o(.text+0x4b8d):/FlashBSD/src/sys/dev/ath/if_ath.c:3126: undefined 
reference to `ieee80211_free_node'
if_ath.o(.text+0x4fb4): In function `ath_txq_update':
/FlashBSD/src/sys/dev/ath/if_ath.c:3286: undefined reference to 
`ieee80211_wme_acnames'
if_ath.o(.text+0x57c0): In function `ath_tx_start':
/FlashBSD/src/sys/dev/ath/if_ath.c:3598: undefined reference to 
`ieee80211_crypto_encap'
if_ath.o(.text+0x5814):/FlashBSD/src/sys/dev/ath/if_ath.c:3626: 

Re: ath buildkernel problem with recent RELENG_6 [Was: Re: buildkernel (zlib module) broken?]

2007-01-28 Thread Kris Kennaway
On Mon, Jan 29, 2007 at 01:02:32AM +0100, Harald Schmalzbauer wrote:
 Am Sonntag, 28. Januar 2007 23:17 schrieb Kris Kennaway:
  On Sun, Jan 28, 2007 at 10:12:26PM +0100, Harald Schmalzbauer wrote:
   Hello,
  
   I don't understand this error:
   === zlib (all)
 [...]
   1 error
   *** Error code 2
  
   Any hints?
 
  Rerun make without -j and discover the real error which was some
  distance back in the interleaved output from your parallel make
  command.
 
 Ahh, ok, sorry, it's my first SMP system so I'm not used to this parallel 
 build stuff...
 
 ath seems to be the problem:

No, your kernel config is the problem ;) You apparently chopped out
too much when cutting it down from GENERIC.

 /FlashBSD/src/sys/dev/ath/if_ath.c:417: undefined reference to 
 `ieee80211_wme_acnames'

Undefined reference almost always means operator provided an
incomplete kernel config file.

Kris


pgpwC97IBmhiv.pgp
Description: PGP signature


Re: ath buildkernel problem with recent RELENG_6 [Was: Re: buildkernel (zlib module) broken?]

2007-01-28 Thread Sam Leffler
Kris Kennaway wrote:
 On Mon, Jan 29, 2007 at 01:02:32AM +0100, Harald Schmalzbauer wrote:
 Am Sonntag, 28. Januar 2007 23:17 schrieb Kris Kennaway:
 On Sun, Jan 28, 2007 at 10:12:26PM +0100, Harald Schmalzbauer wrote:
 Hello,

 I don't understand this error:
 === zlib (all)
 [...]
 1 error
 *** Error code 2

 Any hints?
 Rerun make without -j and discover the real error which was some
 distance back in the interleaved output from your parallel make
 command.
 Ahh, ok, sorry, it's my first SMP system so I'm not used to this parallel 
 build stuff...

 ath seems to be the problem:
 
 No, your kernel config is the problem ;) You apparently chopped out
 too much when cutting it down from GENERIC.
 
 /FlashBSD/src/sys/dev/ath/if_ath.c:417: undefined reference to 
 `ieee80211_wme_acnames'
 
 Undefined reference almost always means operator provided an
 incomplete kernel config file.

man ath shows:

  To compile this driver into the kernel, place the following lines in your
  kernel configuration file:
 
device ath
device ath_hal
device ath_rate_sample
device wlan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: arp: unknown hardware address format

2007-01-28 Thread Adrian Chadd

On 24/01/07, Ilia Gorstkin [EMAIL PROTECTED] wrote:

Hi all!

FreeBSD 6.2-release.
 I'm having trouble with arp:
arp: unknown hardware address format (0x4500)
and
arp: unknown hardware address format (0x4242)
these messages fall on the console in a plenty.


What kind of device is this? Is it a Linux server?

I get the 0x4500 packets all the time from my Linux servers.


Adrian

--
Adrian Chadd - [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ath buildkernel problem with recent RELENG_6 [Was: Re: buildkernel (zlib module) broken?]

2007-01-28 Thread Harald Schmalzbauer
Am Sun, 28 Jan 2007 19:09:02 -0800
schrieb Sam Leffler [EMAIL PROTECTED]:

 Kris Kennaway wrote:
  On Mon, Jan 29, 2007 at 01:02:32AM +0100, Harald Schmalzbauer wrote:
[...]
  ath seems to be the problem:
  
  No, your kernel config is the problem ;) You apparently chopped out
  too much when cutting it down from GENERIC.
  
  /FlashBSD/src/sys/dev/ath/if_ath.c:417: undefined reference to 
  `ieee80211_wme_acnames'
  
  Undefined reference almost always means operator provided an
  incomplete kernel config file.
 
 man ath shows:
 

Sorry, my stupid ;)
I missed that ath was added to generic so my 'nodevice wlan' of course
can't work with new GENERIC.

Sorry for the noise,

-Harry
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


New IPv6 LOR in 6.2-RELEASE

2007-01-28 Thread Peter Losher
FYI: saw this when upgrading one of my boxes (quad-cpu Opteron, 2GB of
RAM) to 6.2-RELEASE:

 Firewall logging enabled
 net.inet.ip.fw.enable: 1 - 1
 lock order reversal:
  1st 0xff00b79c3cc8 inp (raw6inp) @
/usr/src/sys/netinet6/raw_ip6.c:153
  2nd 0xff00b79c3df8 inp (rawinp) @ /usr/src/sys/netinet6/raw_ip6.c:153
 KDB: stack backtrace:
 witness_checkorder() at 0x8042a12a = witness_checkorder+0x4da
 _mtx_lock_flags() at 0x803f4e3c = _mtx_lock_flags+0x5c
 rip6_input() at 0x804ed15e = rip6_input+0x9e
 ip6_input() at 0x804dd288 = ip6_input+0x838
 netisr_processqueue() at 0x80489a07 = netisr_processqueue+0x17
 swi_net() at 0x80489cf6 = swi_net+0x116
 ithread_loop() at 0x803e6f5c = ithread_loop+0x14c
 fork_exit() at 0x803e5cab = fork_exit+0xbb
 fork_trampoline() at 0x805f82ee = fork_trampoline+0xe
 --- trap 0, rip = 0, rsp = 0xb3a43d00, rbp = 0 ---
 Mounting NFS file systems:.
 Limiting icmp unreach response from 262 to 200 packets/sec
 Expensive timeout(9) function: 0x80ba8da0(0) 0.069698243 s

-Peter
-- 
[ http://www.plosh.net/ ] - Earth Halted: Please reboot to continue
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 6.1BETA3 amd64 doesn't detect my floppy drive

2007-01-28 Thread Daniel O'Connor
On Thursday 09 March 2006 12:11, Daniel O'Connor wrote:
 On Tuesday 07 March 2006 09:22, M. Warner Losh wrote:
  Maybe the output of size kernel?

textdata bss dec hex filename
 3069343  305288  212944 3587575  36bdf7 /boot/kernel/kernel (6.0-RC1 custom) 
 5746665  702632  389712 6839009  685ae1 /boot/kernel/kernel (6.1-BETA3) 
 5146715  672352  348688 6167755  5e1ccb /boot/kernel/kernel (5.4-RELEASE)

GENERIC in 6.2 has the same problem.
I trimmed it down (substantially) and my floppy drive is detected again.

This is on a Supermicro P8SCT board with a P4-531 vs the Athlon64 system I saw 
it on before - both are amd64 kernels though.

This kernel works.. (trimmed heavily)
   textdata bss dec hex filename
4433534  617512  271328 5322374  513686 kernel

This one doesn't.. (some stuff added back)
   textdata bss dec hex filename
4709507  651688  278624 5639819  560e8b kernel

This one does.. (no Firewire, with USB)
   textdata bss dec hex filename
4622780  643624  278496 5544900  549bc4 kernel

This one does.. (no USB, with Firewire)
   textdata bss dec hex filename
4520517  625576  271456 5417549  52aa4d kernel

I did the USB/Firewire thing just to make sure one wasn't  the direct cause.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpGuF98gv1iF.pgp
Description: PGP signature


6.2 bge regression

2007-01-28 Thread Daniel O'Connor
I have some Supermicro P8SCT based systems I would like to run 6.2 on,
unfortunately something between 6.1 and 6.2 has broken bge on this board.

This board has 2 bge's and the first one is on before the BIOS hands off to
the OS (I can see the activity light flash) but when the kernel attaches the
light stops flashing. An ifconfig says 'no carrier'.

bge0: Broadcom BCM5721 Gigabit Ethernet, ASIC rev. 0x4101 mem 
0xd100-0xd100 irq 16 at device 0.0 on pci3
miibus0: MII bus on bge0
brgphy0: BCM5750 10/100/1000baseTX PHY on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
bge0: Ethernet address: 00:30:48:89:be:5c
pcib4: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0
pci4: ACPI PCI bus on pcib4
bge1: Broadcom BCM5721 Gigabit Ethernet, ASIC rev. 0x4101 mem 
0xd110-0xd110 irq 17 at device 0.0 on pci4
miibus1: MII bus on bge1
brgphy1: BCM5750 10/100/1000baseTX PHY on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
bge1: Ethernet address: 00:30:48:89:be:5d

From pciconf..
[EMAIL PROTECTED]:0:0:  class=0x02 card=0x02c615d9 chip=0x165914e4 rev=0x11 
hdr=0x00
[EMAIL PROTECTED]:0:0:  class=0x02 card=0x02c615d9 chip=0x165914e4 rev=0x11 
hdr=0x00

This system was updated using CVS so it's really 6.2-PRERELEASE, I am about
to try updating again to RELENG_6 and seeing if I was perhaps out of sync.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpLOIHsAga7u.pgp
Description: PGP signature


Re: 6.2 bge regression

2007-01-28 Thread LI Xin
Hi, Daniel,

Daniel O'Connor wrote:
 I have some Supermicro P8SCT based systems I would like to run 6.2 on,
 unfortunately something between 6.1 and 6.2 has broken bge on this board.
 
 This board has 2 bge's and the first one is on before the BIOS hands off to
 the OS (I can see the activity light flash) but when the kernel attaches the
 light stops flashing. An ifconfig says 'no carrier'.
 
 bge0: Broadcom BCM5721 Gigabit Ethernet, ASIC rev. 0x4101 mem 
 0xd100-0xd100 irq 16 at device 0.0 on pci3
 miibus0: MII bus on bge0
 brgphy0: BCM5750 10/100/1000baseTX PHY on miibus0
 brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
 1000baseTX-FDX, auto
 bge0: Ethernet address: 00:30:48:89:be:5c
 pcib4: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0
 pci4: ACPI PCI bus on pcib4
 bge1: Broadcom BCM5721 Gigabit Ethernet, ASIC rev. 0x4101 mem 
 0xd110-0xd110 irq 17 at device 0.0 on pci4
 miibus1: MII bus on bge1
 brgphy1: BCM5750 10/100/1000baseTX PHY on miibus1
 brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
 1000baseTX-FDX, auto
 bge1: Ethernet address: 00:30:48:89:be:5d
 
 From pciconf..
 [EMAIL PROTECTED]:0:0:  class=0x02 card=0x02c615d9 chip=0x165914e4 
 rev=0x11 hdr=0x00
 [EMAIL PROTECTED]:0:0:  class=0x02 card=0x02c615d9 chip=0x165914e4 
 rev=0x11 hdr=0x00
 
 This system was updated using CVS so it's really 6.2-PRERELEASE, I am about
 to try updating again to RELENG_6 and seeing if I was perhaps out of sync.

There is no difference between RELENG_6_2 and RELENG_6, so I think you
should expect no change.  I have backported some interesting changes
against bge(4) here:

http://people.freebsd.org/~delphij/misc/patch-bge-releng62

You may try it out to see if things gets improved, but I am not very
confident about that, because the changes are mostly unrelated to
BCM5752.  Also, we would appreciate if you could help to test if the
latest -CURRENT snapshot can make your NIC to work correctly, because it
looks like that we need a more complete MFC of the bge(4) changes, not
just the ones I have chosen (for my personal needs).

Cheers,
-- 
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature