Re: another panic (mix ppp and usb to taste)
On 30 Aug, Nick Hibma wrote: /usr/sbin/ppp -quiet -direct -nat /dev/ugen0.1 I was confused by the following from ppp's man-page: -direct This is used for receiving incoming connections. ppp ignores the ``set device'' line and uses descriptor 0 as the link. which seems to imply, I don't need to care the descriptor 1 :-) USB is NOT a serial protocol. It has nothing in common with a serial port. The reason I tried this, was finding a Linux how-to guide for making the ppp over USB work between a PDA (Palm or Handsrping) and the Linux machine. It mentioned having to install the Handspring module or something to work with /dev/ttyUSB (sp?). I figured, I'll try it with a ugen-device... Could we have such a device-module too, BTW? Similar to the serial modems we already have? Or will you just I suggest I write it myself :-)? P.S.: The reason why it crashes is that it looks for an endpoint descriptor for endpoint 0 which doesn't exist. I'll fix that. Yeah, but it seems, that just a few lines above the crash, it checks for the sce being non-NULL... Or is it an optimization artifact? Thanks, -mi On Fri, 24 Aug 2001, Mikhail Teterin wrote: As I was trying to let the Palm Pilot connect to my desktop through usb using PPP, I tried to run /usr/sbin/ppp -quiet -direct -nat /dev/ugen0 While, perhaps, not the right way to do what I want (what is? aren't serial devices the simplest?), it should not panic (nothing should really). But it does, and quite repeatedly (some more comments after the trace): IdlePTD 4984832 initial pcb at 3db040 panicstr: bwrite: buffer is not busy??? panic messages: --- Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 0100 fault virtual address = 0x3 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01d5a0b stack pointer = 0x10:0xce7f1c4c frame pointer = 0x10:0xce7f1c58 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 = 442 (ppp) trap number = 12 panic: page fault cpuid = 0; lapic.id = 0100 boot() called on cpu#0 syncing disks... panic: bwrite: buffer is not busy??? cpuid = 0; lapic.id = 0100 boot() called on cpu#0 Uptime: 10m14s dumping to dev da0b, offset 131200 dump ... 2 1 0 --- [...] #12 0xc030b0bc in trap (frame={tf_fs = -1071644648, tf_es = -830734320, tf_ds = 16777232, tf_edi = 64, tf_esi = 0, tf_ebp = -830530472, tf_isp = -830530504, tf_ebx = -1049243648, tf_edx = -1049243428, tf_ecx = 34, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071818229, tf_cs = 8, tf_eflags = 66178, tf_esp = -830530412, tf_ss = -1049288448}) at ../../../i386/i386/trap.c:405 #13 0xc01d5a0b in ugenpoll (dev=0xc1752100, events=64, p=0xce7abb80) at ../../../dev/usb/ugen.c:1369 #14 0xc01ed604 in spec_poll (ap=0xce7f1c94) at ../../../fs/specfs/spec_vnops.c:333 #15 0xc01ed27d in spec_vnoperate (ap=0xce7f1c94) at ../../../fs/specfs/spec_vnops.c:119 #16 0xc0252333 in vn_poll (fp=0xc17328c0, events=64, cred=0xc1734700, p=0xce7abb80) at vnode_if.h:381 #17 0xc0228b8b in selscan (p=0xce7abb80, ibits=0xce7f1d48, obits=0xce7f1d3c, nfd=1) at ../../../sys/file.h:192 #18 0xc02286b5 in select (p=0xce7abb80, uap=0xce7f1f80) at ../../../kern/sys_generic.c:772 #19 0xc030bf2d in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134842880, tf_esi = 134842880, tf_ebp = 0, tf_isp = -830529580, tf_ebx = 3, tf_edx = 134996480, tf_ecx = 134996352, tf_eax = 93, tf_trapno = 12, tf_err = 2, tf_eip = 673178596, tf_cs = 31, tf_eflags = 643, tf_esp = -1077937708, tf_ss = 47}) at ../../../i386/i386/trap.c:1129 (kgdb) up 13 #13 0xc01d5a0b in ugenpoll (dev=0xc1752100, events=64, p=0xce7abb80) at ../../../dev/usb/ugen.c:1369 1369switch (sce-edesc-bmAttributes UE_XFERTYPE) { (kgdb) p sce $1 = (struct ugen_endpoint *) 0x0 (kgdb) l 1364printf(ugenpoll: no pipe\n); 1365return (EIO); 1366} 1367#endif 1368s = splusb(); 1369switch (sce-edesc-bmAttributes UE_XFERTYPE) { 1370case UE_INTERRUPT: 1371if (events (POLLIN | POLLRDNORM)) { 1372if (sce-q.c_cc 0) 1373revents |= events (POLLIN | POLLRDNORM); (kgdb) p events $3 = 64 (kgdb) p s No symbol s in current context. (kgdb) p revents $5 = 0 What I don't understand, is -- there is a check, just a few lines above: if (sce == NULL) return (EINVAL); How come it is not being caught there? To Unsubscribe: send mail to [EMAIL PROTECTED
webdavfs correction
Seems like Apple has webdavfs for OS X... Any hope for a FreeBSD version? At least -- source? At least with an NDA, so binary modules can be made available for -stable and -current? Do our new Apple employees wield enough influence? -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: webdavfs correction
On 22 Aug, Julian Elischer wrote: so call me ignorant but what IS webdav? (or even dav) On Wed, 22 Aug 2001 [EMAIL PROTECTED] wrote: Seems like Apple has webdavfs for OS X... Any hope for a FreeBSD version? At least -- source? At least with an NDA, so binary modules can be made available for -stable and -current? Do our new Apple employees wield enough influence? From my earlier posting: http://www.webdav.org/ /usr/ports/www/{neon,cadaver,sitecopy}/pkg-descr See also: http://www.xent.com/dec00/0391.html Too bad, the published Apple's link http://www.apple.com/macosx/usingosx/internet.html is broken :( -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: nvi maintainer?
[moved to -current] On 9 Jul, Keith Bostic wrote: From: [EMAIL PROTECTED] Mmm, so there will be a library in /usr/lib, which a commercial application will not be able to link against? No thanks, I'd rather take gdbm and their LGPL... Just to be clear -- they could link against it using the same, standard functionality that FreeBSD uses. They couldn't link against it and use all the additional features/functionality. So we'll have to document, which functions it is Ok to call and which arguments/flags can and can not be passed to them. Brrrgh... My guess is that your answer remains the same -- and, that's cool, I'm used to losing this argument, I do so about twice a year. :-) Just wanted to be clear. Well, can someone comment on the useability of gdbm? I know, it has dbm and ndbm compatibility mode and a less restrictive license. Should we switch over to it? -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
picking a DB (Re: nvi maintainer?)
On 9 Jul, Keith Bostic wrote: My guess is that your answer remains the same -- and, that's cool, I'm used to losing this argument, I do so about twice a year. :-) Just wanted to be clear. Well, can someone comment on the useability of gdbm? I know, it has dbm and ndbm compatibility mode and a less restrictive license. Should we switch over to it? This isn't necessary. The *current* FreeBSD libc Berkeley DB sources are completely safe -- they're under a UC Regents copyright notice. Well, but there are programming bugs in it, as was pointed out in this thread. Unless FreeBSD wants to maintain its own db, we need to select someone else's. DB3 -- despite its technical merits -- does not fit because of restrictive licensing. gdbm's license is not ideal, but acceptable -- so I'm inquiring about its technical merits... I'd welcome your comments in particular, since you are an expert in the field and there is not going to be a conflict of interest. This discussion is only regarding the possibility of making the Berkeley DB 3.X functionality available to the FreeBSD community and its customers. Well, it started out discussing the next release of nvi and promptly concluded, that it would require upgrading dbm. So, now the issue is -- which db to pick: the currently used (buggy), the DB3 (too restrictive a license, IMO), gdbm, or something else (Net or OpenBSD's?). -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: amd feature request (Re: AMD config file question.)
On 25 May, David O'Brien wrote: On Fri, May 25, 2001 at 09:56:42AM -0400, Mikhail Teterin wrote: Now that smbfs is in, can amd be used to mount smb shares? Of course, it can. But can we have something like host type, where all smb-shares available from a host are automaticly accessible? This may be added to the host-type together with NFS, or be made part of a separate smbhost type. I'd vote for the first one, personally... Send me a tested patch and I'll consider it. I want to make sure you won't be causing any problems in the generic case. Heh. That was a feature request only. I don't even know the details of NFS, much less SMB. Sorry, -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic trying to play Civillization (with trace, etc.)
On 12 Mar, Dag-Erling Smorgrav wrote: = Mikhail Teterin [EMAIL PROTECTED] writes: = If you can, please reproduce the panic on a kernel compiled with the = INVARIANTS, INVARIANT_SUPPORT and WITNESS options. = Well, with this options on, the machine does not crash, but the = program segfaults on startup: = = The trace you're showing looks like it's from a shell script that = starts civctp. I need to see the trace from the civctp binary itself. No, that trace was obtained from a simple ktrace civctp There is no shell-wrapper around the binary: file /opt/bin/civctp /opt/bin/civctp: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, stripped It is just one big executable. You are welcome to download it from: http://aldan.algebra.com:8015/~mi/civctp-crash/civctp.bz2 uncompress it and try to run it (just 43Kb compressed). May be, it is because it is a _staticly_ linked Linux executable (the _dynamicly_ linked Netscape works fine). = lock order reversal = 1st lockmgr interlock last acquired @ ../../kern/kern_lock.c:239 = 2nd 0xcefa0520 process lock @ ../../kern/kern_sig.c:183 = 3rd 0xc1029f80 lockmgr interlock @ ../../kern/kern_lock.c:560 = = Haven't seen this one before... If it's reproducible, could you do the = following: No... This the only machine I have at home. No serial console or cable... It is reproduceable -- happens now at boot time... -mi = 1) recompile your kernel with WITNESS_DDB = = 2) hook up a serial console and boot with '-h' in /boot.config = = 3) provoke the reversal, then get the output from 'trace', 'show = mutex' and 'show witness' at the DDB prompt = = 4) type 'continue' to exit DDB and continue running normally. = lock order reversal = 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625 = 2nd 0xc0419680 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:939 = 3rd 0xcefb986c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:948 = = This is a known (and probably benign) bug. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
uk_UA.KOI8-U broken?
As if the __stderr/__sF troubles weren't enough, my locale settings don't work any more. ls(1) just shows the English names for the months, perl complains every time: perl: warning: Please check that your locale settings: LC_ALL = (unset), LANG = "uk_UA.KOI8-U" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). And other programs (elm, vi) misbehave similarly. ru_SU.KOI8-R is fine. Would this be an imperial-sponsored conspiracy ;-) ? The /usr/share/locale/uk_UA.KOI8-U only has LC_COLLATE, LC_CTYPE, LC_TIME, while the ru_SU.KOI8-R has LC_MESSAGES, LC_MONETARY, LC_NUMERIC as well. But it used to work before. Perhaps, the recent changes in locale handling require all (more) LC_* files to be present? -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Confusing location of md5 program
Steve O'Hara-Smith once wrote: On 27-Apr-99 Maxim Sobolev wrote: At a guess, it is there to ensure that when you boot single user, and have only /, you can still verify the integrety of other files... Why not to put it in /bin? I had always understood that sbin meant static binaries (ie: those that could be used even when /lib is hosed) and should contain the vital binaries for such situations. I have just failed to locate the documentation that has left me believing this so could somebody confirm (or deny) ? There is no /lib on FreeBSD and none of the /bin/* (except for rmail) is dynamicly linked. Both of this things are quite easy to find out without any documentation, BTW :-) -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message