Re: buildworld failed
-On [20010209 05:35], John Indra ([EMAIL PROTECTED]) wrote: Dunno whether this happens only to me, but in my machine, latest -CURRENT buildworld target failed with this message: === share/numericdef make: don't know how to make nl_NL.ISO_8859-1.out. Stop Should be fixed. Apologies. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Fallen into ever-mourn, with these wings so torn, after your day my dawn... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current buildworld broken
-On [20010207 11:00], Harti Brandt ([EMAIL PROTECTED]) wrote: With a freshly CVSuped current I get: === usr.bin/ncal cc -O -pipe -Wall -Wmissing-prototypes -fstrict-prototypes -ansi -pedantic -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/ncal/ncal.c /usr/src/usr.bin/ncal/ncal.c: In function `printeaster': /usr/src/usr.bin/ncal/ncal.c:390: warning: unknown conversion type character `F' in format You are probably caught in between commits. Always cvsup after such problems, after you waited an hour or so for your favourite cvsup mirror up pick up any further commits, and then try again, and THEN report things like this. Saves traffic. :) -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Fallen into ever-mourn, with these wings so torn, after your day my dawn... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed: LyX 1.1.5.2 dumping core
-On [20010127 22:30], Patrick Hartling ([EMAIL PROTECTED]) wrote: Making a symlink from /usr/lib/libc.so.5 to /usr/lib/libc.so.3 seems to have fixed my LyX problems. I'm guessing libc.so.5 and libc.so.3 were causing conflicts, especially with the recent changes to libc, but I'm no expert. Whatever the case, I can get back to work on my thesis now. :) Have you tried recompiling LyX with the new libc? That should normally clear any problems. I suspect from what you said above, that when you do ldd `which lyx` it will report lyx being linked against libc.so.3, but for some reason is trying to use the higher version libc. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failed with named-xfer.
Konnichiwa wa MATSUDA-san, -On [20010129 07:40], Munehiro Matsuda ([EMAIL PROTECTED]) wrote: Buildworld failed with following error: cc -O -pipe -I/usr/src/libexec/named-xfer/../../contrib/bind/port/freebsd/include -I/usr/src/libexec/named-xfer/../../contrib/bind/bin/named -I/usr/src/libexec/named-xfer/../../contrib/bind/include -I.-o named-xfer named-xfer.o db_glue.o ns_glue.o tmp_version.o /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a named-xfer.o: In function `main': named-xfer.o(.text+0xe4a): undefined reference to `isc_movefile' named-xfer.o(.text+0xede): undefined reference to `isc_movefile' named-xfer.o(.text+0xf54): undefined reference to `isc_movefile' /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a(logging.o)(.text+0x98): undefined reference to `isc_movefile' /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a(logging.o)(.text+0xca): undefined reference to `isc_movefile' *** Error code 1 Thanks, applied the patch. The BIND import was kind of rushed due to the security stuff being released today. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/usr.sbin/named Makefile
-On [20010129 07:25], [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: In article [EMAIL PROTECTED] you wrote: It seems to me that the same kind of libisc dependency must be provided for 'libexec/named-xfer', because it now stops buildworld with the 'isc_movefile' unresolved message. Correct, fixed. At the same time it seems to me that now 'lib/libbind' contains many files/functions which are also present in the newly created 'lib/libisc'. Is it right ? Could be. I have to look at that. I focused on getting the import done very quickly due to some security stuff coming out later. 3- and 4-STABLE will follow sooner than normal after I've done my make worlds and other tests on them today/tomorrow. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lastest kernel from cvs ( sh exists with signal 8 )
-On [20010122 07:55], Peter Wemm ([EMAIL PROTECTED]) wrote: The Hermit Hacker wrote: d'oh, did it backwards again ... buildkernel then buildworld ... let me go back and rebuild kernel and see if that is all it was in my case ... Argh! I wish people would stop using buildkernel! :-( It calls config(8) in such a way that buries the warning messages where people dont see. config(8) is meant to be used interactively :-( Yeah well, buildkernel was advocated as the next best thing to sliced bread. Myself, I'll stick to the ``old way''. Never failed me thus far. At least, nothing a good rm -rf compile/KERNEL cannot solve. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Killing me is not enough to make me go away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup'ing repo cvs-checkout'ing sources makes cvs complain...
-On [20010121 23:10], Salvo Bartolotta ([EMAIL PROTECTED]) wrote: Following Warner's directions in internat.txt, I removed the crypto-related stuff, and issued the following explicit command: One question: why? crypto is now folded into src-all -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Killing me is not enough to make me go away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lots of page faults
-On [20010120 08:40], Alex Kapranoff ([EMAIL PROTECTED]) wrote: Additional symptoms include very high system CPU state percentage and a lot of page faults. A page fault is not a bad thing, it is merely an indicator from the CPU to the kernel that the page you want to refer to, the next page of executable data of the application you are running, is not in memory [yet]. The CPU causes a page fault and the kernel pages in the part(s) of the application to memory and then resumes operation, now being able to refer to the appropriate page. [snip] Is my RAM rotting or what? Given you get coredumps on cc, as and such, it could be. But not always, I have had current give me coredumps in cc and as before but that was due to problems in the binaries themselves after some changes in the world. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Killing me is not enough to make me go away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unicode support in cd9660 [patch for review]
-On [20001227 20:05], Andrej Cernov ([EMAIL PROTECTED]) wrote: Yes, it is a per-FS hack, but until iconv or something like will be integrated, some hack needed just to read CDs selling at nearby shop. As far as I know, Boris Popov was working on iconv() support. I see he is cc:'d, so I happily await his ideas/statusupdate. Furthermore, even though I only use special characters for Dutch, German, Norwegian, Swedish, Danish, Finnish and Icelandic, I feel that _if_ we start to add Unicode support we do it right from the beginning. Unicode was meant to solve the native character set problem for all languages [as far as my knowledge stretches] and should not be a working, but ugly, hack which only allows per-language solutions. If you want to have people to have the ability to mount their CD's with Russian characters by all means provide the patch on your website. I am by all means not an l10n or i18n hacker nor wizard, otherwise I would've dedicated my ample time working on this and solve it once and for all with all other interested parties. In short: please do it right from the start. Thanks, -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm breaking you down... I'm taking you down... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Foundation: Examples of FreeBSD as teaching aid/research plat
-On [20001109 21:30], Justin T. Gibbs ([EMAIL PROTECTED]) wrote: If possible, please include a contact name, email, or phone number so we can ask additional questions if necessary. Do foreign educational institutes count as well for this purpose? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Knowledge is power... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Foundation: Examples of FreeBSD as teaching aid/research plat
-On [20001110 20:20], Justin T. Gibbs ([EMAIL PROTECTED]) wrote: Do foreign educational institutes count as well for this purpose? Yes. I think the Dutch University of Twente uses FreeBSD a lot for their curriculi. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl And your ways appear a total lack of Faith... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tar : needs some attention?
-On [20001106 17:10], John W. De Boskey ([EMAIL PROTECTED]) wrote: tar: cdrom/disc2/dev/acd0t39: minor number too large; not dumped Is this the expected behaviour, or is it worth digging into tar and making some fixes? I am hoping to update tar soon these weeks. Don't know yet if that's expected behaviour. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl In my mind nothing makes sense... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABI is broken??
-On [20001102 05:30], Garrett Wollman ([EMAIL PROTECTED]) wrote: On Wed, 1 Nov 2000 14:43:55 -0800, "David O'Brien" [EMAIL PROTECTED] said: Any reason to not get [libc ABI changes] in -current now and make the bump? Mostly because they're too small to be worth the pain. I'm waiting for something more significant that I can piggy-back on. Which of course has the implicit risk that if something big doesn't show up these fixes will be added only at the nearing of 5.0-RELEASE and thus with less shake-down time. I also gather it has to do with the Austin project Garrett? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl In my mind nothing makes sense... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is this a typo?
-On [20001026 23:30], Julian Elischer ([EMAIL PROTECTED]) wrote: in the bus_alloc_resource() man page it states: dev is the device that requests ownership of the resource. Before allo- cation, the device is owned by the parent bus. should that be: "Before allocation, the resource is owned by the parent bus." ? I will fix the manpage later on today, your requested change is not entirely accurate, yet. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Judge not, that ye be not judged... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem in fetch
-On [20001027 10:00], Dag-Erling Smorgrav ([EMAIL PROTECTED]) wrote:
Jeroen Ruigrok van der Werven [EMAIL PROTECTED] writes:
[Making sure Dag-Erling gets the mail]
-On [20001026 18:45], Andrea Campi ([EMAIL PROTECTED]) wrote:
When trying to install ports, very often I find everything freezes just
after fetch completes. If I hit ^C and type "make install" again, the
tarball is there, that's why I say that fetch is already done.
If I hit ^T, I see fetch sitting in sbwait, the time not increasing.
Just a note, I got the same thing under 4-STABLE with the latest
sources.
Weird. I develop libfetch on -STABLE these days, and have no such problems.
I guess it is some sites again. I don't have the problem with every
http or ftp site.
Does this only happen with FTP documnts, BTW? I recently changed the
FTP code so it waits for the status code to arrive on the control
socket when the transfer is complete (so that connection caching will
work). That may be the problem; try setting FETCH_CMD to 'fetch -T60'
and see if it times out after sixty seconds.
Might be, cannot be sure 100% right now, from memory, I'd say yes.
The vim6 port for one is problematic.
I'll get a debug/verbose dump for you tomorrow DES.
Thanks!
No problem.
Everybody else, if you don't know how to do this:
# cd /usr/src/lib/libfetch make clean make obj \
make depend -DDEBUG make -DDEBUG make install
then run fetch with -vv, and you'll get a full transcript of the
session (note that this can be quite a lot when fetching a
chunk-encoded HTTP document)
[10:28] [root@lucifer] (7) {1} # FETCH_CMD='fetch -vv -T60' make fetch
vim-6.0j-rt.tar.gz doesn't seem to exist in /usr/ports/distfiles/vim.
Attempting to fetch from
ftp://ftp.prz.tu-berlin.de/pub/unix/editors/vim/unreleased/unix/.
looking up ftp.prz.tu-berlin.de
connecting to ftp.prz.tu-berlin.de:21
fetch: vim-6.0j-rt.tar.gz: File unavailable (e.g., file not found, no
access)
Attempting to fetch from ftp://ftp.vim.org/pub/vim/unreleased/unix/.
looking up ftp.vim.org
connecting to ftp.vim.org:21
setting passive mode
opening data connection
initiating transfer
fetch: remote: 1266150 / 972245439
Receiving vim-6.0j-rt.tar.gz (1266150 bytes): 100%
1266150 bytes transferred in 2.3 seconds (540.03 kBps)
/usr/ports/editors/vim6
[10:29] [root@lucifer] (8) {0} #
It timed out after the 60 seconds had passed.
DEBUG output:
[10:43] [root@lucifer] (30) {0} # FETCH_CMD='fetch -vv -T60' make fetch
vim-6.0j-src.tar.gz doesn't seem to exist in
/usr/ports/distfiles/vim.
Attempting to fetch from
ftp://ftp.prz.tu-berlin.de/pub/unix/editors/vim/unreleased/unix/.
scheme: [ftp]
user: []
password: []
host: [ftp.prz.tu-berlin.de]
port: [0]
document: [/pub/unix/editors/vim/unreleased/unix/vim-6.0j-src.tar.gz]
--- ftp.prz.tu-berlin.de:21
looking up ftp.prz.tu-berlin.de
connecting to ftp.prz.tu-berlin.de:21
220 ProFTPD 1.2.0pre8 Server (ftp.prz.tu-berlin.de) [kumpel.prz.tu-berlin.de]
USER ftp
331 Anonymous login ok, send your complete e-mail address as password.
PASS [EMAIL PROTECTED]
230 Anonymous access granted, restrictions apply.
TYPE I
200 Type set to I.
CWD /pub/unix/editors/vim/unreleased/unix
550 /pub/unix/editors/vim/unreleased/unix: No such file or directory
fetch: vim-6.0j-src.tar.gz: File unavailable (e.g., file not found, no access)
Attempting to fetch from ftp://ftp.vim.org/pub/vim/unreleased/unix/.
scheme: [ftp]
user: []
password: []
host: [ftp.vim.org]
port: [0]
document: [/pub/vim/unreleased/unix/vim-6.0j-src.tar.gz]
--- ftp.vim.org:21
looking up ftp.vim.org
connecting to ftp.vim.org:21
220-Welcome to the FTP archive of The Netherlands Unix Users Group, NLUUG.
220-
220-This server is located in The Netherlands, Europe.
220-If you are abroad, please find an ftp site near you.
220-Most information on this site is mirrored.
220-
220-Information about your login and any transfers you do are logged.
220-If you don't like this, disconnect now.
220-
220-There are currently 153 users logged in (maximum 175).
220-
220-You may login as "ftp" or "anonymous".
220-
220 ftp.nluug.nl FTP server (Version wu-2.6.0(1) Fri Jun 23 09:17:44 EDT 2000)
ready.
USER ftp
331 Guest login ok, send your complete e-mail address as password.
PASS [EMAIL PROTECTED]
230 Guest login ok, access restrictions apply.
TYPE I
200 Type set to I.
CWD /pub/vim/unreleased/unix
250-Unreleased versions of Vim - Vi IMproved - for Unix et al.
250-
250-The files in this directory contain test versions for Unix systems.
250-Get both the "src" and the "rt" (runtime) archive!
250-These are also used for VMS, BeOS, OS/2, Mac, etc., in combination
250-with the "extra" archive (in ../extra).
250-
250-Ctags is no longer included. See http://ctags.sourceforge.net.
250-A copy of the sources is in the "extra" directory.
250-
250- SIZEFILE CONTENTS
250-
Re: Problem in fetch
[Making sure Dag-Erling gets the mail] -On [20001026 18:45], Andrea Campi ([EMAIL PROTECTED]) wrote: When trying to install ports, very often I find everything freezes just after fetch completes. If I hit ^C and type "make install" again, the tarball is there, that's why I say that fetch is already done. If I hit ^T, I see fetch sitting in sbwait, the time not increasing. Just a note, I got the same thing under 4-STABLE with the latest sources. You can run fetch with more verbosity. See what that does. I'll get a debug/verbose dump for you tomorrow DES. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl There is such a thing as a man being too proud to fight... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: I18N Progress, Plans, and Proposals
-On [20001022 10:55], [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: I seriously advice against directly importing the Citrus code. It is very good work and a lot will be borrowed, but on my latest investigations it also made a lot of unnecessary and gratuitous changes. which part looks gratuitous? could you be more specific? #ifdef's for FreeBSD. rune_t/_rune_t type recasting _COMPAT_RUNE #ifdef's. for example. But of course, these are _my_ investigations, I might have totally missed the point in what they were trying to do there. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl The administration of justice is the firmest pillar of government... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
-On [20001021 20:10], Jordan Hubbard ([EMAIL PROTECTED]) wrote: I wish to update rc.network6 and introduce rc.firewall6. H. I must confess that I see /etc as getting rather cluttered these days. Is there no way to perhaps collapse some of the most related functionality into single files and start passing arguments or something? Just a comment.. The IPv6 systems are so much different in set-up than the IPv4 systems. Collapsing of the functions is not really doable. However, Umemoto-san and me will discuss this, since we [he mostly] have been working on this for the last few months. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I love to doubt as well as know... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: smbus PCI device?
-On [2927 03:10], Archie Cobbs ([EMAIL PROTECTED]) wrote: I'm trying to understand this iic/smbus stuff in order to write a driver for some new hardware. The PCI bus shows this device: found- vendor=0x8086, dev=0x2413, revid=0x02 class=0c-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=b, irq=10 map[20]: type 1, range 32, base fe00, size 4 pciconf -l will probably show the class as 0x0c0500 I guess? The class/sub-class/programming interface (highlighted above) indicates a SMBus device as specified by PCI 2.2. However, I'm not sure what that is. Adding the "smbus" device and friends to the kernel config doesn't cause this device to be detected. You'd think all I needed to do then would be to add the device ID to a list in the smbus driver somewhere, but I can't find that list. Does "smbus_pci.c" not exist yet? Normally, that would be enough yes. I think you want: src/sys/dev/iicbus and src/sys/dev/smbus Of course, you can't download the PCI 2.2 spec without being a "member". Cute eh? Am I going down the right path trying to write a driver for this device? Normally adding the vid/rid combo should at least detect it yes. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: updated OpenSSH pam_ssh, the old bug is back
-On [2916 17:10], Alexander Leidinger ([EMAIL PROTECTED]) wrote: after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf. I fixed this in the old version, but it seems the bug is back. I have a look at it and try to produce a patch again. You mean that bug which you reported and produced a patch and which I subsequently committed? The malloc.conf - AJ resulted coredump one? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: updated OpenSSH pam_ssh, the old bug is back
-On [2918 16:20], Alexander Leidinger ([EMAIL PROTECTED]) wrote: On 18 Sep, Jeroen Ruigrok van der Werven wrote: You mean that bug which you reported and produced a patch and which I subsequently committed? The malloc.conf - AJ resulted coredump one? Initially yes, but at the moment I'm under the impression it's another bug (I don't know where it is and how to fix it), the old one seems to be fixed. Is it a malloc.conf - AJ related bug again? =) Anyway, if you find it, don't hesitate to let me know, so I can apply it. Cheers, -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IDE RAID (HPT-370/Abit KT7-RAID) install questions..
-On [2827 23:05], Soren Schmidt ([EMAIL PROTECTED]) wrote: Well, this wouldn't have happend without Jeroen (asmodai) having good contacts at HighPoint, so I thank him for making this possible. No problem. It's all team work anyways, I couldn't write the driver. ;) Hopefully Highpoint will be so friendly to help me out on this RAID issue. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl You are more than you think, less than you could be... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: Brian, I'm afraid you broke libutil... Every program using libutil now must depend on libcrypt too. -=-=- === libexec/fingerd cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi ngerd.c cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil /usr/obj/src/src/i386/usr/lib/libutil.so: undefined reference to `crypt_set_form at' *** Error code 1 Stop in /src/src/libexec/fingerd. *** Error code 1 I get the same thing, even with Brian's latest commit. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Haste makes waste... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: -=-=- === libexec/fingerd cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi ngerd.c cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil /usr/obj/src/src/i386/usr/lib/libutil.so: undefined reference to `crypt_set_form at' *** Error code 1 This should be fixed after my commit. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Morpheus in my Heart, your sand in my veins... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone have newmidi working?
-On [2819 18:15], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote: Newmidi doesn't seem to work. The oplsbc device handling had to be hacked a bit to support non-PnP SBs, but that's inconsequential. It probes and boots fine. It seems that newmidi is completely disconnected from actually being able to work. Doesn't work here. I could forward you my mail I sent the to the other, mayhaps our problems are quite alike. I haven't gotten any response from the author :-( Does anyone have it working? I don't see how it could with the current state of the code. Same here. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl The spirit indeed is willing, but the flesh is weak... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
-On [2822 08:50], Warner Losh ([EMAIL PROTECTED]) wrote: Actually, the real reason is that MMC drives that mostly support the standard, but do it wrong in ways that are hard to detect. Those are going to be the worst to try to support. There are some drives out there that just hang when you issue them certain MMC commands, as an example. They shouldn't but they do and you have to be careful not to send them these commands. This got parsed by me as: mmc-quirk.h It wouldn't be hard to keep it tracked in a quirk file as per the SCSI disk quirk file. But I am not sure it is elegant. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl There is no joy in smallness. Joy is in the infinite... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
-On [2822 06:25], Kenneth D. Merry ([EMAIL PROTECTED]) wrote: It needs an ATAPI passthrough mechanism to work. (FreeBSD doesn't have one at the moment.) Søren, Matt and me were discussing the ATA/CAM issues so that we might be able to approach ATA through CAM. That would clear a lot. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Another morning, black sunday, coming down again... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: Brian, I'm afraid you broke libutil... Every program using libutil now must depend on libcrypt too. Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I walk, I walk alone, into the promised land... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:55], Ollivier Robert ([EMAIL PROTECTED]) wrote: According to Jeroen Ruigrok van der Werven: Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. It would make even make more sense to convince the other BSD to do the same (haven't checked recently what they do) and do the merge. I very much agree. Would it be sensible for the regular cypherpunks to discuss this with the NetBSD and OpenBSD brothers? Otherwise I would be willing to open this discussion on the appropriate lists. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl The administration of justice is the firmest pillar of government... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure
-On [2723 07:15], John Polstra ([EMAIL PROTECTED]) wrote: Some developers just aren't being careful enough. The biggest problem is they don't restore their systems to a 100% pristine state before they test. Think we could come up with a make cleanworld like target which does just that? 't Would be pretty helpful IMHO. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Truth is always exciting. Speak it, then. Life is boring without it... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Virus alert, was: Re: SCSI Question
-On [2709 22:40], Paul Herman ([EMAIL PROTECTED]) wrote: On Sun, 9 Jul 2000, Jeroen Ruigrok van der Werven wrote: -On [2709 21:20], Leif Neland ([EMAIL PROTECTED]) wrote: These messages are infected with the kak virus. See http://www.cai.com/virusinfo/encyclopedia/descriptions/wscript.htm Am I the only one to NOT see this? Probably not. It wasn't in the "Content-Type: text/plain" part of the attachment, just the "text/html" part. Ah right. Spotted it. Which brings us back to a few good rules: - do NOT post in HTML - do not configure your mailer to mail lame virus warnings back to lists where precedence is set to bulk. Thanks for reminding me of the text/html. I looked there before but failed to spot it. *sigh* -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl ``...by God I *KNOW* what this network is for, and you can't have it.'' -- Russ Albery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weird 4.0-STABLE problem, might be related to 5.0 as well
- do not disable. device npx0at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0at nexus? disable flags 0x20 # Advanced Power Management # Serial (COM) ports device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 # PCI Ethernet NICs. device fxp # Intel EtherExpress PRO/100B (82557, 82558) device miibus # MII bus support device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! #pseudo-device bpf #Berkeley packet filter yright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #3: Fri Jun 2 12:11:21 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/RAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (601.37-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT ,PSE36,MMX,FXSR,XMM real memory = 268423168 (262132K bytes) avail memory = 257359872 (251328K bytes) Preloaded elf kernel "kernel" at 0xc02d9000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: ATI Mach64-GB graphics accelerator at 0.0 irq 11 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 pci0: Intel PIIX4 ATA controller at 4.1 pci0: Intel 82371AB/EB (PIIX4) USB controller at 4.2 chip1: Intel 82371AB Power management controller port 0xe800-0xe80f at device 4 .3 on pci0 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter port 0xb000-0xb0ff mem 0xe100- 0xe1000fff irq 12 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xa800-0xa87f mem 0xe080-0xe0800 07f irq 10 at device 10.0 on pci0 xl0: Ethernet address: 00:01:02:26:fb:54 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: 3Com 3c905B-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xe000-0xe 07f irq 11 at device 12.0 on pci0 xl1: Ethernet address: 00:01:02:28:f7:e3 miibus1: MII bus on xl1 xlphy1: 3Com internal media interface on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST39103LW 0002 Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) As soon as I get these problems again I'll notify you guys. I made sure kernel.debug is ok now [7 MB instead of 1.8 MB]. So this mishap should not occur. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Judge not, that ye be not judged... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current jail panic II
-On [2613 17:08], Bart Thate ([EMAIL PROTECTED]) wrote: prp is 0x0 but is not checked upon. The check if prp ==0 is done 2 lines further on. if (prp == 0 || prp-pr_usrreqs-pru_attach == 0) return (EPROTONOSUPPORT); since both if-s return EPROTONOSUPPORT the fix is to move the prp == 0 if in front of the patches lines. I committed a fix to CURRENT. Can you verify if this stops the panics you're seeing? Thanks, -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Love conquers all... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Newmidi Release Candidate is ready
-On [2611 15:16], Seigo Tanimura ([EMAIL PROTECTED]) wrote: The release candidate of newmidi is finally ready. The patch for -current can be found at: Results [after minor tweaks in the patch]: seq0-63: Midi sequencers. sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 device_add_child_ordered:528: pcm at sbc with order 0 as unit -1 make_device:458: pcm at sbc as unit -1 device_add_child_ordered:528: midi at sbc with order 0 as unit -1 make_device:458: midi at sbc as unit -1 device_add_child_ordered:528: midi at sbc with order 0 as unit -1 make_device:458: midi at sbc as unit -1 pcm0: SB DSP 4.16 on sbc0 pcm: setmap c000, 2000; 0xc7d74000 - c000 pcm: setmap e000, 2000; 0xc7d76000 - e000 midi0: SB Midi Interface on sbc0 midi1: SB OPL FM Synthesizer on sbc0 unknown7: Game at port 0x200-0x207 on isa0 unknown8: WaveTable at port 0x620-0x623 on isa0 unknown9: IDE at port 0x180-0x187,0x316-0x317 irq 15 on isa0 I then MAKEDEV'd snd0 again, so that I got the midi0 and sequencer0 devices, but playmidi doesn't play anything. Going to set more debugging on. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl For dust thou art, and unto dust shalt thou return. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Newmidi Release Candidate is ready
-On [2611 15:16], Seigo Tanimura ([EMAIL PROTECTED]) wrote: The release candidate of newmidi is finally ready. The patch for -current can be found at: URI: http://people.FreeBSD.org/~tanimura/patches/newmidirc.diff.gz I will put this patch into the final test stage of 1 month. The date of merge is hence going to be 11th July 2000. Few nits: mss.c: gusc.h isn't in this file anymore, this causes a reject. Also, NMIDI 0 type of constructs are not needed anymore with 4.0 and higher IIRC. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Laat ons drinken op ons grote ongelijk... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
-On [2608 03:12], Kris Kennaway ([EMAIL PROTECTED]) wrote: Instead of using only alphabetic characters, the patch uses the following character set: 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ which is not believed to cause any problems with shells. The PID is also Some shells parse # as a deletion character if memory serves me right. I think I noticed this behaviour when I started using zsh a few weeks ago after ksh. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl ...fools rush in where Angels fear to tread. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vmware1/linux broken
-On [2603 09:30], Julian Elischer ([EMAIL PROTECTED]) wrote: If you use the linux kernel module, you cannot use the vmware module with it. This has changed sometime in the last month or so. the vmware module cannot find a symbol in the linux module that it needs. The obvious: which symbol? =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Who looks under the surface does so at his own risk... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. I just lack the expertise to find out where it is. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I believe because it is impossible... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote: Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? The /dev/da0s1a would be the correct one to use, example: # DeviceMountpoint FStype Options DumpPass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e /tmpufs rw 2 2 /dev/da0s1g /usrufs rw 2 2 /dev/da0s1f /varufs rw 2 2 /dev/da0s1h /work ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 /dev/fd0/diskette msdos rw,noauto 0 0 -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I walk, I walk alone, into the promised land... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: breakage in mtree?
-On [2513 01:30], Marius Strom ([EMAIL PROTECTED]) wrote: cvsup as of ~20 minutes ago, during a buildworld: -o mtree compare.o crc.o create.o misc.o mtree.o spec.o verify.o setflags.o -lmd create.o: In function `cwalk': create.o(.text+0xcf): undefined reference to `check_excludes' Should be fixed by Garrett Wollman's commit. Please re-cvsup. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Veni, Vidi, Vici... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Abit BP6 - UDMA66 and non IBM disks
-On [2509 11:20], Alan Cox ([EMAIL PROTECTED]) wrote: In summary, same disks, three different controllers, problems only occur with the Highpoint controller. (I believe the Abit BP6 uses the Highpoint controller.) It does. It might be worthwhile to note that there are updates of the BP6 BIOS and the HPT366, but given the knowledge we don't use the BIOS of the HPT366 I don't know how much good that will do aside from a better system BIOS which you also get from the upgrade. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Light, a quark resolution of god... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed driver broken in today's -CURRENT?
-On [2507 14:50], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: It is not dead card, it is broken TCP, see my similar report in -current, I notice it several hours ago right after TCP changes was commited. I assume you mean the NewReno commit submitted by Jayanth? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl And we are drunk with Death... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
-On [2506 21:55], Bruce Evans ([EMAIL PROTECTED]) wrote: On Sat, 6 May 2000, Maxim Sobolev wrote: I've just noticed that "sh MAKEDEV acd1" doesn't produce node for acd1 due to incorrect comparasion in the "while" loop. This affecting both 4.0-STABLE and 5.0-CURRENT. With this message I'm attaching short patch which should solve this little problem. This is the intended behaviour. "sh MAKEDEV acdN" is supposed to create N acd devices, numbered from 0 to N-1. This broken behaviour was introduced for cd*, mcd* and scd* in rev.1.171. It has since spread to acd*. Other types of disks are handled correctly. Bah, bah, bah. I am really starting to wonder about this sunburn thing. Can we settle this once and for all in a slightly sane manner? I committed the change so that MAKEDEV acd1 creates acd1 and not just acd0. I personally think this is more consistent with the wd/sa/da/ad numbering scheme and would propose to fix the other cd* entries likewise. Because otherwise somebody other than me will make the same (commit) mistake x days/weeks/months/years into the future. Opinions? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl In this short time of promise, you're a memory... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel builds fail
-On [2430 15:05], Kent Hauser ([EMAIL PROTECTED]) wrote: Thanks. I can now build the GENERIC kernel. Of course, now my real kernel won't link := chapel-hill# make linking kernel ng_base.o: In function `ng_make_node': ng_base.o(.text+0x54): undefined reference to `linker_search_path' *** Error code 1 I think this is related to Peter's recent changes in the module dependency code. Peter? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel breakage in ng_base.c
-On [2430 16:50], Boris Popov ([EMAIL PROTECTED]) wrote: This patch is not 100% correct. ng_base should make an attempt to load module, not KLD. There was a new module_load() function proposed to inclusion in the API, but for some reason it is not committed yet. When Peter committed this all he had worked a few days untill too early in the morning. It is a lack of sufficient sleep which caught up on him. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic at boot (bus_generic_probe) with 2 printers ENABLED
-On [2430 11:50], Leif Neland ([EMAIL PROTECTED]) wrote: In a freshly cvsup'ed current, I get a panic at boot, if both ports are enabled in userconfig. If only one or the other is enabled, it works. I have narrowed it down to it panics the second time ppbconf calls bus_generic_probe: trap 12: page fault while in kernel mode bus_generic_probe+0x25: cmpl $0xc02a502c,0(%ebx) ebx is 0xe0 How about adding: options BUS_DEBUG to your kernel config file and perhaps even boot verbose and show us the details of /var/log/messages? Thanks, -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ldconfig -m not configuring ?
-On [2429 19:20], Salvo Bartolotta ([EMAIL PROTECTED]) wrote: I issued a "ldconfig -r | grep ld-linux" and, actually, I found [snip] What prevents ldconfig -m /usr/compat/linux/lib from doing its duty ? What am I missing ? I might be wrong, but the native ldconfig has nothing to do with the compat/linux libraries for all I know. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DEVFS - what's happening with it?
-On [2427 07:05], Stephen Hocking-Senior Programmer PGS SPS Perth ([EMAIL PROTECTED]) wrote: Haven't seen any discussion for quite some time. The Linux people seem to be getting into a lather about it as well. Rehashing the issues like device persistence, et cetera. If I recall correctly, Boris Popov is working on that, next to his SMB code. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange phenomen accessing a CDROM contents under linuxerator
-On [2412 01:35], Walter Brameld ([EMAIL PROTECTED]) wrote: I see the same thing on 4.0-STABLE, so far only using linux-netscape. When I go to select a directory for download, or when accessing an HTML file to be opened, certain directories always appear to be missing. Only one that comes to mind at the moment is the ports directory when looking in /usr. Aha, that would account for some of my symlinks to give me not the results I was expecting. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Necessity has no law... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DDB and dumping disk
-On [2329 02:15], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote: On Tue, 28 Mar 2000, Jeroen Ruigrok van der Werven wrote: Did you try "call setdumpdev(0xf00)" with the proper show disk/ yet? I tried: db show disk/ad0s1b 0xc0b65880 bd write dumpdev 0xc0b65880 dumpdev: - 0xc0b65880 bd call setdumpdev(0xc0b65880) Unknown symbol So again, I am probably doing something wrong. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl That's your Destiny, the only chance, take it, take it in your hands... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DDB and dumping disk
-On [2328 12:55], Sheldon Hearn ([EMAIL PROTECTED]) wrote: On Mon, 27 Mar 2000 14:50:12 +0200, Jeroen Ruigrok van der Werven wrote: I wasn't complaining, on the contrary! I was happily surprised it was way faster than the SCSI dump. =) So now the only question is whether our existing bootstrapping infrastructure already has some way to use your ddb magic to set dumpdev. :-) Well, I can set dumpdev in ddb, but the problem is that when I reboot that savecore doesn't detect a dump. If I boot the system completely and manually panic and let it dump savecore will detect the dump and put it in /var/crash. So I wonder what I forgot in DDB. I do: db show disk/ad0s1b 0xc0NN I then use this value to: db write dumpdev 0xc0NN dumpdev = - 0x0cNN I can then dump when typing: db panic But after the reboot savecore doesn't recognise the dump. savecore: no coredump Hope this makes it a bit more clear. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl To desire immortality is to desire the eternal perpetuation of a great mistake... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DDB and dumping disk
-On [2328 13:15], Sheldon Hearn ([EMAIL PROTECTED]) wrote: On Tue, 28 Mar 2000 13:02:06 +0200, Jeroen Ruigrok van der Werven wrote: I can then dump when typing: db panic Damnit. So I've just committed bogus advice in dumpon(8). :-( No not really. Your patch is a step in the right direction. I am currently only trying to figure out why the DDB way doesn't trigger savecore to recognise the dump. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl How are the mighty fallen... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DDB and dumping disk
-On [2328 17:40], Bruce Evans ([EMAIL PROTECTED]) wrote: On Tue, 28 Mar 2000, Sheldon Hearn wrote: Given that the moment at which dumpdev is set seems important, I think it's probably better for me to back these isntructions out of the dumpon(8) manual page and wait for something less tricky. Do you agree? Yes. The man page is also misleading about single user mode. dumpon(8) works fine in single user mode. The problem case is when the system crashes before reaching user mode. Exactly. And that is what I am now slowly trying to work on. Brian's addition of show disk in ddb was one step ahead. Now to get the functionality in one way or the other in either the loader or ddb or another thing. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl That's your Destiny, the only chance, take it, take it in your hands... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DDB and dumping disk
-On [2327 14:40], Soren Schmidt ([EMAIL PROTECTED]) wrote: It seems Jeroen Ruigrok van der Werven wrote: the DDB trick works. And it dumps at PIO mode 4, woot! You have to, there is no garantie that DMA and even less interrupts is working proberly on a potentially hosed machine.. I wasn't complaining, on the contrary! I was happily surprised it was way faster than the SCSI dump. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Necessity is the mother of invention... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
-On [2325 03:05], Brad Knowles ([EMAIL PROTECTED]) wrote: I gotta be doing something stupid here. I haven't been able to access the existing 3.4-STABLE filesystems on this machine since I upgraded it to 4.0-STABLE on a second hard drive, and I likewise can't access the 4.0-STABLE filesystems from 3.4-STABLE. Block/character device collapsing breaking you up now? /dev/ Should only be character devices now. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Like cures like... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 2.2.8 to 4.0 upgrade
-On [2325 16:35], Alexander Langer ([EMAIL PROTECTED]) wrote: Thus spake Maxim Kolinko ([EMAIL PROTECTED]): how to upgrade 2.2.8-STABLE to 4.0-STABLE ? cd /usr/src; make aout-to-elf-build upgrade to RELENG_3 first. Yeah. I recently did a 3.0 - 3.4 upgrade by source. That was paying attention as well. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl I may know many things, I may be ignorant... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP; new options for -current!
-On [2319 21:00], Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED], Peter Wemm writes : If you are using old drivers that haven't been newbusified yet, you will need to add 'options COMPAT_OLDPCI' and/or 'options COMPAT_OLDISA' to your kernel configs and regenerate. Otherwise you will get compile failures. I think this is premature. I tried to newbusify if_mn.c, but after having added about 50 lines of code to replace the current about 10, I gave up. We need a highlevel wrapper for newbus before we should force people to upgrade the old-style drivers. I already addressed that in new-bus and there is some discussion and finding out the best way to do a higher level wrapping for a lot of newbus' stuff. So rest assured, work is underway. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl The mediocre teacher tells, the good teacher explains, the superior teacher demonstrates, the great teacher inspires... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pc98
Just curious, who is or are the current and active maintainers of pc98? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl For dust thou art, and unto dust shalt thou return. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP! old wd driver going away
Yes... That's right. Use ata and related stuff instead. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl In my Dreams, I see you, I can tell you, how I feel... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: isa_compat.h and new lack of wdc...
-On [2314 17:50], Visigoth ([EMAIL PROTECTED]) wrote: The line in /sys/i386/isa/isa_compat.h which calls for the wdc code is still there and causing kernel build problems. Minor issue considering all of the new changes related to that driver ;) Aye, sorry. Got called away to a meeting, grrr... I attached a patch that removes the line ( for convienience ) If I am wrong, go easy ;) just trying to be helpful... Yeah, applied and it should fix what you reported. Thanks, -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl To err is human, to forgive divine... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: oddness in -current
-On [2306 09:25], Garance A Drosihn ([EMAIL PROTECTED]) wrote: At 12:17 AM -0700 3/6/00, Chris Wasser wrote: I was just watching a buildworld happen when I noticed (specifically in gcc, and a few other places) the following warning several times: warning: mktemp() possibly used unsafely; consider using mkstemp() I'm not sure if it's a big deal or not, but in the interests of satisfying my own interests, I thought I would mention it. If this has been covered already in this list, then please disregard. Next time I'll capture the entire build process to a file. This probably has not been discussed a lot on current, but the freebsd-audit group has been trying to track down and change all uses of mktemp which might lead to any kind of security problem. And in this case those are probably warnings issued by programs from the contrib directory. Possible suspects: cvs, groff, etc. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Tel: +31 - (0) 10 - 240 39 70 http://www.via-net-works.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic (pmap)
-On [2223 10:01], Jeroen Ruigrok van der Werven ([EMAIL PROTECTED]) wrote:
And I may welcome panic #6 here.
db trace
pmap_remove_all(5a3e000,c061ab70,0,c0230ac0,d62a2f8c) at
pmap_remove_all+0x40
pmap_page_protect(5a3e000,0) at pmap_page_protect+0xde
vm_pageout_page_stats(0) at vm_pageout_page_stats+0x15e
vm_pageout(0) at vm_pageout+0x1fb
fork_trampoline() at fork_trampoline+0x8
[root@tyr] (1) # cd /var/crash/
/var/crash
[root@tyr] (2) # gdb -k /kernel.debug vmcore.2
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd"...
IdlePTD 2625536
initial pcb at 21c9e0
panicstr: from debugger
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc01cdefc
stack pointer = 0x10:0xd62a2f44
frame pointer = 0x10:0xd62a2f50
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 = 2 (pagedaemon)
interrupt mask = net bio cam
panic: from debugger
panic: from debugger
Uptime: 11h59m1s
amrd0: still open, can't shutdown
dumping to dev #da/0x20001, offset 524312
dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492
491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471
470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450
449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429
428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408
407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387
386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366
365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345
344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324
323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303
302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282
281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 !
265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245
244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224
223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203
202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182
181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161
160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140
139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119
118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97
96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68
67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39
38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10
9 8 7 6 5 4 3 2 1 0
---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:304
304 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:304
#1 0xc0143d61 in panic (fmt=0xc01e27f4 "from debugger")
at ../../kern/kern_shutdown.c:554
#2 0xc01244e1 in db_panic (addr=-1071849732, have_addr=0, count=-1,
modif=0xd62a2db0 "") at ../../ddb/db_command.c:433
#3 0xc0124481 in db_command (last_cmdp=0xc02042fc, cmd_table=0xc020415c,
aux_cmd_tablep=0xc021905c) at ../../ddb/db_command.c:333
#4 0xc0124546 in db_command_loop () at ../../ddb/db_command.c:455
#5 0xc012665f in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#6 0xc01c4ec5 in kdb_trap (type=12, code=0, regs=0xd62a2f04)
at ../../i386/i386/db_interface.c:158
#7 0xc01d0c38 in trap_fatal (frame=0xd62a2f04, eva=0)
at ../../i386/i386/trap.c:919
#8 0xc01d0911 in trap_pfault (frame=0xd62a2f04, usermode=0, eva=0)
at ../../i386/i386/trap.c:817
#9 0xc01d04c3 in trap (frame={tf_fs = -701890544, tf_es = -1071906800,
tf_ds = 16, tf_edi = 0, tf_esi = -1061788720, tf_ebp = -701878448,
tf_isp = -701878480, tf_ebx = -1059687328, tf_edx = 0, tf_ecx = 0,
tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1071849732, tf_cs = 8,
tf_eflags = 66118, tf_esp = 94625792, tf_ss = 0})
at ../../i386/i386/trap.c:423
#10 0xc01cdefc in
Panic (pmap)
And I may welcome panic #6 here. db trace pmap_remove_all(5a3e000,c061ab70,0,c0230ac0,d62a2f8c) at pmap_remove_all+0x40 pmap_page_protect(5a3e000,0) at pmap_page_protect+0xde vm_pageout_page_stats(0) at vm_pageout_page_stats+0x15e vm_pageout(0) at vm_pageout+0x1fb fork_trampoline() at fork_trampoline+0x8 Dumping system to disk, and will put out the gdb bt when it's done doing that. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic #3 (ffs)
*sigh*
I think I am going to give up my job and become a buddhist monk...
start = 0, len = 2646, fs = /news
panic: ffs_alloccg: map corrupted
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
db trace
Debugger(c01e7ee3) at Debugger+0x35
panic(c01f28bf,c01f28a0,0,a56,c1d0d8d4) at panic+0x70
ffs_mapsearch(c1d0d800,ccd49000,5d2a8,1,b) at ffs_mapsearch+0x143
ffs_alloccg(c1da7700,b,5d2a8,400) at ffs_alloccg+0x21a
ffs_hashalloc(c1da7700,b,5d2a8,400,c0194cb8) at ffs_hashalloc+0x23
ffs_alloc(c1da7700,b,5d2a8,400,c1d38280) at ffs_alloc+0xad
ffs_balloc(d8a1ce68,d8a4c200,c1d6a180,3,d8b74ba0) at ffs_balloc+0x456
ffs_write(d8a1cea0,d6299a80,4c,c1d6a180,c0201d00) at ffs_write+0x319
vn_write(c1d6a180,d8a1ceec,c1d38280,0,d6299a80) at vn_write+0xda
dofilewrite(d6299a80,c1d6a180,18,280c4000,4c) at dofilewrite+0x91
write(d6299a80,d8a1cf80,280ad140,280ad140,280c404d) at write+0x33
syscall(280c002f,280a002f,bfbf002f,280c404d,280ad140) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic #3 (ffs)
-On [2223 20:35], Karsten W. Rohrbach ([EMAIL PROTECTED]) wrote: which megaraid adapter do you use in this box (hw, fw ver, bios ver, cntl-m ver)... i've seen those panics on our old news box when there where errors on the scsi busses which did not get detected properly. mainly termination issues *sigh* amr0: AMI MegaRAID mem 0xe300-0xe300 irq 10 at device 10.1 on pci0 amr0: firmware EH61 bios 1.31 16MB memory amrd0: MegaRAID logical drive on amr0 amrd0: 35040MB (71761920 sectors) RAID 0 (optimal) And I receive the panics on BOTH the array and the normal da disks. I know the termination is correct. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic (TCP)
It looks fine to me. Perhaps Garrett has something to say about it? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
-On [2221 21:15], Lyndon Nerenberg ([EMAIL PROTECTED]) wrote: LINT has an entry for an 'awe' device, however there doesn't appear to be any corresponding source code in the tree. Is this device dead? If so, the entry should be removed from LINT, or an appropriate comment added. device pcm device sbc Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic (ffs) #2
And here we are again.
This time on another disk:
dev = #amrd/0x20004, block = 2048, fs = /news/spool
panic: ffs_blkfree: freeing free block
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
db trace
Debugger(c01e7ee3) at Debugger+0x35
panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70
ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd
ffs_indirtrunc(c1db6d00,fff4,10bab0,,0,d98cfd84) at
ffs_indirtrunc+0x219
ffs_truncate(d8c79da0,0,0,0,c1d4d700) at ffs_truncate+0x6fd
ufs_setattr(d98cfec8,d98cff3c,c0171857,d98cfec8,d98b52a0) at
ufs_setattr+0x1ce
ufs_vnoperate(d98cfec8,d98b52a0,c0206bac,d98cff80,d8c79da0) at
ufs_vnoperate+0x15
ftruncate(d98b52a0,d98cff80,8098900,bfbff608,bfbf741f) at
ftruncate+0x113
syscall(2f,280a002f,bfbf002f,bfbf741f,bfbff608) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
Dumping the 512 MB to disk now.
See my previous Panic (ffs) mail on CURRENT for a almost exact problem.
No soft-updates. Two different disks on two different controllers now.
Current from 21 Feb.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic (ffs) #2
xc012665f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
#6 0xc01c4ec5 in kdb_trap (type=3, code=0, regs=0xd8b7fc90)
at ../../i386/i386/db_interface.c:158
#7 0xc01d05f4 in trap (frame={tf_fs = -1072431088, tf_es = -701956080,
tf_ds = -701956080, tf_edi = -838037504, tf_esi = 256,
tf_ebp = -659030824, tf_isp = -659030852, tf_ebx = -107170,
tf_edx = 0, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, tf_err = 0,
tf_eip = -1071886047, tf_cs = 8, tf_eflags = 582, tf_esp = -1071668385,
tf_ss = -1071743261}) at ../../i386/i386/trap.c:549
#8 0xc01c5121 in Debugger (msg=0xc01e7ee3 "panic") at machine/cpufunc.h:64
#9 0xc0143d58 in panic (fmt=0xc01f27e0 "ffs_blkfree: freeing free block")
at ../../kern/kern_shutdown.c:552
#10 0xc0195c61 in ffs_blkfree (ip=0xc1d92200, bno=6560, size=8192)
at ../../ufs/ffs/ffs_alloc.c:1337
#11 0xc0197be1 in ffs_truncate (vp=0xd8d11fe0, length=0, flags=0, cred=0x0,
p=0xd8b320c0) at ../../ufs/ffs/ffs_inode.c:337
#12 0xc019c8e6 in ufs_inactive (ap=0xd8b7feb8) at ../../ufs/ufs/ufs_inode.c:84
#13 0xc01a1985 in ufs_vnoperate (ap=0xd8b7feb8)
at ../../ufs/ufs/ufs_vnops.c:2283
#14 0xc016d0ae in vput (vp=0xd8d11fe0) at vnode_if.h:794
#15 0xc01703b9 in unlink (p=0xd8b320c0, uap=0xd8b7ff80)
at ../../kern/vfs_syscalls.c:1421
#16 0xc01d0e96 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 1, tf_esi = 134721536, tf_ebp = -1077945076,
tf_isp = -659030060, tf_ebx = 134750720, tf_edx = 134750812, tf_ecx = 0,
tf_eax = 10, tf_trapno = 7, tf_err = 2, tf_eip = 134533504, tf_cs = 31,
tf_eflags = 647, tf_esp = -1077945120, tf_ss = 47})
at ../../i386/i386/trap.c:1073
#17 0xc01c57c6 in Xint0x80_syscall ()
#18 0x80482c3 in ?? ()
#19 0x80480f9 in ?? ()
(kgdb) up 10
#10 0xc0195c61 in ffs_blkfree (ip=0xc1d92200, bno=6560, size=8192)
at ../../ufs/ffs/ffs_alloc.c:1337
1337panic("ffs_blkfree: freeing free block");
More info will be coming shortly...
As usual, advice, hints, tips (on how to maintain my sanity for example)
are highly appreciated.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
el: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
-On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote: On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. The awe device controls the AWE's wavetable.. newpcm doesn't talk to this (yet - no idea if there are any plans) newmidi is underway... That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic (ffs) #2
*sigh* ignore the gdb output of this one... it was the old one. =( /var/crash was too full. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic (TCP)
-On [2221 12:15], Sameh Ghane ([EMAIL PROTECTED]) wrote:
Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit:
Just caught panic #3 on my Diablo newstransit box running 4.0 from the
7th of February.
My first two were ffs related. And I hadn't enabled DDB and dumpdev back
then =\
No soft-updates.
This box pushes around 360-380 GB in a weekend on network IO.
panic: tcp_setpersist: retransmit pending
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.354
This is interesting as we use 4.0 on a transit nntp server also, running diablo.
We have 60GB IN/OUT each day, and it runs fine:
60 GB is our daily incoming feed. ;)
And add to that between 90-120 GB outgoing a day.
$ uptime
12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64
Nice.
I am currently preprocessing the messages with cleanfeed which causes my
average to be something like 3.xx 3.xx 3.xx
4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 2000
Try downgrading ?
No thanks, I want 4.0 to be bugfree, not work around the problem. ;)
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Panic (ffs)
Ok,
so I rebuild world from today's sources and since diablo isn't that
happy with truncated files I decided to clean up the amr mounted
/news/spool.
'lo and behold:
dev = #da/0x20003, block = 6560, fs = /news
panic: ffs_blkfree: freeing free block
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
The joy! =)
db trace
Debugger(c01e7ee3) at Debugger+0x35
panic(c01f27e0,c01f27c0,c1ccc914,19a0,c1d0d8d4) at panic+0x70
ffs_blkfree(c1d92200,19a0,2000,d8d11fe0,c1d92200) at ffs_blkfree+0x1dd
ffs_truncate(d8d11fe0,0,0,0,0) at ffs_truncate+0x809
ufs_inactive(d8b7feb8,d8b7fec8,c016d0ae,d8b7feb8,0) at ufs_inactive+0x72
ufs_vnoperate(d8b7feb8,0,d8d11fe0,c02020c0,d8d11fe0) at
ufs_vnoperate+0x15
vput(d8d11fe0,d8b320c0,c02065b4,d8b7ff80,c0201ec0) at vput+0x8e
unlink(d8b320c0,d8b7ff80,8082200,807b000,1) at unlink+0x135
syscall(2f,2f,2f,1,807b000) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
So here I am, waiting for the memory to dump again.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Panic (TCP)
Well,
this is fun...
Just caught panic #3 on my Diablo newstransit box running 4.0 from the
7th of February.
This box pushes around 360-380 GB in a weekend on network IO.
panic: tcp_setpersist: retransmit pending
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.354
db trace
Debugger(c01e8063) at Debugger+0x35
panic(c01eddc0,d5ce6b60,d8d8bc48,c018bcb6,d5ce6b60) at panic+0x70
tcp_setpersist(d5ce6b60,d5ce6b60,c018bc24,d8d8bc6c,c0149279) at
tcp_setpersist+0x2c
tcp_timer_persist(d5ce6b60,4000,160,c1cd,cdfae000) at
tcp_timer_persist+0x92
softclock(0,c0160010,cc4d0010,cc4d0010,cdfae000) at softclock+0xd1
doreti_swi(c1d7d000,50b0,2000) at doreti_swi+0xf
ffs_reallocblks(d8d8be04) at ffs_reallocblks+0x3d0
cluster_write(cc5213e8,4332000,0) at cluster_write+0x15a
ffs_write(d8d8bea0,d8cf79c0,fdc,c1f14800,c0201e80) at ffs_write+0x476
vn_write(c1f14800,d8d8beec,c1d30500,0,d8cf79c0) at vn_write+0xda
dofilewrite(d8cf79c0,c1f14800,6,280be020,fdc) at dofilewrite+0x91
write(d8cf79c0,d8d8bf80,280be000,15,280be000) at write+0x33
syscall(bfbf002f,280a002f,bfbf002f,280be000,15) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
This is from the serial console. I'm going to dump the memory to swap
now and do some gdb with my kernel.debug.
Advice is wanted and highly appreciated.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic (TCP)
#13 0xc01c6c9b in doreti_swi ()
#14 0xc0194658 in ffs_reallocblks (ap=0xd8d8be04)
at ../../ufs/ffs/ffs_alloc.c:525
#15 0xc016961a in cluster_write (bp=0xcc5213e8, filesize=70459392)
at vnode_if.h:1056
#16 0xc019ac02 in ffs_write (ap=0xd8d8bea0) at ../../ufs/ufs/ufs_readwrite.c:495
#17 0xc0173d22 in vn_write (fp=0xc1f14800, uio=0xd8d8beec, cred=0xc1d30500,
flags=0, p=0xd8cf79c0) at vnode_if.h:363
#18 0xc0150e5d in dofilewrite (p=0xd8cf79c0, fp=0xc1f14800, fd=6,
buf=0x280be020, nbyte=4060, offset=-1, flags=0) at ../../sys/file.h:156
#19 0xc0150d63 in write (p=0xd8cf79c0, uap=0xd8d8bf80)
at ../../kern/sys_generic.c:298
#20 0xc01d0e7e in syscall (frame={tf_fs = -1078001617, tf_es = 671744047,
tf_ds = -1078001617, tf_edi = 671866880, tf_esi = 21,
tf_ebp = -1077971400, tf_isp = -656883756, tf_ebx = 671866880,
tf_edx = 0, tf_ecx = 0, tf_eax = 4, tf_trapno = 0, tf_err = 2,
tf_eip = 134595120, tf_cs = 31, tf_eflags = 514, tf_esp = -1077971444,
tf_ss = 47}) at ../../i386/i386/trap.c:1055
#21 0xc01c5886 in Xint0x80_syscall ()
#22 0x804ed66 in ?? ()
#23 0x804c18e in ?? ()
#24 0x804abaf in ?? ()
#25 0x804983d in ?? ()
#26 0x80490c5 in ?? ()
---Type return to continue, or q return to quit---
#27 0x8048829 in ?? ()
#28 0x80480f9 in ?? ()
And is there any other person who experienced same kind of
problem and have any hints to diagnose this?
I am updating the box as we speak to sources of today (which btw don't
seem to like a -j4 flag).
I'll again review my changes.
Not sure if needed. But I felt the reason to pipe up about this because
if it is a genuine bug stil in the system we need to get it out of the
system ASAP.
Debugging tips are welcome, since I am not the biggest bulb wrt
debugging.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic (TCP)
-On [2221 13:30], Yoshinobu Inoue ([EMAIL PROTECTED]) wrote:
Might there be incorrect memory over writing?
How you mean?
I think one possibility of the problem is that some code is
incorrectly overwriting some part of the memory, and a tcpcb's
tt_persist-c_flags is happen to overwritten.
Hmmm, this box is a real disk io and network io bastard. It serves as a
newspeer transit box based on diablo 1.27 with a fxp card and an amr
array. Let me know if a dmesg is needed.
Now I am very much interested in the value of
tp-tt_persist-c_flags at panic, if CALLOUT_PENDING and
possibly other flags are just set, or completely broken data
is written on it.
(kgdb) up 10
#10 0xc018abc4 in tcp_setpersist (tp=0xd5ce6b60)
at ../../netinet/tcp_output.c:893
warning: Source file is more recent than executable.
893
(kgdb) print tp-tt_persist-c_flags
$1 = 0
[I am upgrading the box to the latest sources as we speak, hence the
sourcecode is newer]
And if later, I am also interested in other values around
tp-tt_persist-c_flags, to check what kind of value is
written around there.
(kgdb) print tp-tt_persist
$2 = (struct callout *) 0xd5ce6c44
(kgdb) print *(tp-tt_persist)
$3 = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0,
tqe_prev = 0xcc401640}}, c_time = 22275044, c_arg = 0xd5ce6b60,
c_func = 0, c_flags = 0}
Debugging tips are welcome, since I am not the biggest bulb wrt
debugging.
I am not also, and you might have already known these things,
but in case they are useful,
-If DDB is specified in kernel config file, and all src/sys
tree including sys/compile dir is saved onto another
machine, it will be very useful at next panic, because remote GDB
debugging is available by those data.
I have a serial console active so I can do DDB from my workstation.
Hence I always have a kernel and kernel.debug from the same sources.
(Though if the bug happens at very delicate timing, it
might prevent the bug from happening again.)
-Adding some printfs in tcp_output.c:tcp_setpersist() panic
case might be useful.
It might.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic (TCP)
-On [2221 14:40], Yoshinobu Inoue ([EMAIL PROTECTED]) wrote:
Now I am very much interested in the value of
tp-tt_persist-c_flags at panic, if CALLOUT_PENDING and
possibly other flags are just set, or completely broken data
is written on it.
893
(kgdb) print tp-tt_persist-c_flags
$1 = 0
Woops sorry I was worng.
tp-tt_rexmt-c_flags is actually causing the panic, and the
necessary data is the contents of the tp-tt_rexmt-c_flags.
(kgdb) print tp-tt_rexmt-c_flags
$1 = 6
(kgdb) print tp-tt_rexmt
$2 = (struct callout *) 0xd5ce6c2c
(kgdb) print (*tp-tt_rexmt)
$3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c,
tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60,
c_func = 0xc018bcdc tcp_timer_rexmt, c_flags = 6}
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic (ffs)
[root@tyr] (61) # gdb -k /kernel.debug vmcore.1
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd"...
IdlePTD 2625536
initial pcb at 21c9e0
panicstr: from debugger
panic messages:
---
panic: ffs_blkfree: freeing free block
panic: from debugger
Uptime: 39m4s
amrd0: still open, can't shutdown
dumping to dev #da/0x20001, offset 524312
dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495
494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477
476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459
458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441
440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423
422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405
404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387
386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369
368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351
350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333
332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315
314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297
296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279
278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261
260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243
242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225
224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207
206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189
188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171
170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153
152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135
134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117
116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99
98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75
74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51
50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27
26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
---
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:304
#1 0xc0143d61 in panic (fmt=0xc01e27f4 "from debugger")
at ../../kern/kern_shutdown.c:554
#2 0xc01244e1 in db_panic (addr=-1071886047, have_addr=0, count=-1,
modif=0xd8b7fb88 "") at ../../ddb/db_command.c:433
#3 0xc0124481 in db_command (last_cmdp=0xc02042fc, cmd_table=0xc020415c,
aux_cmd_tablep=0xc021905c) at ../../ddb/db_command.c:333
#4 0xc0124546 in db_command_loop () at ../../ddb/db_command.c:455
#5 0xc012665f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
#6 0xc01c4ec5 in kdb_trap (type=3, code=0, regs=0xd8b7fc90)
at ../../i386/i386/db_interface.c:158
#7 0xc01d05f4 in trap (frame={tf_fs = -1072431088, tf_es = -701956080,
tf_ds = -701956080, tf_edi = -838037504, tf_esi = 256,
tf_ebp = -659030824, tf_isp = -659030852, tf_ebx = -107170,
tf_edx = 0, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, tf_err = 0,
tf_eip = -1071886047, tf_cs = 8, tf_eflags = 582, tf_esp = -1071668385,
tf_ss = -1071743261}) at ../../i386/i386/trap.c:549
#8 0xc01c5121 in Debugger (msg=0xc01e7ee3 "panic") at machine/cpufunc.h:64
#9 0xc0143d58 in panic (fmt=0xc01f27e0 "ffs_blkfree: freeing free block")
at ../../kern/kern_shutdown.c:552
#10 0xc0195c61 in ffs_blkfree (ip=0xc1d92200, bno=6560, size=8192)
at ../../ufs/ffs/ffs_alloc.c:1337
#11 0xc0197be1 in ffs_truncate (vp=0xd8d11fe0, length=0, flags=0, cred=0x0,
p=0xd8b320c0) at ../../ufs/ffs/ffs_inode.c:337
#12 0xc019c8e6 in ufs_inactive (ap=0xd8b7feb8) at ../../ufs/ufs/ufs_inode.c:84
#13 0xc01a1985 in ufs_vnoperate (ap=0xd8b7feb8)
at ../../ufs/ufs/ufs_vnops.c:2283
#14 0xc016d0ae in vput (vp=0xd8d11fe0) at vnode_if.h:794
#15 0xc01703b9 in unlink (p=0xd8b320c0, uap=0xd8b7ff80)
at ../../kern/vfs_syscalls.c:1421
#16 0xc01d0e96 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 1, tf_esi = 134721536, tf_ebp = -1077945076,
tf_isp = -659030060, tf_ebx = 134750720, tf_edx = 134750812, tf_ecx = 0,
tf_eax = 10, tf_trapno = 7, tf_err = 2, tf_eip = 134533504, tf_cs = 31,
tf_eflags = 647, tf_esp = -1077945120, tf_ss = 47})
at ../../i386/i386/trap.c:1073
#17 0xc01c57c6 in Xint0x80_syscall ()
#18 0x80482c3 in ?? ()
#19 0x80480f9 in ?? ()
--
Jeroen Ruigrok van
Re: More world breakage
-On [2128 19:30], John Baldwin ([EMAIL PROTECTED]) wrote: === bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 This is indicative of a larger problem with installworld. The short version is that we need install tools just like we have build tools now. In the meantime, should you encounter a broken make world with this use the following WORKAROUND: cd /usr/src/usr.bin/xinstall make make install and resume the make world. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc-2.95.2, jade and freebsd-sgml-documentation
-On [19991201 23:30], Nik Clayton ([EMAIL PROTECTED]) wrote: On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote: i tried to make me a new handbook, so i needed jade. But the newest C++ fashion (g++ under current) has changed to fast for this very old 1998 heavily template based source code distribution ;-). I had a lot of problems with const and not const .. and gave up. It is far to much to post here ... Unfortunately, jade is the tool of choice. I don't run -current, so haven't had a chance to test out jade with the new GCC. I think someone (obrien prolly) committed some patches to the jade port to make it compile on CURRENT. HTH, -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
weird crash
Hi, just today I got this error, never had it before in all those months I have been tracking CURRENT now. Jun 6 17:15:26 daemon /kernel: sio0: 65 more tty-level buffer overflows (total 65) Jun 6 17:15:28 daemon /kernel: sio0: 131 more tty-level buffer overflows (total 196) Jun 6 17:15:29 daemon /kernel: sio0: 38 more tty-level buffer overflows (total 234) until I interrupted it with CTRL-ALT-ESC to drop into DDB. This is some info I got from DDB: [ please bear with me if I didn't get all I need, but it's the first `crash' I intercepted and I think I got all the relevant data, comments appreciated though ] dbtrace Debugger(0c255518) at Debugger+0x37 scgetc(c0294020,2,124bca,c0294020,850ff2c) at scgetc+ox5ec sckdbevent(c0294020,0,0,124bca,850ff2c) at sckbdevent+0x1c4 atkbd_intr(c0294020,0,bfbfd4bc,c0211c92,c06773f0) at atkbd_intr+ox1f atkbd_isa_intr(c06773f0,0,2f,2f,2f) at atkbd_isa_intr+0x1b Xresume1() at Xresume+0x2b --- interrupt, eip=0x28078509, esp=0xc5b6dfe0, ebp=0xbfbfd4bc --- I also have results from show registers, print, show page if those are deemed interesting. What I was able to glance from ps what that the 0xc5b6dfe0 range lay in an xterm memory range... I am not 100% sure about this though. some relevant system information: [asmo...@daemon] (81) $ uname -a FreeBSD daemon.ninth-circle.org 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Thu Jun 3 16:59:10 CEST 1999 asmo...@daemon.ninth-circle.org:/work/FreeBSD/src/sys/compile/DAEMON i386 Jun 2 10:57:38 daemon /kernel: isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 Jun 2 10:57:38 daemon /kernel: atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 Jun 2 10:57:38 daemon /kernel: atkbd0: AT Keyboard irq 1 on atkbdc0 Jun 2 10:57:38 daemon /kernel: atkbd: the current kbd controller command byte 0047 Jun 2 10:57:38 daemon /kernel: atkbd: keyboard ID 0x41ab (2) Jun 2 10:57:38 daemon /kernel: kbdc: RESET_KBD return code:00fa Jun 2 10:57:38 daemon /kernel: kbdc: RESET_KBD status:00aa Jun 2 10:57:38 daemon /kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d Jun 2 10:57:38 daemon /kernel: vga0: Generic ISA VGA on isa0 Jun 2 10:57:38 daemon /kernel: fb0: vga0, vga, type:VGA (5), flags:0x7007f Jun 2 10:57:38 daemon /kernel: fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa 0x2 Jun 2 10:57:38 daemon /kernel: fb0: init mode:24, bios mode:3, current mode:24 Jun 2 10:57:38 daemon /kernel: fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k Jun 2 10:57:38 daemon /kernel: VGA parameters upon power-up Jun 2 10:57:38 daemon /kernel: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: VGA parameters in BIOS for mode 24 Jun 2 10:57:38 daemon /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: EGA/VGA parameters to be used for mode 24 Jun 2 10:57:38 daemon /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: sc0: System console on isa0 Jun 2 10:57:38 daemon /kernel: sc0: fb0 kbd0 Jun 2 10:57:38 daemon /kernel: sc0: VGA color 16 virtual consoles, flags=0x0 Jun 2 10:57:38 daemon /kernel: sio0: irq maps: 0x41 0x51 0x41 0x41 Jun 2 10:57:38 daemon /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jun 2 10:57:38 daemon /kernel: sio0: type 16550A Jun 2 10:57:38 daemon /kernel: sio1: irq maps: 0x41 0x49 0x41 0x41 Jun 2 10:57:38 daemon /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jun 2 10:57:38 daemon /kernel: sio1: type 16550A The system itself is a simple DFI-based motherboard with Intel Pentium 200 MMX and 96 MB RAM. The keyboard is not one of them ps/2's, but a the older type (I don't think that DIN is the correct name though). the device on sio0 is my serial MouseMan: controller isa0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0at isa? port ? conflicts device sc0 at isa? If any more information is required, please tell me and I will see if I can dig it up. 'gards, -- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Accept no limitations
