[releng_8 tinderbox] failure on mips/mips

2012-10-01 Thread FreeBSD Tinderbox
TB --- 2012-10-01 10:16:53 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-10-01 10:16:53 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 
FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2012-10-01 10:16:53 - starting RELENG_8 tinderbox run for mips/mips
TB --- 2012-10-01 10:16:53 - cleaning the object tree
TB --- 2012-10-01 10:16:54 - checking out /src from 
svn://svn.freebsd.org/base/stable/8
TB --- 2012-10-01 10:16:54 - cd /tinderbox/RELENG_8/mips/mips
TB --- 2012-10-01 10:16:54 - /usr/local/bin/svn cleanup /src
TB --- 2012-10-01 10:17:03 - /usr/local/bin/svn update /src
TB --- 2012-10-01 10:21:37 - WARNING: /usr/local/bin/svn returned exit code  1 
TB --- 2012-10-01 10:21:37 - WARNING: sleeping 30 s and retrying...
TB --- 2012-10-01 10:22:07 - /usr/local/bin/svn update /src
TB --- 2012-10-01 10:22:13 - At svn revision 241091S
TB --- 2012-10-01 10:22:14 - building world
TB --- 2012-10-01 10:22:14 - CROSS_BUILD_TESTING=YES
TB --- 2012-10-01 10:22:14 - MAKEOBJDIRPREFIX=/obj
TB --- 2012-10-01 10:22:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2012-10-01 10:22:14 - SRCCONF=/dev/null
TB --- 2012-10-01 10:22:14 - TARGET=mips
TB --- 2012-10-01 10:22:14 - TARGET_ARCH=mips
TB --- 2012-10-01 10:22:14 - TZ=UTC
TB --- 2012-10-01 10:22:14 - __MAKE_CONF=/dev/null
TB --- 2012-10-01 10:22:14 - cd /src
TB --- 2012-10-01 10:22:14 - /usr/bin/make -B buildworld
>>> World build started on Mon Oct  1 10:22:15 UTC 2012
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
[...]
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include -c 
/src/games/fortune/strfile/strfile.c
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include  -static 
-L/obj/mips/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy
sh /src/tools/install.sh -s -o root -g wheel -m 555   strfile 
/obj/mips/src/tmp/legacy/usr/games
===> gnu/usr.bin/gperf (obj,depend,all,install)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf created for /src/gnu/usr.bin/gperf
===> gnu/usr.bin/gperf/doc (obj)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf/doc created for 
/src/gnu/usr.bin/gperf/doc
make: don't know how to make iterator.cc. Stop
*** Error code 2

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2012-10-01 10:22:28 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2012-10-01 10:22:28 - ERROR: failed to build world
TB --- 2012-10-01 10:22:28 - 13.45 user 8.38 system 334.95 real


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


panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread Rick Macklem
Norbert Aschendorff wrote:
> Hi,
> 
> my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site
> 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01
> CEST 2012 l...@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC
> i386) crashes reproducibly when rsync-ing files to an NFSv4 share on
> the FreeBSD machine. The crash makes the system reboot. The crash
> creates files in /var/crash which may be obtained here: [1].
> 
> This problem is not limited to the self-compiled kernel/world
> (stable/9)
> but appears also on pre-compiled 9.1-PRERELEASE. I did not test
> 9.0-RELEASE.
> 
> If I do not use rsync on this NFS share, everything works completely
> fine.
> 
> Workaround: Use rsync over SSH.
> 
> --Norbert
> 
> [1] http://lbo.spheniscida.de/Files/nfs-rsync-crash.tgz (25K), vmcore
> of
> around 300M (90M gzipped, 64M LZMA'd) not included
> 
>From a quick look, the panic is:
Sleeping thread (tid 100099, pid 1599) owns a non-sleepable lock
called from the server side krpc via cv_timedwait_sig().

I assume this means that another mutex or similar is held as well as
the one passed in as an argument to cv_timedwait_sig()?
(I'll keep looking, but I can't spot where another one might be held
 by the NFS or krpc code.)

I'm not knowledgible when it comes to gdb and crash dumps. Is there an
easy command Norbert can type to see all the locks held by
tid 100099, pid 1599?

Is the NFS client using Kerberos or AUTH_SYS for the mount? (And if you
are using Kerberos, have you tried the rsync with an AUTH_SYS mount?)

Does anyone happen to know of outstanding issues (or problems with WITNESS)
for cv_timedwait_sig() called with a locked mutex as the argument lock?
(The mutex will probably get locked by another thread related to the same
 pid, once sleepq_timedwait_sig() unlocks the argument mutex.)

Here's the backtrace from the crash info he referenced, in case someone
else can gain more insight from it:
Unread portion of the kernel message buffer:
Sleeping thread (tid 100099, pid 1599) owns a non-sleepable lock
KDB: stack backtrace of thread 100099:
#0 0xc0aae034 at mi_switch+0xe4
#1 0xc0ae3799 at sleepq_switch+0xd9
#2 0xc0ae3c06 at sleepq_catch_signals+0x3d6
#3 0xc0ae3d04 at sleepq_timedwait_sig+0x14
#4 0xc0a591ff at _cv_timedwait_sig+0x17f
#5 0xc0c87f7e at svc_run_internal+0x7ce
#6 0xc0c87706 at svc_run+0xc6
#7 0xc09f24c4 at nfsrvd_nfsd+0x1d4
#8 0xc0a00ad9 at nfssvc_nfsd+0x109
#9 0xc0c70c58 at sys_nfssvc+0x98
#10 0xc0dfd288 at syscall+0x378
#11 0xc0de64b1 at Xint0x80_syscall+0x21
panic: sleeping thread
cpuid = 0

rick

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


Re: stable/9 panic Bad tailq NEXT(0xffffffff80e52660->tqh_last) != NULL

2012-10-01 Thread John Baldwin
On Thursday, September 27, 2012 4:53:49 pm Sean Bruno wrote:
> On Thu, 2012-09-27 at 10:52 -0700, Sean Bruno wrote:
> > > 
> > > > pcib7:  irq 19 at device 28.7 on pci0
> > > > panic: Bad tailq NEXT(0x80e52660->tqh_last) != NULL
> > > > cpuid = 0
> > > > KDB: stack backtrace:
> > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
> > > > kdb_backtrace() at kdb_backtrace+0x37
> > > > panic() at panic+0x1d8
> > > > rman_init() at rman_init+0x17c
> > > > pcib_alloc_window() at pcib_alloc_window+0x9f
> > > > pcib_attach_common() at pcib_attach_common+0x457
> > > > acpi_pcib_pci_attach() at acpi_pcib_pci_attach+0x1c
> > > > device_attach() at device_attach+0x72
> > > > bus_generic_attach() at bus_generic_attach+0x1a
> > > > acpi_pci_attach() at acpi_pci_attach+0x164
> > > > device_attach() at device_attach+0x72
> > > > bus_generic_attach() at bus_generic_attach+0x1a
> > > > acpi_pcib_attach() at acpi_pcib_attach+0x1a7
> > > > acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0x1f6
> > > > device_attach() at device_attach+0x72
> > > > bus_generic_attach() at bus_generic_attach+0x1a
> > > > acpi_attach() at acpi_attach+0xbc1
> > > > device_attach() at device_attach+0x72
> > > > bus_generic_attach() at bus_generic_attach+0x1a
> > > > nexus_acpi_attach() at nexus_acpi_attach+0x69
> > > > device_attach() at device_attach+0x72
> > > > bus_generic_new_pass() at bus_generic_new_pass+0xd6
> > > > bus_set_pass() at bus_set_pass+0x7a
> > > > configure() at configure+0xa
> > > > mi_startup() at mi_startup+0x77
> > > > btext() at btext+0x2c
> > > > Uptime: 1s
> > > > Automatic reboot in 15 seconds - press a key on the console to abort
> > > > --> Press a key on the console to reboot,
> > > > --> or switch off the system now.
> > > >
> > > 
> > > --
> > > Andriy Gapon
> > > 
> > 
> > resurrecting this thread from my sent items folder, not sure if 
> > mailman will thread this correctly or not
> > 
> > Anyway, after disabling the "broken" pci bridge via some hackery
> > that jhb and eadler had lying around, I was able to get the r620 up 
> > on the "new" BIOS and get an acpidump before and after the firmware update.
> > 
> > I can poke a the machines, but I don't quite see in this nonsense where 
> > it breaks acpi_pcib_pci_attach().  Where should I start poking next?
> > 
> > 
> > http://people.freebsd.org/~sbruno/acpi_112_r620.txt
> > 
> > http://people.freebsd.org/~sbruno/acpi_126_r620.txt
> > 
> > 
> 
> For fun, I added the pciconf output to see if there's anything obviously
> wrong with pcib7.  But, as usual, I have no idea how to interpret this.
> 
> http://people.freebsd.org/~sbruno/r620_pciconf.txt

Can you add extra printfs to see where exactly attach is failing?  I would
start with the attach routine in sys/dev/acpica/acpi_pcib_pci.c:

static int
acpi_pcib_pci_attach(device_t dev)
{
struct acpi_pcib_softc *sc;

ACPI_FUNCTION_TRACE((char *)(uintptr_t)__func__);

pcib_attach_common(dev);
sc = device_get_softc(dev);
sc->ap_handle = acpi_get_handle(dev);
return (acpi_pcib_attach(dev, &sc->ap_prt, sc->ap_pcibsc.secbus));
}

Hmm, so that can only fail inside of acpi_pcib_attach() in
sys/dev/acpica/acpi_pcib.c.  I would add printfs to annotate that.

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


Re: mps in GENERIC, only in amd64? (RELENG_9_1)

2012-10-01 Thread John Baldwin
On Saturday, September 29, 2012 5:58:42 am Harald Schmalzbauer wrote:
>  Hello,
> 
> accidentally I saw that mps is included in sys/amd64/conf/GENERIC, but
> not in sys/i386/conf/GENERIC.
> Is this intended?

Have you tested it on i386?  From the log message, Ken (cc'd) only added it
on amd64 as it hadn't been tested on i386.

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


Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread John Baldwin
On Monday, October 01, 2012 8:07:44 am Rick Macklem wrote:
> Norbert Aschendorff wrote:
> > Hi,
> > 
> > my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site
> > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01
> > CEST 2012 l...@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC
> > i386) crashes reproducibly when rsync-ing files to an NFSv4 share on
> > the FreeBSD machine. The crash makes the system reboot. The crash
> > creates files in /var/crash which may be obtained here: [1].
> > 
> > This problem is not limited to the self-compiled kernel/world
> > (stable/9)
> > but appears also on pre-compiled 9.1-PRERELEASE. I did not test
> > 9.0-RELEASE.
> > 
> > If I do not use rsync on this NFS share, everything works completely
> > fine.
> > 
> > Workaround: Use rsync over SSH.
> > 
> > --Norbert
> > 
> > [1] http://lbo.spheniscida.de/Files/nfs-rsync-crash.tgz (25K), vmcore
> > of
> > around 300M (90M gzipped, 64M LZMA'd) not included
> > 
> >From a quick look, the panic is:
> Sleeping thread (tid 100099, pid 1599) owns a non-sleepable lock
> called from the server side krpc via cv_timedwait_sig().
> 
> I assume this means that another mutex or similar is held as well as
> the one passed in as an argument to cv_timedwait_sig()?

Yes.

> (I'll keep looking, but I can't spot where another one might be held
>  by the NFS or krpc code.)

If this is reproducible, then adding WITNESS to the kernel will add
additional info in the panic message to tell you what other locks are
held and which file:line they were acquired at.

> I'm not knowledgible when it comes to gdb and crash dumps. Is there an
> easy command Norbert can type to see all the locks held by
> tid 100099, pid 1599?

No. :(  Only WITNESS keeps track of that sort of state.

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


Re: atkbd attach excitement during boot

2012-10-01 Thread John Baldwin
On Sunday, September 30, 2012 1:16:23 pm Randy Bush wrote:
> booting 
> 
> FreeBSD fbsd64.psg.com 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r241020: Fri 
Sep 28 07:14:15 UTC 2012 
r...@kaos.glenbarber.us:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> if i do not type a key during boot (after typing  to beastie), i get
> the following
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address   = 0x38
> fault code  = supervisor read data, page not present
> instruction pointer = 0x20:0x80704740
> stack pointer   = 0x28:0x815336e0
> frame pointer   = 0x28:0x81533730
> code segment= base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags= interrupt enabled, resume, IOPL = 0
> current process = 0 (swapper)
> trap number = 12
> panic: page fault
> cpuid = 0
> KDB: stack backtrace:
> #0 0x809221d6 at kdb_backtrace+0x66
> #1 0x808ec40e at panic+0x1ce
> #2 0x80bd91a0 at trap_fatal+0x290
> #3 0x80bd94d8 at trap_pfault+0x1e8
> #4 0x80bd9ade at trap+0x3be
> #5 0x80bc33ff at calltrap+0x8
> #6 0x80be95fb at atkbd_intr+0xab

Can you run 'gdb /boot/kernel/kernel' and do 'l *atkbd_intr+0xab'?

> #7 0x80be9dd6 at atkbd_timeout+0x96
> #8 0x80be9e94 at atkbd_attach_unit+0xb4
> #9 0x80bea0c8 at atkbdattach+0x78

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


Re: atkbd attach excitement during boot

2012-10-01 Thread Randy Bush
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 0; apic id = 00
>> fault virtual address   = 0x38
>> fault code  = supervisor read data, page not present
>> instruction pointer = 0x20:0x80704740
>> stack pointer   = 0x28:0x815336e0
>> frame pointer   = 0x28:0x81533730
>> code segment= base 0x0, limit 0xf, type 0x1b
>> = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags= interrupt enabled, resume, IOPL = 0
>> current process = 0 (swapper)
>> trap number = 12
>> panic: page fault
>> cpuid = 0
>> KDB: stack backtrace:
>> #0 0x809221d6 at kdb_backtrace+0x66
>> #1 0x808ec40e at panic+0x1ce
>> #2 0x80bd91a0 at trap_fatal+0x290
>> #3 0x80bd94d8 at trap_pfault+0x1e8
>> #4 0x80bd9ade at trap+0x3be
>> #5 0x80bc33ff at calltrap+0x8
>> #6 0x80be95fb at atkbd_intr+0xab
> 
> Can you run 'gdb /boot/kernel/kernel' and do 'l *atkbd_intr+0xab'?
> 
>> #7 0x80be9dd6 at atkbd_timeout+0x96
>> #8 0x80be9e94 at atkbd_attach_unit+0xb4
>> #9 0x80bea0c8 at atkbdattach+0x78

fbsd64.psg.com:/root# gdb /boot/kernel/kernel
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 "amd64-marcel-freebsd"...
(gdb) l *atkbd_intr+0xab
0x80be95fb is in atkbd_intr (/usr/src/sys/dev/atkbdc/atkbd.c:512).
507 do {
508 c = atkbd_read_char(kbd, FALSE);
509 } while (c != NOKEY);
510 }
511 return 0;
512 }
513
514 /* test the interface to the device */
515 static int
516 atkbd_test_if(keyboard_t *kbd)

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


[releng_8 tinderbox] failure on mips/mips

2012-10-01 Thread FreeBSD Tinderbox
TB --- 2012-10-01 14:07:03 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-10-01 14:07:03 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 
FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2012-10-01 14:07:03 - starting RELENG_8 tinderbox run for mips/mips
TB --- 2012-10-01 14:07:03 - cleaning the object tree
TB --- 2012-10-01 14:07:04 - checking out /src from 
svn://svn.freebsd.org/base/stable/8
TB --- 2012-10-01 14:07:04 - cd /tinderbox/RELENG_8/mips/mips
TB --- 2012-10-01 14:07:04 - /usr/local/bin/svn cleanup /src
TB --- 2012-10-01 14:07:14 - /usr/local/bin/svn update /src
TB --- 2012-10-01 14:07:21 - At svn revision 241097S
TB --- 2012-10-01 14:07:22 - building world
TB --- 2012-10-01 14:07:22 - CROSS_BUILD_TESTING=YES
TB --- 2012-10-01 14:07:22 - MAKEOBJDIRPREFIX=/obj
TB --- 2012-10-01 14:07:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2012-10-01 14:07:22 - SRCCONF=/dev/null
TB --- 2012-10-01 14:07:22 - TARGET=mips
TB --- 2012-10-01 14:07:22 - TARGET_ARCH=mips
TB --- 2012-10-01 14:07:22 - TZ=UTC
TB --- 2012-10-01 14:07:22 - __MAKE_CONF=/dev/null
TB --- 2012-10-01 14:07:22 - cd /src
TB --- 2012-10-01 14:07:22 - /usr/bin/make -B buildworld
>>> World build started on Mon Oct  1 14:07:23 UTC 2012
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
[...]
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include -c 
/src/games/fortune/strfile/strfile.c
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include  -static 
-L/obj/mips/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy
sh /src/tools/install.sh -s -o root -g wheel -m 555   strfile 
/obj/mips/src/tmp/legacy/usr/games
===> gnu/usr.bin/gperf (obj,depend,all,install)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf created for /src/gnu/usr.bin/gperf
===> gnu/usr.bin/gperf/doc (obj)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf/doc created for 
/src/gnu/usr.bin/gperf/doc
make: don't know how to make iterator.cc. Stop
*** Error code 2

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2012-10-01 14:07:35 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2012-10-01 14:07:35 - ERROR: failed to build world
TB --- 2012-10-01 14:07:35 - 13.16 user 8.13 system 32.03 real


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


Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread Norbert Aschendorff
On 10/01/2012 02:07 PM, Rick Macklem wrote:
> Is the NFS client using Kerberos or AUTH_SYS for the mount? (And if you
> are using Kerberos, have you tried the rsync with an AUTH_SYS mount?)

No, it's not using Kerberos. Only network-based access control or
however it's called (restricted via client IP address).

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


Re: atkbd attach excitement during boot

2012-10-01 Thread John Baldwin
On Monday, October 01, 2012 9:00:36 am Randy Bush wrote:
> >> Fatal trap 12: page fault while in kernel mode
> >> cpuid = 0; apic id = 00
> >> fault virtual address   = 0x38
> >> fault code  = supervisor read data, page not present
> >> instruction pointer = 0x20:0x80704740
> >> stack pointer   = 0x28:0x815336e0
> >> frame pointer   = 0x28:0x81533730
> >> code segment= base 0x0, limit 0xf, type 0x1b
> >> = DPL 0, pres 1, long 1, def32 0, gran 1
> >> processor eflags= interrupt enabled, resume, IOPL = 0
> >> current process = 0 (swapper)
> >> trap number = 12
> >> panic: page fault
> >> cpuid = 0
> >> KDB: stack backtrace:
> >> #0 0x809221d6 at kdb_backtrace+0x66
> >> #1 0x808ec40e at panic+0x1ce
> >> #2 0x80bd91a0 at trap_fatal+0x290
> >> #3 0x80bd94d8 at trap_pfault+0x1e8
> >> #4 0x80bd9ade at trap+0x3be
> >> #5 0x80bc33ff at calltrap+0x8
> >> #6 0x80be95fb at atkbd_intr+0xab
> > 
> > Can you run 'gdb /boot/kernel/kernel' and do 'l *atkbd_intr+0xab'?
> > 
> >> #7 0x80be9dd6 at atkbd_timeout+0x96
> >> #8 0x80be9e94 at atkbd_attach_unit+0xb4
> >> #9 0x80bea0c8 at atkbdattach+0x78
> 
> fbsd64.psg.com:/root# gdb /boot/kernel/kernel
> 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 "amd64-marcel-freebsd"...
> (gdb) l *atkbd_intr+0xab
> 0x80be95fb is in atkbd_intr (/usr/src/sys/dev/atkbdc/atkbd.c:512).
> 507 do {
> 508 c = atkbd_read_char(kbd, FALSE);
> 509 } while (c != NOKEY);
> 510 }
> 511 return 0;
> 512 }

