Re: Recent HEAD: buildworld is broken with clang

2011-08-15 Thread Oleg V. Nauman

Quoting Garrett Cooper yaneg...@gmail.com:


On Aug 14, 2011, at 11:58 AM, Oleg V. Nauman o...@opentransfer.com wrote:

...

There was an issue with file descriptor handling introduced with the  
capsicum work. Please update your src, rebuild your kernel, install,  
or use an older kernel, and try again.


 Thanks. Installing the new kernel fixes the issue so I was able to  
complete buildworld.



-Garrett



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


Re: duplicate output when dumping from ddb

2011-08-15 Thread Sergey Kandaurov
On 10 August 2011 23:04, Navdeep Parhar npar...@gmail.com wrote:
 dump or call doadump from within ddb display duplicate output.
 This is with a serial console.  I have  console=comconsole,vidconsole
 in /boot/loader.conf and  -D -S115200  in /boot.config.

 db dump
 Dumping 1883 out of 12255 MB:Dumping 1883 out of 12255
 MB:..1%..1%..11%..11%..21%..21%..31%..31%..41%..41%..51%..51%..61%..61%..71%..71%..81%..81%..91%..91%

 Dump complete
 Dump complete
 db

 Something seems to have changed in the last couple of months or so.


Just to confirm with my Same here. I use a serial console with same
settings, too. I am out of ideas how to fix it though.

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


Re: buildworld failure

2011-08-15 Thread Alexander Best
On Mon Aug 15 11, Robert Watson wrote:
 
 On Sun, 14 Aug 2011, Alexander Best wrote:
 
 has anybody seen this buildworld failure?
 
 Could you try the attached patch and see if it helps?  I currently have it 
 in the re@ approval queue.  It does appear to fix the problem here.

thanks. the patch fixes the issue.

 
 Generally, I would strongly advise against using modules built with world, 
 and wonder if we should be de-supporting that explicitly at this point.  
 Checking that the below works for you would be great, but you might not 
 want to use MODULES_WITH_WORLD anymore.

usually i set MODULES_OVERRIDE =, because i don't have time to wait for
buildkernel compiling all the modules. however i thought it might be handy
to have the kernel modules available, so i set MODULES_WITH_WORLD instead.
of course i know that building/installing a new kernel and keeping the old
modules is not really a great idea, because quite often the outdated modules
will fail to load.

yet for me it's a timer saver and still gives me the option of loading a
certain module.

so personally i'd like to see MODULES_WITH_WORLD support stay. but if people
decide it should go then that's not too much of a problem with me. ;)

cheers.
alex

 
 (If we do want to keep MODULES_WITH_WORLD, we may want to add it to the 
 tinderboxes.)
 
 Robert
 
 --
 
 Fix two cases involving opt_capsicum.h and module builds:
 
 (1) opt_capsicum.h is no longer required in ffs_alloc.c, so remove the
 #include.
 
 (2) portalfs depends on opt_capsicum.h, so have the Makefile generate one
 if required.
 
 Note, however, that attempting to use modules built without a kernel
 configuration is a bad idea generally -- it's a bit worrying that we still
 provide MODULES_WITH_WORLD.
 
 Approved by:  re (xxx)
 Sponsored by: Google Inc
 
 Index: ufs/ffs/ffs_alloc.c
 ===
 --- ufs/ffs/ffs_alloc.c   (revision 224860)
 +++ ufs/ffs/ffs_alloc.c   (working copy)
 @@ -62,7 +62,6 @@
  #include sys/cdefs.h
  __FBSDID($FreeBSD$);
 
 -#include opt_capsicum.h
  #include opt_quota.h
 
  #include sys/param.h
 Index: modules/portalfs/Makefile
 ===
 --- modules/portalfs/Makefile (revision 224860)
 +++ modules/portalfs/Makefile (working copy)
 @@ -4,6 +4,7 @@
 
  KMOD=portalfs
  SRCS=vnode_if.h \
 - portal_vfsops.c portal_vnops.c
 + portal_vfsops.c portal_vnops.c \
 + opt_capsicum.h
 
  .include bsd.kmod.mk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: duplicate output when dumping from ddb

2011-08-15 Thread Andriy Gapon
on 15/08/2011 13:24 Sergey Kandaurov said the following:
 On 10 August 2011 23:04, Navdeep Parhar npar...@gmail.com wrote:
 dump or call doadump from within ddb display duplicate output.
 This is with a serial console.  I have  console=comconsole,vidconsole
 in /boot/loader.conf and  -D -S115200  in /boot.config.

 db dump
 Dumping 1883 out of 12255 MB:Dumping 1883 out of 12255
 MB:..1%..1%..11%..11%..21%..21%..31%..31%..41%..41%..51%..51%..61%..61%..71%..71%..81%..81%..91%..91%

 Dump complete
 Dump complete
 db

 Something seems to have changed in the last couple of months or so.

 
 Just to confirm with my Same here. I use a serial console with same
 settings, too. I am out of ideas how to fix it though.
 

Let me try to guess... do you have PRINTF_BUFR_SIZE defined?
If you look at vprintf() in sys/kern/subr_prf.c, then it's possible that one
message is printed by putchar() repeatedly called in kvprintf and the duplicate
message is printed by cnputs() under PRINTF_BUFR_SIZE.

Indeed, pca.flags is set to TOCONS | TOLOG in vprintf(), so putchar() would
output a character (via cnputc) when kdb_active is true and also it would add 
the
character to a buffer (via putbuf), because TOLOG is set.

Maybe try to add !kdb_active condition for cnputs() call in vprintf().
-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Loading drivers via kldload

2011-08-15 Thread Andriy Gapon
on 13/08/2011 00:20 David Somayajulu said the following:
 This is pretty bizarre. I have been experimenting with a very simple driver
 (see source below) which essentially checks the PCI vendor and Device ID's in
 the probe routine. The attach and detach are empty functions. When I run
 kldload and load the driver in a system with HBAs which have a valid Subsytem
 Vendor and Device ID's, the driver loads and attaches to the functions.
 
 However when the Subsystem Vendor and Device ID's are zero, the system panics
 and the stack trace is as shown below(FreeBSD 8.2 on amd64 machine). I don't
 understand why ata_pci_attach() is getting invoked.

