Re: can't jump to superuser after buildwerld
On 19/04/07, KAYVEN RIESE [EMAIL PROTECTED] wrote: how in the werld did i manage to remove myself from wheel. i just ran mergemaster -p Given that you means user account it's fairly easy: mergemaster collects all the status of all system and configuration files and compares them with the fresh files. These new files don't know about your user, in fact they don't know about anything. Their contents is the same as files from a fresh install. When running mergemaster you can choose to leave the current file intact, which would keep all your changes, but might miss some of the new stuff that should have been introduced. Another idea would be to install the new file, which would of course overwrite your settings. Maybe this is what happened. If you noticed that you can't do either of these two options, but that you have to merge both files, you can do so, too. In this case removing yourself from wheel is also possible. In the beginning I found it difficult to identify both files correctly. For example the pathes where the files are located can be confused easily. You have to keep in mind that the productive files where copied to /var/tmproot, and that ./etc is actually the brand new file. is there any documentation for that command that would explain the complex nonsense .. Maybe a mergemaster in depth kind of manual would be a good idea for all who are unfamiliar with mergemaster, diff and friends. well.. maybe i just freeked out. still.. i followed instructions.. granted somebody told me a different procedure (that i posted and was editited out from below) and it made mergemaster -p act in a way that i didn't feel prepared for. right now.. as i explained in the other posting, i didn't really follow all the instructions on the makewerld page given below.. but i am a bit afraid to just jump in the middle somewhere.. hrm.. i guess starting from the beginning might be right but.. If you're able to move all the data to another machine it's probably the best solution. After you did the install and configured the machine you can be sure that everything is up and running again. ooo.. i am getting that stomache ache agin. btw.. i dropped to single user mode, vi'ed /etc/group according to the instruction and i am now able to jump to root again. thx a bunch for that! [snip] BTW: Please don't top post. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2-RELEASE does not use second CPU?
Hello! On the Pentium-D box, kernel detects both CPUs, but it seems like scheduler use only one. (from dmesg) Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 19 00:19:54 MSD 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D 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) D CPU 2.80GHz (2808.41-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf64 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe49dSSE3,RSVD2,MON,DS_CPL,EST,CNTX-ID,CX16,b14,b15 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Logical CPUs per core: 2 real memory = 1046757376 (998 MB) avail memory = 1015095296 (968 MB) ACPI APIC Table: INTEL DG965SS FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 SMP: AP CPU #1 Launched! (from top) last pid: 12408; load averages: 4.99, 4.91, 4.08up 0+01:08:02 19:26:23 265 processes: 8 running, 256 sleeping, 1 zombie CPU states: 35.0% user, 0.0% nice, 14.1% system, 0.9% interrupt, 50.0% idle Mem: 267M Active, 503M Inact, 171M Wired, 29M Cache, 109M Buf, 1636K Free Swap: 2006M Total, 2006M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 1399125 1 1090 4684K 2808K RUN0 11:20 18.85% qmgr 1819300 1 40 33552K 30824K select 0 8:58 13.57% perl5.8.8 1821300 1 40 33364K 30644K select 0 9:15 6.05% perl5.8.8 12398125 1 40 3588K 2524K select 0 0:00 2.00% cleanup 1394 root1 1040 3444K 1596K RUN0 1:58 1.66% master 10601125 1 970 3580K 1728K select 0 0:18 0.83% trivial-rewri 10051125 1 970 4536K 2688K RUN0 0:13 0.63% scache All processes runs on CPU0, and I did not see less than 50% idle cpu. What can be wrong? Alex. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-RELEASE does not use second CPU?
Hi, Alex Povolotsky wrote: Hello! On the Pentium-D box, kernel detects both CPUs, but it seems like scheduler use only one. (from dmesg) Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 19 00:19:54 MSD 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D 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) D CPU 2.80GHz (2808.41-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf64 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe49dSSE3,RSVD2,MON,DS_CPL,EST,CNTX-ID,CX16,b14,b15 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Logical CPUs per core: 2 real memory = 1046757376 (998 MB) avail memory = 1015095296 (968 MB) ACPI APIC Table: INTEL DG965SS FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 Are you sure it is second CPU ? :) May be it is single processor with HT? SMP: AP CPU #1 Launched! (from top) last pid: 12408; load averages: 4.99, 4.91, 4.08up 0+01:08:02 19:26:23 265 processes: 8 running, 256 sleeping, 1 zombie CPU states: 35.0% user, 0.0% nice, 14.1% system, 0.9% interrupt, 50.0% idle Mem: 267M Active, 503M Inact, 171M Wired, 29M Cache, 109M Buf, 1636K Free Swap: 2006M Total, 2006M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 1399125 1 1090 4684K 2808K RUN0 11:20 18.85% qmgr 1819300 1 40 33552K 30824K select 0 8:58 13.57% perl5.8.8 1821300 1 40 33364K 30644K select 0 9:15 6.05% perl5.8.8 12398125 1 40 3588K 2524K select 0 0:00 2.00% cleanup 1394 root1 1040 3444K 1596K RUN0 1:58 1.66% master 10601125 1 970 3580K 1728K select 0 0:18 0.83% trivial-rewri 10051125 1 970 4536K 2688K RUN0 0:13 0.63% scache All processes runs on CPU0, and I did not see less than 50% idle cpu. What can be wrong? Alex. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make buildworld fails on one box
Hello! My attempt to make buildworld on freshly cvsupped 6.2-RELEASEp3 fails strangely. AWK=awk sh /usr/src/lib/libncurses/../../contrib/ncurses/include/MKncurses_def.sh /usr/src/lib/libncurses/../../contrib/ncurses/include/ncurses_defs ncurses_def.h sed /usr/src/lib/libncurses/../../contrib/ncurses/include/MKterm.h.awk.in MKterm.h.awk -e /@NCURSES_MAJOR@/s%%5% -e /@NCURSES_MINOR@/s%%2% -e /@NCURSES_CONST@/s%%const% -e /@NCURSES_XNAMES@/s%%1% awk -f MKterm.h.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps term.h.new sh /usr/src/lib/libncurses/../../contrib/ncurses/include/edit_cfg.sh /usr/src/lib/libncurses/ncurses_cfg.h term.h.new ** edit: HAVE_TCGETATTR 1 ** edit: HAVE_TERMIOS_H 1 ** edit: HAVE_TERMIO_H 0 ** edit: BROKEN_LINKER 0 mv -f term.h.new term.h cc -o make_keys -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lc *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 Stop in /usr/src. *** Error code 1 I observe this problem on one box only; attempt to nfs-mount source tree from working box leads to the same fail. Re-installation of the world did not cause any changes. Alex. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Asus DVD Writer not recognized
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Nuennerich wrote: Hi list, we've got a Asus DRW-1814BLT here which is not recognized by 6.2. I can't find it neither in dmesg nor in atacontrol. The Bios detects it fine and even Linux. This writer is SATA: http://www.asus.com/products4.aspx?modelmenu=2model=1488l1=6l2=35l3=0 The device is connected to: atapci0: JMicron JMB363 SATA300 controller port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f mem 0xfbefe000-0xfbef irq 40 at device 0.0 on pci2 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc400 atapci0: [MPSAFE] atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xfbefe000 atapci0: AHCI Version 01.00 controller with 2 ports detected Or: atapci1: VIA 8237A SATA150 controller port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f,0xb000-0xb0ff irq 21 at device 15.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xb400 atapci1: [MPSAFE] atapci1: Reserved 0x100 bytes for rid 0x24 type 4 at atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xbc00 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xb880 Neither works. Any ideas what to try? Thanks in advance Marius SATA ATAPI devices are currently unsupported by FreeBSD. Regards, Niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGJyReHNAJ/fLbfrkRAicfAKCsaTerkSZyItX3WcflIPPWoyjEuQCfWRUs kVjKdF/5gjhKBB0GsHS/9Eg= =nxbW -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail Resource Limits for 6.x ...
On Wed, 18 Apr 2007, Miroslav Lachman wrote: Marc G. Fournier wrote: Is anyone looking into merging in the patch available at: http://www.ualberta.ca/~cdjones/cdjones_jail_soc2006.patch That provides both memory and cpu limits on a jail? It appears to be against REL_6 from last years SOC ... Is anyone using it in production anywhere? I got same question + one more. Why there are SoC projects, which never come in to src tree or wider publicity? Sometimes it is like wasting of human resources... ;( Summer of Code projects are student projects funded by Google for a summer. Many of the project proposals are significantly more ambitious than a single summer, and take much longer to come to fruition -- often being merged in the winter, the next spring, or even a summer or two later. Not all projects are even intended to lead directly to commitable code: some are effectively RD projects to understand new areas of work. However, we have a fairly high success rate in getting things committed within a year or so: remember, things need time for testing, review, revision, etc, and this requires a significant effort by the students, their mentors, and the project as a whole over a very extended period of time. Per the recent announcement on the freebsd-announce mailing list and on the web site, you can learn more about the SoC projects by visiting the FreeBSD web page, and also the FreeBSD wiki which contains more detailed information on each project: http://www.freebsd.org/projects/summerofcode-2007.html http://wiki.freebsd.org//SummerOfCode2007 The 2007 SoC season has barely begun, as the official start date is at the end of May. However, many students have started, and already put information about their projects online. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't jump to superuser after buildwerld
On Thursday 19 April 2007 03:31, you wrote: how in the werld did i manage to remove myself from wheel. i just ran mergemaster -p is there any documentation for that command that would explain the complex nonsense .. mergemaster -p can't mess with your system- it preserves necessary changes for system- you messed up your upgrade with plain mergemaster command when you dumbly pressed i -install key without looking what changes is made to base system configuration files. Next time read what mergemaster says to you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_nullfs in jail?
Hi Guys, Is there any way to have mount_nullfs working inside the jail? Please gime me any idea on that topic. Thank you. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_nullfs in jail?
On 4/19/07, Anton - Valqk [EMAIL PROTECTED] wrote: Hi Guys, Is there any way to have mount_nullfs working inside the jail? I mount nullfs from the host, that's how I share the ports directory across jails. Please gime me any idea on that topic. Thank you. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
iscsi and geom mirror - stupid idea or not ?
what would happen if I made a machine which contained a mirrored geom pair consiting of one local driive and one drive accessed via iscsi on a remote machine ? would this work ? what I am considering is two such machines, geographicly distinct. one is a 'master' and boots off the mirrored drive, the other is a slave and has a separate boot drive which just rngs FreeBSD to make the drive inside it into an iscsi target for the first machine. The idea here is if the first machine is catastrphicly killed (like building falls down on it or something) then the second one can be rebooted from the internal drive, and will hence become the first one. It's basically a way of making a standby machine in case of disaster. I havent really looked at iSCSI until recently, and this is just one of the ideas I came up with looking at the possibilities. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iscsi and geom mirror - stupid idea or not ?
Hi, On Thu, Apr 19, 2007 at 10:48:16AM +0100, Pete French wrote: what would happen if I made a machine which contained a mirrored geom pair consiting of one local driive and one drive accessed via iscsi on a remote machine ? would this work ? what I am considering is two such machines, geographicly distinct. one is a 'master' and boots off the mirrored drive, the other is a slave and has a separate boot drive which just rngs FreeBSD to make the drive inside it into an iscsi target for the first machine. The idea here is if the first machine is catastrphicly killed (like building falls down on it or something) then the second one can be rebooted from the internal drive, and will hence become the first one. It's basically a way of making a standby machine in case of disaster. I havent really looked at iSCSI until recently, and this is just one of the ideas I came up with looking at the possibilities. You could also go and use ggate for that. And seems to get more and more common to work like that, although probably most setups I heard of probably don't have a long distance link between them. There are a few things you should consider: First, you have to make absolutely sure, that for example the mirrored disk is not attached if after a crash the original master comes back and the slave took over. If this happens you're likely to damage something really bad. Second is, something like this gives you mirrored data with practically no gap to the original disk. The price you have to pay: This does not help you against logical errors (a filesystem damage will be replicated just fine...). A setup like this does not serve as a backup. Third is, you'll have to fsck everything, so this defines your minimum service outage. I'm not sure, if I'd trust background fsck here, also bg fsck is a big performance penalty, which might or might not be a problem for your setup. A replication (like rsync, ssync or similar) sure has the drawback of the replication gap for the data. Also you cannot just take over the IP of the NFS server, but have to remount everything. But you have fsck time, lower chance damage due to logical error and the nice effect, that you could do your backups from the replicated data, not affecting your live system. But have to deal with lost data from probably several hours or how to replicate changed data after recovery. - Olli -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpNflENhJcFd.pgp Description: PGP signature
Re: Jail Resource Limits for 6.x ...
Robert Watson wrote: On Wed, 18 Apr 2007, Miroslav Lachman wrote: Marc G. Fournier wrote: Is anyone looking into merging in the patch available at: http://www.ualberta.ca/~cdjones/cdjones_jail_soc2006.patch That provides both memory and cpu limits on a jail? It appears to be against REL_6 from last years SOC ... Is anyone using it in production anywhere? I got same question + one more. Why there are SoC projects, which never come in to src tree or wider publicity? Sometimes it is like wasting of human resources... ;( Summer of Code projects are student projects funded by Google for a summer. Many of the project proposals are significantly more ambitious than a single summer, and take much longer to come to fruition -- often being merged in the winter, the next spring, or even a summer or two later. Not all projects are even intended to lead directly to commitable code: some are effectively RD projects to understand new areas of work. However, we have a fairly high success rate in getting things committed within a year or so: remember, things need time for testing, review, revision, etc, and this requires a significant effort by the students, their mentors, and the project as a whole over a very extended period of time. Per the recent announcement on the freebsd-announce mailing list and on the web site, you can learn more about the SoC projects by visiting the FreeBSD web page, and also the FreeBSD wiki which contains more detailed information on each project: http://www.freebsd.org/projects/summerofcode-2007.html http://wiki.freebsd.org//SummerOfCode2007 The 2007 SoC season has barely begun, as the official start date is at the end of May. However, many students have started, and already put information about their projects online. I understand. But from my point of view - there is lack of PR (Public Relations) for those projects and patches. Somebody did patch with new / experimental features and almost nobody knows about it. And even if somebody find the patch / webpage about some project, there is date from last summer so project seems dead without future or patch can't be applied to current sources. So I thing FreeBSD needs some central place for these informations - maybe called Experimental Area with informations + patches + up-to-date statuses, list of testers, list of bugs / successes, list of untested things etc. So one can easily find / try / test / fix / help with any of useful things around FreeBSD not included in STABLE or CURRENT. I thing some Wiki engine + mailinglist + reminders would be useful for this. Any thoughts? At this time, some things are on SoC pages, some on personal pages of FreeBSD developers and some on the other hard to find places. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Fatal trap 12: page fault while in kernel mode
On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote:
Hello all,
We're running into regular panics on our webserver after upgrading
from 4.x to 6.2-stable:
Hi Again,
The panics keep happening, so I'm trying alternate kernel setups. This is a
trace of a panic on a default SMP kernel with debugging symbols.
I'm At a loss on how to progress at this point, perhaps someone can help me
please?
System info:
uname -a reports FreeBSD webserver 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #0:
Thu Apr 19 11:37:34 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SMP
i386
Backtrace:
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
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 i386-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x34
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06bdefa
stack pointer = 0x28:0xeb9cf938
frame pointer = 0x28:0xeb9cf944
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 = 13577 (perl5.8.8)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 1h37m29s
Dumping 3070 MB (2 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 3071MB (786016 pages) 3055 3039 3023 3007 2991 2975 2959 2943
2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719 2703
2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479 2463
2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223
2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983
1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743
1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503
1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263
1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 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 591 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 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc067550a in boot (howto=260) at ../../../kern/kern_shutdown.c:409
#2 0xc0675831 in panic (fmt=0xc08e46dd %s)
at ../../../kern/kern_shutdown.c:565
#3 0xc088e29c in trap_fatal (frame=0xeb9cf8f8, eva=52)
at ../../../i386/i386/trap.c:837
#4 0xc088dfdb in trap_pfault (frame=0xeb9cf8f8, usermode=0, eva=52)
at ../../../i386/i386/trap.c:745
#5 0xc088dc15 in trap (frame=
{tf_fs = 8, tf_es = -606142424, tf_ds = -926089176, tf_edi =
#-605280928, tf_esi = -605280928, tf_ebp = -342034108, tf_isp = -342034140,
tf_ebx = -605280928, tf_edx = 4, tf_ecx = -926082048, tf_eax = 0, tf_trapno
#= 12, tf_err = 0, tf_eip = -1066672390, tf_cs = 32, tf_eflags = 66050,
tf_esp = -605280928, tf_ss = -605280928}) at ../../../i386/i386/trap.c:435
#6 0xc0879d4a in calltrap () at ../../../i386/i386/exception.s:139
#7 0xc06bdefa in vfs_vmio_release (bp=0xdbec2560) at atomic.h:146
#8 0xc06be728 in getnewbuf (slpflag=0, slptimeo=0, size=6585, maxsize=8192)
at ../../../kern/vfs_bio.c:1779
#9 0xc06bfccc in getblk (vp=0xca2cfdd0, blkno=8438, size=6585, slpflag=0,
slptimeo=0, flags=0) at ../../../kern/vfs_bio.c:2497
#10 0xc075ad41 in nfs_getcacheblk (vp=0xca2cfdd0, bn=8438, size=6585,
td=0xc8cd1c00) at ../../../nfsclient/nfs_bio.c:1261
#11 0xc075a978 in nfs_write (ap=0x0) at ../../../nfsclient/nfs_bio.c:1069
#12 0xc089fde6 in VOP_WRITE_APV (vop=0xc0984440, a=0xeb9cfbec)
at vnode_if.c:698
#13 0xc06dbb26 in vn_write (fp=0xc8940e10, uio=0xeb9cfcbc,
active_cred=0xc89ee880, flags=0, td=0xc8cd1c00) at vnode_if.h:372
#14 0xc0698f63 in dofilewrite (td=0xc8cd1c00, fd=5, fp=0xc8940e10,
auio=0xeb9cfcbc, offset=Unhandled dwarf expression opcode 0x93
) at file.h:252
#15 0xc0698e07 in kern_writev (td=0xc8cd1c00, fd=5, auio=0xeb9cfcbc)
at ../../../kern/sys_generic.c:402
#16 0xc0698d2d in write (td=0xc8cd1c00, uap=0xc8cd1c00)
at ../../../kern/sys_generic.c:326
#17 0xc088e5e3 in syscall (frame=
{tf_fs = 136970299, tf_es = 673775675, tf_ds = -1078001605, tf_edi =
#137019392, tf_esi = 673803768, tf_ebp = -1077942616, tf_isp = -342033052,
tf_ebx = 673713536, tf_edx = 4096, tf_ecx = 0, tf_eax = 4, tf_trapno = 0,
#tf_err
Re: Fatal trap 12: page fault while in kernel mode
On 19/04/07, Kai [EMAIL PROTECTED] wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi Again, The panics keep happening, so I'm trying alternate kernel setups. This is a trace of a panic on a default SMP kernel with debugging symbols. I'm At a loss on how to progress at this point, perhaps someone can help me please? [snip] Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06bdefa stack pointer = 0x28:0xeb9cf938 frame pointer = 0x28:0xeb9cf944 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 = 13577 (perl5.8.8) trap number = 12 panic: page fault Is this perl derived from ports? And if so, did you rebuild it after you upgraded to 6.2? Or is maybe FreeBSD 4.x binary compatibility missing from your kernel? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_nullfs in jail?
On Apr 19, 2007, at 5:17 AM, Vlad GALU wrote: Is there any way to have mount_nullfs working inside the jail? I mount nullfs from the host, that's how I share the ports directory across jails. /me too. easiest way is to create a file /etc/fstab.jailname with the mount in it, like this: /n/yertle1/sources/ports /u/data/jails/lsfe/usr/ports nullfs rw 0 0 which is how I map my ports tree mounted on the jail host via NFS from the main server into the /usr/ports directory of the jail named 'lsfe' in this case. I'm not sure if default jails read the /etc/fstab.jailname files, but ezjail's startup does, and makes for easy jail management.
Re: iscsi and geom mirror - stupid idea or not ?
On 4/19/07, Pete French [EMAIL PROTECTED] wrote: what would happen if I made a machine which contained a mirrored geom pair consiting of one local driive and one drive accessed via iscsi on a remote machine ? would this work ? what I am considering is two such machines, geographicly distinct. one is a 'master' and boots off the mirrored drive, the other is a slave and has a separate boot drive which just rngs FreeBSD to make the drive inside it into an iscsi target for the first machine. The idea here is if the first machine is catastrphicly killed (like building falls down on it or something) then the second one can be rebooted from the internal drive, and will hence become the first one. It's basically a way of making a standby machine in case of disaster. I havent really looked at iSCSI until recently, and this is just one of the ideas I came up with looking at the possibilities. iSCSI is good for many things - although i would not suggest this setup. it sounds like you are trying to use the mirror/iSCSI architecture as some sort of backup scheme. it may make more sense to capture snapshot's of your data and mirror that off to secondary storage. along these same lines is a common iSCSI implementation of having a dedicated piece of hardware that manages RAID, grouping of LUN's and other management functions. this allows you physically, and logically, implement some sort of redundancy/backup schema independent of the iSCSI consumer (i.e. the OS that will be mounting the iSCSI volume). let the machine hosting the iSCSI storage do it's job, and let the client do it's job - it does not make sense to try to mix these too. so the short answer is i would not try to mix iSCSI volumes with local volumes via a software mirror. a properly implemented iSCSI solution can easily account for DR situations, and using filesystem snapshotting will make this task easier as well. -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
On Thursday 19 April 2007, Michael Nottebrock wrote: On Wednesday, 18. April 2007, Beni wrote: Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. I won't pretend to be a true kernel hacker, but I've got a passing acquaintance with ata(4) from hacking in it (and a weirdly patched -STABLE because of that) and k3b experience. I'll see what -- assuming I can trigger this -- I can do. -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot signature.asc Description: This is a digitally signed message part.
Re: make buildworld fails on one box
On Thu, Apr 19, 2007 at 12:09:34PM +0400, Alex Povolotsky wrote: Hello! My attempt to make buildworld on freshly cvsupped 6.2-RELEASEp3 fails strangely. AWK=awk sh /usr/src/lib/libncurses/../../contrib/ncurses/include/MKncurses_def.sh /usr/src/lib/libncurses/../../contrib/ncurses/include/ncurses_defs ncurses_def.h sed /usr/src/lib/libncurses/../../contrib/ncurses/include/MKterm.h.awk.in MKterm.h.awk -e /@NCURSES_MAJOR@/s%%5% -e /@NCURSES_MINOR@/s%%2% -e /@NCURSES_CONST@/s%%const% -e /@NCURSES_XNAMES@/s%%1% awk -f MKterm.h.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps term.h.new sh /usr/src/lib/libncurses/../../contrib/ncurses/include/edit_cfg.sh /usr/src/lib/libncurses/ncurses_cfg.h term.h.new ** edit: HAVE_TCGETATTR 1 ** edit: HAVE_TERMIOS_H 1 ** edit: HAVE_TERMIO_H 0 ** edit: BROKEN_LINKER 0 mv -f term.h.new term.h cc -o make_keys -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lc *** Error code 1 Check system time clock stability (e.g run ntpd). Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Thu Apr 19 21:04:38 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP-DATACENTER ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2398.85-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 Logical CPUs per core: 2 real memory = 2146631680 (2047 MB) avail memory = 2087084032 (1990 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 nvidia0: GeForce 6600 GT mem 0xfa00-0xfaff,0xd000-0xdfff,0xf900-0xf9ff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xd480-0xd49f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801EB (ICH5) 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 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xd800-0xd81f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801EB (ICH5) 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 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xd880-0xd89f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xdc00-0xdc1f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xf8fffc00-0xf8ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: PCI-PCI bridge at device 9.0 on pci2 pci3: PCI bus on pcib3 mlx0: Mylex version 4 RAID interface mem 0xefffe000-0xefff irq 21 at device 9.1 on pci2 mlx0: [GIANT-LOCKED] mlx0: DAC960PRL, 1 channel, firmware 4.08-0-37, 4MB RAM mlxd0: Mylex System Drive on mlx0 mlxd0: 105006MB (215052288 sectors) RAID 0 (online) xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xec00-0xec7f mem 0xfbfefc00-0xfbfefc7f irq 23 at device 11.0 on pci2 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:50:da:d8:1b:ec pcm0: Creative EMU10K1 port 0xe800-0xe81f irq 21 at device 13.0 on pci2 pcm0: SigmaTel STAC9708/11 AC97 Codec isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 atapci1: Intel ICH5 SATA150 controller port 0xd400-0xd407,0xd080-0xd083,0xd000-0xd007,0xcc00-0xcc03,0xc880-0xc88f irq 18 at device 31.2 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 ichsmb0: Intel 82801EB (ICH5) SMBus controller port 0x400-0x41f irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: System Management Bus on ichsmb0 smb0: SMBus generic I/O on smbus0 acpi_button0: Power Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 speaker0: PC speaker port 0x61 on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 on
PR kern/109152 -- RocketPort panics
We have 3 of the 32 port Comtrol PCI cards, the original 5v only cards, not the newer universal PCI cards, and we are trying to upgrade the system with all these serial ports from FreeBSD 4.8 (ya, kinda old) to FreeBSD 6.2. And we are running into what seems like a common problem with these cards: panics about non-busy devices: panic: device_unbusy: called for non-busy device rp0 The PR kern/109152 addresses this issue, and the patch from Craig Leres added to the PR on Tue, 13 Mar 2007 19:27:01 -0700 solves the problems for me. (I was experiencing the problems with HylaFAX, but it seems easy to reproduce.) Can this patch be applied to RELENG_6? I've also tried the patch from John Baldwin posed to freebsd-hackers in http://groups.google.com/group/mailing.freebsd.hackers/browse_frm/thread/883da63a8c62854d that generates a rp_open_count for each device with out any change in the behavior, I would continue to panic the system by sending a FAX. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
snipping dmesg ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default ad0: 114473MB WDC WD1200JB-00GVA0 08.02D08 at ata0-master UDMA100 acd0: DVDR HL-DT-ST DVDRAM GSA-4163B/A104 at ata1-master UDMA33 ad4: 152627MB WDC WD1600JD-00GBB0 02.05D02 at ata2-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 ^ ??? i assume you are asking what those errors mean you most likely have a bad cdrom in there, or the drive has an error. try a different disk, and if that fails try another drive. -p -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpxWXd0rPazw.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
On Thursday 19 April 2007 12:12, Michael Nottebrock wrote: On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, FWIW: I've been running with a kernel from Jan 22 with no problem. I built and installed a new kernel/world today and can't run k3b as described above. I've since reverted to my old kernel and everything's fine again. - Rich -- Richard Kuhns Wintek Corporation E-mail: [EMAIL PROTECTED] 427 N 6th Street Tel: +1 (765) 742-8428 Lafayette, IN 47901-1126 Fax: +1 (765) 742-0646 United States of America ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
On Thursday 19 April 2007 22:47:08 Richard Kuhns wrote: On Thursday 19 April 2007 12:12, Michael Nottebrock wrote: On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, FWIW: I've been running with a kernel from Jan 22 with no problem. I built and installed a new kernel/world today and can't run k3b as described above. I've since reverted to my old kernel and everything's fine again. - Rich I haven't used k3b for a while but I do have problems with kscd, kaudiocreator, and amarok CD playing. I'm running -stable from Feb 26 and latest kde and CD contents are only properly seen if you first insert the cd, then wait, and then choose the app from the hal menu (which takes several seconds to pop up). But even then ripping seems to deadlock, it just hangs and does nothing after you queue and start, and kscd/amarok don't play anything. Amarok merely shows the titles briefly. Both with self-made CDs and official audio CDs. It's possible that my DVD player/recorder is just dying but I'm afraid we're having a more general regression here. Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ---BeginMessage--- Michael Nottebrock wrote: I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just FYI. Subject: Re: [kde-freebsd] problem hal - k3b ? From: Michael Nottebrock [EMAIL PROTECTED] Date: Thu, 19 Apr 2007 18:12:46 +0200 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Beni [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ---End Message--- pgpMnseiiYv2q.pgp Description: PGP signature
Re: can't jump to superuser after buildwerld
my settings got trampled. it's weird. i had my prompt set up to have pwd in the path and i customized the root prompt to do a similar dingy followed by a # instead of a % and it was like really weird how su - still got my root prompt back. that's how it werks now..i have been too lazy to fix my user settings.. On Thu, 19 Apr 2007, Christian Walther wrote: On 19/04/07, KAYVEN RIESE [EMAIL PROTECTED] wrote: how in the werld did i manage to remove myself from wheel. i just ran mergemaster -p Given that you means user account it's fairly easy: mergemaster collects all the status of all system and configuration files and compares them with the fresh files. These new files don't know about your user, in fact they don't know about anything. Their contents is the same as files from a fresh install. When running mergemaster you can choose to leave the current file intact, which would keep all your changes, but might miss some of the new stuff that should have been introduced. Another idea would be to install the new file, which would of course overwrite your settings. Maybe this is what happened. If you noticed that you can't do either of these two options, but that you have to merge both files, you can do so, too. In this case removing yourself from wheel is also possible. In the beginning I found it difficult to identify both files correctly. For example the pathes where the files are located can be confused easily. You have to keep in mind that the productive files where copied to /var/tmproot, and that ./etc is actually the brand new file. is there any documentation for that command that would explain the complex nonsense .. Maybe a mergemaster in depth kind of manual would be a good idea for all who are unfamiliar with mergemaster, diff and friends. well.. maybe i just freeked out. still.. i followed instructions.. granted somebody told me a different procedure (that i posted and was editited out from below) and it made mergemaster -p act in a way that i didn't feel prepared for. right now.. as i explained in the other posting, i didn't really follow all the instructions on the makewerld page given below.. but i am a bit afraid to just jump in the middle somewhere.. hrm.. i guess starting from the beginning might be right but.. If you're able to move all the data to another machine it's probably the best solution. After you did the install and configured the machine you can be sure that everything is up and running again. ooo.. i am getting that stomache ache agin. btw.. i dropped to single user mode, vi'ed /etc/group according to the instruction and i am now able to jump to root again. thx a bunch for that! [snip] BTW: Please don't top post. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
Michael Nottebrock wrote: On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. My problem is the same as Beni's. Splash screen appears and hangs. I have to press power button to turn off and on my laptop. Didn't try ctrl+alt+del though. Ganbold Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
Michael Nottebrock wrote: I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. I see. I know I have updated my system last Saturday (14th April 2007) and I think I updated both hal and kdelibs ports. I have atapicam enabled in kernel. Let me double check it this weekend and I will let you know. thanks, Ganbold Subject: Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? From: Joe Marcus Clarke [EMAIL PROTECTED] Date: Thu, 19 Apr 2007 12:49:26 -0400 To: Michael Nottebrock [EMAIL PROTECTED] To: Michael Nottebrock [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Michael Nottebrock wrote: I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just FYI. Subject: Re: [kde-freebsd] problem hal - k3b ? From: Michael Nottebrock [EMAIL PROTECTED] Date: Thu, 19 Apr 2007 18:12:46 +0200 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Beni [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
On Thu, Apr 19, 2007 at 12:37:08PM -0700, pete wright wrote: ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default ad0: 114473MB WDC WD1200JB-00GVA0 08.02D08 at ata0-master UDMA100 acd0: DVDR HL-DT-ST DVDRAM GSA-4163B/A104 at ata1-master UDMA33 ad4: 152627MB WDC WD1600JD-00GBB0 02.05D02 at ata2-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 ^ ??? i assume you are asking what those errors mean you most likely have a bad cdrom in there, or the drive has an error. try a different disk, and if that fails try another drive. Are you sure the ATAPI command used at that time is attempting to read disc information and not, say, try to get drive capabilities? I'm lead to believe that the DVD drive he has doesn't support a particular ATAPI function (long reads comes to mind). ASC 0x24 ASCQ 0x00 is Illegal field in CDB for most ATAPI operatons... -- | 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]
HEADS UP: Recompile milters after sendmail 8.14 upgrade
sendmail has been updated from version 8.13.8 to 8.14.1 in the HEAD and RELENG_[456] branches. This upgrade includes a new libmilter library which requires all dynamically linked milters to be recompiled (no source code changes are required). Unfortunately, this problem (the need to recompile filters) was found after the MFC. The release engineering team has asked for this notice instead of doing a full backout of sendmail 8.14 in the RELENG_[456] branches. I'm sorry for the adverse effects from the change and will be more careful with future sendmail commits. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