Humm.  It seems this wasn't the actual faulting instruction.  Can you do
'l *0x80704740'?

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


Re: atkbd attach excitement during boot

2012-10-01 Thread Randy Bush
> Humm.  It seems this wasn't the actual faulting instruction.  Can you do
> 'l *0x80704740'?

(gdb) l *0x80704740
0x80704740 is in sckbdevent (/usr/src/sys/dev/syscons/syscons.c:743).
738  * the Xaccel-2.1 keyboard hang, but it can't hurt. XXX
739  */
740 while ((c = scgetc(sc, SCGETC_NONBLOCK)) != NOKEY) {
741
742 cur_tty = SC_DEV(sc, sc->cur_scp->index);
743 if (!tty_opened(cur_tty))
744 continue;
745
746 if ((*sc->cur_scp->tsw->te_input)(sc->cur_scp, c, cur_tty))
747 continue;
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: mps in GENERIC, only in amd64? (RELENG_9_1)

2012-10-01 Thread Kenneth D. Merry
On Mon, Oct 01, 2012 at 08:49:36 -0400, John Baldwin wrote:
> On Saturday, September 29, 2012 5:58:42 am Harald Schmalzbauer wrote:
> >  Hello,
> > 
> > accidentally I saw that mps is included in sys/amd64/conf/GENERIC, but
> > not in sys/i386/conf/GENERIC.
> > Is this intended?
> 
> Have you tested it on i386?  From the log message, Ken (cc'd) only added it
> on amd64 as it hadn't been tested on i386.

That was certainly the case two years ago.  Since then, though, I think
the LSI folks have tested it on i386.  If we get reports of success
using it on i386, I don't see any issue with putting it in GENERIC.

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


Re: mod_auth_kerb2 broken in 8-STABLE? Or is it heimdal to blame?

2012-10-01 Thread George Mamalakis

On 04/07/11 14:08, George Mamalakis wrote:

On 06/04/2011 18:29, George Mamalakis wrote:

Dear all,

I installed mod_auth_kerb2 on my FreeBSD 8-STABLE machine and tried 
to use it. After the installation (which was successful(?!?)), the 
server refused to start giving the error:


# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22 configuration:
httpd: Syntax error on line 103 of 
/usr/local/etc/apache22/httpd.conf: Cannot load 
/usr/local/libexec/apache22/mod_auth_kerb.so into server: 
/usr/local/libexec/apache22/mod_auth_kerb.so: Undefined symbol 
"gsskrb5_register_acceptor_identity"

Starting apache22.
httpd: Syntax error on line 103 of 
/usr/local/etc/apache22/httpd.conf: Cannot load 
/usr/local/libexec/apache22/mod_auth_kerb.so into server: 
/usr/local/libexec/apache22/mod_auth_kerb.so: Undefined symbol 
"gsskrb5_register_acceptor_identity"

/usr/local/etc/rc.d/apache22: WARNING: failed to start apache22

but ldd showed:

# ldd /usr/local/libexec/apache22/mod_auth_kerb.so
/usr/local/libexec/apache22/mod_auth_kerb.so:
libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x800c0)
libheimntlm.so.10 => /usr/lib/libheimntlm.so.10 (0x800d0a000)
libkrb5.so.10 => /usr/lib/libkrb5.so.10 (0x800e0f000)
libhx509.so.10 => /usr/lib/libhx509.so.10 (0x800f7e000)
libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x8010be000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x8011c)
libasn1.so.10 => /usr/lib/libasn1.so.10 (0x801461000)
libroken.so.10 => /usr/lib/libroken.so.10 (0x8015e3000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x8016f5000)
libc.so.7 => /lib/libc.so.7 (0x800647000)