This is because ata_pci_probe returns BUS_PROBE_GENERIC for any pci device that
has PCIC_STORAGE class and PCIS_STORAGE_IDE subclass.  So I'd guess that it 
tries
to attach to your non-trivial hardware in this case and gets some incorrect
resource configuration (e.g. BARs) from the hardware.

Whether we actually have to panic in such situation is a different question.

 I even put a panic() call
 at the top of qla_pci_probe(), and noticed that it wasn't getting invoked!
 
 
 == panic: resource_list_alloc: resource_ entry is busy
 
 0x805F4E0E  at kdb_backtrace+0x5E 0x805C2D07  at
 panic+0x187 0x805F0616  at resource_list_alloc+0x1C6 
 0x804450F7  at pci_alloc_resource+0x147 0x805F0439  at
 bus_alloc_resource+0x89 0x8027A467  at ata_pci_attach+0xE7 
 0x805EEA09  at device_attach+0x69 0x80447ACA  at
 pci_driver_added+0xDA 0x805ECD55  at devclass_driver_added+0x75 
 0x805EE715  at driver_module_handler+0x165 0x805B24B8
 at module_register_init+0xB8 0x805AADB6  at
 linker_load_module+0x996 0x805AB6C4  at kern_kldload+0xB4 
 0x805AB894  at kldload+0x84 0x80600DD5  at
 syscallenter+0x1E5 0x808ACA5B  at syscall+0x4B 0x80895292
 at Xfast_syscall+0xE2

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


Re: upgrade to 9.0-BETA1 with geom_mirror fails

