Notice!!! From Yahoo Window Live Awards Centre.
Yahoo Window Live Awards Centre 124 Stockport Road, Longsight, Manchester M60 2DB United Kingdom. Tel: +447045736125,+447024093946. Dear Prize Winner, This is to inform you that you have won a prize money of (Two Hundred Fifty Thousand) Great Britain Pounds (GBP.250,000.00) for the month of February,2008 Prize promotion which is organized by (YAHOO AWARDS WINDOWS LIVE). (YAHOO) collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Four people are selected monthly to benefit from this promotion and you are one of the Selected Winners. ** PAYMENT OF PRIZE** Winners shall be paid in accordance with their Settlement Centers.Yahoo Prize Award must be claimed not later than (10 days)from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed. Stated below are your identification numbers: BATCH NUMBER: MFI/06/APA-43658 REFERENCE NUMBER: 2007234522 PIN:1207 You are requested to contact our co-ordinator in Manchester and send your winning identification numbers to him: Co-ordinator's Name: Mr. Brad Richards E-Mail:[EMAIL PROTECTED] You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you. (1)Full name(2)Country... (3)Contact Address(4)Telephone Number (5)fax Number..(6)Marital Status.. (7)Occupation.(8)Sex. (9)Date of Birth/Age .(10)Identity card(carte identite) Yours in service, Mrs. Grace Sanders * WARNING! WARNING!! WARNING!!!. You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims.Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Mon, Feb 11, 2008 at 12:29:13PM -0800, Joseph Olatt wrote: On Mon, Feb 11, 2008 at 10:37:02AM +0100, Harald Weis wrote: On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. 1. Check /usr/local/lib/X11/fonts/misc directory to see if there are font files there. In my case, that is where the fonts from package font-misc-misc and font-cursor-misc got installed. (pkg_info -L font-misc-misc-1.0.0 would tell you where the fonts got installed.) 2. Check the xorg.conf (/etc/X11/xorg.conf for me) to see if you have a section similar to the following: Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection If the line 'FontPath /usr/local/lib/X11/fonts/misc/' does not exist, you could get the fixed font error. I've done all these checks at the very beginning. The only remaining problem was the empty fonts.dir file which fully explains to my mind the fatal server error. I then ran mkfontdir and saw that this command does indeed generate an empty fonts.dir file on the bad machine where everything else seems so utterly correct. What I haven't done yet on the bad box (because it's not on my desk and its external, stupid, ISP router does not let me in via SSH) is to copy my fonts.dir file to it. Just for fun to see what happens. I'll do that tomorrow... In the last resort, I shall portupgrade -fP -o x11/xorg xorg But I hate the idea, it's so Unix-unlike, isn't it ? Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
7.0, amd64: Wrong files installed into jails?
Hi, I've created some jails on FreeBSD 7-RC* now, and I realized there must be some kind of problem when I tried to install and run diablo- jdk 1.5 from the freebsdfoundation packages. It complains about /libexec/ld-elf.so.1: /usr/local/lib/compat/pkg/libz.so.3: unsupported file layout and file(1) returns /usr/local/lib/compat/pkg/libz.so.3: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), stripped On the host, which has been upgraded from 6.2 to 7.0-RC1 using cvsup++ +, Java runs just fine, and finds its libraries in /lib (for instance). Presumably because they are still left there: ls -la /lib/libz.* -r--r--r-- 1 root wheel 79824 Jun 16 2005 /lib/libz.so.2 -r--r--r-- 1 root wheel 81448 Apr 28 2007 /lib/libz.so.3 -r--r--r-- 1 root wheel 83648 Jan 28 09:02 /lib/libz.so.4 There are no compat6x-packages installed anywhere, and even installing the compat6x-amd64 package in the jail does not change anything. Does installworld to a clean target install the i386 binaries instead of the amd64 binaries to the /usr/local/lib/compat/ tree?? With best regards, /Eirik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Notice!!! From Yahoo Window Live Awards Centre.
Yahoo Window Live Awards Centre 124 Stockport Road, Longsight, Manchester M60 2DB United Kingdom. Tel: +447045736125,+447024093946. Dear Prize Winner, This is to inform you that you have won a prize money of (Two Hundred Fifty Thousand) Great Britain Pounds (GBP.250,000.00) for the month of February,2008 Prize promotion which is organized by (YAHOO AWARDS WINDOWS LIVE). (YAHOO) collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Four people are selected monthly to benefit from this promotion and you are one of the Selected Winners. ** PAYMENT OF PRIZE** Winners shall be paid in accordance with their Settlement Centers.Yahoo Prize Award must be claimed not later than (10 days)from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed. Stated below are your identification numbers: BATCH NUMBER: MFI/06/APA-43658 REFERENCE NUMBER: 2007234522 PIN:1207 You are requested to contact our co-ordinator in Manchester and send your winning identification numbers to him: Co-ordinator's Name: Mr. Brad Richards E-Mail:[EMAIL PROTECTED] You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you. (1)Full name(2)Country... (3)Contact Address(4)Telephone Number (5)fax Number..(6)Marital Status.. (7)Occupation.(8)Sex. (9)Date of Birth/Age .(10)Identity card(carte identite) Yours in service, Mrs. Grace Sanders * WARNING! WARNING!! WARNING!!!. You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims.Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Analysis of disk file block with ZFS checksum error
Gavin Atkinson wrote: Are the datestamps (Thu Jan 24 23:20:58 2008) found within the corrupt block before or after the datestamp of the file it was found within? i.e. was the corrupt block on the disk before or after the mp3 was written there? Hi Gavin, those dated are later than the original copy (I do not have the file timestamps to prove this, but according to my email record, I am pretty sure of this). So the corrupt block is later than the original write. If this is the case, I assume that the block got written, by mistake, into the middle of the mp3 file. Someone else suggested that it could be caused by a bad transfer block number or bad drive command (corrupted on the way to the drive, since these are not checksummed in the hardware). If the block went to the wrong place, AND if it was a HW glitch, I suppose the best ZFS could then do is retry the write (if its failure was even detected - still not sure if ZFS does a re-check of the disk data checksum after the disk write), not knowing until the later scrub that the block had corrupted a file. I think that anything is possible, but I know I was getting periodic DMA timeouts, etc. around that time. I hesitate, although it is tempting, to use this evidence to focus blame purely on bad HW, given that others seem to be seeing DMA problems too, and there is reasonable doubt whether their problems are HW related or not. In my case, I have been free of DMA errors (cross your fingers) after re-installed FreeBSD completely (giving it a larger boot partition and redoing the ZFS slice too), and before this, I changed the IDE cable just to eliminate one more variable. Therefore, there are too many variables to reach a firm conclusion, since even if the cable was bad, I never saw one DMA error or other indication of anything wrong with HW from the Linux side (and I've been using that HW with both Linux and FreeBSD 6.2 for months now - no apparent flakiness of any kind on either system). So either it *was* bad and FreeBSD 7.0 was being more honest, FreeBSD's drivers and/or ZFS was stressing the HW and revealing weaknesses in the cable, or it was a SW issue that got cleared somehow when I re-installed. Is it possible that the problem lies in the ATA drivers in FreeBSD or even in ZFS and just looks like HW issues? I do not have enough info/expertise to know. If not, then it may very well be true that HW problems are pretty widespread (and that disk HW cannot, in fact, be trusted), and there really *is* a strong need for ZFS *now* to protect our data. If there is a possibility that SW could be involved, any hints on how to further debug this would be of great help to those still experiencing recent DMA errors. I just want to be more sure one way or the other, but I know this issue is not an easy one (however, it's the kind of problem that should receive the highest priority, IMHO). -Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Notice!!! From Yahoo Window Live Awards Centre.
hrmm yea sure im going to give you my personal info. NOT!!! - Original Message - From: Yahoo Window Live Awards Centre. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 11, 2008 7:51 AM Subject: Notice!!! From Yahoo Window Live Awards Centre. Yahoo Window Live Awards Centre 124 Stockport Road, Longsight, Manchester M60 2DB United Kingdom. Tel: +447045736125,+447024093946. Dear Prize Winner, This is to inform you that you have won a prize money of (Two Hundred Fifty Thousand) Great Britain Pounds (GBP.250,000.00) for the month of February,2008 Prize promotion which is organized by (YAHOO AWARDS WINDOWS LIVE). (YAHOO) collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Four people are selected monthly to benefit from this promotion and you are one of the Selected Winners. ** PAYMENT OF PRIZE** Winners shall be paid in accordance with their Settlement Centers.Yahoo Prize Award must be claimed not later than (10 days)from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed. Stated below are your identification numbers: BATCH NUMBER: MFI/06/APA-43658 REFERENCE NUMBER: 2007234522 PIN:1207 You are requested to contact our co-ordinator in Manchester and send your winning identification numbers to him: Co-ordinator's Name: Mr. Brad Richards E-Mail:[EMAIL PROTECTED] You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you. (1)Full name(2)Country... (3)Contact Address(4)Telephone Number (5)fax Number..(6)Marital Status.. (7)Occupation.(8)Sex. (9)Date of Birth/Age .(10)Identity card(carte identite) Yours in service, Mrs. Grace Sanders * WARNING! WARNING!! WARNING!!!. You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims.Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned. ___ 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: ad0: TIMEOUT - WRITE_DMA type errors with 7.0-RC1
On Mon, Feb 11, 2008 at 07:24:55AM -1000, Clifton Royston wrote: On Mon, Feb 11, 2008 at 01:00:57PM +0100, Remco van Bekkum wrote: On Fri, Jan 25, 2008 at 04:38:46PM -0800, Jeremy Chadwick wrote: After having replaced my first SATA disk with one of the same type, having still the same errors, I replaced this 1TB drive with 4x500GB Hitachi P7K500 in raidz. It worked fine for a week, but yesterday I cvsupped and rebuild world. This afternoon everything is breaking down again with the same errors: Feb 11 12:34:09 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:13 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:17 xaero kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Feb 11 12:34:21 xaero kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: FAILURE - WRITE_DMA48 timed out LBA=298014274 Did you try replacing cabling as a previous poster recommended? I've had similar problems with both traditional parallel ATA and SATA due to marginal cables, which of course are not solved by swapping drives. Not saying there's not a software problem here, just that there is still one area to eliminate. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services Hi Clifton, I don't recall exactly anymore, but at least 3 cables have been used without problems on other systems. I'm wondering, the mainboard acts weird sometimes as well: when I press the reset button, it sometimes powers down. Also, I just did a reset after it deadlocked on shutdown because of the errors, and when the system booted, 2 disks were not seen by the bios. I had to power down the box and when it came up again, the disks were back. Can software leave the disks in a state that the bios doesn't detect them after pressing the reset button? I'm 100% certain that on my previous installation, in a 100% different system, I got the same errors. That should normally mean either software or disk. The disk has been replaced, the OS is the same. I'm either having really bad luck or something else is wrong. What is a good way of stress testing disks? Thanks! - Remco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0: TIMEOUT - WRITE_DMA type errors with 7.0-RC1
On Mon, Feb 11, 2008 at 01:00:57PM +0100, Remco van Bekkum wrote: On Fri, Jan 25, 2008 at 04:38:46PM -0800, Jeremy Chadwick wrote: After having replaced my first SATA disk with one of the same type, having still the same errors, I replaced this 1TB drive with 4x500GB Hitachi P7K500 in raidz. It worked fine for a week, but yesterday I cvsupped and rebuild world. This afternoon everything is breaking down again with the same errors: Feb 11 12:34:09 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:13 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:17 xaero kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Feb 11 12:34:21 xaero kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: FAILURE - WRITE_DMA48 timed out LBA=298014274 Did you try replacing cabling as a previous poster recommended? I've had similar problems with both traditional parallel ATA and SATA due to marginal cables, which of course are not solved by swapping drives. Not saying there's not a software problem here, just that there is still one area to eliminate. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: supervisor read data, page not present
Hello!
I bumped my RAM yesterday from 2Gb to 4Gb and ran memtest-x86
-- no errors detected (took 4+ hours).
I then booted and proceeded to use the machine. It seemed fine
for a while, until a sudden (there was nobody at the console at
the time) panic. Below.
The box runs FreeBSD 6.3-STABLE as of Thu Feb 7 on quad-Opteron
(two dual-core CPUs).
Any ideas? Thanks!
-mi
[EMAIL PROTECTED]:amd64/compile/SILVER-SMP (111) kgdb kernel.debug
/meow/crash/vmcore.16
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0x6125538ffd0
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x804139dc
stack pointer = 0x10:0xd6154950
frame pointer = 0x10:0xff01428427c0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 33262 (setiathome-5.27.amd)
trap number = 12
panic: page fault
cpuid = 2
Uptime: 8h29m29s
Dumping 4095 MB (3 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (524016 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903
1887 1871 1855 1839 1823 1807 1791 17
75 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535
1519 1503 1487 1471 1455 1439 1423 14
07 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167
1151 1135 1119 1103 1087 1071 1055 10
39 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751
735 719 703 687 671 655 639 623 607 59
1 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287
271 255 239 223 207 191 175 159 143 1
27 111 95 79 63 47 31 15 ... ok
chunk 2: 2048MB (524288 pages) 2033 2017 2001 1985 1969 1953 1937 1921 1905
1889 1873 1857 1841 1825 1809 1793 17
77 1761 1745 1729 1713 1697 1681 1665 1649 1633 1617 1601 1585 1569 1553 1537
1521 1505 1489 1473 1457 1441 1425 14
09 1393 1377 1361 1345 1329 1313 1297 1281 1265 1249 1233 1217 1201 1185 1169
1153 1137 1121 1105 1089 1073 1057 10
41 1025 1009 993 977 961 945 929 913 897 881 865 849 833 817 801 785 769 753
737 721 705 689 673 657 641 625 609 59
3 577 561 545 529 513 497 481 465 449 433 417 401 385 369 353 337 321 305 289
273 257 241 225 209 193 177 161 145 1
29 113 97 81 65 49 33 17 1
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...
warning: /meow/crash/vmcore.16: no core file handler recognizes format, using
default
warning: you won't be able to access this core file until you terminate
your kernel core files.; do ``info files''
(kgdb) where
#0 doadump () at pcpu.h:172
#1 0x0004 in ?? ()
#2 0x802ba757 in boot (howto=260) at ../../../kern/kern_shutdown.c:409
#3 0x802badf1 in panic (fmt=0xff013c1894c0 ) at
../../../kern/kern_shutdown.c:565
#4 0x8041e31f in trap_fatal (frame=0xff013c1894c0,
eva=18446742980440342528)
at ../../../amd64/amd64/trap.c:669
#5 0x8041e69c in trap_pfault (frame=0xd61548a0, usermode=0) at
../../../amd64/amd64/trap.c:580
#6 0x8041e953 in trap (frame=
{tf_rdi = -1094100703296, tf_rsi = 6675808976776, tf_rdx = 81801216,
tf_rcx = 6675808976776, tf_r8 = 26518416
5758329, tf_r9 = -1098332737512, tf_rax = -1093258379264, tf_rbx = 1, tf_rbp =
-1094100703296, tf_r10 = 66758089767
76, tf_r11 = 971133419505, tf_r12 = 81801216, tf_r13 = 1442140160, tf_r14 =
-1093216129184, tf_r15 = -1093223841584
, tf_trapno = 12, tf_addr = 6675808976848, tf_flags = -2143402319, tf_err = 0,
tf_rip = -2143208996, tf_cs = 8, tf_
rflags = 66182, tf_rsp = -703248032, tf_ss = 0}) at
../../../amd64/amd64/trap.c:353
#7 0x8040456b in calltrap () at ../../../amd64/amd64/exception.S:168
#8 0x804139dc in pmap_remove_entry (pmap=0xff01428427c0,
m=0x6125538ff88, va=81801216)
at ../../../amd64/amd64/pmap.c:1604
#9 0x80414c4f in pmap_enter (pmap=0xff01428427c0, va=81801216,
m=0xff01773daf60, prot=7 '\a',
wired=0) at ../../../amd64/amd64/pmap.c:2134
#10 0x803ea248 in vm_fault (map=0xff0142842660, vaddr=81801216,
fault_type=2 '\002', fault_flags=8)
at ../../../vm/vm_fault.c:907
#11 0x8041e557 in trap_pfault (frame=0xd6154c40, usermode=1) at
../../../amd64/amd64/trap.c:557
#12 0x8041eae3 in trap (frame=
{tf_rdi = 81801216, tf_rsi = 0, tf_rdx = 0, tf_rcx = 482816, tf_r8 =
Re: Analysis of disk file block with ZFS checksum error
On Fri, 2008-02-08 at 17:15 -0700, Joe Peterson wrote: Chris Dillon wrote: That is a chunk of a Mozilla Mork-format database. Perhaps the Firefox URL history or address book from Thunderbird. Interesting (thanks to all who recognized Mork). I do use Firefox and Thunderbird, so it's feasible, but how the heck would a piece of one of those files find its way into 1/2 of a ZFS block in one of my mp3 files? I wonder if it could have been done on write when the file was copied to the ZFS pool (maybe some write-caching issue?), but I thought ZFS would have verified the block after write. It seems unlikely that it would get changed later - I never rewrote that file after the original copy... Are the datestamps (Thu Jan 24 23:20:58 2008) found within the corrupt block before or after the datestamp of the file it was found within? i.e. was the corrupt block on the disk before or after the mp3 was written there? You could possibly confirm this by grepping for that datestamp in the files in your home directory, and with the aid of http://developer.mozilla.org/en/docs/Mork_Structure#Rows, try to establish exactly what the datestamp means (ie was it the time you visited a URL, etc). Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. In the meantime, following an off-list advice, I've used truss(1). I've got now nice truss.out files for two machines (same release): mine which is good and the other machine (in fact a desktop as well) which has the bug. The trouble is that I'm unable to interpret the difference. For example: Every line in the bad truss.out file is prefixed with ``2682: ''. Perhaps a line number? But of which file ? Couldn't find anything within the sources of truss or mkfontscale. No reply yet from the maintainer for mkfontscale [EMAIL PROTECTED] First, I'm replying for convenience to two off-list remarks: I've created 4 truss.out files, 2 on the bad box, 2 on the good one, using the following 2 commands (under root in /usr/local/lib/X11/fonts): truss -o truss.out mkfontdir misc/ truss -fae -o truss-fae.out mkfontdir misc/ After renaming I've got: truss.bad, truss.good, truss-fae.bad, truss-fae.good truss-fae.bad is the _only_ file all lines of which are prefixed with ``2682: ''. All lines of all other files don't have such a prefix. I cannot check for the time being whether this corresponds to a pid. The bad box is at the other end of the town. Second, is there nobody (more competent than me) out there who would accept receiving and looking into e.g. truss-fae.bad.bz2 (12kB) and truss-fae.good.bz2 (18kB) ? You know I'm just asking for the very very obvious thing which should take not more than 5 minutes for an experienced person. Thank you in advance. Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error
On Mon, Feb 11, 2008 at 10:37:02AM +0100, Harald Weis wrote: On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: This is the message (without the stars) I get on a laptop after a fresh install of FreeBSD 6.2-RELEASE i386 (previously 6.0). Searching the archives, I found two reasons which do not apply for me: 1. xorg-fonts-miscbitmaps-7.2 is properly installed 2. the same is true for font-alias-1.0.1 A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. If font-misc-misc and font-cursor-misc are installed, I would do the following: 1. Check /usr/local/lib/X11/fonts/misc directory to see if there are font files there. In my case, that is where the fonts from package font-misc-misc and font-cursor-misc got installed. (pkg_info -L font-misc-misc-1.0.0 would tell you where the fonts got installed.) 2. Check the xorg.conf (/etc/X11/xorg.conf for me) to see if you have a section similar to the following: Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection If the line 'FontPath /usr/local/lib/X11/fonts/misc/' does not exist, you could get the fixed font error. snip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Notice!!! From Yahoo Window Live Awards Centre.
Yahoo Window Live Awards Centre 124 Stockport Road, Longsight, Manchester M60 2DB United Kingdom. Tel: +447045736125,+447024093946. Dear Prize Winner, This is to inform you that you have won a prize money of (Two Hundred Fifty Thousand) Great Britain Pounds (GBP.250,000.00) for the month of February,2008 Prize promotion which is organized by (YAHOO AWARDS WINDOWS LIVE). (YAHOO) collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Four people are selected monthly to benefit from this promotion and you are one of the Selected Winners. ** PAYMENT OF PRIZE** Winners shall be paid in accordance with their Settlement Centers.Yahoo Prize Award must be claimed not later than (10 days)from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed. Stated below are your identification numbers: BATCH NUMBER: MFI/06/APA-43658 REFERENCE NUMBER: 2007234522 PIN:1207 You are requested to contact our co-ordinator in Manchester and send your winning identification numbers to him: Co-ordinator's Name: Mr. Brad Richards E-Mail:[EMAIL PROTECTED] You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you. (1)Full name(2)Country... (3)Contact Address(4)Telephone Number (5)fax Number..(6)Marital Status.. (7)Occupation.(8)Sex. (9)Date of Birth/Age .(10)Identity card(carte identite) Yours in service, Mrs. Grace Sanders * WARNING! WARNING!! WARNING!!!. You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims.Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount of ext2fs volume stuck in D+ state (disk uninterruptible wait)
Joe Peterson wrote: I just tried (under FreeBSD 7.0-RC1) to mount an ext2fs volume - I've mounted it before with no trouble on this same FreeBSD version. This time, mount appeared to hang. I noticed that I can see the contents of the volume under the mount point, so the mount seemed to work, but the process is stuff. ps shows: root 1307 0.0 0.0 3156 792 p6 D+5:21PM 0:00.00 mount /mnt/linux-home The ps man page says that D means: Marks a process in disk (or other short term, uninterruptible) wait. Is there any way I can investigate what is going on? I cannot umount (device busy) or break out of the mount command... http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Asus m2a-vm hdmi
FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD This is completely off topic, but which BIOS are you using ? I bought one of these today and it refuses to boot BSD at all from an IDE drive or a USB drive. The only thing which boots is the CD - all others complain that they do not know which drive they are booting from. Am trying to upgrade the BIOS to see if this fixes it, but any further info would be greatkly apprceiated! cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
mount of ext2fs volume stuck in D+ state (disk uninterruptible wait)
I just tried (under FreeBSD 7.0-RC1) to mount an ext2fs volume - I've mounted it before with no trouble on this same FreeBSD version. This time, mount appeared to hang. I noticed that I can see the contents of the volume under the mount point, so the mount seemed to work, but the process is stuff. ps shows: root 1307 0.0 0.0 3156 792 p6 D+5:21PM 0:00.00 mount /mnt/linux-home The ps man page says that D means: Marks a process in disk (or other short term, uninterruptible) wait. Is there any way I can investigate what is going on? I cannot umount (device busy) or break out of the mount command... Thanks, Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Notice!!! From Yahoo Window Live Awards Centre.
Yahoo Window Live Awards Centre 124 Stockport Road, Longsight, Manchester M60 2DB United Kingdom. Tel: +447045736125,+447024093946. Dear Prize Winner, This is to inform you that you have won a prize money of (Two Hundred Fifty Thousand) Great Britain Pounds (GBP.250,000.00) for the month of February,2008 Prize promotion which is organized by (YAHOO AWARDS WINDOWS LIVE). (YAHOO) collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Four people are selected monthly to benefit from this promotion and you are one of the Selected Winners. ** PAYMENT OF PRIZE** Winners shall be paid in accordance with their Settlement Centers.Yahoo Prize Award must be claimed not later than (10 days)from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed. Stated below are your identification numbers: BATCH NUMBER: MFI/06/APA-43658 REFERENCE NUMBER: 2007234522 PIN:1207 You are requested to contact our co-ordinator in Manchester and send your winning identification numbers to him: Co-ordinator's Name: Mr. Brad Richards E-Mail:[EMAIL PROTECTED] You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you. (1)Full name(2)Country... (3)Contact Address(4)Telephone Number (5)fax Number..(6)Marital Status.. (7)Occupation.(8)Sex. (9)Date of Birth/Age .(10)Identity card(carte identite) Yours in service, Mrs. Grace Sanders * WARNING! WARNING!! WARNING!!!. You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims.Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0: TIMEOUT - WRITE_DMA type errors with 7.0-RC1
On Mon, 11 Feb 2008 13:00:57 +0100 [EMAIL PROTECTED] (Remco van Bekkum) wrote: here? It's on an amd64, Asus m2a-vm with ati xp600, AMD BE-2350 CPU, 2GB 800MHz RAM. FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD Phenom 9500 and 4GB RAM[1]. Different disk, though. The (single) disk drive has worked without problems so far. I'm using standard ufs2 filesystems on that disk. I'm running RELENG_7: [EMAIL PROTECTED] uname -a FreeBSD kg-vm.kg4.no 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #6: Sat Jan 26 20:58:51 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] atacontrol list ATA channel 0: Master: acd0 Optiarc DVD RW AD-5170A/1.12 ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 SAMSUNG HD501LJ/CR100-12 Serial ATA II Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: no device present Slave: no device present References: 1) http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0: TIMEOUT - WRITE_DMA type errors with 7.0-RC1
On Mon, Feb 11, 2008 at 01:00:57PM +0100, Remco van Bekkum wrote: On Fri, Jan 25, 2008 at 04:38:46PM -0800, Jeremy Chadwick wrote: Joe, I wanted to send you a note about something that I'm still in the process of dealing with. The timing couldn't be more ironic. I decided it would be worthwhile to migrate from my two-disk ZFS stripe with a non-ZFS disk for nightly backups, to to a RAIDZ pool of all 3 disks combined (since they're all the same size). I had another terminal with gstat -I500ms running in it, so I could see overall I/O. All was going well until about the 81GB mark of the copy. gstat started showing 0KB in/out on all the drives, and the rsync was stalled. ^Z did nothing, which is usually a bad sign. :-) I ssh'd in and did a dmesg (summarised): ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951071 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951327 ad6: FAILURE - WRITE_DMA timed out LBA=13951071 ad6: FAILURE - WRITE_DMA timed out LBA=13951327 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951583 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951839 ad6: FAILURE - WRITE_DMA timed out LBA=13951583 ad6: FAILURE - WRITE_DMA timed out LBA=13951839 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13952095 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13952351 g_vfs_done():ad6s1d[WRITE(offset=7142916096, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143047168, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143178240, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143309312, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143440384, length=131072)]error = 5 It appears my /dev/ad6 (a Seagate -- more irony) must have some bad blocks. Actually, after letting things go for a while, I realised the box just locked up. Probably kernel panic'd due to the I/O problem. I'll have to poke at SMART stats later to see what showed up. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hi all, After having replaced my first SATA disk with one of the same type, having still the same errors, I replaced this 1TB drive with 4x500GB Hitachi P7K500 in raidz. It worked fine for a week, but yesterday I cvsupped and rebuild world. This afternoon everything is breaking down again with the same errors: Feb 11 12:34:09 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:13 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:17 xaero kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Feb 11 12:34:21 xaero kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: FAILURE - WRITE_DMA48 timed out LBA=298014274 Feb 11 12:34:29 xaero kernel: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:33 xaero kernel: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:37 xaero kernel: ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Feb 11 12:34:41 xaero kernel: ad8: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Feb 11 12:34:45 xaero kernel: ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly Feb 11 12:34:45 xaero kernel: ad8: FAILURE - WRITE_DMA48 timed out LBA=298013590 So of 6 new disk I have 4 with the same errors. It would be quite safe then to not blame the disks imho. I've tested the second drive in another machine, but still got these timeout errors. What's wrong here? It's on an amd64, Asus m2a-vm with ati xp600, AMD BE-2350 CPU, 2GB 800MHz RAM. Regards, Remco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe,
[releng_7 tinderbox] failure on ia64/ia64
TB --- 2008-02-11 08:46:52 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 08:46:52 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2008-02-11 08:46:53 - cleaning the object tree TB --- 2008-02-11 08:46:56 - cvsupping the source tree TB --- 2008-02-11 08:46:56 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2008-02-11 08:47:04 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 08:47:04 - cd /src TB --- 2008-02-11 08:47:04 - /usr/bin/make -B buildworld World build started on Mon Feb 11 08:47:05 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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 09:27:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 09:27:06 - ERROR: failed to build world TB --- 2008-02-11 09:27:06 - tinderbox aborted TB --- 2055.01 user 222.84 system 2413.59 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]
[releng_7 tinderbox] failure on i386/pc98
TB --- 2008-02-11 08:25:33 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 08:25:33 - starting RELENG_7 tinderbox run for i386/pc98 TB --- 2008-02-11 08:25:33 - cleaning the object tree TB --- 2008-02-11 08:25:50 - cvsupping the source tree TB --- 2008-02-11 08:25:50 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/pc98/supfile TB --- 2008-02-11 08:25:58 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 08:25:58 - cd /src TB --- 2008-02-11 08:25:58 - /usr/bin/make -B buildworld World build started on Mon Feb 11 08:25:58 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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 09:00:01 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 09:00:01 - ERROR: failed to build world TB --- 2008-02-11 09:00:01 - tinderbox aborted TB --- 1677.30 user 227.11 system 2067.48 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]
[releng_7 tinderbox] failure on i386/i386
TB --- 2008-02-11 08:10:55 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 08:10:55 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2008-02-11 08:10:55 - cleaning the object tree TB --- 2008-02-11 08:11:18 - cvsupping the source tree TB --- 2008-02-11 08:11:18 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/i386/supfile TB --- 2008-02-11 08:11:26 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 08:11:26 - cd /src TB --- 2008-02-11 08:11:26 - /usr/bin/make -B buildworld World build started on Mon Feb 11 08:11: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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 08:46:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 08:46:52 - ERROR: failed to build world TB --- 2008-02-11 08:46:52 - tinderbox aborted TB --- 1679.28 user 218.31 system 2156.87 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: mount of ext2fs volume stuck in D+ state (disk uninterruptible wait)
New information: it looks as though this ext2fs was already mounted when the mount was attempted. I have reproduced the issue by simply trying to mount the ext2fs volume more than once. Given this, I'd expect the mount to return an already mounted error rather than hanging, so this is perhaps a straightforward bug. -Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount of ext2fs volume stuck in D+ state (disk uninterruptible wait)
Kris Kennaway wrote: Joe Peterson wrote: I just tried (under FreeBSD 7.0-RC1) to mount an ext2fs volume - I've mounted it before with no trouble on this same FreeBSD version. This time, mount appeared to hang. I noticed that I can see the contents of the volume under the mount point, so the mount seemed to work, but the process is stuff. ps shows: root 1307 0.0 0.0 3156 792 p6 D+5:21PM 0:00.00 mount /mnt/linux-home The ps man page says that D means: Marks a process in disk (or other short term, uninterruptible) wait. Is there any way I can investigate what is going on? I cannot umount (device busy) or break out of the mount command... http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html But unfortunately I do not have KDB and DDB compiled into the kernel. And, obviously, if I reboot, I will lose this opportunity. I suspect this to be an intermittent thing. Is there anything I can extract while the system is running that would be useful? Thanks, Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Asus m2a-vm hdmi
On Tue, 12 Feb 2008 00:40:44 + Pete French [EMAIL PROTECTED] wrote: FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD This is completely off topic, but which BIOS are you using ? I bought I'm currently using the 1604 bios. When I bought it, the folks at the store flashed it to bios 1603 (minimum needed for Phenom support). More info on the board overview page[1] one of these today and it refuses to boot BSD at all from an IDE drive or a USB drive. I haven't tried with an IDE drive, and I can't remember if I tried with a USB stick. trying to upgrade the BIOS to see if this fixes it, but any further info would be greatkly apprceiated! References: 1) http://tingox.googlepages.com/asus_m2a-vm_hdmi -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0: TIMEOUT - WRITE_DMA type errors with 7.0-RC1
On Fri, Jan 25, 2008 at 04:38:46PM -0800, Jeremy Chadwick wrote: Joe, I wanted to send you a note about something that I'm still in the process of dealing with. The timing couldn't be more ironic. I decided it would be worthwhile to migrate from my two-disk ZFS stripe with a non-ZFS disk for nightly backups, to to a RAIDZ pool of all 3 disks combined (since they're all the same size). I had another terminal with gstat -I500ms running in it, so I could see overall I/O. All was going well until about the 81GB mark of the copy. gstat started showing 0KB in/out on all the drives, and the rsync was stalled. ^Z did nothing, which is usually a bad sign. :-) I ssh'd in and did a dmesg (summarised): ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951071 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951327 ad6: FAILURE - WRITE_DMA timed out LBA=13951071 ad6: FAILURE - WRITE_DMA timed out LBA=13951327 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951583 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13951839 ad6: FAILURE - WRITE_DMA timed out LBA=13951583 ad6: FAILURE - WRITE_DMA timed out LBA=13951839 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13952095 ad6: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=13952351 g_vfs_done():ad6s1d[WRITE(offset=7142916096, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143047168, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143178240, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143309312, length=131072)]error = 5 g_vfs_done():ad6s1d[WRITE(offset=7143440384, length=131072)]error = 5 It appears my /dev/ad6 (a Seagate -- more irony) must have some bad blocks. Actually, after letting things go for a while, I realised the box just locked up. Probably kernel panic'd due to the I/O problem. I'll have to poke at SMART stats later to see what showed up. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hi all, After having replaced my first SATA disk with one of the same type, having still the same errors, I replaced this 1TB drive with 4x500GB Hitachi P7K500 in raidz. It worked fine for a week, but yesterday I cvsupped and rebuild world. This afternoon everything is breaking down again with the same errors: Feb 11 12:34:09 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:13 xaero kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:17 xaero kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Feb 11 12:34:21 xaero kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly Feb 11 12:34:25 xaero kernel: ad6: FAILURE - WRITE_DMA48 timed out LBA=298014274 Feb 11 12:34:29 xaero kernel: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:33 xaero kernel: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Feb 11 12:34:37 xaero kernel: ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Feb 11 12:34:41 xaero kernel: ad8: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Feb 11 12:34:45 xaero kernel: ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly Feb 11 12:34:45 xaero kernel: ad8: FAILURE - WRITE_DMA48 timed out LBA=298013590 So of 6 new disk I have 4 with the same errors. It would be quite safe then to not blame the disks imho. I've tested the second drive in another machine, but still got these timeout errors. What's wrong here? It's on an amd64, Asus m2a-vm with ati xp600, AMD BE-2350 CPU, 2GB 800MHz RAM. Regards, Remco ___ 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-02-11 07:31:31 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 07:31:31 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-02-11 07:31:32 - cleaning the object tree TB --- 2008-02-11 07:31:55 - cvsupping the source tree TB --- 2008-02-11 07:31:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-02-11 07:32:02 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 07:32:02 - cd /src TB --- 2008-02-11 07:32:02 - /usr/bin/make -B buildworld World build started on Mon Feb 11 07:32:05 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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 08:10:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 08:10:55 - ERROR: failed to build world TB --- 2008-02-11 08:10:55 - tinderbox aborted TB --- 1726.49 user 227.31 system 2363.60 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]
minimal gmirror commands on lifecd 7.0 RC2 amd64
Hello all I always use the live cd to create my gmirrors with the following commands Start live cd -- fixit cdrom Livecd Then chroot /dist mount -t devfs devfs /dev gmirror load gmirror label -v -b round-robin gm0 /dev/ad0 But on the amd64 live cd I get the following error gmirror unknown command : label Usage :gmirror help gmirror list gmirror status gmirror load gmirror unload it looks like I miss a lot of gmirror options. I reported this on the list earlier with RC1 I now use my 7.0 Beta3 livecd that has all the commands. Someone also (don't know who anymore ) told me to create a link but I could not figure out how, and the person also told me that he thought it was already fixed. Regards, Johan Hendriks ___ 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-02-11 09:00:01 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 09:00:01 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2008-02-11 09:00:01 - cleaning the object tree TB --- 2008-02-11 09:00:10 - cvsupping the source tree TB --- 2008-02-11 09:00:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2008-02-11 09:00:17 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 09:00:17 - cd /src TB --- 2008-02-11 09:00:17 - /usr/bin/make -B buildworld World build started on Mon Feb 11 09:00: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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 09:34:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 09:34:50 - ERROR: failed to build world TB --- 2008-02-11 09:34:50 - tinderbox aborted TB --- 1720.11 user 214.64 system 2089.00 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: X.org: Fatal server error
On Sun, Feb 10, 2008 at 06:13:33PM -0800, Joseph Olatt wrote: On Thu, Feb 07, 2008 at 01:44:03PM +0100, Harald Weis wrote: This is the message (without the stars) I get on a laptop after a fresh install of FreeBSD 6.2-RELEASE i386 (previously 6.0). Searching the archives, I found two reasons which do not apply for me: 1. xorg-fonts-miscbitmaps-7.2 is properly installed 2. the same is true for font-alias-1.0.1 A good reason in my case seems to be: all fonts.dir files are empty. Running ``mkfontdir [-e encodings/] misc/'' creates always an empty fonts.dir file, but with the '-e' option a correct encodings.dir file. Conclusion: mkfontdir appears to be broken, or rather mkfontscale as the former is just a single-line shell script. I would check and see if you have the following packages installed: 1. font-misc-misc 2. font-cursor-misc They are installed alright, like all other packages containing the pattern ``font'' in their name. In the meantime, following an off-list advice, I've used truss(1). I've got now nice truss.out files for two machines (same release): mine which is good and the other machine (in fact a desktop as well) which has the bug. The trouble is that I'm unable to interpret the difference. For example: Every line in the bad truss.out file is prefixed with ``2682: ''. Perhaps a line number? But of which file ? Couldn't find anything within the sources of truss or mkfontscale. No reply yet from the maintainer for mkfontscale [EMAIL PROTECTED] Thanks for any help, Harald -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 ___ 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-02-11 09:27:06 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 09:27:06 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-02-11 09:27:06 - cleaning the object tree TB --- 2008-02-11 09:27:15 - cvsupping the source tree TB --- 2008-02-11 09:27:15 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2008-02-11 09:27:21 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 09:27:21 - cd /src TB --- 2008-02-11 09:27:21 - /usr/bin/make -B buildworld World build started on Mon Feb 11 09:27:22 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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 09:58:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 09:58:48 - ERROR: failed to build world TB --- 2008-02-11 09:58:48 - tinderbox aborted TB --- 1598.00 user 211.59 system 1901.81 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: [releng_7 tinderbox] failure on i386/i386
Fixed! On Mon, February 11, 2008 9:46 am, FreeBSD Tinderbox wrote: TB --- 2008-02-11 08:10:55 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-11 08:10:55 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2008-02-11 08:10:55 - cleaning the object tree TB --- 2008-02-11 08:11:18 - cvsupping the source tree TB --- 2008-02-11 08:11:18 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/i386/supfile TB --- 2008-02-11 08:11:26 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-11 08:11:26 - cd /src TB --- 2008-02-11 08:11:26 - /usr/bin/make -B buildworld World build started on Mon Feb 11 08:11: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 stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] building profiled archive library ranlib libarchive_p.a gzip -cn /src/lib/libarchive/archive_entry.3 archive_entry.3.gz gzip -cn /src/lib/libarchive/archive_read.3 archive_read.3.gz gzip -cn /src/lib/libarchive/archive_util.3 archive_util.3.gz gzip -cn /src/lib/libarchive/archive_write.3 archive_write.3.gz gzip -cn /src/lib/libarchive/archive_write_disk.3 archive_write_disk.3.gz make: don't know how to make cpio.5. Stop *** Error code 2 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-11 08:46:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-11 08:46:52 - ERROR: failed to build world TB --- 2008-02-11 08:46:52 - tinderbox aborted TB --- 1679.28 user 218.31 system 2156.87 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-i386.full ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-i386 To unsubscribe, send any mail to [EMAIL PROTECTED] -- /\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