which showed that everything should have been fine. I googled it a 
bit and found this thread regarding my error message: 
http://forum.nginx.org/read.php?23,88476 , which started on May 2010, 
and pointed to this PR: 
http://www.freebsd.org/cgi/query-pr.cgi?pr=147454 , which started on 
June 2010. What is stated, is that heimdal-1.1 was broken in FreeBSD, 
and that it should be fixed at some moment in the future. (I tested 
mod_auth_kerb2 on another machine running heimdal from ports (1.4_1) 
and I had exactly the same problem).


I searched to find where this notorious function 
(gsskrb5_register_acceptor_identity) was located, and I found its 
declaration in: /usr/include/gssapi/gssapi_krb5.h, and its definition 
in: /usr/lib/libgssapi_krb5.so.


So, I added -lgssapi_krb5 in KRB5_LDFLAGS variable of 
/usr/ports/www/mod_auth_kerb2/work/mod_auth_kerb-5.4/Makefile , since 
this where the location of gsskrb5_register_acceptor_identity 
originally seemed to be, and reinstalled the port using gmake this 
time (inside the port's work directory). After that, the module works 
just fine. The initial content of this line was:


KRB5_LDFLAGS = -L/usr/lib -lgssapi -lheimntlm -lkrb5 -lhx509 
-lcom_err -lcrypto -lasn1 -lroken -lcrypt


I've sent an analogous email to the port maintainer, but I am not 
sure if it is their "fault". Hence, I decided to send this email to 
the stable list for two reasons: First, someone else may be having a 
similar problem and wants to find a rough solution. Secondly, there 
are people reading this list that know heimdal's code, so somebody 
may know another (much more elegant) way to fix this bug.


Thank you all for your time in advance,

Regards,

mamalos.



OK,

I spoke with the maintainer who confirmed the problem. He also 
suggested to change line 96 of /usb/bin/krb5-config to include 
gssapi_krb5 among its libraries. He also gave me the relevant patch, 
and asked me to send a PR to FreeBSD. The patch is as follows:


--- /usr/bin/krb5-config.orig   2011-02-17 03:18:57.0 +0100
+++ /usr/bin/krb5-config2011-04-06 23:41:31.0 +0200
@@ -93,7 +93,7 @@
 lib_flags="-L${libdir}"
 case $library in
 gssapi)
