panic on RELENG_5 on em(4)
Hi,
I'm running RELENG_5 around Oct 12, got a panic related to em(4).
After some searching, I saw a similar panic reported on -current
(his/her system is also RELENG_5) in May, but no further replies.
The kernel is similar to GENERIC with IPFW and have HTT
enabled in loader.conf. Box is a 2*Xeon with HTT, SMP kernel
is enabled, thus there are 4 logical cpus. For some reasons,
I did not have DDB compiled. The kgdb outputs are enclosed.
If there are people interested to help debug this, I can send
information as request.
Thanks,,
Rong-En Fan
(kgdb and console):
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 06
fault virtual address = 0xbfc38018
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc05fb49f
stack pointer = 0x10:0xe6448bc0
frame pointer = 0x10:0xe6448c24
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 77 (irq16: em0)
trap number = 12
panic: page fault
cpuid = 2
#0 doadump () at pcpu.h:160
No locals.
#1 0xc04c1268 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412
first_buf_printf = 1
#2 0xc04c1616 in panic (fmt=0xc062dcbe %s)
at /usr/src/sys/kern/kern_shutdown.c:568
td = (struct thread *) 0xc313bd80
bootopt = 260
newpanic = 0
ap = 0xc313bd80 L\023\020\t
buf = page fault, '\0' repeats 245 times
#3 0xc06121dd in trap_fatal (frame=0xe6448b80, eva=0)
at /usr/src/sys/i386/i386/trap.c:817
code = 16
type = 12
ss = 16
esp = 0
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27,
ssd_dpl = 0, ssd_p = 1, ssd_xx = 1, ssd_xx1 = 0, ssd_def32 = 1, ssd_gran = 1}
#4 0xc0611ed4 in trap_pfault (frame=0xe6448b80, usermode=0, eva=3217260568)
at /usr/src/sys/i386/i386/trap.c:735
va = 3217260544
vm = (struct vmspace *) 0x0
map = 0xc0673280
rv = 1
ftype = 1 '\001'
td = (struct thread *) 0xc313bd80
p = (struct proc *) 0xc313a54c
#5 0xc0611ab9 in trap (frame=
{tf_fs = -1022033896, tf_es = 16, tf_ds = -431751152, tf_edi = -10217512\
96, tf_esi = -1017843008, tf_ebp = -431715292, tf_isp = -431715412, tf_ebx = -\
1008379904, tf_edx = 0, tf_ecx = 234907650, tf_eax = 57350, tf_trapno = 12, tf\
_err = 0, tf_eip = -1067469665, tf_cs = 8, tf_eflags = 66055, tf_esp = -431715\
256, tf_ss = -1021353488}) at /usr/src/sys/i386/i386/trap.c:425
td = (struct thread *) 0xc313bd80
p = (struct proc *) 0xc313a54c
sticks = 3863251848
i = 0
ucode = 0
type = 12
code = 0
eva = 3217260568
#6 0xc05fdc4a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
No locals.
#7 0xc3150018 in ?? ()
No symbol table info available.
#8 0x0010 in ?? ()
No symbol table info available.
#9 0xe6440010 in ?? ()
No symbol table info available.
#10 0xc3195000 in ?? ()
No symbol table info available.
#11 0xc354f2c0 in ?? ()
No symbol table info available.
#12 0xe6448c24 in ?? ()
No symbol table info available.
#13 0xe6448bac in ?? ()
No symbol table info available.
#14 0xc3e55800 in ?? ()
No symbol table info available.
#15 0x in ?? ()
No symbol table info available.
#16 0x0e006802 in ?? ()
No symbol table info available.
#17 0xe006 in ?? ()
No symbol table info available.
#18 0x000c in ?? ()
No symbol table info available.
#19 0x in ?? ()
No symbol table info available.
#20 0xc05fb49f in bus_dmamap_load (dmat=0xc3353400, map=0x0, buf=0xe006802,
buflen=2046, callback=0xc045f8e8 em_dmamap_cb, callback_arg=0xe6448c48,
flags=0) at pmap.h:200
lastaddr = 0
error = 0
nsegs = 0
195 vm_paddr_t pa;
196
197 if ((pa = PTD[va PDRSHIFT]) PG_PS) {
198 pa = (pa ~(NBPDR - 1)) | (va (NBPDR - 1));
199 } else {
200 pa = *vtopte(va);
201 pa = (pa PG_FRAME) | (va PAGE_MASK);
202 }
203 return pa;
204 }
#21 0xc04602f1 in em_get_buf (i=88, adapter=0xc3195000, nmp=0x0)
at /usr/src/sys/dev/em/if_em.c:2531
mp = (struct mbuf *) 0xc3e55800
rx_buffer = (struct em_buffer *) 0xc354f2c0
ifp = (struct ifnet *) 0xc354f2c0
paddr = 3272850816
error = -1021751296
2526
2527/*
2528 * Using memory from the mbuf cluster pool, invoke the
2529 * bus_dma machinery to arrange the memory mapping.
2530 */
2531error = bus_dmamap_load(adapter-rxtag, rx_buffer-map,
2532mtod(mp, void *), mp-m_len,
2533em_dmamap_cb, paddr, 0);
2534if (error) {
2535m_free(mp);
#22 0xc0460b6e in em_process_receive_interrupts
Re: make.conf for 6.0
Thomas T. Veldhouse [EMAIL PROTECTED] wrote: Hmm ... I find this thread surprising, as this is the first I have heard of FreeBSD working correctly with -O2. So, is this the options suggested for make.conf on x86? CFLAGS= -O2 -pipe -fno-strict-aliasing COPTFLAGS= -O2 -pipe In fact, those are the defaults (at least in FreeBSD 6 on i386; amd64 uses additional options like -frename-registers), so I would suggest to _not_ specify the options in make.conf at all. If you specify a CPUTYPE setting in /etc/make.conf, then appropriate -march=xxx options will be added to CFLAGS and COPTFLAGS automatically, so you don't have to care for that either. As the saying goes: Less is more ... ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. File names are infinite in length, where infinity is set to 255 characters. -- Peter Collinson, The Unix File System ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
On Thu, 27 Oct 2005, Mark Andrews wrote: On 2005-10-26, Mark Andrews wrote: Leading zeros are ambigious. Some platforms treat them as octal others treat them as decimal. There is nothing ambiguous about the example provided. (Perhaps it wasn't a good example, but it's always a bug if '04' is not correctly decoded, regardless of the numeric base in use.) You want a ambigious example? 192.168.222.012 It amazed me that no RFC ever appears to have standardised this format (although it is alluded to in passing as being decimal in various other places). Eg, 1035 has: [[[ The RDATA section of an A line in a master file is an Internet address expressed as four decimal numbers separated by dots without any imbedded spaces (e.g., 10.2.0.52 or 192.0.5.6). ]]] (although that's DNS zone file format, not /etc/hosts.) It's much easier to just reject octal and hexadecimal than to work out when and when not it is ambigious. It is also better to demand all 4 octets. It also generates less support complaints. I'm happy to reject octal and hex too! Anyway, count this as one (minor) support gripe :-) Thanks for your time, jan -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ stty intr ^m ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
man inet_addr and you'll find: All numbers supplied as ``parts'' in a `.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal). So a leading zero means hex. Stop trying to make it look pretty. Standards are a good thing and need to be followed. Jan Grant wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Thu, 27 Oct 2005, Mark Andrews wrote: On 2005-10-26, Mark Andrews wrote: Leading zeros are ambigious. Some platforms treat them as octal others treat them as decimal. There is nothing ambiguous about the example provided. (Perhaps it wasn't a good example, but it's always a bug if '04' is not correctly decoded, regardless of the numeric base in use.) You want a ambigious example? 192.168.222.012 It amazed me that no RFC ever appears to have standardised this format (although it is alluded to in passing as being decimal in various other places). Eg, 1035 has: [[[ The RDATA section of an A line in a master file is an Internet address expressed as four decimal numbers separated by dots without any imbedded spaces (e.g., 10.2.0.52 or 192.0.5.6). ]]] (although that's DNS zone file format, not /etc/hosts.) It's much easier to just reject octal and hexadecimal than to work out when and when not it is ambigious. It is also better to demand all 4 octets. It also generates less support complaints. I'm happy to reject octal and hex too! Anyway, count this as one (minor) support gripe :-) Thanks for your time, jan -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
On Thu, 27 Oct 2005, Paul T. Root wrote: man inet_addr and you'll find: All numbers supplied as ``parts'' in a `.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal). So a leading zero means hex. Stop trying to make it look pretty. Standards are a good thing and need to be followed. I also found: [[[ STANDARDS The inet_ntop() and inet_pton() functions conform to X/Open Networking Services Issue 5.2 (``XNS5.2''). Note that inet_pton() does not accept 1-, 2-, or 3-part dotted addresses; all four parts must be specified and are interpreted only as decimal values. This is a narrower input set than that accepted by inet_aton(). ]]] on that same man page :-) Cheers, jan PS. I only raised the issue in case anyone else was bitten by it (which is why a PR might be handy). Having fixed /etc/hosts, I don't think this is worth wasting more energy on. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
Jan Grant wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Thu, 27 Oct 2005, Paul T. Root wrote: man inet_addr and you'll find: All numbers supplied as ``parts'' in a `.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal). So a leading zero means hex. Stop trying to make it look pretty. Standards are a good thing and need to be followed. I also found: [[[ STANDARDS The inet_ntop() and inet_pton() functions conform to X/Open Networking Services Issue 5.2 (``XNS5.2''). Note that inet_pton() does not accept 1-, 2-, or 3-part dotted addresses; all four parts must be specified and are interpreted only as decimal values. This is a narrower input set than that accepted by inet_aton(). ]]] on that same man page :-) Sure but the hosts(5) man page says that it follows inet_addr(3) spec. Sorry, I neglected to put that little leap in. Cheers, jan PS. I only raised the issue in case anyone else was bitten by it (which is why a PR might be handy). Having fixed /etc/hosts, I don't think this is worth wasting more energy on. Yeah, you're right there. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Bind9 Problem, please help
Please help, thanks Oct 27 21:35:15 mailhub named[71639]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 27 21:35:15 mailhub named[71639]: command channel listening on 127.0.0.1#953 Oct 27 21:35:15 mailhub named[71639]: errno2result.c:109: unexpected error: Oct 27 21:35:15 mailhub named[71639]: unable to convert errno to isc_result: 6: Device not configured Oct 27 21:35:16 mailhub named[71640]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 27 21:35:16 mailhub named[71640]: command channel listening on 127.0.0.1#953 Oct 27 21:35:16 mailhub named[71640]: errno2result.c:109: unexpected error: Oct 27 21:35:16 mailhub named[71640]: unable to convert errno to isc_result: 6: Device not configured ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
On Thu, 27 Oct 2005, Paul T. Root wrote: Jan Grant wrote: On Thu, 27 Oct 2005, Paul T. Root wrote: man inet_addr and you'll find: All numbers supplied as ``parts'' in a `.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal). So a leading zero means hex. Stop trying to make it look pretty. Standards are a good thing and need to be followed. [ STANDARDS section from the man page snipped ] Sure but the hosts(5) man page says that it follows inet_addr(3) spec. Sorry, I neglected to put that little leap in. You're right. So, we appear to agree that either the man page for hosts(5) is in need of an update, or the resolver is currently not conforming to the described behaviour? Since 1.2.3.04foo is currently an illegal /etc/hosts entry. Cheers, -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ They modified their trousers secretly. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind9 Problem, please help
Please help, thanks Oct 27 21:35:15 mailhub named[71639]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 27 21:35:15 mailhub named[71639]: command channel listening on 127.0.0.1# 953 Oct 27 21:35:15 mailhub named[71639]: errno2result.c:109: unexpected error: Oct 27 21:35:15 mailhub named[71639]: unable to convert errno to isc_result: 6: Device not configured Oct 27 21:35:16 mailhub named[71640]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 27 21:35:16 mailhub named[71640]: command channel listening on 127.0.0.1# 953 Oct 27 21:35:16 mailhub named[71640]: errno2result.c:109: unexpected error: Oct 27 21:35:16 mailhub named[71640]: unable to convert errno to isc_result: 6: Device not configured [ENXIO]The named file is a character special or block special file, and the device associated with this special file does not exist. [ENXIO]The named file is a fifo, no process has it open for reading, and the arguments specify it is to be opened for writing. What mount ops does /u1/dns have? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: Bind9 Problem, please help
Mark Andrews wrote: This is a multi-part message in MIME format. --060508000808090604020506 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mark Andrews wrote: Please help, thanks Oct 27 21:35:15 mailhub named[71639]: starting BIND 9.3.1 -u bind -t /u1/dn s -c /etc/named.conf -f Oct 27 21:35:15 mailhub named[71639]: command channel listening on 127.0.0. 1# 953 Oct 27 21:35:15 mailhub named[71639]: errno2result.c:109: unexpected error: Oct 27 21:35:15 mailhub named[71639]: unable to convert errno to isc_result : 6: Device not configured Oct 27 21:35:16 mailhub named[71640]: starting BIND 9.3.1 -u bind -t /u1/dn s -c /etc/named.conf -f Oct 27 21:35:16 mailhub named[71640]: command channel listening on 127.0.0. 1# 953 Oct 27 21:35:16 mailhub named[71640]: errno2result.c:109: unexpected error: Oct 27 21:35:16 mailhub named[71640]: unable to convert errno to isc_result : 6: Device not configured [ENXIO]The named file is a character special or block speci al file, and the device associated with this special fi le does not exist. [ENXIO]The named file is a fifo, no process has it open for reading, and the arguments specify it is to be opene d for writing. What mount ops does /u1/dns have? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] sorry for my ignorance but i dont know what you mean by mount ops The output of mount for the filesystem. Filesystem SizeUsed Avail Capacity Mounted on /dev/da0s1a248M138M 90M60%/ devfs 1.0K1.0K 0B 100%/dev /dev/da0s1e248M224K228M 0%/tmp /dev/da0s1f 31G1.9G 27G 7%/usr /dev/da0s1d248M165M 63M72%/var this is my /u1/dns drwxr-xr-x 2 root daemon 512 Jul 12 2002 dev Do the major and minor number match those in /dev? /u1/dev crw-r--r-- 1 root daemon2, 2 Jul 12 2002 null crw-r--r-- 1 root daemon2, 3 Jul 12 2002 random crw-r--r-- 1 root daemon2, 12 Jul 12 2002 zero /dev crw-rw-rw- 1 root wheel2, 2 Oct 27 22:33 null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 zero so, random has a different no., how do u recreate /dev/random that will match /u1/dev/random? drwxr-xr-x 2 root daemon 512 Jan 7 2005 etc drwxr-xr-x 5 root daemon 512 Jul 12 2002 var and my /u1 is a symbolic link of /usr/u1 (i did that because my /usr has more spaces) the whole /u1/dns is copied from a running DNS server which is going to die s oon (i recreated them to a new box) --060508000808090604020506 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN html head meta content=text/html;charset=ISO-8859-1 http-equiv=Content-Type title/title /head body bgcolor=#ff text=#00 Mark Andrews wrote: blockquote cite=[EMAIL PROTECTED] type=cite blockquote type=cite pre wrap=Please help, thanks Oct 27 21:35:15 mailhub named[71639]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 27 21:35:15 mailhub named[71639]: command channel listening on 127.0.0.1# 953 Oct 27 21:35:15 mailhub named[71639]: errno2result.c:109: unexpected error: Oct 27 21:35:15 mailhub named[71639]: unable to convert errno to isc_result: 6: Device not configured Oct 27 21:35:16 mailhub named[71640]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 27 21:35:16 mailhub named[71640]: command channel listening on 127.0.0.1# 953 Oct 27 21:35:16 mailhub named[71640]: errno2result.c:109: unexpected error: Oct 27 21:35:16 mailhub named[71640]: unable to convert errno to isc_result: 6: Device not configured /pre /blockquote pre wrap=! [ENXIO]The named file is a character special or block specia l file, and the device associated with this special fil e does not exist. [ENXIO]The named file is a fifo, no process has it open for reading, and the arguments specify it is to be opened for writing. What mount ops does /u1/dns have? /pre blockquote type=cite pre wrap= ___ a class=moz-txt-link-abbreviated
Re: Bind9 Problem, please help
In the last episode (Oct 27), pinoyskull said: Filesystem SizeUsed Avail Capacity Mounted on /dev/da0s1a248M138M 90M60%/ devfs 1.0K1.0K 0B 100%/dev /dev/da0s1e248M224K228M 0%/tmp /dev/da0s1f 31G1.9G 27G 7%/usr /dev/da0s1d248M165M 63M72%/var You should mount a devfs onto /u01/dev. /etc/rc.d/named should have done this for you. Try removing your existing /u1/dev directory and running /etc/rc.d/named restart. -- Dan Nelson [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: Bind9 Problem, please help
pinoyskull wrote: Mark Andrews wrote: This is a multi-part message in MIME format. --060508000808090604020506 ---clip --- /u1/dev crw-r--r-- 1 root daemon2, 2 Jul 12 2002 null crw-r--r-- 1 root daemon2, 3 Jul 12 2002 random crw-r--r-- 1 root daemon2, 12 Jul 12 2002 zero /dev crw-rw-rw- 1 root wheel2, 2 Oct 27 22:33 null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 zero chmod 666 /u1/dev/random /u1/dev/null /u1/dev/zero seems better for the user bind By the way , the major,minor of random are not the same ??? Henri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP! 6.0-RELEASE coming
All, Wanted to let everyone know that the testing on RC1 has gone well enough that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone that we have talked to has applauded the stability and functionality of the system, so we are really pleased and really eager to wrap it up and get it out to everyone. Over the next 24 hours we will be synchronizing the RELENG_6_0 tree to get in all of the appropriate bug fixes, then we will do some test builds as a final verification. Everyone is still welcome to update their sources on the RELENG_6_0 branch and provide feedback for the next 48 hours or so. The release will likely be announced by the end of the weekend or early next week, at the latest. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
Wanted to let everyone know that the testing on RC1 has gone well enough that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone that we have talked to has applauded the stability and functionality of the system, so we are really pleased and really eager to wrap it up and get it out to everyone. Indeed, I've been using 6.0 since BETA1 for a very long time and it seems stable like a rock. Congratulations! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
On Thu, 27 Oct 2005 20:09:36 +0200 Felipe Alfaro Solana [EMAIL PROTECTED] wrote: Wanted to let everyone know that the testing on RC1 has gone well enough that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone that we have talked to has applauded the stability and functionality of the system, so we are really pleased and really eager to wrap it up and get it out to everyone. Indeed, I've been using 6.0 since BETA1 for a very long time and it seems stable like a rock. Congratulations! One thing I noticed with the ata code on 6.x. Put in a CF to your PCMCIA to CF adaptor and try to boot your laptop. The kernel will immidiately core dump. This never happened on 5.x. #uname -a FreeBSD lapdance.yazzy.net 6.0-RC1 FreeBSD 6.0-RC1 #12: Wed Oct 12 09:06:40 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPDANCE i386 Cheers, Marcin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
Marcin Jessa wrote: On Thu, 27 Oct 2005 20:09:36 +0200 Felipe Alfaro Solana [EMAIL PROTECTED] wrote: Wanted to let everyone know that the testing on RC1 has gone well enough that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone that we have talked to has applauded the stability and functionality of the system, so we are really pleased and really eager to wrap it up and get it out to everyone. Indeed, I've been using 6.0 since BETA1 for a very long time and it seems stable like a rock. Congratulations! One thing I noticed with the ata code on 6.x. Put in a CF to your PCMCIA to CF adaptor and try to boot your laptop. The kernel will immidiately core dump. This never happened on 5.x. #uname -a FreeBSD lapdance.yazzy.net 6.0-RC1 FreeBSD 6.0-RC1 #12: Wed Oct 12 09:06:40 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPDANCE i386 Cheers, Marcin This was just fixed a couple of hours ago. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
On 27/10/2005, at 21:12, Marcin Jessa wrote: On Thu, 27 Oct 2005 20:09:36 +0200 Felipe Alfaro Solana [EMAIL PROTECTED] wrote: Wanted to let everyone know that the testing on RC1 has gone well enough that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone that we have talked to has applauded the stability and functionality of the system, so we are really pleased and really eager to wrap it up and get it out to everyone. Indeed, I've been using 6.0 since BETA1 for a very long time and it seems stable like a rock. Congratulations! One thing I noticed with the ata code on 6.x. Put in a CF to your PCMCIA to CF adaptor and try to boot your laptop. The kernel will immidiately core dump. This never happened on 5.x. #uname -a FreeBSD lapdance.yazzy.net 6.0-RC1 FreeBSD 6.0-RC1 #12: Wed Oct 12 09:06:40 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPDANCE i386 I've just committed a fix for this a few hours ago.. Søren Schmidt [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Panic/Reboot in 5.4-STABLE
Panics occur as often as every few hours (usually once or twice a day) on eight identical systems used as VPN devices in hospital radiology appliance maintenance network. One other system running 4.10-RELEASE on Soekris Net4801 doesn't experience this problem. dmesg output: WARNING: pseudo-random number generator used for IPsec processing Fatal trap 12: page fault while in kernel mode fault virtual address = 0x23 fault code = supervisor read, page not present instruction pointer = 0x8:0xc06c9530 stack pointer = 0x10:0xcc7378f4 frame pointer = 0x10:0xcc737904 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 498 (isakmpd) trap number = 12 panic: page fault Uptime: 18h55m51s Dumping 255 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #1: Fri Oct 14 10:37:20 EDT 2005 [EMAIL PROTECTED]:/usr/obj/var/cvsup/usr/src/sys/RADIOLOGY WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 1500MHz (1496.34-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf07 Stepping = 7 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,M CA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 268173312 (255 MB) avail memory = 252772352 (241 MB) npx0: math processor on motherboard npx0: INT 16 interface acpi0: GATEWA N0CPP063 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82850 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xdc00-0xdc7f mem 0xff9ffc00-0xff9ffc7f irq 3 at device 10.0 on pci2 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:bb:82:cc rl0: D-Link DFE-530TX+ 10/100BaseTX port 0xd800-0xd8ff mem 0xff9ff800-0xff9ff8ff irq 9 at device 11.0 on pci2 miibus1: MII bus on rl0 rlphy0: RealTek internal media interface on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0d:88:35:27:a3 rl1: D-Link DFE-530TX+ 10/100BaseTX port 0xd400-0xd4ff mem 0xff9ff400-0xff9ff4ff irq 10 at device 12.0 on pci2 miibus2: MII bus on rl1 rlphy1: RealTek internal media interface on miibus2 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: Ethernet address: 00:0d:88:35:27:89 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xef40-0xef5f irq 5 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: serial bus, SMBus at device 31.3 (no driver attached) uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xef80-0xef9f irq 9 at device 31.4 on pci0 usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: floppy drive controller port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console ppc0: ECP parallel printer port port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 orm0:
Re: Strange crashing/rebooting problem
On 10/26/05, Alan Amesbury [EMAIL PROTECTED] wrote: This is pretty much classic Dell. We've purchased a number of systems without operating systems on which we run FreeBSD. However, they continually operate under the assumption that we are running Windoze or Linux, and expect those to do things like BIOS updates. Have you tried running the Linux versions under FreeBSD's Linux emulation? I haven't tried this yet either, but that'd be my first whack at it. These links ftp://ftp.dell.com/diags/ED5061A0.tar.gz ftp://ftp.dell.com/diags/EI5061A0.ZIP ftp://ftp.dell.com/diags/MP1038A0.tar.gz ftp://ftp.us.dell.com/diags/MP1038A0.zip point at the Dell 32-bit diagnostics (first pair) and the memory diagnostics utilities (second pair). Yes, those are the diagnostics I was thinking of. Bryan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
What about Gleb Smirnoff NFS locking leak patch ? I put it on production, everything works just fine. The question is: this patch will be merged to main source tree for 6.0-RELEASE ? Scott Long wrote: SL Wanted to let everyone know that the testing on RC1 has gone well enough SL that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone SL that we have talked to has applauded the stability and functionality of SL the system, so we are really pleased and really eager to wrap it up and SL get it out to everyone. Over the next 24 hours we will be synchronizing SL the RELENG_6_0 tree to get in all of the appropriate bug fixes, then we SL will do some test builds as a final verification. Everyone is still SL welcome to update their sources on the RELENG_6_0 branch and provide SL feedback for the next 48 hours or so. The release will likely be SL announced by the end of the weekend or early next week, at the latest. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
Vladimir Sharun wrote: What about Gleb Smirnoff NFS locking leak patch ? I put it on production, everything works just fine. The question is: this patch will be merged to main source tree for 6.0-RELEASE ? Scott Long wrote: SL Wanted to let everyone know that the testing on RC1 has gone well enough SL that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone SL that we have talked to has applauded the stability and functionality of SL the system, so we are really pleased and really eager to wrap it up and SL get it out to everyone. Over the next 24 hours we will be synchronizing SL the RELENG_6_0 tree to get in all of the appropriate bug fixes, then we SL will do some test builds as a final verification. Everyone is still SL welcome to update their sources on the RELENG_6_0 branch and provide SL feedback for the next 48 hours or so. The release will likely be SL announced by the end of the weekend or early next week, at the latest. I beleive that this was committed a few hours ago. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0 RC1 usbd.conf (and installation comments)
On 10/26/05, Patrick Lamaizière [EMAIL PROTECTED] wrote: Yes but be carefull, by sample amavisd-new uses scripts in /etc/rc.d and not in /usr/local/etc/rc.d. Why the mail server does not work anymore ? Yes, this is most annoying. I haven't gotten around to submitting a ports PR complaining about /etc/rc.d/amavisd -- it's so obvious I figured it must have been intentional, but I can't figure out how it makes sense organizationally for a port to drop things in /etc/rc.d. Bryan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! 6.0-RELEASE coming
On Thu, Oct 27, 2005 at 10:43:35PM +0300, Vladimir Sharun wrote: What about Gleb Smirnoff NFS locking leak patch ? I put it on production, everything works just fine. The question is: this patch will be merged to main source tree for 6.0-RELEASE ? It already was. Kris pgpDf8ksiSV4z.pgp Description: PGP signature
Re: Bind9 Problem, please help
The output of mount for the filesystem. Filesystem SizeUsed Avail Capacity Mounted on /dev/da0s1a248M138M 90M60%/ devfs 1.0K1.0K 0B 100%/dev /dev/da0s1e248M224K228M 0%/tmp /dev/da0s1f 31G1.9G 27G 7%/usr /dev/da0s1d248M165M 63M72%/var I said mount not df. e.g. /dev/ad0s3a on / (ufs, local, noatime) /dev/ad0s3g on /home (ufs, local, noatime) /dev/ad0s3f on /usr (ufs, local, noatime) /dev/ad0s3e on /var (ufs, local, noatime) /dev/ad0s2 on /c (ntfs, local, read-only) procfs on /proc (procfs, local) this is my /u1/dns drwxr-xr-x 2 root daemon 512 Jul 12 2002 dev Do the major and minor number match those in /dev? /u1/dev crw-r--r-- 1 root daemon2, 2 Jul 12 2002 null crw-r--r-- 1 root daemon2, 3 Jul 12 2002 random crw-r--r-- 1 root daemon2, 12 Jul 12 2002 zero /dev crw-rw-rw- 1 root wheel2, 2 Oct 27 22:33 null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 zero so, random has a different no., how do u recreate /dev/random that will match /u1/dev/random? mknod. Also make sure the permissions match. drwxr-xr-x 2 root daemon 512 Jan 7 2005 etc drwxr-xr-x 5 root daemon 512 Jul 12 2002 var and my /u1 is a symbolic link of /usr/u1 (i did that because my /usr has mo re spaces) the whole /u1/dns is copied from a running DNS server which is going to die s oon (i recreated them to a new box) Copying /dev between different OS's or even different revisions of the same OS can cause problems. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: HEADS UP! 6.0-RELEASE coming
On Thu, 27 Oct 2005 21:21:51 +0200 Søren Schmidt [EMAIL PROTECTED] wrote: On 27/10/2005, at 21:12, Marcin Jessa wrote: On Thu, 27 Oct 2005 20:09:36 +0200 Felipe Alfaro Solana [EMAIL PROTECTED] wrote: Wanted to let everyone know that the testing on RC1 has gone well enough that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone that we have talked to has applauded the stability and functionality of the system, so we are really pleased and really eager to wrap it up and get it out to everyone. Indeed, I've been using 6.0 since BETA1 for a very long time and it seems stable like a rock. Congratulations! One thing I noticed with the ata code on 6.x. Put in a CF to your PCMCIA to CF adaptor and try to boot your laptop. The kernel will immidiately core dump. This never happened on 5.x. #uname -a FreeBSD lapdance.yazzy.net 6.0-RC1 FreeBSD 6.0-RC1 #12: Wed Oct 12 09:06:40 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPDANCE i386 I've just committed a fix for this a few hours ago.. I just rebuilt my kernel and the issue is indeed gone. Great work as usual. Thanks Søren! Marcin. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.x/6.x network stability
Morning All, I've been having a heap of trouble with the primary network interface on a box that was running 5.4 and recently upgraded to 6.0-Beta5 where the interface would just go dead. Nothing in ifconfig or syslog or dmesg would indicate a problem, but nothing would go in or out. The only way to fix it was reboot. A week ago, after searching the mailing lists I realised it might be the fact that I was using Netatalk and that might not be MP safe so I set debug.mpsafenet=0 in /boot/loader.conf and the box has been stable ever since. Is anyone looking at the kernel Netatalk code? Is this likely to be the real reason for the problem? Thanks, Carl. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x/6.x network stability
On Fri, Oct 28, 2005 at 09:55:21AM +1000, Carl Makin wrote: Morning All, I've been having a heap of trouble with the primary network interface on a box that was running 5.4 and recently upgraded to 6.0-Beta5 where the interface would just go dead. Nothing in ifconfig or syslog or dmesg would indicate a problem, but nothing would go in or out. The only way to fix it was reboot. A week ago, after searching the mailing lists I realised it might be the fact that I was using Netatalk and that might not be MP safe so I set debug.mpsafenet=0 in /boot/loader.conf and the box has been stable ever since. Is anyone looking at the kernel Netatalk code? Is this likely to be the real reason for the problem? The netatalk code gets looked at now an then, but very few people stress test it. As more of the kernel is getting properly locked down, the odds of the other parts breaking increases due to increased concurrency so I wouldn't be at all surprised if there's a netatalk issue. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpKRI2W4vnhv.pgp Description: PGP signature
Easy way to kill a 5.x/6.x box as a basic user.
Morning All, I've been playing with some GIS software and 32Mb TIFF images. Running ImageMagick's convert utility under my normal user login to convert the image to gif or jpeg blows away the system every time. No panic seen on the console and no core dump found, the system just quietly reboots. Upon reboot /var is full and corrupt and takes ages for the background fsck to fix it so I normally boot into single user mode and do it myself. Is anyone else seeing this? I can happily supply an image that causes the problem if someone wants to try it. Carl. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Easy way to kill a 5.x/6.x box as a basic user.
On Thursday 27 October 2005 17:12, Carl Makin wrote:
Morning All,
I've been playing with some GIS software and 32Mb TIFF images. Running
ImageMagick's convert utility under my normal user login to convert
the image to gif or jpeg blows away the system every time. No panic
seen on the console and no core dump found, the system just quietly
reboots. Upon reboot /var is full and corrupt and takes ages for the
background fsck to fix it so I normally boot into single user mode and
do it myself.
Is anyone else seeing this? I can happily supply an image that causes
the problem if someone wants to try it.
Carl.
Just a guess but it may be the software is opening too many files. Try
installing /usr/ports/sysutils/lsof then while your program is running
run lsof -c {watever you program name is} +r5. If you see screenfulls
of open files then thats the problem.
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
Date: Thu, 27 Oct 2005 13:05:23 +0930 From: Daniel O'Connor [EMAIL PROTECTED] Subject: Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c The command I use most is wicontrol -L Try ifconfig ath0 list scan # ifconfig ath0 list scan ifconfig: list: bad value # ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
On Fri, 28 Oct 2005 10:05, James Long wrote: Date: Thu, 27 Oct 2005 13:05:23 +0930 From: Daniel O'Connor [EMAIL PROTECTED] Subject: Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c The command I use most is wicontrol -L Try ifconfig ath0 list scan # ifconfig ath0 list scan ifconfig: list: bad value # Er weird.. Is this in 6.0 or 5.x? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpmnSJF40rkd.pgp Description: PGP signature
Re: 5.x/6.x network stability
Carl Makin wrote: Morning All, I've been having a heap of trouble with the primary network interface on a box that was running 5.4 and recently upgraded to 6.0-Beta5 where the interface would just go dead. Nothing in ifconfig or syslog or dmesg would indicate a problem, but nothing would go in or out. The only way to fix it was reboot. What sort of network card? I've been having the same syptoms with a sk driver gigabit card. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind9 Problem, please help
ok, after reading all your replies (thank you very much), it seems the my problem with dev has been fixed, what i did was i recreated my /u1/dns/dev that matches the one that's on /dev, /dev crw-rw-rw- 1 root wheel2, 2 Oct 28 12:00 /dev/null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 /dev/random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 /dev/zero /u1/dns/dev crw-rw-rw- 1 root daemon2, 2 Oct 28 11:52 null crw-rw-rw- 1 root daemon 249, 0 Oct 28 11:52 random crw-rw-rw- 1 root daemon2, 12 Oct 28 11:52 zero i cranked it up and i got this === Oct 28 12:00:24 mailhub named[85612]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:00:25 mailhub named[85612]: command channel listening on 127.0.0.1#953 Oct 28 12:01:39 mailhub named[85846]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:39 mailhub named[85846]: command channel listening on 127.0.0.1#953 Oct 28 12:01:40 mailhub named[85848]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:40 mailhub named[85848]: command channel listening on 127.0.0.1#953 Oct 28 12:01:41 mailhub named[85850]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:41 mailhub named[85850]: command channel listening on 127.0.0.1#953 Oct 28 12:01:42 mailhub named[85860]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:42 mailhub named[85860]: command channel listening on 127.0.0.1#953 === it's a looping message ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Easy way to kill a 5.x/6.x box as a basic user.
On Fri, 28 Oct 2005, 10:12+1000, Carl Makin wrote: Morning All, I've been playing with some GIS software and 32Mb TIFF images. Running ImageMagick's convert utility under my normal user login to convert the image to gif or jpeg blows away the system every time. No panic seen on the console and no core dump found, the system just quietly reboots. Upon reboot /var is full and corrupt and takes ages for the background fsck to fix it so I normally boot into single user mode and do it myself. Is anyone else seeing this? I can happily supply an image that causes the problem if someone wants to try it. Known problem. Were discussed severeal times in the past (e.g. subject vnode_pager_putpages errors in -stable). -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind9 Problem, please help
ok, after reading all your replies (thank you very much), it seems the my problem with dev has been fixed, what i did was i recreated my /u1/dns/dev that matches the one that's on /dev, /dev crw-rw-rw- 1 root wheel2, 2 Oct 28 12:00 /dev/null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 /dev/random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 /dev/zero /u1/dns/dev crw-rw-rw- 1 root daemon2, 2 Oct 28 11:52 null crw-rw-rw- 1 root daemon 249, 0 Oct 28 11:52 random crw-rw-rw- 1 root daemon2, 12 Oct 28 11:52 zero i cranked it up and i got this === Oct 28 12:00:24 mailhub named[85612]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:00:25 mailhub named[85612]: command channel listening on 127.0.0.1#953 Oct 28 12:01:39 mailhub named[85846]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:39 mailhub named[85846]: command channel listening on 127.0.0.1#953 Oct 28 12:01:40 mailhub named[85848]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:40 mailhub named[85848]: command channel listening on 127.0.0.1#953 Oct 28 12:01:41 mailhub named[85850]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:41 mailhub named[85850]: command channel listening on 127.0.0.1#953 Oct 28 12:01:42 mailhub named[85860]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:42 mailhub named[85860]: command channel listening on 127.0.0.1#953 === it's a looping message Stop whatever you are using to start named. As root run named -u bind -t /u1/dns -c /etc/named.conf -g This will keep named in the foreground and send to logs to the terminal. Once you have addressed whatever problems are reported you can go back to doing what you were doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: 5.x/6.x network stability
John Pettitt wrote: Carl Makin wrote: Morning All, the interface would just go dead. Nothing in ifconfig or syslog or dmesg would indicate a problem, but nothing would go in or out. The only way to fix it was reboot. What sort of network card? I've been having the same syptoms with a sk driver gigabit card. Intel Etherexpress 10/100 using the fxp driver and some other brand X card using the rl (RealTek) driver. Interestingly disabling ACPI seemed to lengthen the time between failures by a day or so, but it still failed. It's been running for a week now without a problem by setting debug.mpsafenet=0 in loader.conf. Are you using any oddball protocols or devices? Carl. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind9 Problem, please help
Mark Andrews wrote: ok, after reading all your replies (thank you very much), it seems the my problem with dev has been fixed, what i did was i recreated my /u1/dns/dev that matches the one that's on /dev, /dev crw-rw-rw- 1 root wheel2, 2 Oct 28 12:00 /dev/null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 /dev/random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 /dev/zero /u1/dns/dev crw-rw-rw- 1 root daemon2, 2 Oct 28 11:52 null crw-rw-rw- 1 root daemon 249, 0 Oct 28 11:52 random crw-rw-rw- 1 root daemon2, 12 Oct 28 11:52 zero i cranked it up and i got this === Oct 28 12:00:24 mailhub named[85612]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:00:25 mailhub named[85612]: command channel listening on 127.0.0.1#953 Oct 28 12:01:39 mailhub named[85846]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:39 mailhub named[85846]: command channel listening on 127.0.0.1#953 Oct 28 12:01:40 mailhub named[85848]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:40 mailhub named[85848]: command channel listening on 127.0.0.1#953 Oct 28 12:01:41 mailhub named[85850]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:41 mailhub named[85850]: command channel listening on 127.0.0.1#953 Oct 28 12:01:42 mailhub named[85860]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:42 mailhub named[85860]: command channel listening on 127.0.0.1#953 === it's a looping message Stop whatever you are using to start named. As root run named -u bind -t /u1/dns -c /etc/named.conf -g This will keep named in the foreground and send to logs to the terminal. Once you have addressed whatever problems are reported you can go back to doing what you were doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] this is what i got after i ran (named -u bind -t /u1/dns -c /etc/named.conf -g 28-Oct-2005 12:37:13.282 starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -g 28-Oct-2005 12:37:13.285 loading configuration from '/etc/named.conf' 28-Oct-2005 12:37:13.321 listening on IPv4 interface fxp0, (ip adress) 28-Oct-2005 12:37:13.322 listening on IPv4 interface lo0, 127.0.0.1#53 28-Oct-2005 12:37:13.373 command channel listening on 127.0.0.1#953 28-Oct-2005 12:37:13.373 ignoring config file logging statement due to -g option 28-Oct-2005 12:37:13.373 couldn't open pid file '/var/run/named.pid': File exists 28-Oct-2005 12:37:13.373 exiting (due to early fatal error) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind9 Problem, please help
Mark Andrews wrote: ok, after reading all your replies (thank you very much), it seems the my problem with dev has been fixed, what i did was i recreated my /u1/dns/dev that matches the one that's on /dev, /dev crw-rw-rw- 1 root wheel2, 2 Oct 28 12:00 /dev/null crw-rw-rw- 1 root wheel 249, 0 Oct 28 00:57 /dev/random crw-rw-rw- 1 root wheel2, 12 Oct 27 16:57 /dev/zero /u1/dns/dev crw-rw-rw- 1 root daemon2, 2 Oct 28 11:52 null crw-rw-rw- 1 root daemon 249, 0 Oct 28 11:52 random crw-rw-rw- 1 root daemon2, 12 Oct 28 11:52 zero i cranked it up and i got this === Oct 28 12:00:24 mailhub named[85612]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:00:25 mailhub named[85612]: command channel listening on 127.0.0.1#953 Oct 28 12:01:39 mailhub named[85846]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:39 mailhub named[85846]: command channel listening on 127.0.0.1#953 Oct 28 12:01:40 mailhub named[85848]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:40 mailhub named[85848]: command channel listening on 127.0.0.1#953 Oct 28 12:01:41 mailhub named[85850]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:41 mailhub named[85850]: command channel listening on 127.0.0.1#953 Oct 28 12:01:42 mailhub named[85860]: starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -f Oct 28 12:01:42 mailhub named[85860]: command channel listening on 127.0.0.1#953 === it's a looping message Stop whatever you are using to start named. As root run named -u bind -t /u1/dns -c /etc/named.conf -g This will keep named in the foreground and send to logs to the terminal. Once you have addressed whatever problems are reported you can go back to doing what you were doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] this is what i got after i ran (named -u bind -t /u1/dns -c /etc/named.conf -g 28-Oct-2005 12:37:13.282 starting BIND 9.3.1 -u bind -t /u1/dns -c /etc/named.conf -g 28-Oct-2005 12:37:13.285 loading configuration from '/etc/named.conf' 28-Oct-2005 12:37:13.321 listening on IPv4 interface fxp0, (ip adress) 28-Oct-2005 12:37:13.322 listening on IPv4 interface lo0, 127.0.0.1#53 28-Oct-2005 12:37:13.373 command channel listening on 127.0.0.1#953 28-Oct-2005 12:37:13.373 ignoring config file logging statement due to -g option 28-Oct-2005 12:37:13.373 couldn't open pid file '/var/run/named.pid': File exists 28-Oct-2005 12:37:13.373 exiting (due to early fatal error) The permissions of /u1/dns/var/run are? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
