date:20080118

On Friday 18 January 2008 09:31:44 am Pete French wrote:
  Just the stack trace offsets.
 
 is all the info you need here?
 
 http://toybox.twisted.org.uk/~pete/acpi_panic.jpg

Yep.

So it appears to be dying here:

(gdb) l *madt_probe+0x119
0xc06e7c69 is in madt_probe (/usr/src/sys/i386/acpica/madt.c:241).
236 if (xsdt == NULL) {
237 if (bootverbose)
238 printf(MADT: Failed to map XSDT\n);
239 return (ENXIO);
240 }
241 count = (xsdt-Length - sizeof(ACPI_TABLE_HEADER)) /
242 sizeof(UINT64);
243 for (i = 0; i  count; i++)
244 if (madt_probe_table(xsdt-TableOffsetEntry[i]))
245 break;

where it reads 'xsdt-Length'.  xsdt was just mapped into a temporary part of
KVA (used for kernel dumps) a few lines earlier:

218 /*
219  * For ACPI = 2.0, use the XSDT if it is available.
220  * Otherwise, use the RSDT.  We map the XSDT or RSDT at page 1
221  * in the crashdump area.  Page 0 is used to map in the
222  * headers of candidate ACPI tables.
223  */
224 if (rsdp-Revision = 2  rsdp-XsdtPhysicalAddress != 0) {
225 /*
226  * AcpiOsGetRootPointer only verifies the checksum for
227  * the version 1.0 portion of the RSDP.  Version 2.0 has
228  * an additional checksum that we verify first.
229  */
230 if (AcpiTbChecksum(rsdp, ACPI_RSDP_XCHECKSUM_LENGTH) != 
0) {
231 if (bootverbose)
232 printf(MADT: RSDP failed extended 
checksum\n);
233 return (ENXIO);
234 }
235 xsdt = madt_map_table(rsdp-XsdtPhysicalAddress, 1, 
XSDT_SIG);

You can try adding some printfs to see what the values of 
'rsdp-XsdtPhysicalAddress' and
'xsdt' after the call to madt_map_table() are.  Actually, try this perhaps:

Index: madt.c
===
RCS file: /host/cvs/usr/cvs/src/sys/i386/acpica/madt.c,v
retrieving revision 1.19.2.4
diff -u -r1.19.2.4 madt.c
--- madt.c  5 Oct 2007 15:22:36 -   1.19.2.4
+++ madt.c  18 Jan 2008 15:01:40 -
@@ -164,7 +164,20 @@
}
length = header-Length;
madt_unmap(header, sizeof(ACPI_TABLE_HEADER));
+   if (length  (MAXDUMPPGS - offset) * PAGE_SIZE) {
+   printf(MADT: %s is too long, truncating\n, sig);
+   length = (MAXDUMPPGS - offset) * PAGE_SIZE;
+   }
table = madt_map(pa, offset, length);
+   header = table;
+   if (header-Length != length) {
+   /*
+* If we truncated the table, fixup the length to
+* perpetuate the lie and skip the checksum.
+*/
+   header-Length = length;
+   return (table);
+   }
if (ACPI_FAILURE(AcpiTbVerifyTableChecksum(table))) {
if (bootverbose)
printf(MADT: Failed checksum for table %s\n, sig);
@@ -267,6 +280,10 @@
if (bootverbose)
printf(MADT: Found table at 0x%jx\n,
(uintmax_t)madt_physaddr);
+   if (madt_length  MAXDUMPPGS * PAGE_SIZE) {
+   printf(MADT: Table is too large, ignoring\n);
+   return (ENXIO);
+   }
 
/*
 * Verify that we can map the full table and that its checksum is


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

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

On Thursday 17 January 2008 07:39:54 pm Pete French wrote:
  MADT is the ACPI table that enumerates APICs.  Do you have the offset of 
  madt_probe()?
 
 I am sujre I can get it for you - do I need to do anything special
 in DDB, or is it just the numbers in the bt that you are after ?
 I can make this panic very easily and do whatever is necessary to
 get info out.

Just the stack trace offsets.

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

Re: kldstat causes kernel to print odd message

On Friday 18 January 2008 12:57:54 am Peter Jeremy wrote:
 On Fri, Jan 18, 2008 at 08:17:40AM +1030, Daniel O'Connor wrote:
 On Fri, 18 Jan 2008, John Baldwin wrote:
  amd64 uses link_elf_obj.c, all the other archs use link_elf.c, hence
  the duplication.
 
 Then why does amd64 need link_elf.c at all?

I don't think it does, but it's currently marked standard in sys/conf/files
so it is probably laziness (i.e. moving it to all the sys/conf/files.arch
for non-amd64) that keeps it in there.

 I guess one option would be to put #ifdef amd64 around the error message 
 in link_elf.c.
 
 If there's a possibility that multiple ELF linkers could be required in
 the future, a cleaner option might be to make link_elf_error() just cache
 the error message and only report it after all possible linkers have
 refused to load the file.

I think this is the better idea.

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

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

 So it appears to be dying here:

 (gdb) l *madt_probe+0x119
 0xc06e7c69 is in madt_probe (/usr/src/sys/i386/acpica/madt.c:241).
 236 if (xsdt == NULL) {
 237 if (bootverbose)
 238 printf(MADT: Failed to map XSDT\n);
 239 return (ENXIO);
 240 }
 241 count = (xsdt-Length - sizeof(ACPI_TABLE_HEADER)) /
 242 sizeof(UINT64);
 243 for (i = 0; i  count; i++)
 244 if 
 (madt_probe_table(xsdt-TableOffsetEntry[i]))
 245 break;

 where it reads 'xsdt-Length'.  xsdt was just mapped into a temporary part of
 KVA (used for kernel dumps) a few lines earlier:

O.K., that is interesting, because my source code doesnt look like thiat,
mine uses 'xsdt-Header.Length' instead of 'xsdt-Length' - is that
code above from 7.0 ?

 You can try adding some printfs to see what the values of 
 'rsdp-XsdtPhysicalAddress' and
 'xsdt' after the call to madt_map_table() are.  Actually, try this perhaps:

Thanks for the patch - it didn;t help matters unfortunately, but I am
adding some printfs on xsdt itself and also rsdp-XsdtPhysicalAddress to
see what we get.

Will build a new kernel and let you know.

cheers,

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

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

 So it appears to be dying here:

 (gdb) l *madt_probe+0x119
 0xc06e7c69 is in madt_probe (/usr/src/sys/i386/acpica/madt.c:241).
 236 if (xsdt == NULL) {
 237 if (bootverbose)
 238 printf(MADT: Failed to map XSDT\n);
 239 return (ENXIO);
 240 }
 241 count = (xsdt-Length - sizeof(ACPI_TABLE_HEADER)) /
 242 sizeof(UINT64);
 243 for (i = 0; i  count; i++)
 244 if 
 (madt_probe_table(xsdt-TableOffsetEntry[i]))
 245 break;

Turns out that it isn't - it's in the other branch of the if using the
RSDT instead of the XSDT. Not sure why the debugger was giving
misleading information. I added prints to find out which path it was
taking and to print out some values after the line
rsdt = madt_map_table(rsdp-RsdtPhysicalAddress, 1, ACPI_SIG_RSDT);

The value of rsdtl is 0x800e7610, but the value of rsdp-XsdtPhysicalAddress
is zero! So I guess that is where the panic is comming from. So where
now ? Is there an equivalent patch to the one you emailed
earlier for this branch of the if ?

I wont have access to the machine over the weekend, but I can make more tests
on monday morning.

thanks for the help,

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

Re: PCI MSI (was Re: What current Dell Systems are supported/work)

On Friday 18 January 2008 05:30:06 am Parv wrote:
(Dropped Vivek K from recipient list; edited the URLs in my previous
message.)

in message [EMAIL PROTECTED],
wrote John Baldwin thusly...

On Thursday 17 January 2008 06:05:17 am Parv wrote:
...
Speaking of MSI being on by default in recent 6-STABLE ... well,
that caused my ThinkPad T61 (8859-CTO) ...

dmesg:

http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/dmesg

kernel (combined for easy perusal):

http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/kern/combined/T61-SMP.debug--combined

/boot/device.hints:

http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/boot/device.hints

For starters, can you get the output of 'pciconf -lc'?

Hi John,

You can find pciconf -lc at ...

http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lc

and pciconf -lv, just in case ...

http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lv

There was no page fault or trap 12 message when the panic happened.
After some of messages are printed (as in dmesg), kdb is entered ...

Tomorrow, rather later today, I will type up the trace output.
Please let me know if you would like to see any other output that I
could possibly provide.

This is good enough for me to see the bug, I'll work on fixing it. There are
some locking changes in the x86 interrupt code I need to MFC.

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

[releng_7 tinderbox] failure on ia64/ia64

TB --- 2008-01-18 20:39:33 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-18 20:39:33 - starting RELENG_7 tinderbox run for ia64/ia64
TB --- 2008-01-18 20:39:33 - cleaning the object tree
TB --- 2008-01-18 20:39:50 - cvsupping the source tree
TB --- 2008-01-18 20:39:50 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/ia64/ia64/supfile
TB --- 2008-01-18 20:39:58 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-18 20:39:58 - cd /src
TB --- 2008-01-18 20:39:58 - /usr/bin/make -B buildworld
 World build started on Fri Jan 18 20:39:59 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-18 20:49:54 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-18 20:49:54 - ERROR: failed to build world
TB --- 2008-01-18 20:49:54 - tinderbox aborted
TB --- 508.08 user 43.73 system 620.65 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Xin LI

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Steven Hartland wrote:
 With the announcement of 6.3 and with 7.0 looking like it wont be far
 behind I'd interested to hear what people thought of the relative
 benefits of each where?
 
 I know 7 has had a lot of work done on locking and ULE but are there
 any other reasons to go for that instead of 6.3? Conversely are there
 any reason which would point away from 7 such as stability issues?

7.0 is relatively new, while 6.3 would be a more conservative choice of
release if you have a lot of binaries running on previous release
because there are less changes.  However, I think it's good to use 7.0
as a development platform for future applications as there are a lot of
performance/stability/feature additions that will never be simply MFC'ed
because we try hard to maintain API/ABI stability for -STABLE branches.

Cheers,
- --
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHkRmRi+vbBBjt66ARAmaPAKCA7bJU2854yjBNNK0vkkkn9xy5kwCdGpLN
tqEIud77ODnRq3zB0QKYkrc=
=N/o9
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD 7.0-BETA3 Available

2008-01-18 Thread s3raphi


I am trying to run freebsd-update on 7.0-RC1 on a system with a ZFS root and
am also having problems with flags:

[EMAIL PROTECTED] ~]# freebsd-update install
Installing updates...chflags: ///lib/libc.so.7: Operation not supported

Is there a workaround for this? 

-S3raphi


thompsa wrote:
 
 On Mon, Nov 19, 2007 at 08:35:16AM -0800, Colin Percival wrote:
 Ken Smith wrote:
  The 7.0-BETA3 builds are now available.  If you would like to download
  an ISO image to install from they are available here:
  
ftp://ftp.freebsd.org/pub/FreeBSD/releases/arch/ISO-IMAGES/7.0/
  
  (adjust arch to be your architecture, e.g. amd64, i386, etc.).  If
 you
  would like to use cvsup to update an older machine the release tag is
  still RELENG_7.
 
 Due to a communications mix-up, it isn't yet possible to upgrade to
 7.0-BETA3
 using FreeBSD Update -- the bits are being assembled as I type this and
 binary
 upgrading to 7.0-BETA3 should work by the end of the day.
  
 I thought i'd have a go at updating from 7.0-BETA2 to BETA3 but hit a
 snag, I am using ZFS on root which doesn't support file flags so it
 borked in install_unschg(), 
   chflags noschg ${BASEDIR}/${F} || return 1
 
 Is there any way to test the underlying filesystem supports flags first?
 
 
 cheers,
 Andrew
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
 

-- 
View this message in context: 
http://www.nabble.com/FreeBSD-7.0-BETA3-Available-tp13839547p14958104.html
Sent from the freebsd-stable mailing list archive at Nabble.com.

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

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Joe Peterson

One word: ZFS!  It's awesome.

-Joe


Steven Hartland wrote:
 With the announcement of 6.3 and with 7.0 looking like it wont be 
 far behind I'd interested to hear what people thought of the relative
 benefits of each where?
 
 I know 7 has had a lot of work done on locking and ULE but are there
 any other reasons to go for that instead of 6.3? Conversely are there
 any reason which would point away from 7 such as stability issues?
 
 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 [EMAIL PROTECTED]
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic when copying to ext2fs

2008-01-18 Thread Jakob

I think the dump I can see is output of an execution loop in 
ext2_linux_balloc.c (/usr/src/sys/gnu/fs/ext2fs) from 289 (repeat: label) to 
414 (goto repeat:). But I haven't found yet why in previous branch it is ok.

On Fri, 18 Jan 2008 14:44:07 +0100
Ivan Voras [EMAIL PROTECTED] wrote:

 Jakub Siroky wrote:
  I have two large ext2fs partitions (368 and 313GB) to hold data shared 
  between several OSes. While there were no problems on 6-STABLE branch I was 
  quite disappointed after upgrade to 7-STABLE. Whenever I copy/write to 
  ext2fs partition the system freezes totally without crashdump. So I set 
  debugging settings to kernel config (DEBUG,WITNESS,..) and in console I 
  reproduced error situation ending with full screen of unstoppable running 
  text with lot of memory addresses and a few recognisable words: 'new block 
  bit set for ext already' - again with no crashdump. Then I have formatted 
  1GB partition with ext2fs and the problem on this small partition appears 
  only sometimes. 
 
 Interesting. I have ext2fs partitions in the same size range for the
 same purpose under 8-CURRENT and I don't have the problems you
 described, so it's unlikely the problem were introduced in 7. Did you
 run e2fsck on the file systems? Can you verify there is no hardware or
 driver data corruption (though I don't know how would you verify this
 one - maybe by writing to the partition from one OS and reading from the
 other, amd using md5 to check)?
 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: (Xorg), uid 0: exited on signal 4 (core dumped)

2008-01-18 Thread Chris H.


Quoting chris# [EMAIL PROTECTED]:


Greetings all,
As the title of this message indicates; I'm struggling with the ability
of getting the Xorg server running on a recent build of FreeBSD 7.
Of likely interest:
###
kernel info (2 proc pentium3):
7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Wed Jan 16 18:39:53 PST 2008
Installed from disc#1
src and port src cvsup'd 2008-01-10
agp related info from dmesg:
agp0: Intel 82443GX host to PCI bridge on hostb0
hostb0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf800
agp0: allocating GATT for aperture of size 64M
pcib1: PCI-PCI bridge at device 1.0 on pci0
pcib1:   domain0
pcib1:   secondary bus 1
pcib1:   subordinate bus   2
pcib1:   I/O decode0xf000-0xfff
pcib1:   no prefetched decode

I forgot to add something...
From Xorg.log:
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Fri Jan 18 13:21:21 2008
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout Simple Layout
(**) |--Screen Screen 1 (0)
(**) |   |--Monitor NEC

That's as far as it got. :(



I built the Xorg server from source. The only thing worth mentioning
in my make.conf file is: CPUTYPE?=pentium3
(added AFTER build/install world/kernel).

I didn't notice an inordinate number of error messages during
the Xorg server build. But given that it's only a PIII, it's slow
enough that I didn't watch the entire build process. While I could
have run script to capture the output of the build, I didn't, as
I've not run into any troubles (worth mentioning) with Xorg server
in the past. Not sure where to go from here. Wondering if anyone has
had a similar problem, and might be able to provide a solution.
If I haven't provided enough info, I'd be happy to provide anything
missing - just tell me what to do. :)

Thank you for all your time and consideration.

--Chris


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



--
panic: kernel trap (ignored)



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

Re: panic when copying to ext2fs

2008-01-18 Thread Kris Kennaway


Jakub Siroky wrote:
I have two large ext2fs partitions (368 and 313GB) to hold data shared between several OSes.  While there were no problems on 6-STABLE branch I was quite 
disappointed after upgrade to 7-STABLE. Whenever I copy/write to ext2fs 
partition the system freezes totally without crashdump. So I set 
debugging settings to kernel config (DEBUG,WITNESS,..) and in console I 
reproduced error situation ending with full screen of unstoppable 
running text with lot of memory addresses and a few recognisable words: 
'new block bit set for ext already' - again with no crashdump. Then I 
have formatted 1GB partition with ext2fs and the problem on this small 
partition appears only sometimes.


1) Please wrap your lines so your emails can be easily read.

2) Check the developer's handbook, it explains how to configure the 
debugger so you can investigate this further.


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

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Steven Hartland

- Original Message - 
From: Mike Tancsa [EMAIL PROTECTED]
I am also testing a core2 and quad core box with 8 gig of RAM on a 4 
port Areca controller that will replace a 6.2 postgresql server next 
week some time.  Just doing some benchmarking/testing of that now and 
hope to have RELENG_7 64bit deployed next week on it if all goes as planned.


That would be very interesting from our side to know the results of.
One of our main uses of FreeBSD is core boxes running webhosting, running
DB, DNS etc. We also make extensive use of Supermicro Dual and Quad core
machines with Areca controllers so...

   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 [EMAIL PROTECTED]

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

[releng_7 tinderbox] failure on amd64/amd64

TB --- 2008-01-19 02:15:04 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-19 02:15:04 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2008-01-19 02:15:04 - cleaning the object tree
TB --- 2008-01-19 02:15:10 - cvsupping the source tree
TB --- 2008-01-19 02:15:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/amd64/amd64/supfile
TB --- 2008-01-19 02:15:16 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-19 02:15:16 - cd /src
TB --- 2008-01-19 02:15:16 - /usr/bin/make -B buildworld
 World build started on Sat Jan 19 02:15:17 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-19 02:26:56 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-19 02:26:56 - ERROR: failed to build world
TB --- 2008-01-19 02:26:56 - tinderbox aborted
TB --- 578.16 user 50.28 system 711.95 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

7.0, ZFS and freebsd-update (was: Re: FreeBSD 7.0-BETA3 Available_

2008-01-18 Thread Royce Williams


s3raphi wrote, on 1/18/2008 12:19 PM:

I am trying to run freebsd-update on 7.0-RC1 on a system with a ZFS root and
am also having problems with flags:

[EMAIL PROTECTED] ~]# freebsd-update install
Installing updates...chflags: ///lib/libc.so.7: Operation not supported

Is there a workaround for this? 


Since all of my filesystems on my 7.0 system are ZFS, I've been making 
a copy of freebsd-update with the chflag calls commented out.  Since 
ZFS doesn't support flags yet, this is harmless.


If any of your primary filesystems are not ZFS, this is not a good 
solution.


If you go this route, you'll have to watch for changes to 
freebsd-update and reapply them.


I expect that once ZFS is no longer considered experimental, 
freebsd-update will have a way to handle this.


Royce

--
Royce D. Williams- IP Engineering, ACS
http://www.tycho.org/royce/   - PGP: 3FC087DB/1776A531
That'd be the hardware turbo-charged lipstick on a pig option. - MJR
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Mike Tancsa


At 04:48 PM 1/18/2008, Mike Tancsa wrote:

At 04:11 PM 1/18/2008, Steven Hartland wrote:

I know 7 has had a lot of work done on locking and ULE but are there
any other reasons to go for that instead of 6.3? Conversely are there
any reason which would point away from 7 such as stability issues?


Our production experiences with 7 have been good so far. I just did 
a rather busy customer mail server this morning and so far so good. 
I migrated it from 6.3 to 7 and am just finishing the portupgrade 
process.  We have also been running a 7.x box in our spam/virus 
scanning cluster since late Nov 2007 and no issues there either.  We 
havent done any benchmarks to see if its faster than the 6.x boxes, 
but its certainly stable so far and seems to at least keep up to the 
other boxes.


The 7.x box is a little faster according to my colleague. Below are 
the average scanning times per message.  Assuming that in a 24hr 
period each box will get approximately the same mix of spam, the 
times below are how long an average scan took. He also said the 7x 
box does perform better under high load when a large blast comes in 
all at once.


Lines: 15643Total: 61114.90 Average: 3.91
Lines: 15446Total: 61079.90 Average: 3.95
Lines: 15633Total: 62584.70 Average: 4.00
Lines: 15481Total: 60892.80 Average: 3.93
Lines: 15515Total: 60714.40 Average: 3.91

Lines: 15603Total: 58300.40 Average: 3.74

As well as spam scanning, they do AV stuff as well.

---Mike 


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

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Mike Tancsa


At 04:11 PM 1/18/2008, Steven Hartland wrote:

I know 7 has had a lot of work done on locking and ULE but are there
any other reasons to go for that instead of 6.3? Conversely are there
any reason which would point away from 7 such as stability issues?


I think it depends what apps you run, what drivers you rely on.  The 
less esoteric your hardware is, the better the chances are that 
things will work well (eg. em nics vs nfe or tl etc etc).


Our production experiences with 7 have been good so far. I just did a 
rather busy customer mail server this morning and so far so good. I 
migrated it from 6.3 to 7 and am just finishing the portupgrade 
process.  We have also been running a 7.x box in our spam/virus 
scanning cluster since late Nov 2007 and no issues there either.  We 
havent done any benchmarks to see if its faster than the 6.x boxes, 
but its certainly stable so far and seems to at least keep up to the 
other boxes.


I am also testing a core2 and quad core box with 8 gig of RAM on a 4 
port Areca controller that will replace a 6.2 postgresql server next 
week some time.  Just doing some benchmarking/testing of that now and 
hope to have RELENG_7 64bit deployed next week on it if all goes as planned.


---Mike 


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

Re: FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Jack Raats


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ken,

After CVSuping newvers.sh still tells me I am using the prerelease

Jack


- - Original Message -
From: Ken Smith [EMAIL PROTECTED]
To: freebsd-stable freebsd-stable@freebsd.org
Sent: Friday, January 18, 2008 8:18 PM
Subject: FreeBSD 6.3-RELEASE Available



In case you aren't subscribed to [EMAIL PROTECTED]:

 http://www.freebsd.org/releases/6.3R/announce.html

- --
   Ken Smith
- - From there to here, from here to  |   [EMAIL PROTECTED]
 there, funny things are everywhere.   |
 - Theodore Geisel |


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32) - GPGrelay v0.959

iD8DBQFHkQotPh5RwW/NzC4RAg/5AKCGrjDK5BYFO45FT8cJZoS6CfO1dQCffdwR
OTiUL2ITF2U6D565O//6CJY=
=4Owp
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

[releng_7 tinderbox] failure on i386/pc98

TB --- 2008-01-18 20:28:51 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-18 20:28:51 - starting RELENG_7 tinderbox run for i386/pc98
TB --- 2008-01-18 20:28:51 - cleaning the object tree
TB --- 2008-01-18 20:29:06 - cvsupping the source tree
TB --- 2008-01-18 20:29:06 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/i386/pc98/supfile
TB --- 2008-01-18 20:29:14 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-18 20:29:14 - cd /src
TB --- 2008-01-18 20:29:14 - /usr/bin/make -B buildworld
 World build started on Fri Jan 18 20:29:15 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-18 20:39:33 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-18 20:39:33 - ERROR: failed to build world
TB --- 2008-01-18 20:39:33 - tinderbox aborted
TB --- 532.72 user 43.92 system 642.02 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-pc98.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

On Friday 18 January 2008 11:48:10 am Pete French wrote:
  So it appears to be dying here:
 
  (gdb) l *madt_probe+0x119
  0xc06e7c69 is in madt_probe (/usr/src/sys/i386/acpica/madt.c:241).
  236 if (xsdt == NULL) {
  237 if (bootverbose)
  238 printf(MADT: Failed to map 
XSDT\n);
  239 return (ENXIO);
  240 }
  241 count = (xsdt-Length - 
sizeof(ACPI_TABLE_HEADER)) /
  242 sizeof(UINT64);
  243 for (i = 0; i  count; i++)
  244 if 
(madt_probe_table(xsdt-TableOffsetEntry[i]))
  245 break;
 
  where it reads 'xsdt-Length'.  xsdt was just mapped into a temporary part 
of
  KVA (used for kernel dumps) a few lines earlier:
 
 O.K., that is interesting, because my source code doesnt look like thiat,
 mine uses 'xsdt-Header.Length' instead of 'xsdt-Length' - is that
 code above from 7.0 ?

That doesn't matter actually.

  You can try adding some printfs to see what the values 
of 'rsdp-XsdtPhysicalAddress' and
  'xsdt' after the call to madt_map_table() are.  Actually, try this 
perhaps:
 
 Thanks for the patch - it didn;t help matters unfortunately, but I am
 adding some printfs on xsdt itself and also rsdp-XsdtPhysicalAddress to
 see what we get.

Hmm, ok.

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

[releng_7 tinderbox] failure on i386/i386

TB --- 2008-01-18 20:17:43 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-18 20:17:43 - starting RELENG_7 tinderbox run for i386/i386
TB --- 2008-01-18 20:17:43 - cleaning the object tree
TB --- 2008-01-18 20:18:09 - cvsupping the source tree
TB --- 2008-01-18 20:18:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/i386/i386/supfile
TB --- 2008-01-18 20:18:18 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-18 20:18:18 - cd /src
TB --- 2008-01-18 20:18:18 - /usr/bin/make -B buildworld
 World build started on Fri Jan 18 20:18:20 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-18 20:28:51 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-18 20:28:51 - ERROR: failed to build world
TB --- 2008-01-18 20:28:51 - tinderbox aborted
TB --- 533.16 user 45.12 system 668.06 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-i386.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Ken Smith


On Fri, 2008-01-18 at 21:21 +0100, Jack Raats wrote:

 After CVSuping newvers.sh still tells me I am using the prerelease

You most likely used the RELENG_6 branch tag.  At this point it should
have been the only one that would have produced 6.3-PRERELEASE.

I just changed it to say 6.3-STABLE.

-- 
Ken Smith
- From there to here, from here to  |   [EMAIL PROTECTED]
  there, funny things are everywhere.   |
  - Theodore Geisel |



signature.asc
Description: This is a digitally signed message part

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

 Just the stack trace offsets.

is all the info you need here?

http://toybox.twisted.org.uk/~pete/acpi_panic.jpg
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

[releng_7 tinderbox] failure on ia64/ia64

TB --- 2008-01-19 02:48:03 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-19 02:48:03 - starting RELENG_7 tinderbox run for ia64/ia64
TB --- 2008-01-19 02:48:03 - cleaning the object tree
TB --- 2008-01-19 02:48:07 - cvsupping the source tree
TB --- 2008-01-19 02:48:07 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/ia64/ia64/supfile
TB --- 2008-01-19 02:48:12 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-19 02:48:12 - cd /src
TB --- 2008-01-19 02:48:12 - /usr/bin/make -B buildworld
 World build started on Sat Jan 19 02:48:13 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-19 02:58:05 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-19 02:58:05 - ERROR: failed to build world
TB --- 2008-01-19 02:58:05 - tinderbox aborted
TB --- 506.78 user 41.70 system 601.27 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Jakub Siroky

Hello, please could you try to make large (hundred of GB) ext2 volume with 
e2fsprogs and copy large amount of data to it? On amd64 SMP (two cores) 
RELENG_7_0 it should lead to unrecoverable panic or scrolling strings 
ext2_new_block: bit already set for block %d. On 6.2-STABLE there is no 
problem with linux partitions.

Jakub Siroky

On Fri, 18 Jan 2008 16:48:28 -0500
Mike Tancsa [EMAIL PROTECTED] wrote:

 At 04:11 PM 1/18/2008, Steven Hartland wrote:
 I know 7 has had a lot of work done on locking and ULE but are there
 any other reasons to go for that instead of 6.3? Conversely are there
 any reason which would point away from 7 such as stability issues?
 
 I think it depends what apps you run, what drivers you rely on.  The 
 less esoteric your hardware is, the better the chances are that 
 things will work well (eg. em nics vs nfe or tl etc etc).
 
 Our production experiences with 7 have been good so far. I just did a 
 rather busy customer mail server this morning and so far so good. I 
 migrated it from 6.3 to 7 and am just finishing the portupgrade 
 process.  We have also been running a 7.x box in our spam/virus 
 scanning cluster since late Nov 2007 and no issues there either.  We 
 havent done any benchmarks to see if its faster than the 6.x boxes, 
 but its certainly stable so far and seems to at least keep up to the 
 other boxes.
 
 I am also testing a core2 and quad core box with 8 gig of RAM on a 4 
 port Areca controller that will replace a 6.2 postgresql server next 
 week some time.  Just doing some benchmarking/testing of that now and 
 hope to have RELENG_7 64bit deployed next week on it if all goes as planned.
 
  ---Mike 
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: To 6.3 or to 7.0 that is the question?

 I know 7 has had a lot of work done on locking and ULE but are there
 any other reasons to go for that instead of 6.3? Conversely are there
 any reason which would point away from 7 such as stability issues?

7 is great - very stable, fast, includes ZFS, has gcc 4.0 and is excellent
in my opinion. I have moved all our production systems to the pre-release
using ULE (after thorough testing) and havent regretted it once.

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

[releng_7 tinderbox] failure on i386/pc98

TB --- 2008-01-19 02:37:28 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-19 02:37:28 - starting RELENG_7 tinderbox run for i386/pc98
TB --- 2008-01-19 02:37:28 - cleaning the object tree
TB --- 2008-01-19 02:37:33 - cvsupping the source tree
TB --- 2008-01-19 02:37:33 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/i386/pc98/supfile
TB --- 2008-01-19 02:37:39 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-19 02:37:39 - cd /src
TB --- 2008-01-19 02:37:39 - /usr/bin/make -B buildworld
 World build started on Sat Jan 19 02:37:40 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-19 02:48:03 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-19 02:48:03 - ERROR: failed to build world
TB --- 2008-01-19 02:48:03 - tinderbox aborted
TB --- 531.75 user 41.88 system 634.89 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-pc98.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

(Xorg), uid 0: exited on signal 4 (core dumped)

2008-01-18 Thread notarealuser


Greetings all,
As the title of this message indicates; I'm struggling with the ability
of getting the Xorg server running on a recent build of FreeBSD 7.
Of likely interest:
###
kernel info (2 proc pentium3):
7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Wed Jan 16 18:39:53 PST 2008
Installed from disc#1
src and port src cvsup'd 2008-01-10
agp related info from dmesg:
agp0: Intel 82443GX host to PCI bridge on hostb0
hostb0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf800
agp0: allocating GATT for aperture of size 64M
pcib1: PCI-PCI bridge at device 1.0 on pci0
pcib1:   domain0
pcib1:   secondary bus 1
pcib1:   subordinate bus   2
pcib1:   I/O decode0xf000-0xfff
pcib1:   no prefetched decode


I built the Xorg server from source. The only thing worth mentioning
in my make.conf file is: CPUTYPE?=pentium3
(added AFTER build/install world/kernel).

I didn't notice an inordinate number of error messages during
the Xorg server build. But given that it's only a PIII, it's slow
enough that I didn't watch the entire build process. While I could
have run script to capture the output of the build, I didn't, as
I've not run into any troubles (worth mentioning) with Xorg server
in the past. Not sure where to go from here. Wondering if anyone has
had a similar problem, and might be able to provide a solution.
If I haven't provided enough info, I'd be happy to provide anything
missing - just tell me what to do. :)

Thank you for all your time and consideration.

--Chris


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

Re: FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Mark Linimon

On Fri, Jan 18, 2008 at 03:51:43PM -0500, Ken Smith wrote:
 Due to resource limitations (both human and computer) there won't
 be an ia64 6.3-RELEASE but there will be an ia64 7.0-RELEASE.

Unless something changes rapidly, ia64-7 will not have any packages
shipped with it: the last I tried, it was unable to build any.

Anyone who is interested in working on this should contact me off-list.

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

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Mike Tancsa


At 05:06 PM 1/18/2008, Jakub Siroky wrote:

Hello, please could you try to make large (hundred of GB) ext2 volume with


I dont use ext2 anywhere. Only UFS2.

---Mike


e2fsprogs and copy large amount of data to it? On amd64 SMP (two 
cores) RELENG_7_0 it should lead to unrecoverable panic or scrolling 
strings ext2_new_block: bit already set for block %d. On 
6.2-STABLE there is no problem with linux partitions.


Jakub Siroky

On Fri, 18 Jan 2008 16:48:28 -0500
Mike Tancsa [EMAIL PROTECTED] wrote:

 At 04:11 PM 1/18/2008, Steven Hartland wrote:
 I know 7 has had a lot of work done on locking and ULE but are there
 any other reasons to go for that instead of 6.3? Conversely are there
 any reason which would point away from 7 such as stability issues?

 I think it depends what apps you run, what drivers you rely on.  The
 less esoteric your hardware is, the better the chances are that
 things will work well (eg. em nics vs nfe or tl etc etc).

 Our production experiences with 7 have been good so far. I just did a
 rather busy customer mail server this morning and so far so good. I
 migrated it from 6.3 to 7 and am just finishing the portupgrade
 process.  We have also been running a 7.x box in our spam/virus
 scanning cluster since late Nov 2007 and no issues there either.  We
 havent done any benchmarks to see if its faster than the 6.x boxes,
 but its certainly stable so far and seems to at least keep up to the
 other boxes.

 I am also testing a core2 and quad core box with 8 gig of RAM on a 4
 port Areca controller that will replace a 6.2 postgresql server next
 week some time.  Just doing some benchmarking/testing of that now and
 hope to have RELENG_7 64bit deployed next week on it if all goes 
as planned.


  ---Mike

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


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

Re: FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Peter Jeremy

On Fri, Jan 18, 2008 at 02:18:40PM -0500, Ken Smith wrote:
  http://www.freebsd.org/releases/6.3R/announce.html

Thank you.

One question: What has happened to iA64?  I notice it has been removed
from the release notes.  Is it running late or dead?

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.


pgpsCFY0NdPUF.pgp
Description: PGP signature

[releng_7 tinderbox] failure on amd64/amd64

TB --- 2008-01-18 20:05:32 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-18 20:05:32 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2008-01-18 20:05:32 - cleaning the object tree
TB --- 2008-01-18 20:05:59 - cvsupping the source tree
TB --- 2008-01-18 20:05:59 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/amd64/amd64/supfile
TB --- 2008-01-18 20:06:11 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-18 20:06:11 - cd /src
TB --- 2008-01-18 20:06:11 - /usr/bin/make -B buildworld
 World build started on Fri Jan 18 20:06:13 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-18 20:17:42 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-18 20:17:42 - ERROR: failed to build world
TB --- 2008-01-18 20:17:42 - tinderbox aborted
TB --- 578.04 user 54.95 system 730.56 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

On Friday 18 January 2008 01:02:04 pm Pete French wrote:
  So it appears to be dying here:
 
  (gdb) l *madt_probe+0x119
  0xc06e7c69 is in madt_probe (/usr/src/sys/i386/acpica/madt.c:241).
  236 if (xsdt == NULL) {
  237 if (bootverbose)
  238 printf(MADT: Failed to map 
XSDT\n);
  239 return (ENXIO);
  240 }
  241 count = (xsdt-Length - 
sizeof(ACPI_TABLE_HEADER)) /
  242 sizeof(UINT64);
  243 for (i = 0; i  count; i++)
  244 if 
(madt_probe_table(xsdt-TableOffsetEntry[i]))
  245 break;
 
 Turns out that it isn't - it's in the other branch of the if using the
 RSDT instead of the XSDT. Not sure why the debugger was giving
 misleading information. I added prints to find out which path it was
 taking and to print out some values after the line
 rsdt = madt_map_table(rsdp-RsdtPhysicalAddress, 1, ACPI_SIG_RSDT);
 
 The value of rsdtl is 0x800e7610, but the value of rsdp-XsdtPhysicalAddress
 is zero! So I guess that is where the panic is comming from. So where
 now ? Is there an equivalent patch to the one you emailed
 earlier for this branch of the if ?

The patch would be the same, it tried to fix an issue where if the table is
longer than the space we are borrowing to map things we could end up with 
problems.  I.e. the changes weren't in the RSDT/XSDT path at all, but in the 
common code used to map tables.  If you are using RSDT, then 
RsdtPhysicalAddress is what you care about rather than XsdtPhysicalAddress.

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

Re: FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Abdullah Ibn Hamad Al-Marri

Congrats!
 
Regards, 
-Abdullah Ibn Hamad Al-Marri
Arab Portal
http://www.WeArab.Net/

- Original Message 
 From: Ken Smith [EMAIL PROTECTED]
 To: freebsd-stable freebsd-stable@freebsd.org
 Sent: Friday, January 18, 2008 10:18:40 PM
 Subject: FreeBSD 6.3-RELEASE Available
 
 
 In case you aren't subscribed to [EMAIL PROTECTED]:
 
   http://www.freebsd.org/releases/6.3R/announce.html
 
 -- 
 Ken Smith
 - From there to here, from here to  | 
 
 [EMAIL PROTECTED]
   there, funny things are everywhere.   |
   - Theodore Geisel |
 
 





  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

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

[releng_7 tinderbox] failure on powerpc/powerpc

TB --- 2008-01-19 02:58:05 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-19 02:58:05 - starting RELENG_7 tinderbox run for powerpc/powerpc
TB --- 2008-01-19 02:58:05 - cleaning the object tree
TB --- 2008-01-19 02:58:08 - cvsupping the source tree
TB --- 2008-01-19 02:58:08 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/powerpc/powerpc/supfile
TB --- 2008-01-19 02:58:15 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-19 02:58:15 - cd /src
TB --- 2008-01-19 02:58:15 - /usr/bin/make -B buildworld
 World build started on Sat Jan 19 02:58:16 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-19 03:08:38 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-19 03:08:38 - ERROR: failed to build world
TB --- 2008-01-19 03:08:38 - tinderbox aborted
TB --- 533.15 user 41.43 system 632.75 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Backup solution suggestions [ggated]

2008-01-18 Thread Tom Judge


Ulrich Spoerlein wrote:

On Jan 18, 2008 9:11 AM, Johan Ström [EMAIL PROTECTED] wrote:

Your no,barely, bad hell no seems to fit pretty good.. I did some
testing during the night with the above (non-production) setup.
What I did was doing some rsyncing over the night:

while true ; do
 echo `date` Clearing vmail  logfile
 rm -rf vmail
 echo `date` Starting rsync  logfile
 rsync -vr /usr/var/vmail . |tee -a logfile
 echo `date` Rsync finished   logfile
done

I started this at ~02.0. The results? A freshly rebooted 6.2 (6.2-
RELEASE-p6 FreeBSD 6.2-RELEASE-p6 #0: Fri Jul 27 15:47:50 UTC 2007)
box in the morning..
[...]
What I dont have is a coredump, judging from dmesg -a savecore wasnt
even run.. running it now, 5 hours later, didnt find any cores.

The other end (7.0 server) wasnt affected at all.

Not realy sure what it had been doing, because looking at my
bandwidth graphs from the switch, nothing was done at all.. It didnt
even go through one iteration of rsync... ~7.5k files/directorys
seems to have been transfered, then the log doesnt say more. But
according to the BW graph, after ~03.00 no traffic was sent at all...

Some known bug with 6.2?


There was some ggatec problems with TCP and/or sockets, I think they
have been mostly resolved post-6.2. If you want to pursue this further
(it *would* be a cool setup, no doubt) I'd suggest three things:
- Update to 6.3
- Leave GELI out of the loop for now (only do ggate, with random data perhaps)
- Build a kernel *without* options PREEMPTION



Hi,

We have 4 production High Avaliability NFS clusters running 
GMirror+GGate+LinuxHA (2 Nodes per cluster) on RELENG_6_2.  This setup 
has proved very stable for us you have to do some tuning though:


/etc/sysctl.conf:
net.inet.tcp.sendspace=1048576
net.inet.tcp.recvspace=1048576
kern.ipc.maxsockbuf=2049152

/boot/loader.conf:
kern.ipc.nmbclusters=32768


Command line options to ggate[cd]
ggate[dc]_buf_size=1310720
ggatec_timeout=5
ggatec_queue_size=2048

Cluster node uptimes range from 40-160 days with the last reboots being 
caused by power problems not FreeBSD issues.


The problems may be in the tuning or with geli, personally I would leave 
geli out at try with the above configuration.  Then try above with geli 
to see what the problem is.


Tom







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

[releng_7 tinderbox] failure on sparc64/sparc64

TB --- 2008-01-19 03:04:56 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-19 03:04:56 - starting RELENG_7 tinderbox run for sparc64/sparc64
TB --- 2008-01-19 03:04:56 - cleaning the object tree
TB --- 2008-01-19 03:04:58 - cvsupping the source tree
TB --- 2008-01-19 03:04:58 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/sparc64/sparc64/supfile
TB --- 2008-01-19 03:05:03 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-19 03:05:03 - cd /src
TB --- 2008-01-19 03:05:03 - /usr/bin/make -B buildworld
 World build started on Sat Jan 19 03:05:04 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-19 03:13:43 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-19 03:13:43 - ERROR: failed to build world
TB --- 2008-01-19 03:13:43 - tinderbox aborted
TB --- 448.59 user 40.00 system 527.27 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

 MADT is the ACPI table that enumerates APICs.  Do you have the offset of 
 madt_probe()?

I startet copying down the hex, but it turned out to be a more accurate idea
to get my colleague to take a photo with his camera phone. Panic and kdb
'bt' output can be found here:

http://toybox.twisted.org.uk/~pete/acpi_panic.jpg

if theres anything else you need me to do in kdb then pleae let me know,
as this is very easy for me to reproduce during ther work day.

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

Re: 7.0-PRERELEASE desktop system periodically freezes momentarily

2008-01-18 Thread Wayne Sierke

On Thu, 2008-01-17 at 20:50 +0100, Kris Kennaway wrote:
 Wayne Sierke wrote:
  On Mon, 2008-01-14 at 21:06 +0100, Kris Kennaway wrote:
  Same deal as before then.  It cannot be the same problem as in the 
  previous 6.x trace (unless you are using a non-mpsafe filesystem, i.e. 
  not UFS).
 
  Kris
  
  In fact I have some MSDOSFS auto-mounting from /etc/fstab, but normally
  not in active use (by me - as for what gnome-* are doing in the
  background?).
  
  Without those mounts the stuttering in glxgears when 'Harddisk' is
  enabled in System Monitor is barely perceptible. The stuttering with
  Network Monitor remains as do the other freezes.
  
  I didn't have the same luck getting nvidia-driver working with
  LOCK_PROFILING in RELENG_7 as I did with MUTEX_PROFILING in RELENG_6.
  Looks like I'll have to test with nv or vesa driver instead, now.
  
  I've also prepared a KTR testing kernel but in the process realise I
  don't know which trace classes to include?
 
 KTR_SCHED
 
 Kris

Ah, yes. Thanks. I've finally latched on to the whole schedgraph
concept. Links to logs below.

ktr-sched_gnome-netmonitor.out is just the 2Hz stutter in glxgears with
the gnome Network Monitor applet active. I believe I've caught an
instance of one stutter.

ktr-sched_move-glxgears_1.out is a first attempt to catch the freeze
that occurs when moving the glxgears window.

Because of the freeze it's difficult to stop the recording promptly. It
appears that all keyboard and mouse input (other than movement) is
either ignored or discarded during the freeze[1]. Consequently, I have
to wait until the system unfreezes before clicking over the terminal
window to activate it and then pressing enter to run the waiting
'debug.ktr.mask=0' command.

ktr-sched_move-glxgears_2.out is a second attempt.

ktr-sched_move-glxgears_3.out was conducted by running the command:

sleep 2; sysctl debug.ktr.mask=0

then waiting about 1.5 seconds, then dragging the glxgears window in an
attempt to have the freeze active at the end of recording.

What's a sensible upper limit for KTR_ENTRIES?


Wayne

[1] With the very curious exception that when the freeze occurs due to
an alt-tab window-switching action, mouse and keyboard *do* get buffered
- if I continue hitting alt-tab after the system freezes, those alt-tabs
get played out when the system unfreezes. Similarly if I click over a
window while the system is frozen during alt-tab, that mouse click gets
played as normal when the system unfreezes. Odd.


http://au.dyndns.ws/public/ktr-sched_gnome-netmonitor.out.bz2
http://au.dyndns.ws/public/ktr-sched_move-glxgears_1.out.bz2
http://au.dyndns.ws/public/ktr-sched_move-glxgears_2.out.bz2
http://au.dyndns.ws/public/ktr-sched_move-glxgears_3.out.bz2

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

Re: PCI MSI (was Re: What current Dell Systems are supported/work)

On Friday 18 January 2008 08:50:31 am John Baldwin wrote:
 On Friday 18 January 2008 05:30:06 am Parv wrote:
  There was no page fault or trap 12 message when the panic happened.
  After some of messages are printed (as in dmesg), kdb is entered ...
  
ioapic0: Assigning PCI IRQ 23 to local APIC 1
msi: Assigning MSI IRQ 256 to local APIC 0
panic: blockabke sleep block (sleep mutex) msi @ 
  /misc/src-6/sys/i386/i386/msi.c:381
cpuid: 0
kdb: stack backtrace
kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \
  [I skipped from here to the db prompt]
.
.
.
  
  Tomorrow, rather later today, I will type up the trace output.
  Please let me know if you would like to see any other output that I
  could possibly provide.
 
 This is good enough for me to see the bug, I'll work on fixing it.  There are
 some locking changes in the x86 interrupt code I need to MFC.

Try this patch:

Index: amd64/amd64/intr_machdep.c
===
RCS file: /host/cvs/usr/cvs/src/sys/amd64/amd64/intr_machdep.c,v
retrieving revision 1.15.2.5
diff -u -r1.15.2.5 intr_machdep.c
--- amd64/amd64/intr_machdep.c  26 Nov 2007 15:08:35 -  1.15.2.5
+++ amd64/amd64/intr_machdep.c  18 Jan 2008 15:05:08 -
@@ -43,13 +43,14 @@
 #include sys/param.h
 #include sys/bus.h
 #include sys/interrupt.h
-#include sys/lock.h
 #include sys/ktr.h
 #include sys/kernel.h
+#include sys/lock.h
 #include sys/mutex.h
 #include sys/proc.h
 #include sys/syslog.h
 #include sys/systm.h
+#include sys/sx.h
 #include machine/clock.h
 #include machine/intr_machdep.h
 #ifdef DDB
@@ -70,7 +71,8 @@
 
 static int intrcnt_index;
 static struct intsrc *interrupt_sources[NUM_IO_INTS];
-static struct mtx intr_table_lock;
+static struct sx intr_table_lock;
+static struct mtx intrcnt_lock;
 static STAILQ_HEAD(, pic) pics;
 
 #ifdef SMP
@@ -108,14 +110,14 @@
 {
int error;
 
-   mtx_lock_spin(intr_table_lock);
+   sx_xlock(intr_table_lock);
if (intr_pic_registered(pic))
error = EBUSY;
else {
STAILQ_INSERT_TAIL(pics, pic, pics);
error = 0;
}
-   mtx_unlock_spin(intr_table_lock);
+   sx_xunlock(intr_table_lock);
return (error);
 }
 
@@ -137,16 +139,16 @@
(mask_fn)isrc-is_pic-pic_enable_source, irq%d:, vector);
if (error)
return (error);
-   mtx_lock_spin(intr_table_lock);
+   sx_xlock(intr_table_lock);
if (interrupt_sources[vector] != NULL) {
-   mtx_unlock_spin(intr_table_lock);
+   sx_xunlock(intr_table_lock);
intr_event_destroy(isrc-is_event);
return (EEXIST);
}
intrcnt_register(isrc);
interrupt_sources[vector] = isrc;
isrc-is_enabled = 0;
-   mtx_unlock_spin(intr_table_lock);
+   sx_xunlock(intr_table_lock);
return (0);
 }
 
@@ -170,19 +172,18 @@
error = intr_event_add_handler(isrc-is_event, name, handler, arg,
intr_priority(flags), flags, cookiep);
if (error == 0) {
+   sx_xlock(intr_table_lock);
intrcnt_updatename(isrc);
-   mtx_lock_spin(intr_table_lock);
if (!isrc-is_enabled) {
isrc-is_enabled = 1;
 #ifdef SMP
if (assign_cpu)
intr_assign_next_cpu(isrc);
 #endif
-   mtx_unlock_spin(intr_table_lock);
isrc-is_pic-pic_enable_intr(isrc);
-   } else
-   mtx_unlock_spin(intr_table_lock);
+   }
isrc-is_pic-pic_enable_source(isrc);
+   sx_xunlock(intr_table_lock);
}
return (error);
 }
@@ -306,12 +307,12 @@
 #ifndef DEV_ATPIC
atpic_reset();
 #endif
-   mtx_lock_spin(intr_table_lock);
+   sx_xlock(intr_table_lock);
STAILQ_FOREACH(pic, pics, pics) {
if (pic-pic_resume != NULL)
pic-pic_resume(pic);
}
-   mtx_unlock_spin(intr_table_lock);
+   sx_xunlock(intr_table_lock);
 }
 
 void
@@ -319,12 +320,12 @@
 {
struct pic *pic;
 
-   mtx_lock_spin(intr_table_lock);
+   sx_xlock(intr_table_lock);
STAILQ_FOREACH(pic, pics, pics) {
if (pic-pic_suspend != NULL)
pic-pic_suspend(pic);
}
-   mtx_unlock_spin(intr_table_lock);
+   sx_xunlock(intr_table_lock);
 }
 
 static void
@@ -347,8 +348,8 @@
 {
char straystr[MAXCOMLEN + 1];
 
-   /* mtx_assert(intr_table_lock, MA_OWNED); */
KASSERT(is-is_event != NULL, (%s: isrc with no event, __func__));
+   mtx_lock_spin(intrcnt_lock);
is-is_index = intrcnt_index;
intrcnt_index += 2;
snprintf(straystr, MAXCOMLEN + 1, stray irq%d,
@@ -357,17 +358,18 @@
is-is_count = intrcnt[is-is_index];

FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Ken Smith


In case you aren't subscribed to [EMAIL PROTECTED]:

  http://www.freebsd.org/releases/6.3R/announce.html

-- 
Ken Smith
- From there to here, from here to  |   [EMAIL PROTECTED]
  there, funny things are everywhere.   |
  - Theodore Geisel |



signature.asc
Description: This is a digitally signed message part

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Steven Hartland

- Original Message - 
From: Mike Tancsa [EMAIL PROTECTED]
I am also testing a core2 and quad core box with 8 gig of RAM on a 4 
port Areca controller that will replace a 6.2 postgresql server next 
week some time.  Just doing some benchmarking/testing of that now and 
hope to have RELENG_7 64bit deployed next week on it if all goes as planned.


That would be very interesting from our side to know the results of.
One of our main uses of FreeBSD is core boxes running webhosting, running
DB, DNS etc. We also make extensive use of Supermicro Dual and Quad core
machines with Areca controllers so...

   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 [EMAIL PROTECTED]

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

Re: FreeBSD 6.3-RELEASE Available

2008-01-18 Thread Ken Smith


On Sat, 2008-01-19 at 07:47 +1100, Peter Jeremy wrote:
 On Fri, Jan 18, 2008 at 02:18:40PM -0500, Ken Smith wrote:
   http://www.freebsd.org/releases/6.3R/announce.html
 
 Thank you.
 
 One question: What has happened to iA64?  I notice it has been removed
 from the release notes.  Is it running late or dead?
 

Actually both ia64 and powerpc were removed.  Powerpc is running late,
I'll do a follow-up announcement once we've had a chance to get it
loaded and it propagates.  Due to resource limitations (both human and
computer) there won't be an ia64 6.3-RELEASE but there will be an ia64
7.0-RELEASE.

-- 
Ken Smith
- From there to here, from here to  |   [EMAIL PROTECTED]
  there, funny things are everywhere.   |
  - Theodore Geisel |



signature.asc
Description: This is a digitally signed message part

[releng_7 tinderbox] failure on powerpc/powerpc

TB --- 2008-01-18 20:49:54 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-18 20:49:54 - starting RELENG_7 tinderbox run for powerpc/powerpc
TB --- 2008-01-18 20:49:54 - cleaning the object tree
TB --- 2008-01-18 20:50:09 - cvsupping the source tree
TB --- 2008-01-18 20:50:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/powerpc/powerpc/supfile
TB --- 2008-01-18 20:50:18 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-18 20:50:18 - cd /src
TB --- 2008-01-18 20:50:18 - /usr/bin/make -B buildworld
 World build started on Fri Jan 18 20:50:19 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-18 21:00:39 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-18 21:00:39 - ERROR: failed to build world
TB --- 2008-01-18 21:00:39 - tinderbox aborted
TB --- 533.09 user 44.13 system 645.20 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

[releng_7 tinderbox] failure on sparc64/sparc64

TB --- 2008-01-18 20:56:07 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-01-18 20:56:07 - starting RELENG_7 tinderbox run for sparc64/sparc64
TB --- 2008-01-18 20:56:07 - cleaning the object tree
TB --- 2008-01-18 20:56:19 - cvsupping the source tree
TB --- 2008-01-18 20:56:20 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s 
/tinderbox/RELENG_7/sparc64/sparc64/supfile
TB --- 2008-01-18 20:56:26 - building world (CFLAGS=-O2 -pipe)
TB --- 2008-01-18 20:56:26 - cd /src
TB --- 2008-01-18 20:56:26 - /usr/bin/make -B buildworld
 World build started on Fri Jan 18 20:56:27 UTC 2008
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
[...]
=== lib/libpam/modules/pam_rootok (buildincludes)
=== lib/libpam/modules/pam_securetty (buildincludes)
=== lib/libpam/modules/pam_self (buildincludes)
=== lib/libpam/modules/pam_ssh (buildincludes)
=== lib/libpam/modules/pam_tacplus (buildincludes)
=== lib/libpam/modules/pam_unix (buildincludes)
=== lib/libpam/libpam (buildincludes)
make: don't know how to make security/openpam_attr.h. Stop
*** Error code 2

Stop in /src/lib/libpam.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-01-18 21:05:03 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-01-18 21:05:03 - ERROR: failed to build world
TB --- 2008-01-18 21:05:03 - tinderbox aborted
TB --- 448.91 user 42.41 system 535.60 real


http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Steven Hartland

With the announcement of 6.3 and with 7.0 looking like it wont be 
far behind I'd interested to hear what people thought of the relative

benefits of each where?

I know 7 has had a lot of work done on locking and ULE but are there
any other reasons to go for that instead of 6.3? Conversely are there
any reason which would point away from 7 such as stability issues?

   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 [EMAIL PROTECTED]

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

Re: panic: vm_fault: fault on nofualt entry, addr: 81423000

 The patch would be the same, it tried to fix an issue where if the table is
 longer than the space we are borrowing to map things we could end up with 
 problems.  I.e. the changes weren't in the RSDT/XSDT path at all, but in the 
 common code used to map tables.  If you are using RSDT, then 
 RsdtPhysicalAddress is what you care about rather than XsdtPhysicalAddress.

Ah, O.K., yes, looking at the patch thats obvious, sorry. I also
just found a bug in my printf code - I wasnt printing the vlaue of
of RsdtPhysicalAddress in the second part of the 'if' at all. Will
fix that and re-test on monday.

cheers,

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

Re: To 6.3 or to 7.0 that is the question?

2008-01-18 Thread Stephen Montgomery-Smith


Steven Hartland wrote:
With the announcement of 6.3 and with 7.0 looking like it wont be far 
behind I'd interested to hear what people thought of the relative

benefits of each where?

I know 7 has had a lot of work done on locking and ULE but are there
any other reasons to go for that instead of 6.3? Conversely are there
any reason which would point away from 7 such as stability issues?

   Regards
   Steve


I really like FreeBSD 7.x, except for one issue.  On my Dell Lattitude 
D800 laptop, xorg freezes the computer solid on starting or stopping. 
(But I guess I like the advantages of 7.x to the extent that I haven't 
gone back to 6.x).


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

[releng_7 tinderbox] failure on i386/i386