-   lib_flags="$lib_flags -lgssapi -lheimntlm"
+   lib_flags="$lib_flags -lgssapi -lgssapi_krb5 -lheimntlm"
;;
 kadm-client)
lib_flags="$lib_flags -lkadm5clnt"



And the relevant PR is:

http://www.freebsd.org/cgi/query-pr.cgi?pr=156245

Thank you all for your time,

mamalos


Hi all,

I am bringing this matter back again because the same things hold for my 
current system too (/usr/bin/krb5-config does not seem to link 
gssapi-things properly):


# uname -a
FreeBSD example.com 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Jun 18 
21:04:14 EEST 2012 r...@example.com:/usr/obj/usr/src/sys/FILESRV  amd64

# pkg_info -Ix apache kerb
ap22-mod_auth_kerb-5.4_3 An Apache module for authenticating users with 
Kerberos v5

apache22-2.2.22_8   Version 2.2.x of Apache web server with prefork MPM.

Should I send a PR or is there something that I've done wrong?

Thanx all in advance.

--
George Mamalakis

IT and Security Officer
Electrical and Computer Engineer (Aristotle Un. of Thessaloniki),
MSc (Imperial College of London)

Department of Electrical and Computer Engineering
Faculty of Engineering
Aristotle University of Thessalonik

[releng_8 tinderbox] failure on mips/mips

2012-10-01 Thread FreeBSD Tinderbox
TB --- 2012-10-01 18:01:07 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-10-01 18:01:07 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 
FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2012-10-01 18:01:07 - starting RELENG_8 tinderbox run for mips/mips
TB --- 2012-10-01 18:01:07 - cleaning the object tree
TB --- 2012-10-01 18:01:08 - checking out /src from 
svn://svn.freebsd.org/base/stable/8
TB --- 2012-10-01 18:01:08 - cd /tinderbox/RELENG_8/mips/mips
TB --- 2012-10-01 18:01:08 - /usr/local/bin/svn cleanup /src
TB --- 2012-10-01 18:01:17 - /usr/local/bin/svn update /src
TB --- 2012-10-01 18:06:02 - WARNING: /usr/local/bin/svn returned exit code  1 
TB --- 2012-10-01 18:06:02 - WARNING: sleeping 30 s and retrying...
TB --- 2012-10-01 18:06:32 - /usr/local/bin/svn update /src
TB --- 2012-10-01 18:06:39 - At svn revision 241109S
TB --- 2012-10-01 18:06:40 - building world
TB --- 2012-10-01 18:06:40 - CROSS_BUILD_TESTING=YES
TB --- 2012-10-01 18:06:40 - MAKEOBJDIRPREFIX=/obj
TB --- 2012-10-01 18:06:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2012-10-01 18:06:40 - SRCCONF=/dev/null
TB --- 2012-10-01 18:06:40 - TARGET=mips
TB --- 2012-10-01 18:06:40 - TARGET_ARCH=mips
TB --- 2012-10-01 18:06:40 - TZ=UTC
TB --- 2012-10-01 18:06:40 - __MAKE_CONF=/dev/null
TB --- 2012-10-01 18:06:40 - cd /src
TB --- 2012-10-01 18:06:40 - /usr/bin/make -B buildworld
>>> World build started on Mon Oct  1 18:06:41 UTC 2012
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
[...]
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include -c 
/src/games/fortune/strfile/strfile.c
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include  -static 
-L/obj/mips/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy
sh /src/tools/install.sh -s -o root -g wheel -m 555   strfile 
/obj/mips/src/tmp/legacy/usr/games
===> gnu/usr.bin/gperf (obj,depend,all,install)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf created for /src/gnu/usr.bin/gperf
===> gnu/usr.bin/gperf/doc (obj)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf/doc created for 
/src/gnu/usr.bin/gperf/doc
make: don't know how to make iterator.cc. Stop
*** Error code 2

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2012-10-01 18:06:50 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2012-10-01 18:06:50 - ERROR: failed to build world
TB --- 2012-10-01 18:06:50 - 12.32 user 7.42 system 343.36 real


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