2011-08-15 Thread Andriy Gapon
on 13/08/2011 17:09 Mark Felder said the following:
 Here's a followup with some pics I was able to take. Sorry about the quality 
 :-(
 
 http://feld.me/stuff/freebsd/geom_mirror_9/

I guess that the root cause of your trouble is the GEOM_PART integrity check
failing (see the messages in IMG_1312.JPG).
You should investigate and fix that.

Meanwhile you may want to set the kern.geom.part.check_integrity loader tunable 
to
zero (either in loader prompt or in loader.conf).

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


diskless client can not be loaded (works at r224471)

2011-08-15 Thread Boris Samorodov
Hi!

I use the same kernel for both host and diskless stations.
The FreeBSD-9 r224471 kernel at the host system works fine,
but the r224870 kernel oes not work. The file /pxeboot seems to be
loaded but then the host system does not answer to client's nfs
questions.

Here are the relevan parts of tcpdump logs at the host system (kaka is
the diskless station and 192.168.111.254 is the host system):
- r224471 kernel (works) -
kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
16:08:28.325938 IP (tos 0x0, ttl 64, id 2002, offset 0, flags [none], proto UDP 
(17), length 264)
192.168.111.254.nfs  kaka.4: reply ok 236 lookup fh 1237,78874/9609217 DIR 
755 ids 0/0 sz 1024 nlink 8 rdev 192/38338761 fsid 7e fileid 92a001 a/m/ctime 
1313410061.00 1313410058.00 1313410058.00 post dattr: DIR 755 ids 
0/0 sz 512 nlink 19 rdev 192/38338760 fsid 7e fileid 92a000 a/m/ctime 
1313410040.00 1313393850.00 1313393850.00
16:08:28.326130 IP (tos 0x0, ttl 20, id 197, offset 0, flags [none], proto UDP 
(17), length 140)
kaka.5  192.168.111.254.nfs: 112 lookup fh 1237,78874/9609217 
boot.4th.split
16:08:28.326180 IP (tos 0x0, ttl 64, id 2003, offset 0, flags [none], proto UDP 
(17), length 144)
192.168.111.254.nfs  kaka.5: reply ok 116 lookup ERROR: No such file or 
directory post dattr: DIR 755 ids 0/0 sz 1024 nlink 8 rdev 192/38338761 fsid 7e 
fileid 92a001 a/m/ctime 1313410061.00 1313410058.00 1313410058.00
16:08:28.326420 IP (tos 0x0, ttl 20, id 198, offset 0, flags [none], proto UDP 
(17), length 104)
kaka.exp2  192.168.111.254.entrust-aams: [udp sum ok] UDP, length 76
16:08:28.326555 IP (tos 0x0, ttl 64, id 2004, offset 0, flags [none], proto UDP 
(17), length 96)
192.168.111.254.entrust-aams  kaka.exp2: [bad udp cksum 55c4!] UDP, length 
68
16:08:28.326717 IP (tos 0x0, ttl 20, id 199, offset 0, flags [none], proto UDP 
(17), length 128)
kaka.7  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
16:08:28.326770 IP (tos 0x0, ttl 64, id 2005, offset 0, flags [none], proto UDP 
(17), length 264)
192.168.111.254.nfs  kaka.7: reply ok 236 lookup fh 1237,78874/9609217 DIR 
755 ids 0/0 sz 1024 nlink 8 rdev 192/38338761 fsid 7e fileid 92a001 a/m/ctime 
1313410061.00 1313410058.00 1313410058.00 post dattr: DIR 755 ids 
0/0 sz 512 nlink 19 rdev 192/38338760 fsid 7e fileid 92a000 a/m/ctime 
1313410040.00 1313393850.00 1313393850.00
16:08:28.326965 IP (tos 0x0, ttl 20, id 200, offset 0, flags [none], proto UDP 
(17), length 144)
kaka.8  192.168.111.254.nfs: 116 lookup fh 1237,78874/9609217 
boot.4th.gz.split
- r224870 kernel (no answer) -
15:21:45.825058 IP (tos 0x0, ttl 20, id 196, offset 0, flags [none], proto UDP 
(17), length 128)
kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
15:21:47.281800 IP (tos 0x0, ttl 20, id 197, offset 0, flags [none], proto UDP 
(17), length 128)
kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
15:21:51.282086 IP (tos 0x0, ttl 20, id 198, offset 0, flags [none], proto UDP 
(17), length 128)
kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
-

Some additional info about the host:
-
% uname -a
FreeBSD h30.sp.ipt.ru 9.0-BETA1 FreeBSD 9.0-BETA1 #29 r224870: Mon Aug 15 
03:12:15 MSK 2011 b...@h30.sp.ipt.ru:/usr/obj/usr/src/sys/BB  i386

% ifconfig re0
re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC
ether 00:1f:d0:91:e4:96
inet 192.168.16.30 netmask 0xff00 broadcast 192.168.16.255
inet 192.168.100.99 netmask 0xff00 broadcast 192.168.100.255
inet 192.168.111.254 netmask 0xff00 broadcast 192.168.111.255
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: Ethernet autoselect (100baseTX full-duplex)
status: active

% sudo tail /var/log/xferlog
Aug 15 16:20:29 h30 tftpd[2653]: Full access allowedin /etc/hosts.allow
Aug 15 16:20:29 h30 tftpd[2653]: Filename: '/pxeboot'
Aug 15 16:20:29 h30 tftpd[2653]: Mode: 'octet'
Aug 15 16:20:29 h30 tftpd[2653]: Got ERROR packet: TFTP Aborted
Aug 15 16:20:29 h30 tftpd[2655]: Full access allowedin /etc/hosts.allow
Aug 15 16:20:29 h30 tftpd[2655]: Filename: '/pxeboot'
Aug 15 16:20:29 h30 tftpd[2655]: Mode: 'octet'
Aug 15 16:20:29 h30 tftpd[2655]: 192.168.111.11: read request for /pxeboot: 
success
Aug 15 16:20:29 h30 tftpd[2655]: Sent 268288 bytes in 0 seconds

% showmount -e
/home  192.168.111.11 192.168.111.12 
/usr/local 192.168.111.11 192.168.111.12 
/diskless  192.168.111.11 192.168.111.12

% showmount -a
All mount points on localhost:
kaka:/diskless

% sockstat -4l
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS  
www  httpd  2537  3  tcp4 6 *:80 

Re: upgrade to 9.0-BETA1 with geom_mirror fails

2011-08-15 Thread Mark Felder

On Mon, 15 Aug 2011 08:13:48 -0500, Andriy Gapon a...@freebsd.org wrote:



I guess that the root cause of your trouble is the GEOM_PART integrity  
check

failing (see the messages in IMG_1312.JPG).
You should investigate and fix that.

Meanwhile you may want to set the kern.geom.part.check_integrity loader  
tunable to

zero (either in loader prompt or in loader.conf).



Thanks for the tip. Hopefully someone stumbles upon that and finds it
useful during a google search, because I wasn't finding anything :-)

Since it was a 3 way mirror it was trivial to break the mirror and rebuild
with GPT. I wanted to do that for a while anyway. After the rebuild was
complete it had no issues booting up. I'm guessing it was just something
stupid with the old disk layout.


Cheers,


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


Re: gptzfsboot error using HP Smart Array P410i Controller

2011-08-15 Thread John Baldwin
On Sunday, August 07, 2011 5:59:31 pm Xin LI wrote:
 On 08/01/11 06:07, Christoph Hoffmann wrote:
  Hello,
 
  The initial reboot followed the installation of ZFS-only version 5/28
  system reports error:
 
  Attempting Boot From Hard Drive (C:)
   gptzfsboot: error 1 lba 32
   gptzfsboot: error 1 lba 1
   gptzfsboot: No ZFS pools located, can't boot
 
  The same installation procedure on older ProLiant with Compaq Smart
  Array 5i do not cause any problems.
 
 Looks like for some reason the drive number (%dl) didn't get passed
 through ARGS (by pmbr.s).

MBR boot loaders aren't defined to do that.  They pass %dl directly via the 
register.  For gptboot and gptzfsboot, sys/boot/i386/gptboot/gptldr.S 
already stores the saved value of %dl in MEM_ARG.

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


Re: gptzfsboot error using HP Smart Array P410i Controller

2011-08-15 Thread John Baldwin
On Friday, August 05, 2011 10:08:27 am Christoph Hoffmann wrote:
 Hello Everyone,
 
 Despite the BIOS information about the nonexistent floppy, the zfsboot.c 
code 
 will prevent to boot from the first HDD if a floppy is given as a first 
available device.
 
 The drive 0x0 (floppy) will be probed before the code below and an error 
occurs:
 […]
 gptzfsboot: error 1 lba 32
   
 gptzfsboot: error 1 lba 1 
   
 […]
 
 The continue statement will skip the rest of the iteration because  
  if ((i | DRV_HARD) == *(uint8_t *)PTOV(ARGS)) 
 is true if the drive equals 0x80. As a result we do not call probe_drive()
 for this drive.

But that shouldn't happen if ARGS has a drive number of 0.  (In that case 0x80 
!= 0x0, so it shouldn't match.)

This shows that PTOV(ARGS) actually has a %dl value of 0x80 which is correct.  
The question is how your initial 'dsk' ended up using 0x0 instead of 0x80.
Note that your 'type' is 0, so that means that it was ok initially (TYPE_AD is 
0):

dsk-drive = *(uint8_t *)PTOV(ARGS);
dsk-type = dsk-drive  DRV_HARD ? TYPE_AD : TYPE_FD;

Somewhere between where 'dsk' is initalized in main() and before probe_drive() 
is called in main() for 'dsk', 'dsk-drive' is getting clobbered.  Can you add 
some additional printfs to nail down where that is happening?

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


daily snapshots updated (Was: Re: Where to download latest FreeBSD snapshots)

2011-08-15 Thread Hiroki Sato
Test Rat ttse...@gmail.com wrote
  in 86y5z1ymyi@gmail.com:

tt Can you add architecture name to HEAD snapshots? It often saves time
tt checking whether snapshot is suitable for testing months after being
tt dowloaded.

 Thank you for your feedback.  While I have received various ideas and
 am still working on them, I recently added changes for the followng:

 1. Use $TARGET and $TARGET_ARCH in ISO image names.  Now it is like
the following:

FreeBSD-9.0-HEAD-20110809-JPSNAP-i386-i386-bootonly.iso

Also, SHA-256 checksum files have been added in the same
directory.

 2. Use a clean build environment.  This should fix an iso9660 format
breakage issue in makefs(8).

 3. The uncompressed tree of the release tarballs is added under the
trees/ directory.

 Currently, snapshots of 7 platforms are being built natively.

-- Hiroki


pgpY8PRqoq4gw.pgp
Description: PGP signature


Re: make test under lang/perl5.14 causes panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/ia64/ia64/trap.c:562

2011-08-15 Thread Anton Shterenlikht
On Fri, Aug 12, 2011 at 05:45:55PM -0700, Marcel Moolenaar wrote:
 
 On Aug 12, 2011, at 7:19 AM, Anton Shterenlikht wrote:
 
  On ia64 r221488
 
 Please update to at least r223700, as that was a major stability fix.

UZI uname -a
FreeBSD mech-as221.men.bris.ac.uk 9.0-BETA1 FreeBSD 9.0-BETA1 #5 r224876: Mon 
Aug 15 12:06:05 BST 2011 
r...@mech-as221.men.bris.ac.uk:/usr/obj/usr/src/sys/UZI  ia64
UZI 

make test run with no panic once (though lots of errors,
I should probably let the perl team know), and
panicked on the second run:

# make test

*skip many tests*

op/64bitint.t . ok 
op/alarm.t  Write 
failed: Broken pipe


isitmychild: rmatrix mismatch between process lock (index 8) and sigacts (index 
166): w_rmatrix[8][166] == 1 but w_rmatrix[166][8] == 4
KDB: stack backtrace:
panic: blockable sleep lock (sleep mutex) process lock @ 
/usr/src/sys/ia64/ia64/trap.c:562
cpuid = 1
KDB: enter: panic
[ thread pid 64967 tid 100400 ]
Stopped at  kdb_enter+0x92: [I2]addl r14=0xffe211b0,gp ;;
db 

db show thread
Thread 100400 at 0xe000121eb9e0:
 proc (pid 64967): 0xe000121de000
 name: perl
 stack: 0xa00097206000-0xa0009720dfff
 flags: 0x4  pflags: 0
 state: RUNNING (CPU 1)
 priority: 194
 container lock: sched lock 1 (0x9ffc00a73780)
db 

db show proc
Process 64967 (perl) at 0xe000121de000:
 state: NORMAL
 uid: 0  gids: 0, 5
 parent: pid 63774 at 0xe0001194c468
 ABI: FreeBSD ELF64
 arguments: ./perl
 threads: 1
100400   Run CPU 1   perl
db 

db bt
Tracing pid 64967 tid 100400 td 0xe000121eb9e0
kdb_enter(0x9ffc0095b7e0, 0x9ffc0095b7e0, 0x9ffc00375110, 0x793) at 
kdb_enter+0x92
panic(0x9ffc00964638, 0x9ffc00959f18, 0x9ffc00959ef8, 
0x9ffc0099caa8, 0x232, 0x9ffc0099caa8) at panic+0x2e0
witness_checkorder(0xe000121de0f8, 0x9, 0x9ffc0099caa8, 0x232, 0x0) at 
witness_checkorder+0x1b0
_mtx_lock_flags(0xe000121de0f8, 0x0, 0x9ffc0099caa8, 0x232, 
0x9ffc0081d160, 0x716, 0xa0009720d258) at _mtx_lock_flags+0x130
trap(0x14, 0xa0009720c400) at trap+0x940
ivt_Data_TLB() at ivt_Data_TLB+0x1d0
--- trapframe at 0xa0009720c400
uma_zalloc_arg(0xe040fed6fb00, 0x0, 0x1) at uma_zalloc_arg+0x121
malloc(0x9, 0x9ffc00a1f9f0, 0x1) at malloc+0x290
unw_alloc(0x10c0, 0x9ffc007d8a10) at unw_alloc+0x210
uwx_init(0x0, 0x9ffc00820590, 0x28a, 0x9ffc00c27330) at uwx_init+0x70
unw_create_from_pcb(0xa0009720c750, 0xa0009720c7f0, 0x9ffc007fe680) 
at unw_create_from_pcb+0x20
db_backtrace(0xe000121eb9e0, 0xa0009720c7f0, 0x) at 
db_backtrace+0x20
db_trace_self(0x9ffc00101100) at db_trace_self+0x40
db_trace_self_wrapper(0x9ffc003e3620) at db_trace_self_wrapper+0x70
kdb_backtrace(0x9ffc00a484c0, 0x9ffc0040ef60, 0x410, 
0x9ffc00c27330) at kdb_backtrace+0xc0
_isitmyx(0xa0202400, 0xa0207300, 0x1, 0x9ffc00964de8) at 
_isitmyx+0x1c0
isitmychild(0xa0202400, 0xa0207300, 0x9ffc00412cb0, 0x999, 
0x9ffc0095b8e8) at isitmychild+0x30
witness_checkorder(0xe00011d75ca8, 0x9, 0x9ffc00be9f90, 0x288, 0x0) at 
witness_checkorder+0x5e0
_mtx_lock_flags(0xe00011d75ca8, 0x0, 0x9ffc0095b8e8, 0x288) at 
_mtx_lock_flags+0x130
kern_sigaction(0xe000121de000, 0xe, 0x0, 0xa0009720d380, 
0x9ffc0095b8e8) at kern_sigaction+0x90
sigaction(0xe000121eb9e0, 0xa0009720d4e8, 0x0, 0xa0009720d380) at 
sigaction+0xb0
syscallenter(0xe000121eb9e0, 0xa0009720d3a0, 0xa0009720d3a8) at 
syscallenter+0x4e0
syscall(0xa0009720d4c8, 0xe000121eb9e0, 0x7fffe1a0, 
0x9ffc00818520, 0x8, 0x120bc9930) at syscall+0x60
epc_syscall_return() at epc_syscall_return
db 
 Latest and greatest is preferred though.
 
 FYI,
 
 -- 
 Marcel Moolenaar
 mar...@xcllnt.net
 
 

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Buildworld failure after update r224806 to r224886

2011-08-15 Thread Ivan Klymenko
Hello, all!

I have:
uname -a
FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806M: Sat Aug 13
15:43:38 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9  amd64

Buildworld failure after update r224806 to r224886

In my configuration files since nothing has changed...

Building of the world accompanied by the following errors:

...
=== include/rpc (all)
gzip -cn heimdal.info  heimdal.info.gz
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
ranlib libavl_p.a
=== cddl/lib/libctf (all)
=== kerberos5/lib (all)
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
distcc[31852] ERROR: compile (null) on localhost failed
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
distcc[31847] ERROR: compile (null) on localhost failed
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
/usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
distcc[31856] ERROR: compile (null) on localhost failed
*** Error code 1
/usr/local/libexec/ccache/world/cc -pg -O2 -mmmx -msse -msse2 -msse3 -mssse3 
-pipe -march=core2 -DCTF_OLD_VERSIONS 
-I/usr/src/cddl/lib/libctf/../../../sys/cddl/compat/opensolaris  
-I/usr/src/cddl/lib/libctf/../../../cddl/compat/opensolaris/include  
-I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/head  
-I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf  
-I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/lib/libctf/common  
-I/usr/src/cddl/lib/libctf/../../../sys/cddl/contrib/opensolaris/uts/common 
-DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wno-pointer-sign 
-Wno-unknown-pragmas -c 
/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf/ctf_create.c
 -o ctf_create.po
gzip -cn atrun.8  atrun.8.gz
1 error
*** Error code 2
1 error
*** Error code 2
/usr/local/libexec/ccache/world/cc -pg -O2 -mmmx -msse -msse2 -msse3 -mssse3 
-pipe -march=core2 -DCTF_OLD_VERSIONS 
-I/usr/src/cddl/lib/libctf/../../../sys/cddl/compat/opensolaris  
-I/usr/src/cddl/lib/libctf/../../../cddl/compat/opensolaris/include  
-I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/head  
-I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf  
-I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/lib/libctf/common  
-I/usr/src/cddl/lib/libctf/../../../sys/cddl/contrib/opensolaris/uts/common 
-DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wno-pointer-sign 
-Wno-unknown-pragmas -c 
/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf/ctf_decl.c
 -o ctf_decl.po
/usr/local/libexec/ccache/world/cc -c -O2 -mmmx -msse -msse2 -msse3 -mssse3 
-pipe -march=core2 -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include 
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I.  
-I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -std=gnu99  
-fvisibility=hidden -DHIDE_EXPORTS -p -fPIC -fexceptions -D__GLIBC__=3 
-DElfW=__ElfN -o unwind-sjlj.po 
/usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-sjlj.c
/usr/local/libexec/ccache/world/cc -c -O2 -mmmx -msse -msse2 -msse3 -mssse3 
-pipe -march=core2 -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include 
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I.  
-I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -std=gnu99  
-fvisibility=hidden -DHIDE_EXPORTS -p -fPIC -fexceptions -D__GLIBC__=3 
-DElfW=__ElfN -o gthr-gnat.po 
/usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr-gnat.c
/usr/local/libexec/ccache/world/cc -c -O2 -mmmx -msse -msse2 -msse3 -mssse3 
-pipe -march=core2 -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include 
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I.  
-I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -std=gnu99  

Re: Buildworld failure after update r224806 to r224886

2011-08-15 Thread Niclas Zeising
On 2011-08-15 19:38, Ivan Klymenko wrote:
 Hello, all!
 
 I have:
 uname -a
 FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806M: Sat Aug 13
 15:43:38 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9  amd64
 
 Buildworld failure after update r224806 to r224886
 
 In my configuration files since nothing has changed...
 
 Building of the world accompanied by the following errors:
 
 ...
 === include/rpc (all)
 gzip -cn heimdal.info  heimdal.info.gz
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
 ranlib libavl_p.a
 === cddl/lib/libctf (all)
 === kerberos5/lib (all)
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
 distcc[31852] ERROR: compile (null) on localhost failed
 *** Error code 1
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
 distcc[31847] ERROR: compile (null) on localhost failed
 *** Error code 1
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylex'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyin'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyytext'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyyerror'
 /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `_nsyylineno'
 distcc[31856] ERROR: compile (null) on localhost failed
 *** Error code 1
 /usr/local/libexec/ccache/world/cc -pg -O2 -mmmx -msse -msse2 -msse3 -mssse3 
 -pipe -march=core2 -DCTF_OLD_VERSIONS 
 -I/usr/src/cddl/lib/libctf/../../../sys/cddl/compat/opensolaris  
 -I/usr/src/cddl/lib/libctf/../../../cddl/compat/opensolaris/include  
 -I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/head  
 -I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf  
 -I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/lib/libctf/common
   -I/usr/src/cddl/lib/libctf/../../../sys/cddl/contrib/opensolaris/uts/common 
 -DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wno-pointer-sign 
 -Wno-unknown-pragmas -c 
 /usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf/ctf_create.c
  -o ctf_create.po
 gzip -cn atrun.8  atrun.8.gz
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 /usr/local/libexec/ccache/world/cc -pg -O2 -mmmx -msse -msse2 -msse3 -mssse3 
 -pipe -march=core2 -DCTF_OLD_VERSIONS 
 -I/usr/src/cddl/lib/libctf/../../../sys/cddl/compat/opensolaris  
 -I/usr/src/cddl/lib/libctf/../../../cddl/compat/opensolaris/include  
 -I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/head  
 -I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf  
 -I/usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/lib/libctf/common
   -I/usr/src/cddl/lib/libctf/../../../sys/cddl/contrib/opensolaris/uts/common 
 -DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wno-pointer-sign 
 -Wno-unknown-pragmas -c 
 /usr/src/cddl/lib/libctf/../../../cddl/contrib/opensolaris/common/ctf/ctf_decl.c
  -o ctf_decl.po
 /usr/local/libexec/ccache/world/cc -c -O2 -mmmx -msse -msse2 -msse3 -mssse3 
 -pipe -march=core2 -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
 -DHAVE_GTHR_DEFAULT  
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include  
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I.  
 -I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -std=gnu99  
 -fvisibility=hidden -DHIDE_EXPORTS -p -fPIC -fexceptions -D__GLIBC__=3 
 -DElfW=__ElfN -o unwind-sjlj.po 
 /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-sjlj.c
 /usr/local/libexec/ccache/world/cc -c -O2 -mmmx -msse -msse2 -msse3 -mssse3 
 -pipe -march=core2 -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
 -DHAVE_GTHR_DEFAULT  
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include  
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I.  
 -I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -std=gnu99  
 -fvisibility=hidden -DHIDE_EXPORTS -p -fPIC -fexceptions -D__GLIBC__=3 
 -DElfW=__ElfN -o gthr-gnat.po 
 /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr-gnat.c
 /usr/local/libexec/ccache/world/cc -c -O2 -mmmx -msse -msse2 -msse3 -mssse3 
 -pipe -march=core2 -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
 -DHAVE_GTHR_DEFAULT  
 -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include  
 

Re: Buildworld failure after update r224806 to r224886

2011-08-15 Thread Ivan Klymenko
В Mon, 15 Aug 2011 20:12:35 +0200
Niclas Zeising niclas.zeis...@gmail.com пишет:

  ...
  
  
  Someone have any idea what is that?
  
  Thanks!
 
 
 There was a period when there was a bug in dev/std{in,err,out}, which
 amongst other things made it impossible to complete a buildworld.
 Compile a new kernel (past r224842), boot to that kernel and rebuild
 world, that should work. For details see UPDATING r224875.
 HTH!
 
Ooops!

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


Re: nroff -mandoc | more no longer works

2011-08-15 Thread Christian Weisgerber
Robert Watson rwat...@freebsd.org wrote:

 I'm guessing this relates to nroff/groff tweaks, but I was a bit unhappy to 
 learn that the command I've used for the last decade to render man pages 
 while 
 editing them (nroff -mandoc foo.1 | more) no longer works (output below).

nroff -c -mandoc foo.1  should work as expected.

-- 
Christian naddy Weisgerber  na...@mips.inka.de

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


Re: [Soekris] FreeBSD 9.0 beta on a Net5501?

2011-08-15 Thread Bryan Irvine
On Sun, Aug 14, 2011 at 12:50 PM, C. P. Ghost cpgh...@cordula.ws wrote:
 On Thu, Aug 4, 2011 at 2:21 PM, Patrick Lamaiziere
 patf...@davenulle.org wrote:
 Hello,

 I've tried to update my net5501 running an old FreeBSD-current from
 october to 9.0 beta 1. Unfortunaly installworld crashed and the system
 is broken now :

 # make installworld
 ...
 === libexec/rtld-elf (install)
 chflags noschg /usr/libexec/ld-elf.so.1
 install -s -o root -g wheel -m 555  -C -b -fschg -S ld-elf.so.1 /libexec
 install -o root -g wheel -m 444 rtld.1.gz  /usr/share/man/man1
 *** Signal 4

 Stop in /usr/src/libexec/rtld-elf.
 *** Error code 1

 # ls
 Instruction interdite(core dumped)
 (instruction interdite = illegal/forbidden instruction)

 The world and kernel were built with llvm/clang.

 [CC-ing freebsd-current@]

 Is this issue resolved?

 I'm having a bunch of net4801 in production here,
 and I was planning to move them to 9.0 soon after
 RELEASE. So thanks for the heads up. I'll be holding
 back now, and will stay with 8.2-STABLE.

 Unfortunately, I have no spare net4801 (and no net5501)
 at the moment, so I can't test BETA on them. :(

I have access to a 4801.  I can test if needed.  I don't run freebsd
though so I'd need some help with understanding what needs to be
tested.


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


Re: [Soekris] FreeBSD 9.0 beta on a Net5501?

2011-08-15 Thread Mike Tancsa
On 8/14/2011 3:50 PM, C. P. Ghost wrote:
 I'm having a bunch of net4801 in production here,
 and I was planning to move them to 9.0 soon after
 RELEASE. So thanks for the heads up. I'll be holding
 back now, and will stay with 8.2-STABLE.

I netbooted an old 4801 box and it seems fine too. Testing the watchdog
as well as the hifn that was in it and both seem to work just fine.


4801# dmesg
Copyright (c) 1992-2011 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-BETA1 #2: Sun Aug 14 19:15:05 EDT 2011
mdtan...@ich10.sentex.ca:/usr/HEAD/obj/usr/HEAD/src/sys/ipsec i386
ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237)
module_register: module pci/xhci already exists!
Module pci/xhci failed to register: 17
CPU: Geode(TM) Integrated Processor by National Semi (586-class CPU)
  Origin = Geode by NSC  Id = 0x540  Family = 5  Model = 4  Stepping = 0
  Features=0x808131FPU,TSC,MSR,CX8,CMOV,MMX
real memory  = 134217728 (128 MB)
avail memory = 116346880 (110 MB)
kbd1 at kbdmux0
ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.
cryptosoft0: software crypto on motherboard
pcib0: Host to PCI bridge pcibus 0 on motherboard
pci0: PCI bus on pcib0
sis0: NatSemi DP8381[56] 10/100BaseTX port 0xe100-0xe1ff mem
0xa000-0xafff irq 10 at device 6.0 on pci0
sis0: Silicon Revision: DP83816A
miibus0: MII bus on sis0
nsphyter0: DP83815 10/100 media interface PHY 0 on miibus0
nsphyter0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
sis0: Ethernet address: 00:00:24:c8:fa:e0
sis1: NatSemi DP8381[56] 10/100BaseTX port 0xe200-0xe2ff mem
0xa0001000-0xa0001fff irq 10 at device 7.0 on pci0
sis1: Silicon Revision: DP83816A
miibus1: MII bus on sis1
nsphyter1: DP83815 10/100 media interface PHY 0 on miibus1
nsphyter1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
sis1: Ethernet address: 00:00:24:c8:fa:e1
sis2: NatSemi DP8381[56] 10/100BaseTX port 0xe300-0xe3ff mem
0xa0002000-0xa0002fff irq 10 at device 8.0 on pci0
sis2: Silicon Revision: DP83816A
miibus2: MII bus on sis2
nsphyter2: DP83815 10/100 media interface PHY 0 on miibus2
nsphyter2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
sis2: Ethernet address: 00:00:24:c8:fa:e2
pci0: processor at device 14.0 (no driver attached)
Geode Soekris net4801 comBIOS ver. 1.31 20070408 Copyright (C) 2000-2007
isab0: PCI-ISA bridge port 0x6100-0x613f,0x6200-0x623f at device 18.0
on pci0
isa0: ISA bus on isab0
pci0: bridge at device 18.1 (no driver attached)
atapci0: National Geode SC1100 ATA33 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 18.2 on pci0
ata0: ATA channel 0 on atapci0
ata1: ATA channel 1 on atapci0
Timecounter Geode frequency 2700 Hz quality 1000
pci0: bridge at device 18.5 (no driver attached)
ohci0: OHCI (generic) USB controller mem 0xa001-0xa0010fff irq 5
at device 19.0 on pci0
usbus0: OHCI (generic) USB controller on ohci0
cpu0 on motherboard
pmtimer0 on isa0
orm0: ISA Option ROM at iomem 0xc8000-0xd0fff pnpid ORM on isa0
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atrtc0: AT realtime clock at port 0x70 irq 8 on isa0
Event timer RTC frequency 32768 Hz quality 0
ppc0: parallel port not found.
uart0: 16550 or compatible at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: console (115200,n,8,1)
uart1: 16550 or compatible at port 0x2f8-0x2ff irq 3 on isa0
Timecounters tick every 0.976 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: 0x0e11 at usbus0
uhub0: 0x0e11 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0
Root mount waiting for: usbus0
uhub0: 3 ports with 3 removable, self powered
Trying to mount root from nfs: []...
NFS ROOT: 10.255.255.1:/home/pxe9
hifn0 mem
0xa0003000-0xa0003fff,0xa0004000-0xa0005fff,0xa0008000-0xa000 irq 11
at device 14.0 on pci0
hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801ext clk, 4x mult
4801#

And using /usr/src/tools/crypto/cryptostats

% ssh -c 3des 10.255.255.60 /home/mdtancsa/cryptostats
241 symmetric crypto ops (0 errors, 0 times driver blocked)
0 key ops (0 errors, 0 times driver blocked)
0 crypto dispatch thread activations
0 crypto return thread activations
% ssh -c 3des 10.255.255.60 /home/mdtancsa/cryptostats
271 symmetric crypto ops (0 errors, 0 times driver blocked)
0 key ops (0 errors, 0 times driver blocked)
0 crypto dispatch thread activations
0 crypto return thread activations


Seems to be kicking the hifn card.



-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/

Re: diskless client can not be loaded (works at r224471)

2011-08-15 Thread Rick Macklem
Boris Samorodov wrote:
 Hi!
 
 I use the same kernel for both host and diskless stations.
 The FreeBSD-9 r224471 kernel at the host system works fine,
 but the r224870 kernel oes not work. The file /pxeboot seems to be
 loaded but then the host system does not answer to client's nfs
 questions.
 
 Here are the relevan parts of tcpdump logs at the host system (kaka is
 the diskless station and 192.168.111.254 is the host system):
 - r224471 kernel (works) -
 kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
 16:08:28.325938 IP (tos 0x0, ttl 64, id 2002, offset 0, flags [none],
 proto UDP (17), length 264)
 192.168.111.254.nfs  kaka.4: reply ok 236 lookup fh
 1237,78874/9609217 DIR 755 ids 0/0 sz 1024 nlink 8 rdev 192/38338761
 fsid 7e fileid 92a001 a/m/ctime 1313410061.00 1313410058.00
 1313410058.00 post dattr: DIR 755 ids 0/0 sz 512 nlink 19 rdev
 192/38338760 fsid 7e fileid 92a000 a/m/ctime 1313410040.00
 1313393850.00 1313393850.00
 16:08:28.326130 IP (tos 0x0, ttl 20, id 197, offset 0, flags [none],
 proto UDP (17), length 140)
 kaka.5  192.168.111.254.nfs: 112 lookup fh 1237,78874/9609217
 boot.4th.split
 16:08:28.326180 IP (tos 0x0, ttl 64, id 2003, offset 0, flags [none],
 proto UDP (17), length 144)
 192.168.111.254.nfs  kaka.5: reply ok 116 lookup ERROR: No such file
 or directory post dattr: DIR 755 ids 0/0 sz 1024 nlink 8 rdev
 192/38338761 fsid 7e fileid 92a001 a/m/ctime 1313410061.00
 1313410058.00 1313410058.00
 16:08:28.326420 IP (tos 0x0, ttl 20, id 198, offset 0, flags [none],
 proto UDP (17), length 104)
 kaka.exp2  192.168.111.254.entrust-aams: [udp sum ok] UDP, length 76
 16:08:28.326555 IP (tos 0x0, ttl 64, id 2004, offset 0, flags [none],
 proto UDP (17), length 96)
 192.168.111.254.entrust-aams  kaka.exp2: [bad udp cksum 55c4!] UDP,
 length 68
 16:08:28.326717 IP (tos 0x0, ttl 20, id 199, offset 0, flags [none],
 proto UDP (17), length 128)
 kaka.7  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
 16:08:28.326770 IP (tos 0x0, ttl 64, id 2005, offset 0, flags [none],
 proto UDP (17), length 264)
 192.168.111.254.nfs  kaka.7: reply ok 236 lookup fh
 1237,78874/9609217 DIR 755 ids 0/0 sz 1024 nlink 8 rdev 192/38338761
 fsid 7e fileid 92a001 a/m/ctime 1313410061.00 1313410058.00
 1313410058.00 post dattr: DIR 755 ids 0/0 sz 512 nlink 19 rdev
 192/38338760 fsid 7e fileid 92a000 a/m/ctime 1313410040.00
 1313393850.00 1313393850.00
 16:08:28.326965 IP (tos 0x0, ttl 20, id 200, offset 0, flags [none],
 proto UDP (17), length 144)
 kaka.8  192.168.111.254.nfs: 116 lookup fh 1237,78874/9609217
 boot.4th.gz.split
 - r224870 kernel (no answer) -
 15:21:45.825058 IP (tos 0x0, ttl 20, id 196, offset 0, flags [none],
 proto UDP (17), length 128)
 kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
 15:21:47.281800 IP (tos 0x0, ttl 20, id 197, offset 0, flags [none],
 proto UDP (17), length 128)
 kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
 15:21:51.282086 IP (tos 0x0, ttl 20, id 198, offset 0, flags [none],
 proto UDP (17), length 128)
 kaka.4  192.168.111.254.nfs: 100 lookup fh 1237,78874/9609216 boot
 -
 
 Some additional info about the host:
 -
 % uname -a
 FreeBSD h30.sp.ipt.ru 9.0-BETA1 FreeBSD 9.0-BETA1 #29 r224870: Mon Aug
 15 03:12:15 MSK 2011 b...@h30.sp.ipt.ru:/usr/obj/usr/src/sys/BB i386
 
 % ifconfig re0
 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
 1500
 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC
 ether 00:1f:d0:91:e4:96
 inet 192.168.16.30 netmask 0xff00 broadcast 192.168.16.255
 inet 192.168.100.99 netmask 0xff00 broadcast 192.168.100.255
 inet 192.168.111.254 netmask 0xff00 broadcast 192.168.111.255
 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
 media: Ethernet autoselect (100baseTX full-duplex)
 status: active
 
 % sudo tail /var/log/xferlog
 Aug 15 16:20:29 h30 tftpd[2653]: Full access allowedin
 /etc/hosts.allow
 Aug 15 16:20:29 h30 tftpd[2653]: Filename: '/pxeboot'
 Aug 15 16:20:29 h30 tftpd[2653]: Mode: 'octet'
 Aug 15 16:20:29 h30 tftpd[2653]: Got ERROR packet: TFTP Aborted
 Aug 15 16:20:29 h30 tftpd[2655]: Full access allowedin
 /etc/hosts.allow
 Aug 15 16:20:29 h30 tftpd[2655]: Filename: '/pxeboot'
 Aug 15 16:20:29 h30 tftpd[2655]: Mode: 'octet'
 Aug 15 16:20:29 h30 tftpd[2655]: 192.168.111.11: read request for
 /pxeboot: success
 Aug 15 16:20:29 h30 tftpd[2655]: Sent 268288 bytes in 0 seconds
 
 % showmount -e
 /home 192.168.111.11 192.168.111.12
 /usr/local 192.168.111.11 192.168.111.12
 /diskless 192.168.111.11 192.168.111.12
 
 % showmount -a
 All mount points on localhost:
 kaka:/diskless
 
 % sockstat -4l
 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
 www httpd 2537 3 tcp4 6 *:80 *:*
 root Xorg 2388 3 tcp4 *:6000 *:*
 www httpd 2386 3 tcp4 6 *:80 *:*
 www httpd 2385 3 tcp4 6 *:80 *:*
 www httpd 2384 3 tcp4 6 *:80 *:*
 www 

Three LOR with latest -current

2011-08-15 Thread John
Hi folks,

   I'm seeing 3 lock order reversals with an up-to-date -current
system. Stock system, GENERIC kernel. Let me know if this isn't
enough information. Just booting the system and the dmesg.

Thanks,
John


lock order reversal:
 1st 0xfe0289627db8 ufs (ufs) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/ufs/ffs/ffs_snapshot.c:425
 2nd 0xff9f0db49778 bufwait (bufwait) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/kern/vfs_bio.c:2658
 3rd 0xfe00404a8098 ufs (ufs) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/ufs/ffs/ffs_snapshot.c:546
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
kdb_backtrace() at kdb_backtrace+0x37
_witness_debugger() at _witness_debugger+0x2e
witness_checkorder() at witness_checkorder+0x807
__lockmgr_args() at __lockmgr_args+0xdc6
ffs_lock() at ffs_lock+0x8c
VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b
_vn_lock() at _vn_lock+0x47
ffs_snapshot() at ffs_snapshot+0x1c31
ffs_mount() at ffs_mount+0xa24
vfs_donmount() at vfs_donmount+0xddc
nmount() at nmount+0x63
syscallenter() at syscallenter+0x1aa
syscall() at syscall+0x4c
Xfast_syscall() at Xfast_syscall+0xdd
--- syscall (378, FreeBSD ELF64, nmount), rip = 0x800abde1c, rsp = 
0x7fffd968, rbp = 0x801008130 ---


lock order reversal:
 1st 0xff9f0db49778 bufwait (bufwait) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/kern/vfs_bio.c:2658
 2nd 0xfe004034dcb0 snaplk (snaplk) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/ufs/ffs/ffs_snapshot.c:818
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
kdb_backtrace() at kdb_backtrace+0x37
_witness_debugger() at _witness_debugger+0x2e
witness_checkorder() at witness_checkorder+0x807
__lockmgr_args() at __lockmgr_args+0xdc6
ffs_lock() at ffs_lock+0x8c
VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b
_vn_lock() at _vn_lock+0x47
ffs_snapshot() at ffs_snapshot+0x1b0c
ffs_mount() at ffs_mount+0xa24
vfs_donmount() at vfs_donmount+0xddc
nmount() at nmount+0x63
syscallenter() at syscallenter+0x1aa
syscall() at syscall+0x4c
Xfast_syscall() at Xfast_syscall+0xdd
--- syscall (378, FreeBSD ELF64, nmount), rip = 0x800abde1c, rsp = 
0x7fffd968, rbp = 0x801008130 ---


lock order reversal:
 1st 0xfe004034dcb0 snaplk (snaplk) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/kern/vfs_vnops.c:301
 2nd 0xfe0289627db8 ufs (ufs) @ 
/usr/src.2011-08-14_10.53pm_EDT/sys/ufs/ffs/ffs_snapshot.c:1620
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
kdb_backtrace() at kdb_backtrace+0x37
_witness_debugger() at _witness_debugger+0x2e
witness_checkorder() at witness_checkorder+0x807
__lockmgr_args() at __lockmgr_args+0xdc6
ffs_snapremove() at ffs_snapremove+0xe7
ffs_truncate() at ffs_truncate+0x302
ufs_inactive() at ufs_inactive+0x260
vinactive() at vinactive+0x72
vputx() at vputx+0x386
vn_close() at vn_close+0x118
vn_closefile() at vn_closefile+0x5a
_fdrop() at _fdrop+0x23
closef() at closef+0x5c
kern_close() at kern_close+0x121
syscallenter() at syscallenter+0x1aa
syscall() at syscall+0x4c
Xfast_syscall() at Xfast_syscall+0xdd
--- syscall (6, FreeBSD ELF64, close), rip = 0x800b5e2bc, rsp = 0x7fffd968, 
rbp = 0 ---

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


[patch] Disable TSC on SMP VMs

2011-08-15 Thread Mike Silbersack


Hi all,

Thanks to a lightning strike, I recently upgraded my ESXi 4.1 system from 
an old Athlon X2 to a shiny new Core i5-2500K.  I order to see how fast it 
was, I decided to run some buildworlds.  I tried my FreeBSD 9 based VM 
first, and was unhappy with what I saw - many mpt timeouts were reported, 
and the filesystem ended up requiring a lot of fscking.  My FreeBSD 8 
based VM, on the other hand, was quite happy.


After some trial and error, I determined that using the TSC as a 
timecounter with the VM in SMP mode was the root cause.  If I switch the 
VM to one vCPU and run with the TSC, the buildworld runs fine.  If I leave 
it with two vCPUs and change the timecounter to ACPI, then it runs fine 
too.  Based on these results, I created the attached patch; it turns the 
priority of the TSC down to -100 if it determines that it is running 
inside a virtualized SMP environment.  (I did not do testing on KVM or 
qemu, but I am assuming that they probably do not have TSC emulation 
perfect either.)


I'd like to get this into 9.0 so that it works reliably for people who run 
it in a virtual environment on modern hardware.  If someone could code 
review the patch, I would greatly appreciate it.


Thanks,

Mike Silby Silbersack
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org