RE: mps in GENERIC, only in amd64? (RELENG_9_1)

2012-10-01 Thread Desai, Kashyap


> -Original Message-
> From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> sta...@freebsd.org] On Behalf Of Kenneth D. Merry
> Sent: Monday, October 01, 2012 8:58 PM
> To: John Baldwin
> Cc: Harald Schmalzbauer; freebsd-stable@freebsd.org
> Subject: Re: mps in GENERIC, only in amd64? (RELENG_9_1)
> 
> On Mon, Oct 01, 2012 at 08:49:36 -0400, John Baldwin wrote:
> > On Saturday, September 29, 2012 5:58:42 am Harald Schmalzbauer wrote:
> > >  Hello,
> > >
> > > accidentally I saw that mps is included in sys/amd64/conf/GENERIC,
> but
> > > not in sys/i386/conf/GENERIC.
> > > Is this intended?
> >
> > Have you tested it on i386?  From the log message, Ken (cc'd) only
> added it
> > on amd64 as it hadn't been tested on i386.
> 
> That was certainly the case two years ago.  Since then, though, I think
> the LSI folks have tested it on i386.  If we get reports of success
> using it on i386, I don't see any issue with putting it in GENERIC.

YES LSI has tested i386 arch on different Released FreeBSDs of 7.x, 8.x and 9.x 
series.

~ Kashyap

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


Re: mps in GENERIC, only in amd64? (RELENG_9_1)

2012-10-01 Thread Kenneth D. Merry
On Mon, Oct 01, 2012 at 23:38:33 +0530, Desai, Kashyap wrote:
> 
> 
> > -Original Message-
> > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> > sta...@freebsd.org] On Behalf Of Kenneth D. Merry
> > Sent: Monday, October 01, 2012 8:58 PM
> > To: John Baldwin
> > Cc: Harald Schmalzbauer; freebsd-stable@freebsd.org
> > Subject: Re: mps in GENERIC, only in amd64? (RELENG_9_1)
> > 
> > On Mon, Oct 01, 2012 at 08:49:36 -0400, John Baldwin wrote:
> > > On Saturday, September 29, 2012 5:58:42 am Harald Schmalzbauer wrote:
> > > >  Hello,
> > > >
> > > > accidentally I saw that mps is included in sys/amd64/conf/GENERIC,
> > but
> > > > not in sys/i386/conf/GENERIC.
> > > > Is this intended?
> > >
> > > Have you tested it on i386?  From the log message, Ken (cc'd) only
> > added it
> > > on amd64 as it hadn't been tested on i386.
> > 
> > That was certainly the case two years ago.  Since then, though, I think
> > the LSI folks have tested it on i386.  If we get reports of success
> > using it on i386, I don't see any issue with putting it in GENERIC.
> 
> YES LSI has tested i386 arch on different Released FreeBSDs of 7.x, 8.x and 
> 9.x series.
> 

That confirms it.  I'll go ahead and check it into head if someone with an
i386 build environment can confirm that the driver in head builds properly
on i386.

Thanks,

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


Re: mps in GENERIC, only in amd64? (RELENG_9_1)

2012-10-01 Thread John Baldwin
On Monday, October 01, 2012 3:54:50 pm Kenneth D. Merry wrote:
> On Mon, Oct 01, 2012 at 23:38:33 +0530, Desai, Kashyap wrote:
> > 
> > 
> > > -Original Message-
> > > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> > > sta...@freebsd.org] On Behalf Of Kenneth D. Merry
> > > Sent: Monday, October 01, 2012 8:58 PM
> > > To: John Baldwin
> > > Cc: Harald Schmalzbauer; freebsd-stable@freebsd.org
> > > Subject: Re: mps in GENERIC, only in amd64? (RELENG_9_1)
> > > 
> > > On Mon, Oct 01, 2012 at 08:49:36 -0400, John Baldwin wrote:
> > > > On Saturday, September 29, 2012 5:58:42 am Harald Schmalzbauer wrote:
> > > > >  Hello,
> > > > >
> > > > > accidentally I saw that mps is included in sys/amd64/conf/GENERIC,
> > > but
> > > > > not in sys/i386/conf/GENERIC.
> > > > > Is this intended?
> > > >
> > > > Have you tested it on i386?  From the log message, Ken (cc'd) only
> > > added it
> > > > on amd64 as it hadn't been tested on i386.
> > > 
> > > That was certainly the case two years ago.  Since then, though, I think
> > > the LSI folks have tested it on i386.  If we get reports of success
> > > using it on i386, I don't see any issue with putting it in GENERIC.
> > 
> > YES LSI has tested i386 arch on different Released FreeBSDs of 7.x, 8.x 
and 9.x series.
> > 
> 
> That confirms it.  I'll go ahead and check it into head if someone with an
> i386 build environment can confirm that the driver in head builds properly
> on i386.

The module build is already enabled on all platforms in sys/modules/Makefile.
You can just add it to i386 GENERIC in a checkout and do
'make buildworld TARGET=i386 && make buildkernel TARGET=i386' to test a cross-
build.

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


Re: mps in GENERIC, only in amd64? (RELENG_9_1)

2012-10-01 Thread Kenneth D. Merry
On Mon, Oct 01, 2012 at 16:59:58 -0400, John Baldwin wrote:
> On Monday, October 01, 2012 3:54:50 pm Kenneth D. Merry wrote:
> > On Mon, Oct 01, 2012 at 23:38:33 +0530, Desai, Kashyap wrote:
> > > 
> > > 
> > > > -Original Message-
> > > > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> > > > sta...@freebsd.org] On Behalf Of Kenneth D. Merry
> > > > Sent: Monday, October 01, 2012 8:58 PM
> > > > To: John Baldwin
> > > > Cc: Harald Schmalzbauer; freebsd-stable@freebsd.org
> > > > Subject: Re: mps in GENERIC, only in amd64? (RELENG_9_1)
> > > > 
> > > > On Mon, Oct 01, 2012 at 08:49:36 -0400, John Baldwin wrote:
> > > > > On Saturday, September 29, 2012 5:58:42 am Harald Schmalzbauer wrote:
> > > > > >  Hello,
> > > > > >
> > > > > > accidentally I saw that mps is included in sys/amd64/conf/GENERIC,
> > > > but
> > > > > > not in sys/i386/conf/GENERIC.
> > > > > > Is this intended?
> > > > >
> > > > > Have you tested it on i386?  From the log message, Ken (cc'd) only
> > > > added it
> > > > > on amd64 as it hadn't been tested on i386.
> > > > 
> > > > That was certainly the case two years ago.  Since then, though, I think
> > > > the LSI folks have tested it on i386.  If we get reports of success
> > > > using it on i386, I don't see any issue with putting it in GENERIC.
> > > 
> > > YES LSI has tested i386 arch on different Released FreeBSDs of 7.x, 8.x 
> and 9.x series.
> > > 
> > 
> > That confirms it.  I'll go ahead and check it into head if someone with an
> > i386 build environment can confirm that the driver in head builds properly
> > on i386.
> 
> The module build is already enabled on all platforms in sys/modules/Makefile.
> You can just add it to i386 GENERIC in a checkout and do
> 'make buildworld TARGET=i386 && make buildkernel TARGET=i386' to test a cross-
> build.

I just figured I'd save myself the time if someone else had already done
it.

I built it on i386 and just checked in the change.

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


[releng_8 tinderbox] failure on mips/mips

2012-10-01 Thread FreeBSD Tinderbox
TB --- 2012-10-01 21:56:44 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-10-01 21:56:44 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 
FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2012-10-01 21:56:44 - starting RELENG_8 tinderbox run for mips/mips
TB --- 2012-10-01 21:56:44 - cleaning the object tree
TB --- 2012-10-01 21:56:45 - checking out /src from 
svn://svn.freebsd.org/base/stable/8
TB --- 2012-10-01 21:56:45 - cd /tinderbox/RELENG_8/mips/mips
TB --- 2012-10-01 21:56:45 - /usr/local/bin/svn cleanup /src
TB --- 2012-10-01 21:56:54 - /usr/local/bin/svn update /src
TB --- 2012-10-01 22:01:56 - WARNING: /usr/local/bin/svn returned exit code  1 
TB --- 2012-10-01 22:01:56 - WARNING: sleeping 30 s and retrying...
TB --- 2012-10-01 22:02:26 - /usr/local/bin/svn update /src
TB --- 2012-10-01 22:02:33 - At svn revision 241114S
TB --- 2012-10-01 22:02:34 - building world
TB --- 2012-10-01 22:02:34 - CROSS_BUILD_TESTING=YES
TB --- 2012-10-01 22:02:34 - MAKEOBJDIRPREFIX=/obj
TB --- 2012-10-01 22:02:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2012-10-01 22:02:34 - SRCCONF=/dev/null
TB --- 2012-10-01 22:02:34 - TARGET=mips
TB --- 2012-10-01 22:02:34 - TARGET_ARCH=mips
TB --- 2012-10-01 22:02:34 - TZ=UTC
TB --- 2012-10-01 22:02:34 - __MAKE_CONF=/dev/null
TB --- 2012-10-01 22:02:34 - cd /src
TB --- 2012-10-01 22:02:34 - /usr/bin/make -B buildworld
>>> World build started on Mon Oct  1 22:02:35 UTC 2012
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
[...]
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include -c 
/src/games/fortune/strfile/strfile.c
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include  -static 
-L/obj/mips/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy
sh /src/tools/install.sh -s -o root -g wheel -m 555   strfile 
/obj/mips/src/tmp/legacy/usr/games
===> gnu/usr.bin/gperf (obj,depend,all,install)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf created for /src/gnu/usr.bin/gperf
===> gnu/usr.bin/gperf/doc (obj)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf/doc created for 
/src/gnu/usr.bin/gperf/doc
make: don't know how to make iterator.cc. Stop
*** Error code 2

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2012-10-01 22:02:44 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2012-10-01 22:02:44 - ERROR: failed to build world
TB --- 2012-10-01 22:02:44 - 12.08 user 7.90 system 360.26 real


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


Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread Rick Macklem
John Baldwin wrote:
> On Monday, October 01, 2012 8:07:44 am Rick Macklem wrote:
> > Norbert Aschendorff wrote:
> > > Hi,
> > >
> > > my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site
> > > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29
> > > 12:52:01
> > > CEST 2012
> > > l...@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC
> > > i386) crashes reproducibly when rsync-ing files to an NFSv4 share
> > > on
> > > the FreeBSD machine. The crash makes the system reboot. The crash
> > > creates files in /var/crash which may be obtained here: [1].
> > >
> > > This problem is not limited to the self-compiled kernel/world
> > > (stable/9)
> > > but appears also on pre-compiled 9.1-PRERELEASE. I did not test
> > > 9.0-RELEASE.
> > >
> > > If I do not use rsync on this NFS share, everything works
> > > completely
> > > fine.
> > >
> > > Workaround: Use rsync over SSH.
> > >
> > > --Norbert
> > >
> > > [1] http://lbo.spheniscida.de/Files/nfs-rsync-crash.tgz (25K),
> > > vmcore
> > > of
> > > around 300M (90M gzipped, 64M LZMA'd) not included
> > >
> > >From a quick look, the panic is:
> > Sleeping thread (tid 100099, pid 1599) owns a non-sleepable lock
> > called from the server side krpc via cv_timedwait_sig().
> >
> > I assume this means that another mutex or similar is held as well as
> > the one passed in as an argument to cv_timedwait_sig()?
> 
> Yes.
> 
> > (I'll keep looking, but I can't spot where another one might be held
> >  by the NFS or krpc code.)
> 
> If this is reproducible, then adding WITNESS to the kernel will add
> additional info in the panic message to tell you what other locks are
> held and which file:line they were acquired at.
> 
Norbert, would you be able to build a kernel with WITNESS and then reproduce
it?

> > I'm not knowledgible when it comes to gdb and crash dumps. Is there
> > an
> > easy command Norbert can type to see all the locks held by
> > tid 100099, pid 1599?
> 
> No. :( Only WITNESS keeps track of that sort of state.
> 
Ok, thanks. (At least a know a little more about gdb and kernel dumps now;-)

rick

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


ZFS fails to receive valid snapshots (patch included)

2012-10-01 Thread Steven Hartland

Just a quick heads up about an issue we've been seeing
here recently where zfs receive fails on valid replication
streams.

Problem:-
When using zfs receive to restore data saved with zfs send
there is the possibility that the receive will fail due to
replication of snapshots information being processed in a
random order.

In addition to this when receiving snapshots where the parent
from snapshot is replaced by another needless failures occur
which can be seen clearly in verbose mode.

More info and a fix can be found in the PR
http://www.freebsd.org/cgi/query-pr.cgi?pr=172259

Any feedback welcome

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

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


[releng_8 tinderbox] failure on mips/mips

2012-10-01 Thread FreeBSD Tinderbox
TB --- 2012-10-02 01:52:25 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-10-02 01:52:25 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 
FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2012-10-02 01:52:25 - starting RELENG_8 tinderbox run for mips/mips
TB --- 2012-10-02 01:52:25 - cleaning the object tree
TB --- 2012-10-02 01:52:26 - checking out /src from 
svn://svn.freebsd.org/base/stable/8
TB --- 2012-10-02 01:52:26 - cd /tinderbox/RELENG_8/mips/mips
TB --- 2012-10-02 01:52:26 - /usr/local/bin/svn cleanup /src
TB --- 2012-10-02 01:52:35 - /usr/local/bin/svn update /src
TB --- 2012-10-02 01:52:43 - At svn revision 241118S
TB --- 2012-10-02 01:52:44 - building world
TB --- 2012-10-02 01:52:44 - CROSS_BUILD_TESTING=YES
TB --- 2012-10-02 01:52:44 - MAKEOBJDIRPREFIX=/obj
TB --- 2012-10-02 01:52:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2012-10-02 01:52:44 - SRCCONF=/dev/null
TB --- 2012-10-02 01:52:44 - TARGET=mips
TB --- 2012-10-02 01:52:44 - TARGET_ARCH=mips
TB --- 2012-10-02 01:52:44 - TZ=UTC
TB --- 2012-10-02 01:52:44 - __MAKE_CONF=/dev/null
TB --- 2012-10-02 01:52:44 - cd /src
TB --- 2012-10-02 01:52:44 - /usr/bin/make -B buildworld
>>> World build started on Tue Oct  2 01:52:45 UTC 2012
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
[...]
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include -c 
/src/games/fortune/strfile/strfile.c
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include  -static 
-L/obj/mips/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy
sh /src/tools/install.sh -s -o root -g wheel -m 555   strfile 
/obj/mips/src/tmp/legacy/usr/games
===> gnu/usr.bin/gperf (obj,depend,all,install)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf created for /src/gnu/usr.bin/gperf
===> gnu/usr.bin/gperf/doc (obj)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf/doc created for 
/src/gnu/usr.bin/gperf/doc
make: don't know how to make iterator.cc. Stop
*** Error code 2

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2012-10-02 01:52:57 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2012-10-02 01:52:57 - ERROR: failed to build world
TB --- 2012-10-02 01:52:57 - 13.07 user 8.46 system 32.62 real


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


[releng_8 tinderbox] failure on mips/mips

2012-10-01 Thread FreeBSD Tinderbox
TB --- 2012-10-02 05:42:39 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-10-02 05:42:39 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 
FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2012-10-02 05:42:39 - starting RELENG_8 tinderbox run for mips/mips
TB --- 2012-10-02 05:42:39 - cleaning the object tree
TB --- 2012-10-02 05:42:40 - checking out /src from 
svn://svn.freebsd.org/base/stable/8
TB --- 2012-10-02 05:42:40 - cd /tinderbox/RELENG_8/mips/mips
TB --- 2012-10-02 05:42:40 - /usr/local/bin/svn cleanup /src
TB --- 2012-10-02 05:42:53 - /usr/local/bin/svn update /src
TB --- 2012-10-02 05:43:03 - At svn revision 241121S
TB --- 2012-10-02 05:43:04 - building world
TB --- 2012-10-02 05:43:04 - CROSS_BUILD_TESTING=YES
TB --- 2012-10-02 05:43:04 - MAKEOBJDIRPREFIX=/obj
TB --- 2012-10-02 05:43:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2012-10-02 05:43:04 - SRCCONF=/dev/null
TB --- 2012-10-02 05:43:04 - TARGET=mips
TB --- 2012-10-02 05:43:04 - TARGET_ARCH=mips
TB --- 2012-10-02 05:43:04 - TZ=UTC
TB --- 2012-10-02 05:43:04 - __MAKE_CONF=/dev/null
TB --- 2012-10-02 05:43:04 - cd /src
TB --- 2012-10-02 05:43:04 - /usr/bin/make -B buildworld
>>> World build started on Tue Oct  2 05:43:04 UTC 2012
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
[...]
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include -c 
/src/games/fortune/strfile/strfile.c
cc -O2 -pipe   -I/obj/mips/src/tmp/legacy/usr/include  -static 
-L/obj/mips/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy
sh /src/tools/install.sh -s -o root -g wheel -m 555   strfile 
/obj/mips/src/tmp/legacy/usr/games
===> gnu/usr.bin/gperf (obj,depend,all,install)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf created for /src/gnu/usr.bin/gperf
===> gnu/usr.bin/gperf/doc (obj)
/obj/mips/src/tmp/src/gnu/usr.bin/gperf/doc created for 
/src/gnu/usr.bin/gperf/doc
make: don't know how to make iterator.cc. Stop
*** Error code 2

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2012-10-02 05:43:17 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2012-10-02 05:43:17 - ERROR: failed to build world
TB --- 2012-10-02 05:43:17 - 13.43 user 8.01 system 38.14 real


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