smbfs panic

[Tim Robbins]

Here's a backtrace of a smbfs panic. Looks like it does not correctly
handle the smbfs_getpages error it is encountering and leaves garbage
vnodes lying around. The panic probably comes from the VI_LOCK macro
call on smbfs_node.c line 321.

# cp blah.tar.gz ~tim
cp: /home/tim/blah.tar.gz: Bad address

in dmesg:
smbfs_getpages: error 60
vm_fault: pager read error, pid 433 (cp)

Upon trying to halt:
syncing disks, buffers remaining...
done

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0xdeadc0de
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc0171e23
stack pointer   = 0x10:0xc5bd2a1c
frame pointer   = 0x10:0xc5bd2a3c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
process eflags  = interrupt enabled, IOPL = 0
current process = halt
kernel: type 12 trap, code=0
Stopped at_mtx_lock_flags+0x43:   cmpl $0xc02afd80,0(%ebx)
db> trace
_mtx_lock_flags(deadc0de,0,c0f280b7,141,c0f05000) at _mtx_lock_flags+0x43
smbfs_reclaim(c5bd2a94,12,c0602540,c0602540,0) at smbfs_reclaim+0x11a
vclean(c0f53a68,8,c0602540,6,c0f53a68) at vclean+0x229
vgonel(c0f53a68,c0602540,c02903f2,94a,0) at vgonel+0x5c
smbfs_umount(c0ea8400,8,c0602540,c0602540,0) at smbfs_umount+0x3c
dounmount(c0ea8400,8,c0602540,,c216304c) at dounmount+0x204
vfs_unmountall(...)
boot(...)
reboot(...)
syscall(...)
Xint0x80_syscall(...)
--- syscall (55, FreeBSD ELF32, reboot), eip = 0x8048e9f, esp = 0xbfbffb1c, ebp = 
0xbfbffb60 ---



Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: /proc ( procfs ) DP2

[Kris Kennaway]

On Thu, Nov 21, 2002 at 08:36:19AM +0100, Christophe Yayon wrote:
> Hi all,
> 
> i am new to CURRENT, i have just installed DP2 and i saw that /proc is not
> mounted... Could i create in fstab and mount it or is it not necessary ?

You could if you like, but it's not necessary for most things (it's
omitted because it's historically a big security risk).

> Where could i see more docs about CURRENT/5.0 ?

The release notes are available on the website.

Kris



msg47058/pgp0.pgp
Description: PGP signature

My -current status

[Michael Reifenberger]

Hi,
after upgrading to -cuurent as of now on my A30p IBM Notebook I have the
following changed state:
- firewire is working.
  I get a "contigmalloc1: size must not be 0" most of the time after a
  cold-boot tough.
- I get still some "ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST"
- ATA-CF and SD Cards are working.
- I got a strange
  "swap_pager_strategy: bp 0xc3f0f900 blk 0 size 0, not page bounded"
  during X-Server startup (maybe DRI related?).
- Anywhere between a past current and now the lpd-device got lost.
  I get:
ppc0 port 0x7bc-0x7be,0x3bc-0x3c3 irq 7 drq 0 on acpi0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppi0:  on ppbus0
pps0:  on ppbus0
  But no lpd (of course it's in the config-file)

Anyway most, of the Noteboot is working.

Congrats to all involved!


Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS

cam: invalid value for tunable kern.cam.scsi_delay
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Wed Nov 20 08:50:17 CET 2002
root@nihil:/usr/src/sys/i386/compile/nihil
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0547000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc05470a8.
Preloaded elf module "/boot/kernel/procfs.ko" at 0xc05470f8.
Preloaded elf module "/boot/kernel/pseudofs.ko" at 0xc05471a4.
Preloaded elf module "/boot/kernel/md.ko" at 0xc0547254.
Preloaded elf module "/boot/kernel/linux.ko" at 0xc05472fc.
Preloaded elf module "/boot/kernel/sysvshm.ko" at 0xc05473a8.
Preloaded elf module "/boot/kernel/sysvsem.ko" at 0xc0547454.
Preloaded elf module "/boot/kernel/sysvmsg.ko" at 0xc0547500.
Preloaded elf module "/boot/kernel/miibus.ko" at 0xc05475ac.
Preloaded elf module "/boot/kernel/if_dc.ko" at 0xc0547658.
Preloaded elf module "/boot/kernel/if_fxp.ko" at 0xc0547704.
Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc05477b0.
Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc054785c.
Preloaded elf module "/boot/kernel/usb.ko" at 0xc0547908.
Preloaded elf module "/boot/kernel/ums.ko" at 0xc05479b0.
Preloaded elf module "/boot/kernel/umass.ko" at 0xc0547a58.
Preloaded elf module "/boot/kernel/linprocfs.ko" at 0xc0547b04.
Preloaded elf module "/boot/kernel/radeon.ko" at 0xc0547bb4.
Preloaded elf module "/boot/kernel/if_ep.ko" at 0xc0547c60.
Preloaded elf module "/boot/kernel/aic.ko" at 0xc0547d0c.
Preloaded elf module "/boot/kernel/if_ed.ko" at 0xc0547db4.
Preloaded elf module "/boot/kernel/nfsserver.ko" at 0xc0547e60.
Preloaded elf module "/boot/kernel/nfsclient.ko" at 0xc0547f10.
Preloaded elf module "/boot/kernel/firewire.ko" at 0xc0547fc0.
Preloaded elf module "/boot/kernel/sbp.ko" at 0xc0548070.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0548118.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1198986680 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (1198.99-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
  
Features=0x383f9ff

real memory  = 1073086464 (1023 MB)
avail memory = 1037807616 (989 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
VESA: v2.0, 32704k memory, flags:0x1, mode table:0xc034bf62 (122)
VESA: ATI MOBILITY RADEON
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
Using $PIR table, 14 entries at 0xc00fdeb0
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-fast"  frequency 3579545 Hz
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_cpu0:  on 

Re: buildkernel broken at bluetooth?

[Julian Elischer]

On Wed, 20 Nov 2002, walt wrote:

> mkdep -f .depend -a   -nostdinc -I../../../../netgraph/bluetooth/include -D_KERNEL 
> -DKLD_MODULE -I- -I../../../../netgraph/bluetooth/include -I. -I@ -I@/dev 
>-I@/../include 
> -I/usr/obj/usr/local/mnt/src/i386/usr/include 
> 
>/usr/local/mnt/src/sys/modules/netgraph/bluetooth/bluetooth/../../../../netgraph/bluetooth/common/ng_bluetooth.c
> /usr/local/mnt/src/sys/netgraph/bluetooth/common/ng_bluetooth.c:38:26: 
>ng_bluetooth.h: 
> No such file or directory
> mkdep: compile failed
> 
> 
> My /usr/src is a symlink to another partition which is mounted
> on /usr/local/mnt/src.  I can make it compile by modifying the
> Makefiles in sys/modules/netgraph/bluetooth like this:
> 
> CFLAGS+=   -I${.CURDIR}/../../../../netgraph/bluetooth/include

I think you have the correct answer..

Obviously I didn;t see this isn testing as my directories are not
symlinked...
I'll fix it now..

thanks for the notice

Julian

> 
> Maybe there's a better way to do this?
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

/boot & rcng

[Christophe Yayon]

Hi all,

i have just install DP2; and i have some little questions :

could i  mount /boot to a separate partition (label) ?
why is the a lilo file in /boot ? compatibility ?

i also checked /etc/rc.d/* (rcng) and i have seen that there is again
'NetBSD' choice (case section), does it will be clean when release ?

I saw nfsiod process (ps) but no nfs client/server, how could i disable
them ?


Thanks in advance, bye.

--
[EMAIL PROTECTED] ; http://www.freebsdfr.org




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: /boot & rcng

[Kris Kennaway]

On Thu, Nov 21, 2002 at 09:39:41AM +0100, Christophe Yayon wrote:
> Hi all,
> 
> i have just install DP2; and i have some little questions :
> 
> could i  mount /boot to a separate partition (label) ?

That was something that people had in mind when /boot was created, but
I don't know if the support is actually there yet.

> why is the a lilo file in /boot ? compatibility ?

There isn't..perhaps you're confusing a FreeBSD file with a LILO file
that has the same name.

> i also checked /etc/rc.d/* (rcng) and i have seen that there is again
> 'NetBSD' choice (case section), does it will be clean when release ?

I couldn't parse this.

> I saw nfsiod process (ps) but no nfs client/server, how could i disable
> them ?

NFS client/server support is controlled by your kernel configuration file.

Kris



msg47062/pgp0.pgp
Description: PGP signature

About gbde questions

[kai ouyang]

Hi,everybody,
 I have some puzzles on the 'gbde' function.
 I saw the gbde(4), I do not understand the 'cold' true meaning. My point 
is that if the disk were stealed by somebody, he could not see anything in 
the disk unless he knows the "pass-phrase". right?
 In the first barrier, the manual said that "metadata" is necessary to 
locate the lock-sector, I want to know how we get "metadata".
 I added the option "GEOM_BDE" into my kernel conf file. I am trying
I do as following gbde(8):
Current# gbde init /dev/da1s1f -l /etc/da1s1f.lock
gbde: illegal option -- l
Usage error: Invalid option
Usage:
   gbde attach dest -l filename
   gbde detach dest
   gbde init dest [-i] [-f filename] -l filename
   gbde setkey dest [-n key] -l filename
   gbde destroy dest [-n key] -l filename
Current# touch /etc/da1s1f.lock
Current# gbde init /dev/da1s1f -f /etc/da1s1f.lock
gbde: Missing number_of_keys property

The 'da1s1f' partition exists, but I do not mount it. I first try to test 
'da0s1f', but the box info:"gbde: /dev/da0s1f: Device busy".

If I want to test the 'gbde' function, could somebody give me some help? 
How can I do?

Best Regards
 Ouyang Kai




_
ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: /boot & rcng

[Sean Kelly]

On Thu, Nov 21, 2002 at 12:53:21AM -0800, Kris Kennaway wrote:
> On Thu, Nov 21, 2002 at 09:39:41AM +0100, Christophe Yayon wrote:
...
> > why is the a lilo file in /boot ? compatibility ?
> 
> There isn't..perhaps you're confusing a FreeBSD file with a LILO file
> that has the same name.

(16) smkelly@edgemaster:~$ ls -l /boot/liloboot
-r-xr-xr-x  1 root  wheel  212992 Nov 18 11:12 /boot/liloboot

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/liloldr/Makefile
says:
This is `liloboot', which creates a file which can be treated like a
Linux kernel image, and is designed to be dropped into a Linux system
and booted via LILO.  Once booted, the user is greeted by the FreeBSD
loader.  This still isn't quite complete, as the the root= specification
from LILO isn't currently passed to the loader yet.

-- 
Sean Kelly | PGP KeyID: D2E5E296
[EMAIL PROTECTED] | http://www.zombie.org

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

sparc64 tinderbox failure

[Mike Barcroft]

Thu Nov 21 09:15:00 GMT 2002
...
U sys/kern/kern_thread.c
U sys/kern/sched_4bsd.c
U sys/modules/netgraph/bluetooth/bluetooth/Makefile
U sys/modules/netgraph/bluetooth/bt3c/Makefile
U sys/modules/netgraph/bluetooth/h4/Makefile
U sys/modules/netgraph/bluetooth/hci/Makefile
U sys/modules/netgraph/bluetooth/l2cap/Makefile
U sys/modules/netgraph/bluetooth/socket/Makefile
U sys/modules/netgraph/bluetooth/ubt/Makefile
cvs [update aborted]: cannot make directory include: File exists

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

installworld fell over

[Julian Elischer]

here:

--
>>> Installing everything..
--
cd /usr/src; make -f Makefile.inc1 install
===> share/info
===> include
creating osreldate.h from newvers.sh
setvar PARAMFILE
/usr/src/include/../sys/sys/param.h;  . /usr/src/include/../sys/conf/newvers.sh;   
 echo
"$COPYRIGHT" > osreldate.h;   echo "#ifdef _KERNEL" >>
osreldate.h;echo '#error "/usr/include/osreldate.h
cannot be used in the kernel, use sys/param.h"' >> osreldate.h;  echo
"#else" >> osreldate.h;echo \#'undef
__FreeBSD_version' >> osreldate.h;echo \#'define
__FreeBSD_version' $RELDATE >> osreldate.h;  echo "#endif" >>
osreldate.h
touch: not found

has something changed in the build environment?
 also, after that I got:
hostname: not found
expr: not found


has someone been fiddling with the PATH in the build?





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Hard-locks with Linux emulation

[Marc Recht]

Hi!

While using Mulberry (mail/mulberry) the system often locks up completely.
Nothing but reset helps then. I don't get any error (WITHNESS* is on).

Marc


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

[PATCH] Re: smbfs panic

[Terry Lambert]

Tim Robbins wrote:
> Here's a backtrace of a smbfs panic. Looks like it does not correctly
> handle the smbfs_getpages error it is encountering and leaves garbage
> vnodes lying around. The panic probably comes from the VI_LOCK macro
> call on smbfs_node.c line 321.
> 
> # cp blah.tar.gz ~tim
> cp: /home/tim/blah.tar.gz: Bad address


Read the list archives.  We discussed this to death.  The correct
thing to do is to back off and retry -- that's decimal 60, which
is hex 0x3c, which, according to /sys/netsmb/smb_rq.h is:

#define SMBR_REXMIT0x0004  /* request should be retransmitted */
#define SMBR_INTR  0x0008  /* request interrupted */
#define SMBR_RESTART   0x0010  /* request should be repeated if possible */
#define SMBR_NORESTART 0x0020  /* request is not restartable */

If you don't want to try to implement this, note that the read/write
works (try 'dd' instead of 'cp', so you aren't using mmap'ed pages,
and see that 'dd' works).

I don't think it's worth writing the code to attempt the retry, until
you know that the code will work -- that it's backed up far enough
that the retry won't fail.  This basically means you need to know why
it's failing in the first place, which means you need to be familiar
with how the server is implemented (not likely, unless your name is
"Luke Howard", you're a Microsoft employee, or you have a Windows
source license -- otherwise it's probably about two weeks worth of
work).

The attached patch works around the problem by disabling the getpages
and putpages code in the smbfs.  This basically turns paging operations
into reads and writes, which we know from using 'dd' instead of 'cp'
will work.

Note: this is only a workaround: it disables obviously incorrect code,
but doesn't provide replacement code for the bogus code.

-- Terry
Index: smbfs_io.c
===
RCS file: /cvs/src/sys/fs/smbfs/smbfs_io.c,v
retrieving revision 1.13
diff -c -r1.13 smbfs_io.c
*** smbfs_io.c  4 Aug 2002 10:29:30 -   1.13
--- smbfs_io.c  21 Nov 2002 05:53:23 -
***
*** 400,405 
--- 400,406 
return error;
  }
  
+ #if BROKEN_PAGE_IO
  /*
   * Vnode op for VM getpages.
   * Wish wish  get rid from multiple IO routines
***
*** 655,660 
--- 656,662 
return rtvals[0];
  #endif /* SMBFS_RWGENERIC */
  }
+ #endif/* BROKEN_PAGE_IO */
  
  /*
   * Flush and invalidate all dirty buffers. If another process is already
Index: smbfs_node.h
===
RCS file: /cvs/src/sys/fs/smbfs/smbfs_node.h,v
retrieving revision 1.2
diff -c -r1.2 smbfs_node.h
*** smbfs_node.h18 Sep 2002 09:27:04 -  1.2
--- smbfs_node.h21 Nov 2002 05:53:47 -
***
*** 75,83 
  #define VTOSMB(vp)((struct smbnode *)(vp)->v_data)
  #define SMBTOV(np)((struct vnode *)(np)->n_vnode)
  
  struct vop_getpages_args;
- struct vop_inactive_args;
  struct vop_putpages_args;
  struct vop_reclaim_args;
  struct ucred;
  struct uio;
--- 75,85 
  #define VTOSMB(vp)((struct smbnode *)(vp)->v_data)
  #define SMBTOV(np)((struct vnode *)(np)->n_vnode)
  
+ #if BROKEN_PAGE_IO
  struct vop_getpages_args;
  struct vop_putpages_args;
+ #endif/* BROKEN_PAGE_IO */
+ struct vop_inactive_args;
  struct vop_reclaim_args;
  struct ucred;
  struct uio;
***
*** 89,96 
--- 91,100 
struct smbfattr *fap, struct vnode **vpp);
  u_int32_t smbfs_hash(const u_char *name, int nmlen);
  
+ #if BROKEN_PAGE_IO
  int  smbfs_getpages(struct vop_getpages_args *);
  int  smbfs_putpages(struct vop_putpages_args *);
+ #endif/* BROKEN_PAGE_IO */
  int  smbfs_readvnode(struct vnode *vp, struct uio *uiop, struct ucred *cred);
  int  smbfs_writevnode(struct vnode *vp, struct uio *uiop, struct ucred *cred, int 
ioflag);
  void smbfs_attr_cacheenter(struct vnode *vp, struct smbfattr *fap);
Index: smbfs_vnops.c
===
RCS file: /cvs/src/sys/fs/smbfs/smbfs_vnops.c,v
retrieving revision 1.24
diff -c -r1.24 smbfs_vnops.c
*** smbfs_vnops.c   26 Sep 2002 14:07:43 -  1.24
--- smbfs_vnops.c   21 Nov 2002 05:52:32 -
***
*** 96,102 
--- 96,104 
{ &vop_create_desc, (vop_t *) smbfs_create },
{ &vop_fsync_desc,  (vop_t *) smbfs_fsync },
{ &vop_getattr_desc,(vop_t *) smbfs_getattr },
+ #if BROKEN_PAGE_IO
{ &vop_getpages_desc,   (vop_t *) smbfs_getpages },
+ #endif/* BROKEN_PAGE_IO */
{ &vop_inactive_desc,   (vop_t *) smbfs_inactive },
{ &vop_ioctl_desc,  (vop_t *) smbfs_ioctl },
{ &vop_islocked_desc,   (vop_t *) vop_stdislocked },
***
*** 108,114 
--- 110,118 
{ &vop_open_desc,   (vop_t *) smbfs_open },
{ &vop

Re: installworld fell over

[Ruslan Ermilov]

On Thu, Nov 21, 2002 at 01:25:44AM -0800, Julian Elischer wrote:
> 
> here:
> 
> --
> >>> Installing everything..
> --
> cd /usr/src; make -f Makefile.inc1 install
> ===> share/info
> ===> include
> creating osreldate.h from newvers.sh
> setvar PARAMFILE
> /usr/src/include/../sys/sys/param.h;  . /usr/src/include/../sys/conf/newvers.sh; 
>   echo
> "$COPYRIGHT" > osreldate.h;   echo "#ifdef _KERNEL" >>
> osreldate.h;echo '#error "/usr/include/osreldate.h
> cannot be used in the kernel, use sys/param.h"' >> osreldate.h;  echo
> "#else" >> osreldate.h;echo \#'undef
> __FreeBSD_version' >> osreldate.h;echo \#'define
> __FreeBSD_version' $RELDATE >> osreldate.h;  echo "#endif" >>
> osreldate.h
> touch: not found
> 
> has something changed in the build environment?
>  also, after that I got:
> hostname: not found
> expr: not found
> 
> 
> has someone been fiddling with the PATH in the build?
> 
This is a FAQ question -- installworld is trying to do what buildworld
was supposed to do.  This can be caused by a number of reasons: either
your computer's date/time is set incorrectly, or you updated sources
and forgot to re-buildworld, or some sources' modtime is set to point
to the future causing them to fake make(1) to think they should always
be rebuild.  (All of this is of course assumes that the buildworld and
installworld were run with the same options, the same MAKEOBJDIRPREFIX,
tc.)


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age



msg47069/pgp0.pgp
Description: PGP signature

Re: Cross-Development with NetBSD

[Ruslan Ermilov]

On Thu, Nov 21, 2002 at 12:10:14AM -0700, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Wilkinson,Alex" <[EMAIL PROTECTED]> writes:
> : Is FreeBSD likely to follow the in footsteps of NetBSD and create a framework to 
>do crossbuilds ?
> : 
> : http://ezine.daemonnews.org/200211/xdevnetbsd.html
> 
> FreeBSD already has cross builds for a while, since before NetBSD's
> cross build infrastructure.  However, NetBSD's infrastructure is a
> little more extensive because it is possible to do incremental builds
> and build full releases that work in a cross build evironment.
> 
What do you mean by "incremental builds and full releases that work ..."?


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age



msg47070/pgp0.pgp
Description: PGP signature

Re: installworld fell over

[Julian Elischer]

On Thu, 21 Nov 2002, Ruslan Ermilov wrote:

> On Thu, Nov 21, 2002 at 01:25:44AM -0800, Julian Elischer wrote:
> > 
> > here:
> > 
> > --
> > >>> Installing everything..
> > --
> > cd /usr/src; make -f Makefile.inc1 install
> > ===> share/info
> > ===> include
> > creating osreldate.h from newvers.sh
> > setvar PARAMFILE
> > /usr/src/include/../sys/sys/param.h;  . /usr/src/include/../sys/conf/newvers.sh;   
> echo
> > "$COPYRIGHT" > osreldate.h;   echo "#ifdef _KERNEL" >>
> > osreldate.h;echo '#error "/usr/include/osreldate.h
> > cannot be used in the kernel, use sys/param.h"' >> osreldate.h;  echo
> > "#else" >> osreldate.h;echo \#'undef
> > __FreeBSD_version' >> osreldate.h;echo \#'define
> > __FreeBSD_version' $RELDATE >> osreldate.h;  echo "#endif" >>
> > osreldate.h
> > touch: not found
> > 
> > has something changed in the build environment?
> >  also, after that I got:
> > hostname: not found
> > expr: not found
> > 
> > 
> > has someone been fiddling with the PATH in the build?
> > 
> This is a FAQ question -- installworld is trying to do what buildworld
> was supposed to do.  This can be caused by a number of reasons: either
> your computer's date/time is set incorrectly, or you updated sources
> and forgot to re-buildworld, or some sources' modtime is set to point
> to the future causing them to fake make(1) to think they should always
> be rebuild.  (All of this is of course assumes that the buildworld and
> installworld were run with the same options, the same MAKEOBJDIRPREFIX,
> tc.)

Thanks i did a few operations between the buildworld and the
installworld.. but nothing drastic..

I then did a make buildkernel and that seems to have fixed it (?)



> 
> 
> Cheers,
> -- 
> Ruslan ErmilovSysadmin and DBA,
> [EMAIL PROTECTED] Sunbay Software AG,
> [EMAIL PROTECTED]FreeBSD committer,
> +380.652.512.251  Simferopol, Ukraine
> 
> http://www.FreeBSD.orgThe Power To Serve
> http://www.oracle.com Enabling The Information Age
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: your mail

[Chris Howells]

Hi,

Argh, sorry about loosing the subject. Unfortunately messages from my
normal ISP are't getting through to freebsd.org mailng lists (I've
contacted them about it) and I'm having to use a crappy uni web mail
system) which I'm not used to, so forgot the subject

--- reply 


> If you have a second box and a null modem cable, you can set up
FreeBSD to
> use a serial console by unplugging the keyboard.  You can then
capture the
> boot output on the second machine and e-mail that out.  If it
doesn't
> automatically use the serial console w/o a keyboard, you can do:



Thanks for the reply. Sadly this isn't going to be possible since my
laptop doesn't have a serial port :( I'll have to try the verbose
boot, that may give more information.

Cheers,
Chris Howells

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Call for testers: acpica-unix-20021118.tar.gz

[Mitsuru IWASAKI]

Hi all,

I've made patches for the latest ACPI CA snapshot between 20021002 and
20021118.
http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff

A lot of bugs are fixed, please check the change log at:
http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt

Please test them and feedback to [EMAIL PROTECTED] if you find any
problems.  I'll import them into src tree before RC1.

Thanks

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Issue with DP2 install

[Ceri Davies]

Installed 5.0-DP2 last night.

Everything went absolutely fine (the second time - the first time was my fault
though), but there was one thing that may be of concern to new users.

I have a crappy NE2000 clone that I use with my cable modem.
sysinstall probed this as ed1 and therefore wrote an entry to rc.conf as:

ifconfig_ed1="DHCP"

Which is all fine, but when the install finished and I booted into GENERIC,
the card was detected as ed0, so obviously the network configuration failed.

While this is easy enough to fix, I thought I'd best mention it in case it's
considered a hurdle for any new users.  Is it possible that the kernel for
sysinstall uses a different device.hints than GENERIC ?

The card is also probed as ed0 under -STABLE, and the dmesg (from -STABLE - I
can't get the -CURRENT one at the moment) entry looks like this:

ed0:  port 0xc400-0xc41f irq 17 at device 12.0 on 
pci0
ed0: address 00:40:95:44:3f:bc, type NE2000 (16 bit) 

Ceri

PS sysinstall also mentions that the developer set contains all sources but
   no games, which is slightly obvious now.
-- 
The Dwarf Father's rock!

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

alpha tinderbox failure

[Dag-Erling Smorgrav]

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Thu Nov 21 03:02:40 PST 2002
--
>>> Kernel build for GENERIC completed on Thu Nov 21 03:33:00 PST 2002
--
>>> Kernel build for LINT started on Thu Nov 21 03:33:00 PST 2002
--
===> vinum
"Makefile", line 4446: warning: duplicate script for target "geom_bsd.o" ignored
cc1: warnings being treated as errors
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c: In function `ahd_ddb_in':
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c:1931: warning: unsigned int format, different 
type arg (arg 2)
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c: In function `ahd_ddb_out':
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c:1991: warning: unsigned int format, different 
type arg (arg 2)
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c:1991: warning: unsigned int format, different 
type arg (arg 4)
/h/des/src/sys/dev/aic7xxx/aic79xx_osm.c:1991: warning: unsigned int format, different 
type arg (arg 5)
*** Error code 1

Stop in /h/des/obj/h/des/src/sys/LINT.
*** Error code 1

Stop in /h/des/src.
*** Error code 1

Stop in /h/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [PATCH] Re: smbfs panic

[Tim Robbins]

On Thu, Nov 21, 2002 at 02:02:39AM -0800, Terry Lambert wrote:

> Tim Robbins wrote:
> > Here's a backtrace of a smbfs panic. Looks like it does not correctly
> > handle the smbfs_getpages error it is encountering and leaves garbage
> > vnodes lying around. The panic probably comes from the VI_LOCK macro
> > call on smbfs_node.c line 321.
> > 
> > # cp blah.tar.gz ~tim
> > cp: /home/tim/blah.tar.gz: Bad address
> 
> 
> Read the list archives.  We discussed this to death.  The correct
> thing to do is to back off and retry -- that's decimal 60, which
> is hex 0x3c, which, according to /sys/netsmb/smb_rq.h is:

I am aware that the "Bad address" errors have been discussed before, but I
had not seen the panic on unmount/halt mentioned. Thanks for the workaround
and suggested correct fix, I'll have a go at implementing that next week.


Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Weird ACPI related problem

[Vallo Kallaste]

On Wed, Nov 20, 2002 at 12:27:08PM -0500, Robert Watson <[EMAIL PROTECTED]>
wrote:

> Well, it's definitely not intended behavior :-).  A few questions for you:
> 
> (1) How much memory does this machine have?  How much swap space is
> configured at the point where you get to the swapspace failure?
> 
> (2) What exactly were the messages you pointed out in the bootup regardin
> the load of acpi.ko?  Could you provide us with verbose dmesg output?

I've booted up with 0:fd(0,a)/boot/loader -hv by interacting with
boot2 I think, still there's no verbose boot messages, sorry. Here's
what I got, cut-n-paste from xterm. There is no swap configured at all
accordingly to swapinfo. The getty attaches to internal console, so
there's some commands and responses missing just before
'swap_pager_getswapspace: failed' line. Those are:

# swapinfo
Device  1K-blocks   UsedAvail   CapacityType
# cd /boot/kernel
# kldload acpi.ko
[now comes the..]
swap_pager_getswapspace: failed


Console: serial port
BIOS drive A: is disk0
BIOS drive B: is disk1
BIOS drive C: is disk2
BIOS 639kB/128256kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Mon Nov 18 21:57:03 GMT 2002)
/kernel text=0x3e38e8 data=0x52cfc+0x818c8 syms=[0x4+0x4c7c0+0x4+0x5b140]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/kernel]...   
ACPI autoload failed - no such file or directory
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT-20021119-JPSNAP #0: Mon Nov 18 23:40:09 GMT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/kernel" at 0xc0662000.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1699956616 Hz
CPU: Pentium 4 (1699.96-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf13  Stepping = 3
  
Features=0x3febfbff
real memory  = 132382720 (126 MB)
avail memory = 121856000 (116 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
Using $PIR table, 9 entries at 0xc00f3d20
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
agp0:  mem 
0xffa8-0xffaf,0xf000-0xf7ff irq 11 at device 2.0 on pci0
agp0: detected 892k stolen memory
agp0: aperture size is 128M
uhci0:  port 0xe800-0xe81f irq 11 at device 
29.0 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xe880-0xe89f irq 9 at device 
29.1 on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xec00-0xec1f irq 10 at device 
29.2 on pci0
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pcib1:  at device 30.0 on pci0
pci1:  on pcib1
fxp0:  port 0xdc00-0xdc3f mem 0xff8ff000-0xff8f irq 11 at 
device 8.0 on pci1
fxp0: Ethernet address 00:03:47:29:85:a5
inphy0:  on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at 
device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0:  at device 31.3 (no driver attached)
pci0:  at device 31.5 (no driver attached)
pmtimer0 on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
fdc0:  at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
Timecounters tick every 10.000 msec
ata1-slave: timeout waiting for interrupt
ata1-slave: ATAPI identify failed
ad0: 19541MB  [39703/16/63] at ata0-master UDMA100
acd0: CDROM  at ata1-master PIO4
Mounting root from cd9660:cd0a
setrootbyname failed
iso_mountroot: can't find rootvp
Root mount failed: 6
Mounting root from cd9660:acd0a
cd9660: RockRidge Extension
Enter full pathname of shell or RETURN for /bin/sh: 
+---+
| You are now running

Re: My -current status

[Giorgos Keramidas]

On 2002-11-21 09:26, Michael Reifenberger <[EMAIL PROTECTED]> wrote:
> - I got a strange
>   "swap_pager_strategy: bp 0xc3f0f900 blk 0 size 0, not page bounded"
>   during X-Server startup (maybe DRI related?).

This is probably something unrelated to x11, which your X server
triggered.  I don't use X11 at home and I got this message a few
times, after I started using an md-filesystem of 300 mb for /tmp.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: /boot & rcng

[Giorgos Keramidas]

On 2002-11-21 09:39, Christophe Yayon <[EMAIL PROTECTED]> wrote:
> i also checked /etc/rc.d/* (rcng) and i have seen that there is again
> 'NetBSD' choice (case section), does it will be clean when release ?

You obviously refer to parts of the rc.d scripts that look like:

case ${OSTYPE} in
FreeBSD)
...
;;
NetBSD)
...
;;
esac

These are parts that set up different behavior for the scripts,
depending on whether they are run on a NetBSD or a FreeBSD host.

FreeBSD and NetBSD have been trying to run the same scripts, without
local changes, which makes it easier to track changes from one source
tree to the other.  The parts that really do need to behave
differently depending on the operating system that the scripts run on,
are encapsulated in blocks like the one above.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

smbfs problems

[Vallo Kallaste]

Hi

Some info about failures I see:

root:vallo# kldstat
Id Refs AddressSize Name
 13 0xc010 3be9e0   kernel
 21 0xc04bf000 480d4acpi.ko
root:vallo# smbutil view //vallo@poweredge
smbutil: smb_lib_init: can't find kernel module

It means kernel module will not be loaded upon first use of smbfs.
This can and can not be considered as bug.

root:vallo# cd /boot/kernel
root:vallo# kldload smbfs.ko 
root:vallo# kldstat 
Id Refs AddressSize Name
 18 0xc010 3be9e0   kernel
 21 0xc04bf000 480d4acpi.ko
 31 0xc17dc000 2smbfs.ko
root:vallo# smbutil view //vallo@poweredge
Password:
ShareType   Comment
---
IPC$ pipe   Remote IPC
work disk
toolsdisk
usersdisk   
private  disk   
test disk   

Now the writing part:

After creating 5MB file using /dev/urandom, I'm trying to copy it
over to users/vallo smb share mounted at /mnt, which fails. The copy
is interruptible using Ctrl-C. Examination at NT4 server shows 0
byte file. Umount of /mnt fails with device busy. Umount -f /mnt
fails to return prompt, but after interrupting the smbfs is
unmounted.  There is no kernel messages or something in syslog. The
copy operation returns failure ~3 seconds after start.

root:vallo# mount
/dev/ad0s1a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad0s1d on /usr (ufs, NFS exported, local, soft-updates)
procfs on /proc (procfs, local)
myhakas:/opt/src-current/src on /usr/src (nfs)
myhakas:/opt/src-current/ports on /usr/ports (nfs, read-only)
//VALLO@POWEREDGE/USERS on /mnt (smbfs)
root:vallo# cd /home/vallo/
root:vallo# dd if=/dev/urandom of=testfile bs=1m count=5
5+0 records in
5+0 records out
5242880 bytes transferred in 0.518492 secs (10111784 bytes/sec)
root:vallo# cp testfile /mnt/vallo/
cp: /mnt/vallo/testfile: Operation timed out
^C
root:vallo#
root:vallo# ls -la /mnt/vallo
^C
root:vallo# 
root:vallo# umount /mnt
umount: unmount of /mnt failed: Device busy
root:vallo# umount -f /mnt
^C
root:vallo# mount
/dev/ad0s1a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad0s1d on /usr (ufs, NFS exported, local, soft-updates)
procfs on /proc (procfs, local)
myhakas:/opt/src-current/src on /usr/src (nfs)
myhakas:/opt/src-current/ports on /usr/ports (nfs, read-only)
root:vallo# 
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: smbfs problems

[Vallo Kallaste]

[snip]
> After creating 5MB file using /dev/urandom, I'm trying to copy it
> over to users/vallo smb share mounted at /mnt, which fails. The copy
> is interruptible using Ctrl-C. Examination at NT4 server shows 0
> byte file. Umount of /mnt fails with device busy. Umount -f /mnt
> fails to return prompt, but after interrupting the smbfs is
> unmounted.  There is no kernel messages or something in syslog. The
> copy operation returns failure ~3 seconds after start.
[snip]

Sorry forgot to add one detail. Althought dd'ing the same file to
smbfs mount works, it'll sometimes modify the file being copied
(size is different). It doesn't happen reliably, sometimes the file
is copied fine, sometimes not. At the times the file isn't copied
right there's an error message:

root:vallo# dd if=testfile of=/mnt/vallo/test1  
dd: /mnt/vallo/test1: Bad address
9356+0 records in
9355+0 records out
4789760 bytes transferred in 20.350003 secs (235369 bytes/sec)
root:vallo# ls -la /mnt/vallo/
total 4710
drwxr-xr-x  1 root  wheel16384 Nov 21 15:10 .
drwxr-xr-x  1 root  wheel16384 Jan  1  1970 ..
-rwxr-xr-x  1 root  wheel  4789760 Nov 21 15:10 test1
-rwxr-xr-x  1 root  wheel0 Nov 21 14:52 testfile
root:vallo# ls -la /home/vallo/testfile 
-rw-r--r--  1 root  wheel  5242880 Nov 21 14:52 /home/vallo/testfile

It seems to me that adding conv=sync flag to dd removes the
abovementioned failure case. 10 tries of dd with this flag added did
fine.

root:vallo# dd if=testfile of=/mnt/vallo/test1 conv=sync
10240+0 records in
10240+0 records out
5242880 bytes transferred in 24.295283 secs (215798 bytes/sec)
root:vallo# ls -la /mnt/vallo/
total 5152
drwxr-xr-x  1 root  wheel16384 Nov 21 15:13 .
drwxr-xr-x  1 root  wheel16384 Jan  1  1970 ..
-rwxr-xr-x  1 root  wheel  5242880 Nov 21 15:13 test1
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Cross-Development with NetBSD

[M. Warner Losh]

In message: <[EMAIL PROTECTED]>
Ruslan Ermilov <[EMAIL PROTECTED]> writes:
: On Thu, Nov 21, 2002 at 12:10:14AM -0700, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > "Wilkinson,Alex" <[EMAIL PROTECTED]> writes:
: > : Is FreeBSD likely to follow the in footsteps of NetBSD and create a framework to 
:do crossbuilds ?
: > : 
: > : http://ezine.daemonnews.org/200211/xdevnetbsd.html
: > 
: > FreeBSD already has cross builds for a while, since before NetBSD's
: > cross build infrastructure.  However, NetBSD's infrastructure is a
: > little more extensive because it is possible to do incremental builds
: > and build full releases that work in a cross build evironment.
: > 
: What do you mean by "incremental builds and full releases that work ..."?

ruslan,

First and foremost, I ment no disrespect in what I said.  You
have made the upgrade path for FreeBSD almost painless for a wide
range of releases (less painful than NetBSD has been at times for me).
You gave FreeBSD the ability to cross build world about a year or a
year and a half ahead of NetBSD's similarly integrated ability.

NetBSD builds a directory full of tools that you can later use to
incrementally build, say, 'ls' or 'cat' because one can define
USETOOLS to be 'yes' and have the make automatically pick them up when
rebuilding.  There are a few of the details I'm a little unclear on,
but that's the jist of it.

Second, the NetBSD have tested almost all of their platforms in a
cross build release scenario.  They know that the binaries that result
from 'make release' build on i386 actually boot on the target
platform.  They have build 1.6.x for many of their platforms this
way.  So far, the FreeBSD has done all its builds natively.

One of the cool things about the NetBSD approach, btw, is that they
have a src/tools directory.  This directory lists all the build tools
for building in one place.  I think that this is a little cleaner than
what we have in the Makefile.inc1 right now.  On the other hand, it is
a lot more complicated than what we have now, and I'm not sure that
added complexity is worth it.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: cvs commit: src/sys/geom geom_slice.c

[Vallo Kallaste]

On Wed, Nov 20, 2002 at 09:19:01PM +0100, Poul-Henning Kamp
<[EMAIL PROTECTED]> wrote:

> This should fix a large part of the disklabel -e bogosity people
> have been seeing.
> 
> In message <[EMAIL PROTECTED]>, Poul-Henning Kamp
>  writes:
> >phk 2002/11/20 12:12:52 PST
> >
> >  Modified files:
> >sys/geom geom_slice.c 
> >  Log:
> >  Remember to update the providers idea of its size when we reconfigure
> >  a slice child.
> >  
> >  Approved by:re
> >  
> >  Revision  ChangesPath
> >  1.27  +1 -0  src/sys/geom/geom_slice.c

root:vallo# ident /usr/src/sys/geom/geom_slice.c 
/usr/src/sys/geom/geom_slice.c:
 $FreeBSD: src/sys/geom/geom_slice.c,v 1.27 2002/11/20 20:12:52 phk Exp $
root:vallo# fdisk ad0
*** Working on device /dev/ad0 ***
parameters extracted from in-core disklabel are:
cylinders=39703 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=39703 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 16382961 (7999 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 15/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 16383024, size 16383024 (7999 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 15/ sector 63
The data for partition 3 is:

The data for partition 4 is:

root:vallo# disklabel ad0s1
# /dev/ad0s1c:
type: ESDI
disk: ad0s1
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 39703
sectors/unit: 40020624
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   52428804.2BSD 2048 16384 32776   # (Cyl.0 - 520*)
  b:   524288   524288unused0 0 # (Cyl.  520*- 1040*)
  c: 163829610unused0 0 # (Cyl.0 - 16252*)
  d: 15334385  10485764.2BSD 2048 16384 28552   # (Cyl. 1040*- 16252*)
Warning, partition c doesn't cover the whole unit!
Warning, An incorrect partition c may cause problems for standard system utilities
root:vallo# disklabel -r ad0s1
# /dev/ad0s1c:
type: ESDI
disk: ad0s1
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 39703
sectors/unit: 40020624
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   524288   634.2BSD 2048 16384 32776   # (Cyl.0*- 520*)
  b:   524288   524351unused0 0 # (Cyl.  520*- 1040*)
  c: 16382961   63unused0 0 # (Cyl.0*- 16252*)
  d: 15334385  10486394.2BSD 2048 16384 28552   # (Cyl. 1040*- 16252*)
Warning, partition c doesn't start at 0!
Warning, partition c doesn't cover the whole unit!
Warning, An incorrect partition c may cause problems for standard system utilities
root:vallo# 
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

current and doscmd

[Dimitar Peikov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
Last night I was played with the 'doscmd' tool and define that should boot 
from C only and to use /dev/ads1 mounted as /d for C:. So running the 
'doscmd' causes machine to restart. I thought that this is an illegal state, 
so if someone is interested in this, I can send more information (machine 
hardware, current config, and exact 'doscmd' configuration).
My box is last cvsupped on monday evening to current.

PS: I'm not currently subscribed to the freebsd-current mailing list, please 
Cc: me.

- -- 
Dimitar Peikov
Programmer Analyst
Globalization Group
"We Build e-Business"  

RILA Solutions  
27 Building, Acad.G.Bonchev Str.  
1113 Sofia, Bulgaria  

phone: (+359 2) 9797320 
phone: (+359 2) 9797300 
fax:   (+359 2) 9733355  
http://www.rila.com 

GnuPG key   http://earth.rila.bg/~mitko/mitko.key.asc
GnuPG key   http://www.bgzone.com/~mitko/mitko.key.asc
Key fingerprint 97AF 6192 78E2 AC68 FD56  CCB0 68B9 DF7D B3C1 9ED7
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE93PAEaLnffbPBntcRApnAAJ47vSe8RDFOhu0hpILyUm17YGfAWwCgrFce
q6ncxVNLNuN5DAuZY42Gq10=
=m9Jf
-END PGP SIGNATURE-

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: /proc ( procfs ) DP2

[Vallo Kallaste]

On Thu, Nov 21, 2002 at 12:15:42AM -0800, Kris Kennaway
<[EMAIL PROTECTED]> wrote:

> On Thu, Nov 21, 2002 at 08:36:19AM +0100, Christophe Yayon wrote:
> > Hi all,
> > 
> > i am new to CURRENT, i have just installed DP2 and i saw that /proc is not
> > mounted... Could i create in fstab and mount it or is it not necessary ?
> 
> You could if you like, but it's not necessary for most things (it's
> omitted because it's historically a big security risk).

The OpenOffice suite crashes at startup without /proc mounted.
OpenOffice docs say that /proc is only needed for initial install
program and does not say it's needed afterwards. Still, it's needed.
Am I missing something? In case it's unavoidable the docs should be
modified.

Thanks
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Cross-Development with NetBSD

[Ruslan Ermilov]

On Thu, Nov 21, 2002 at 06:28:09AM -0700, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> : On Thu, Nov 21, 2002 at 12:10:14AM -0700, M. Warner Losh wrote:
> : > In message: <[EMAIL PROTECTED]>
> : > "Wilkinson,Alex" <[EMAIL PROTECTED]> writes:
> : > : Is FreeBSD likely to follow the in footsteps of NetBSD and create a framework 
>to do crossbuilds ?
> : > : 
> : > : http://ezine.daemonnews.org/200211/xdevnetbsd.html
> : > 
> : > FreeBSD already has cross builds for a while, since before NetBSD's
> : > cross build infrastructure.  However, NetBSD's infrastructure is a
> : > little more extensive because it is possible to do incremental builds
> : > and build full releases that work in a cross build evironment.
> : > 
> : What do you mean by "incremental builds and full releases that work ..."?
> 
> ruslan,
> 
>   First and foremost, I ment no disrespect in what I said.  You
> have made the upgrade path for FreeBSD almost painless for a wide
> range of releases (less painful than NetBSD has been at times for me).
> You gave FreeBSD the ability to cross build world about a year or a
> year and a half ahead of NetBSD's similarly integrated ability.
> 
Sorry if I sounded so, I didn't mean to.  :-)

> NetBSD builds a directory full of tools that you can later use to
> incrementally build, say, 'ls' or 'cat' because one can define
> USETOOLS to be 'yes' and have the make automatically pick them up when
> rebuilding.  There are a few of the details I'm a little unclear on,
> but that's the jist of it.
> 
We also can, this just requires a few really tiny tweaks to Makefile.inc1,
and I've posted them already some time ago -- basically, for each architecture
you should build the subset of buildworld targets (WMAKE_TGTS), up to and
including _libraries (if you want to build roughly any bit later), and
them you can ``make {depend|all} SUBDIR_OVERRIDE=bin/cat'' for each of
the desired TARGET_ARCH.

> Second, the NetBSD have tested almost all of their platforms in a
> cross build release scenario.  They know that the binaries that result
> from 'make release' build on i386 actually boot on the target
> platform.  They have build 1.6.x for many of their platforms this
> way.  So far, the FreeBSD has done all its builds natively.
> 
I know that the Alpha and sparc64 binaries produced on i386 work.
I know that cross-compiling i386 on either Alpha or sparc64 is
broken (GCC sometimes produces different assembler output than
the native compiler).  I lack the necessary hardware to actually
test/fix the issues with cross-releases.

> One of the cool things about the NetBSD approach, btw, is that they
> have a src/tools directory.  This directory lists all the build tools
> for building in one place.  I think that this is a little cleaner than
> what we have in the Makefile.inc1 right now.  On the other hand, it is
> a lot more complicated than what we have now, and I'm not sure that
> added complexity is worth it.
> 
When you say "build tools", do you mean them in our build-tools sense,
or something else?


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age



msg47086/pgp0.pgp
Description: PGP signature

Re: [acpi-jp 1940] Re: ACPI errors and then panic

[Mitsuru IWASAKI]

Hi,

> On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote:
> > From: Nate Lawson <[EMAIL PROTECTED]>
> > Subject: ACPI errors and then panic
> > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT)
> > Message-ID: <[EMAIL PROTECTED]>
> > 
> > > My laptop appears to work ok without ACPI but of course I don't get
> > > suspend, resume, etc.  I have never been able to get ACPI to work with it,
> > > including with a -current as of 2 hours ago.  If ACPI is enabled, I get a
> > > spew of:
> > > 
> > > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name
> > > 
> > > and then a panic from acpi_attach.
> 
> I sent a reply including the requested traces on Oct 25.  Do you need any
> more information?

Please try with new ACPI CA patches at:
http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff
Some memory leak releated bugs were fixed, so your problem might be
solved by this hopefully.

> One interesting thing is that the oem sysctl node seems bogus:
>hint.acpi.0.oem=IBM   ??
> where the ?'s are invalid characters like the happy face.

I saw similar problem long time ago.  My problem was acpi.ko
is too old and badly matched with kernel.  Please make sure
that your acpi.ko is fresh as well as kernel when you try.

> > BTW, what's model name?  Some ThinkPad's are blacklisted such as
> > IBM 600E.  And may I add your ACPI data to our repo. (in Japan) ?
> 
> IBM T23.  Feel free to use the dsdt and/or asl however you wish.

OK, I'll add them to our CVS repo.

Thanks

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

sparc64 tinderbox failure

[Mike Barcroft]

Thu Nov 21 15:15:00 GMT 2002
U MAINTAINERS
U include/Makefile
U secure/lib/libcrypto/Makefile
U secure/lib/libssl/Makefile
U secure/usr.bin/openssl/Makefile
U sys/kern/kern_proc.c
U sys/kern/kern_synch.c
U sys/kern/sched_4bsd.c
cvs [update aborted]: cannot make directory include: File exists

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

installworld fail

[Ying-Chieh Liao]

I'm in DP2, and cvsup and then make world...


if [ -L /usr/share/examples/sunrpc ]; then  rm -f /usr/share/examples/sunrpc;  fi
if [ -L /usr/share/examples/worm ]; then  rm -f /usr/share/examples/worm;  fi
mtree -deU   -f /usr/src/share/examples/../../etc/mtree/BSD.usr.dist -p /usr
/tmp/install.UiNprj9F/mtree: 1: Syntax error: "(" unexpected
*** Error code 2

Stop in /usr/src/share/examples.
*** Error code 1

Stop in /usr/src/share.
*** Error code 1

Stop in /usr/src.
*** Error code 1

-- 
Testing can show the presence of bugs, but not their absence.
--- Edsger W. Dijkstra



msg47089/pgp0.pgp
Description: PGP signature

recommended VAIO for ACPI hacking (Re: cvs commit:www/en/releases/5.0R todo.sgml)

[Mitsuru IWASAKI]

[moved to current@ and acpi-jp@jp]

Hi,

> According to Mitsuru IWASAKI:
> > If your ACPI BIOS check OS type (try; acpidump | grep _OS_), you might
> > need to do something.  The black list feature (for non-Windows) might be
> > good idea for avoiding confusion.
> 
> Will try tonite when I'll have my laptop.

Thanks.

> > Also, development resources are limited.  For example, none of ACPI
> > developers has VAIO.
> 
> Well, I don't know enough to be a developper but I do have a VAIO (Z600TEK)
> and can test things. Just ask.

BTW, I'm planning to buy VAIO (maybe used one) to improve ACPI support.
Any recommendations?
# Recommendation means some sort of `Sigh!  My VAIO doesn't work with
# ACPI at all!!' :-)

Thanks


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: recommended VAIO for ACPI hacking (Re: cvs commit: www/en/releases/5.0Rtodo.sgml)

[Michael Bretterklieber]

Hi,

I have an VAIO FX601, and ACPI never worked.

I get a lot of errors related to ACPI during boot and acpidump also 
prints errors.

After suspending the laptop, the system never wakes-up, display still 
stays black.

So this ACPI BIOS seems to be completely buggy,

bye,

Mitsuru IWASAKI schrieb:
[moved to current@ and acpi-jp@jp]

Hi,



According to Mitsuru IWASAKI:


If your ACPI BIOS check OS type (try; acpidump | grep _OS_), you might
need to do something.  The black list feature (for non-Windows) might be
good idea for avoiding confusion.


Will try tonite when I'll have my laptop.



Thanks.



Also, development resources are limited.  For example, none of ACPI
developers has VAIO.


Well, I don't know enough to be a developper but I do have a VAIO (Z600TEK)
and can test things. Just ask.



BTW, I'm planning to buy VAIO (maybe used one) to improve ACPI support.
Any recommendations?
# Recommendation means some sort of `Sigh!  My VAIO doesn't work with
# ACPI at all!!' :-)

Thanks


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message


--
--- --
Michael Bretterklieber		- [EMAIL PROTECTED]	
JAWA Management Software GmbH 	- http://www.jawa.at
Liebenauer Hauptstr. 200	-- privat 
A-8041 GRAZ			GSM: ++43-(0)676-93 96 698		
Tel: ++43-(0)316-403274-12	E-mail:   [EMAIL PROTECTED]
Fax: ++43-(0)316-403274-10 	http://www.inode.at/mbretter
--- --
"...the number of UNIX installations has grown to 10, with more expected..."
	   - Dennis Ritchie and Ken Thompson, June 1972


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: recommended VAIO for ACPI hacking (Re: cvs commit: www/en/releases/5.0R todo.sgml)

[Ollivier Robert]

According to Mitsuru IWASAKI:
> BTW, I'm planning to buy VAIO (maybe used one) to improve ACPI support.
> Any recommendations?
> # Recommendation means some sort of `Sigh!  My VAIO doesn't work with
> # ACPI at all!!' :-)

The Z600TEK I have (PIII/700/jogdial) can suspend to memory (sleep mode)
but is completely hung upon resume and I can't break into DDB. All the
other functions in ACPI like thermal measures and automatic speed fallback
when I unplug the power supply works.

Suspend to disk (aka hibernation) doesn't work at all (I fugre it tries to
save into the DOS slice I've kept for that purpose).

I can't use the keys on the keyboard to do that BTW, only zzz works.

APM works although as I said, it doesn't suspend from within X.

Arigato Iwasaki-san.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun  4 22:44:19 CEST 2000

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

DP2 Fatal Trap

[Scott Sipe]

First install of DP2 went crazy weird (posted earlier).  A minimal install 
(just the minimal distribution) went fine and I could login but didn't really 
try anything more than that.  Now the install went fine, the boot goes fine 
(no errors that I can see) but when I log in I get:


Fatal Trap 12: Page fault while in kernel mode
fault virtual address   = 0x89
fault code  = supervisor read, page not present
IP  = 0x8:0xc031f044
SP  = 0x10:0xd99a6c98
FP  = 0x10:0xd99a6cc0
Code Segment= base 0x0, limit 0xf, type 0x1b
= DPL0, pres 1, def32 1, gran 1 (<-- not 100% 
sure of this line)
Processor eflags= interrupt enabled, resume, IOPL=0
Current Process = 446 (tcsh)
Trap Number = 12
Panic: Page Fault
Syncing disks... panic: bwrite: buffer is not busy???


I have 512MB of ram, AthlonXP cpu, and the swap partition was mounted during 
boot.

I posted my STABLE dmesg, I can do it again if it would help, I can't get my 
current dmesg (don't have a serial console unless a palm pilot will work 
somehow)

thanks,
Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: fetch: multiple choices

[Bill Fenner]

>What on earth does this mean?
>
>>> mrtg-2.9.26b.tar.gz doesn't seem to exist in /tmp/distfiles/.
>>> Attempting to fetch from
>http://people.ee.ethz.ch/~oetiker/webtools/mrtg/pub/.
>fetch: mrtg-2.9.26b.tar.gz: Multiple Choices

It means the web server is behaving oddly.  Here's a patch that gives
you a chance of understanding what's going on; it makes fetch -v display
the returned page in this case.


Index: http.c
===
RCS file: /home/ncvs/src/lib/libfetch/http.c,v
retrieving revision 1.64
diff -u -r1.64 http.c
--- http.c  30 Oct 2002 15:01:29 -  1.64
+++ http.c  21 Nov 2002 17:46:39 -
@@ -1005,10 +1005,15 @@
/* all other cases: we got a redirect */
e = conn->err;
need_auth = 0;
+   if (!new) {
+   DEBUG(fprintf(stderr, "redirect with no new location\n"));
+   if ((f = _http_funopen(conn, chunked)) != NULL) {
+   _http_print_html(stderr, f);
+   }
+   }
_fetch_close(conn);
conn = NULL;
if (!new) {
-   DEBUG(fprintf(stderr, "redirect with no new location\n"));
break;
}
if (url != URL)


  Bill

Re: About gbde questions

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, "kai ouyang" writes:
>Hi,everybody,
>  I have some puzzles on the 'gbde' function.
>  I saw the gbde(4), I do not understand the 'cold' true meaning. My point 
>is that if the disk were stealed by somebody, he could not see anything in 
>the disk unless he knows the "pass-phrase". right?

Right.  By "cold disk" we mean that the pass-phrase and key-material
is not available.  A laptop which is only suspended does _not_ meet
this criteria.

>  In the first barrier, the manual said that "metadata" is necessary to 
>locate the lock-sector, I want to know how we get "metadata".

It is generated by gbde init.  If you don't specify a location it will
be stored in the first sector.

>The 'da1s1f' partition exists, but I do not mount it. I first try to test 
>'da0s1f', but the box info:"gbde: /dev/da0s1f: Device busy".

Yes, you want to newfs and mount /dev/da0s1f.bde

I think the "-l" is a mistake in the usage, it should be "-L".

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: DP2 Fatal Trap

[John Baldwin]

On 21-Nov-2002 Scott Sipe wrote:
> 
> First install of DP2 went crazy weird (posted earlier).  A minimal install 
> (just the minimal distribution) went fine and I could login but didn't really 
> try anything more than that.  Now the install went fine, the boot goes fine 
> (no errors that I can see) but when I log in I get:
> 
> 
> Fatal Trap 12: Page fault while in kernel mode
> fault virtual address = 0x89
> fault code= supervisor read, page not present
> IP= 0x8:0xc031f044
> SP= 0x10:0xd99a6c98
> FP= 0x10:0xd99a6cc0
> Code Segment  = base 0x0, limit 0xf, type 0x1b
>   = DPL0, pres 1, def32 1, gran 1 (<-- not 100% 
>sure of this
line)
> Processor eflags  = interrupt enabled, resume, IOPL=0
> Current Process   = 446 (tcsh)
> Trap Number   = 12
> Panic: Page Fault
> Syncing disks... panic: bwrite: buffer is not busy???
> 
> 
> I have 512MB of ram, AthlonXP cpu, and the swap partition was mounted during 
> boot.
> 
> I posted my STABLE dmesg, I can do it again if it would help, I can't get my 
> current dmesg (don't have a serial console unless a palm pilot will work 
> somehow)

Hmm, is this from a GENERIC kernel?

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Bluetooth questions

[Shizuka Kudo]

Hi all,

I just cvsup-ed in the latest Bluetooth stack and rebuild world/kernel. My bluetooth 
USB dongle
attached OK except with the following issue observed

1. The Mitsumi USB driver attached OK after I manually loaded "ng_ubt" and plugged in 
the dongle
2. If I loaded netgraph, ng_ubt at "loader" prompt and had the dongle plugged in 
already, the
system failed to attach. I could, however, un-plug & then re-insert the dongle to make 
the driver
attached successfully.

I haven't tested any functions yet, but will try tomorrow connecting to my mobile 
phone after
finding how to proceed. Here's the dmesg extract. If a full dmesg is required, I can 
attach it in
a separate message. By the way, the latest ACPI 20021118 diff from Wasaki-san works 
fine here with
a intel Celeron 1.2G on 815ep.

uhci0:  port 0xd000-0xd01f irq 11 at 
device 31.2 on
pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
wMaxPacketSize=49;
nframes=6, buffer size=294
ubt0: Could not create Netgraph node
device_probe_and_attach: ubt0 attach returned 6
ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
wMaxPacketSize=49;
nframes=6, buffer size=294
ubt0: Could not create Netgraph node
device_probe_and_attach: ubt0 attach returned 6
ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
wMaxPacketSize=49;
nframes=6, buffer size=294
ubt0: Could not create Netgraph node
device_probe_and_attach: ubt0 attach returned 6   <--- ubt0 failed to attach
ugen0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2  <--- fall back to ugen0

...

start_init: trying /sbin/init
splash: image decoder found: logo_saver
ugen0: at uhub0 port 2 (addr 2) disconnected  <--- I unplugged the dongle 
after bootup
ugen0: detached
ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2   <--- dongle re-inserted and 
attached
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
wMaxPacketSize=49;
nframes=6, buffer size=294



__
Do you Yahoo!?
Yahoo! Mail Plus – Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Compiling -CURRENT and PCMCIA support.

[Ryan Sommers]

?On Tue, 2002-11-19 at 22:13, Ryan Sommers wrote:
> My question is could I keep and build the CURRENT source tree on the
> FreeBSD desktop, mount it over NFS to the laptop, and install it over
> the NFS mount? 

Is the kernel on the 5.0SP2 ISO built with PCCard support? I installed
from CD-ROM onto a Compaq laptop only to notice nothing about the PCMCIA
Ethernet card I had in the dmesg output. I saw the PCCARD Support
section of the release notes and I'm wondering if this has anything to
do with it.

I'm probably going to have to compile a kernel with either the OLDCARD
support or some other options so my next question, is it possible to
build a -CURRENT kernel on 4.7? I'm getting the following when I tried
to build a kernel for the laptop on my 4.7 workstation. Note: I
installed net/cvsup-mirror and then fetched current with the following
supfile and all of this is run as my cvs user:

*default host=localhost

*default prefix=/usr/home/cvs/
*default base=/usr/home/cvs/
*default release=cvs delete use-rel-suffix
*default tag=.

#cvs-all
src-all



bash-2.05a$ uname -a
FreeBSD lobo 4.7-RELEASE FreeBSD 4.7-RELEASE #5: Fri Nov  8 15:29:17 CST
2002 ryans@lobo:/usr/obj/usr/src/sys/LOBO  i386
bash-2.05a$ make buildkernel KERNCONF=LAPTOP MAKEOBJDIRPREFIX=~
make: no target to make.
"/usr/home/cvs/src/Makefile.inc1", line 141: warning: "make -f /dev/null
-m /usr/home/cvs/src/share/mk  CPUTYPE=dummy -V CPUTYPE" returned
non-zero status

--
>>> Kernel build for LAPTOP started on Thu Nov 21 09:37:05 CST 2002
--
===> LAPTOP
mkdir -p /usr/home/cvs/usr/home/cvs/src/sys
cd /usr/home/cvs/src/sys/i386/conf; 
PATH=/usr/home/cvs/usr/home/cvs/src/i386/usr/sbin:/usr/home/cvs/usr/home/cvs/src/i386/usr/bin:/usr/home/cvs/usr/home/cvs/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/home/cvs/usr/home/cvs/src/sys/LAPTOP  
/usr/home/cvs/src/sys/i386/conf/LAPTOP
../../conf/files: coda/coda_fbsd.c must be optional, mandatory or
standard
Your version of config(8) is out of sync with your kernel source.
*** Error code 1

Stop in /usr/home/cvs/src.
*** Error code 1

Stop in /usr/home/cvs/src.
bash-2.05a$

Ryan.

-- 
Ryan "leadZERO" Sommers
[EMAIL PROTECTED]
ICQ: 1019590   AIM/MSN: leadZERO




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Scott Sipe]

On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
> Hmm, is this from a GENERIC kernel?

This is from straight from DP2 iso image cd install, X-Developer install, 
first boot after the install finished, generic kernel etc.

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[John Baldwin]

On 21-Nov-2002 Scott Sipe wrote:
> On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
>> Hmm, is this from a GENERIC kernel?
> 
> This is from straight from DP2 iso image cd install, X-Developer install, 
> first boot after the install finished, generic kernel etc.

Ok, generic kernel is the only really important part. :)  Can you
do me a favor and see if you have a /boot/kernel.GENERIC/kernel.debug
or a /boot/kernel/kernel.debug?  If so, can you please do
'gdb -k kernel.debug' and then at the prompt do 'l *'
where  is the second part of the instruction pointer
from the panic message?  (I.e., w/o the leading '0x8:' part.)

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Cross-Development with NetBSD

[Terry Lambert]

Ruslan Ermilov wrote:
> On Thu, Nov 21, 2002 at 12:10:14AM -0700, M. Warner Losh wrote:
> > In message: <[EMAIL PROTECTED]>
> > "Wilkinson,Alex" <[EMAIL PROTECTED]> writes:
> > : Is FreeBSD likely to follow the in footsteps of NetBSD and create
> > : a framework to do crossbuilds ?
> > :
> > : http://ezine.daemonnews.org/200211/xdevnetbsd.html
> >
> > FreeBSD already has cross builds for a while, since before NetBSD's
> > cross build infrastructure.  However, NetBSD's infrastructure is a
> > little more extensive because it is possible to do incremental builds
> > and build full releases that work in a cross build evironment.
>
> What do you mean by "incremental builds and full releases that work ..."?

You know, like changing one line in /usr/src/lib/libstand on
a source tree on a x86 box, typing "make release", and having
only the things that need to be rebuilt being rebuilt, resulting
in a working FreeBSD-Alpha or FreeBSD-SPARC64 release CDROM image.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Debugging kernel panic, routetbl

[Craig Rodrigues]

Hi,

Can someone give me some ideas for how to debug a kernel
panic and isolate where the problem could be?

I've been trying out the Netgraph ATM stuff for a while,
and things have been working fine for a number of weeks.
However, when I cvsup'd -CURRENT from a few days ago,
I have one of my machines crashing after
route add is called on my ATM card.

The crash I am getting is soon after the ATM card is initialized
with ifconfig, and route add is called.  This did not happen before,
and the ATM driver source that I am using has worked fine for weeks.

ddb gives me this message:

Memory modified after free 0x1383600(252)
panic: Most recently used by routetbl


And gdb over a serial port gives me this:

GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you ar=
e
welcome to change it and/or distribute copies of it under certain condition=
s.
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-undermydesk-freebsd"...
(kgdb) target /dev remote /dev/cuaa0
Remote debugging using /dev/cuaa0
Debugger (msg0x12 )
at /usr/src/sys/i386/i386/db_interface.c:323
323 }
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
(kgdb) where
#0  Debugger (msg0x12 )
at /usr/src/sys/i386/i386/db_interface.c:323
#1  0xc031892b in panic (fmt0x1 )
at /usr/src/sys/kern/kern_shutdown.c:503
#2  0xc035b4b7 in bremfree (bp0xc2426868) at /usr/src/sys/kern/vfs_bio.c=
:632
#3  0xc035deb0 in getblk (vp0xc1368000, blkno196864, size16384, sl=
pflag0, 
slptimeo0) at /usr/src/sys/kern/vfs_bio.c:2344
#4  0xc035b5ea in breadn (vp0xc1368000, blkno137438953490, size18,=
 
rablkno0x0, rabsize0x0, cnt0, cred0x0, bpp0x12)
at /usr/src/sys/kern/vfs_bio.c:690
#5  0xc035b59c in bread (vp0x12, blkno137438953490, size18, cred=
0x12, 
bpp0x12) at /usr/src/sys/kern/vfs_bio.c:672
#6  0xc043a256 in ffs_update (vp0xc1367000, waitfor0)
at /usr/src/sys/ufs/ffs/ffs_inode.c:102
#7  0xc044dc5f in ffs_fsync (ap0xc5bbdb10)
at /usr/src/sys/ufs/ffs/ffs_vnops.c:315
#8  0xc044cece in ffs_sync (mp0xc135e000, waitfor2, cred0xc09f6e00=
, 
td0xc0577100) at vnode_if.h:612
#9  0xc036f308 in sync (td0xc0577100, uap0x0)
at /usr/src/sys/kern/vfs_syscalls.c:138
#10 0xc031830c in boot (howto256) at /usr/src/sys/kern/kern_shutdown.c:2=
73
#11 0xc0318943 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#12 0xc04738bd in mtrash_ctor (mem0xc13e2d00, size32, arg0x0)
at /usr/src/sys/vm/uma_dbg.c:138
#13 0xc04722d7 in uma_zalloc_arg (zone0xc09d0140, udata0x0, flags0=
)
at /usr/src/sys/vm/uma_core.c:1358
#14 0xc030d0c6 in malloc (size4, type0xc05783e0, flags0)
at /usr/src/sys/kern/kern_malloc.c:182
#15 0xc02fbd35 in fdcopy (td0x12) at /usr/src/sys/kern/kern_descrip.c:12=
65
#16 0xc0304140 in fork1 (td0xc0a0c540, flags20, pages0, procp0x=
c5bbdcd4)
at /usr/src/sys/kern/kern_fork.c:446
#17 0xc0303872 in fork (td0xc0a0c540, uap0xc5bbdd10)
at /usr/src/sys/kern/kern_fork.c:122
#18 0xc04a763e in syscall (frame
  {tf_fs  47, tf_es  47, tf_ds  47, tf_edi  0, tf_esi  1=
35254016, tf_ebp  -1077937816, tf_isp  -977543820, tf_ebx  0, tf_e=
dx  672047128, tf_ecx  3, tf_eax  2, tf_trapno  12, tf_err  =
2, tf_eip  134723747, tf_cs  31, tf_eflags  514, tf_esp  -10779=
37860, tf_ss  47})
at /usr/src/sys/i386/i386/trap.c:1033
#19 0xc049704d in Xint0x80_syscall () at {standard input}:140
#20 0x0804b326 in ?? ()
#21 0x0804ae8f in ?? ()
#22 0x0804aed7 in ?? ()
#23 0x0804aed7 in ?? ()
#24 0x0804b2a1 in ?? ()
#25 0x0804aeff in ?? ()
#26 0x0804aed7 in ?? ()
#27 0x0804bf6e in ?? ()
#28 0x0804af71 in ?? ()
#29 0x0804add9 in ?? ()
#30 0x0804b18d in ?? ()
#31 0x0804aef1 in ?? ()
#32 0x0804aed7 in ?? ()
#33 0x0804add9 in ?? ()
#34 0x0804add9 in ?? ()
#35 0x0804add9 in ?? ()
#36 0x0804b2a1 in ?? ()
#37 0x0804aeff in ?? ()
#38 0x08053767 in ?? ()
#39 0x0805364b in ?? ()
#40 0x0804814c in ?? ()
(kgdb) detach
Ending remote debugging.
(kgdb) quit

Script done on Wed Nov 20 04:13:05 2002

-- 
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: smbfs problems

[Terry Lambert]

[ ... smbfs ... ]

Vallo Kallaste wrote:
> Now the writing part:
> 
> After creating 5MB file using /dev/urandom, I'm trying to copy it
> over to users/vallo smb share mounted at /mnt, which fails. The copy
> is interruptible using Ctrl-C. Examination at NT4 server shows 0
> byte file. Umount of /mnt fails with device busy. Umount -f /mnt
> fails to return prompt, but after interrupting the smbfs is
> unmounted.  There is no kernel messages or something in syslog. The
> copy operation returns failure ~3 seconds after start.

Try using 'dd' instead of 'cp', or the patch I posted last night.

The "shows 0 byte file" is a normal artifact of how file
metadata is handled in Windows filesystems: unlike UNIX, a
partial file does not have the metadata, including the file
size, updated until the file is closed.  Therefore FTP restart
is pretty meaningless on Windows, unless you have an FTP client
that closes and reopens for writing the file it is transferring
at intervals, among other things -- one of which is that any
interrupted create operation will leave a 0 length file.

I don't know why your umount fails with "device busy"; what you
need to do is look at the connections which are open, and why it
cares about whether or not they are abandoned, in the unmount
case.  I rather expect that the connection(s) are jammed up, so
you can't close them so you have virtual circuit instances that
you can't get rid of.  I would expect even a "force" to take
whatever time it takes to dump the open handles, plus 2MSL plus
however much time it keeps the connection in the half-close
state, waiting for a FIN/ACK from the server.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

mbuf header bloat ?

[Luigi Rizzo]

[Bcc to -net because it is relevant there. This email has been
triggered by a private discussion i was having with other committers
(who will easily recognise themselves :) which suggested the
possibility of adding more fields to mbuf headers]

Just recently came up to my attention that we have the following
code in 

#define MAC_MAX_POLICIES4
struct label {
int l_flags;
union {
void*l_ptr;
long l_long;
}   l_perpolicy[MAC_MAX_POLICIES];
};

(what are l_perpolicy[], ints ? Could this be written a bit better ?)
and then in 

struct pkthdr {
struct  ifnet *rcvif;   /* rcv interface */
int len;/* total packet length */
/* variables for ip and tcp reassembly */
void*header;/* pointer to packet header */
/* variables for hardware checksum */
int csum_flags; /* flags regarding checksum */
int csum_data;  /* data field used by csum routines */
SLIST_HEAD(packet_tags, m_tag) tags; /* list of packet tags */
struct  label label;/* MAC label of data in packet */  
};
 
The label is 5 ints, the pkthdr a total of 11 ints (and m_hdr takes
another 6, for a total of 136 bytes of header info on 64-bit architectures).

Of the pkthdr, only 3 fields (rcvif, len, tags) are of really general
use, the rest being used only in certain cases and for very specific
purposes (e.g. reassembly of fragments, or hw capabilities, or MAC).

Now that Sam has done the excellent work of integrating packet tags
to carry annotations around, i really believe that we should try
to move out of the pkthdr all non-general fields, and move them to
m_tags so we only pay the cost when needed and not in all cases.
Also this pays a lot in terms of ABI compatibility and extensibility.
I understand that for 5.0 it is a bit late to act, but i do hope
that we can reconsider this issue for 5.1 and pull out of the pkthdr
at least the MAC label, and possibly also the csum_* fields, much
in the same way it has been done for VLAN labels.

cheers
luigi

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: smbfs problems

[Terry Lambert]

Vallo Kallaste wrote:
> Sorry forgot to add one detail. Althought dd'ing the same file to
> smbfs mount works, it'll sometimes modify the file being copied
> (size is different). It doesn't happen reliably, sometimes the file
> is copied fine, sometimes not. At the times the file isn't copied
> right there's an error message:
> 
> root:vallo# dd if=testfile of=/mnt/vallo/test1
> dd: /mnt/vallo/test1: Bad address
> 9356+0 records in
> 9355+0 records out
> 4789760 bytes transferred in 20.350003 secs (235369 bytes/sec)
> 
> It seems to me that adding conv=sync flag to dd removes the
> abovementioned failure case. 10 tries of dd with this flag added did
> fine.

The 'conv-sync' flag to 'dd' pads the operation out to a record
boundary, if the input of the operation is not a full record in
length.

This observation is consistent with an incomplete final write,
for lack of data.  Probably this has to do with the TCP_PUSH
option and/or the SMB server's connection flags.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Bluetooth questions

[Maksim Yevmenkin]

Hello,

Shizuka Kudo wrote:
> 
> Hi all,
> 
> I just cvsup-ed in the latest Bluetooth stack and rebuild world/kernel. My bluetooth 
>USB dongle
> attached OK except with the following issue observed
> 
> 1. The Mitsumi USB driver attached OK after I manually loaded "ng_ubt" and plugged 
>in the dongle

good :)

> 2. If I loaded netgraph, ng_ubt at "loader" prompt and had the dongle plugged in 
>already, the
> system failed to attach. I could, however, un-plug & then re-insert the dongle to 
>make the driver
> attached successfully.

hmm... i have not tried that. will try today. i have kernel
compiled with 'options NETGRAPH'. everything works just fine
if i load ng_ubt from loader prompt and boot with dongle
attached. 
 
> I haven't tested any functions yet, but will try tomorrow connecting to my mobile 
>phone after
> finding how to proceed. Here's the dmesg extract. If a full dmesg is required, I can 
>attach it in
> a separate message. By the way, the latest ACPI 20021118 diff from Wasaki-san works 
>fine here with
> a intel Celeron 1.2G on 815ep.
> 
> uhci0:  port 0xd000-0xd01f irq 11 at 
>device 31.2 on
> pci0
> usb0:  on uhci0
> usb0: USB revision 1.0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2
> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
>wMaxPacketSize=49;
> nframes=6, buffer size=294
> ubt0: Could not create Netgraph node
> device_probe_and_attach: ubt0 attach returned 6

hmm... device was detected but driver failed to create 
Netgraph node. i wonder if it is an ordering issue. perhaps
Netgraph was not initialized at this point yet?

> ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2
> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
>wMaxPacketSize=49;
> nframes=6, buffer size=294
> ubt0: Could not create Netgraph node
> device_probe_and_attach: ubt0 attach returned 6
> ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2
> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
>wMaxPacketSize=49;
> nframes=6, buffer size=294
> ubt0: Could not create Netgraph node
> device_probe_and_attach: ubt0 attach returned 6   <--- ubt0 failed to attach

you will see this three times, because USB tries to find
driver for each of the three interfaces on the dongle.

> ugen0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2  <--- fall back to ugen0

yep. ugen takes everything :)
 
> start_init: trying /sbin/init
> splash: image decoder found: logo_saver
> ugen0: at uhub0 port 2 (addr 2) disconnected  <--- I unplugged the dongle 
>after bootup
> ugen0: detached
> ubt0: Mitsumi product 0x641f, rev 1.10/1.14, addr 2   <--- dongle re-inserted and 
>attached
> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; 
>wMaxPacketSize=49;
> nframes=6, buffer size=294

ok this looks good. at this point everything was initalized
and driver was able to detect and attach the dongle.

max.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Cross-Development with NetBSD

[John Baldwin]

On 21-Nov-2002 Terry Lambert wrote:
> Ruslan Ermilov wrote:
>> On Thu, Nov 21, 2002 at 12:10:14AM -0700, M. Warner Losh wrote:
>> > In message: <[EMAIL PROTECTED]>
>> > "Wilkinson,Alex" <[EMAIL PROTECTED]> writes:
>> > : Is FreeBSD likely to follow the in footsteps of NetBSD and create
>> > : a framework to do crossbuilds ?
>> > :
>> > : http://ezine.daemonnews.org/200211/xdevnetbsd.html
>> >
>> > FreeBSD already has cross builds for a while, since before NetBSD's
>> > cross build infrastructure.  However, NetBSD's infrastructure is a
>> > little more extensive because it is possible to do incremental builds
>> > and build full releases that work in a cross build evironment.
>>
>> What do you mean by "incremental builds and full releases that work ..."?
> 
> You know, like changing one line in /usr/src/lib/libstand on
> a source tree on a x86 box, typing "make release", and having
> only the things that need to be rebuilt being rebuilt, resulting
> in a working FreeBSD-Alpha or FreeBSD-SPARC64 release CDROM image.

Make release is a very poor example b/c make release goes to great
efforts to create a clean-room environment for a release.  make
rerelease is quite helpful though and does do what you want to
restart a previous release. :)  Also, make buildworld -DNOCLEAN
isn't too shabby, though if I could do make TARGET_ARCH=alpha
everything I would prefer that.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Cross-Development with NetBSD

[Terry Lambert]

Ruslan Ermilov wrote:
> > NetBSD builds a directory full of tools that you can later use to
> > incrementally build, say, 'ls' or 'cat' because one can define
> > USETOOLS to be 'yes' and have the make automatically pick them up when
> > rebuilding.  There are a few of the details I'm a little unclear on,
> > but that's the jist of it.
>
> We also can, this just requires a few really tiny tweaks to Makefile.inc1,
> and I've posted them already some time ago -- basically, for each architecture
> you should build the subset of buildworld targets (WMAKE_TGTS), up to and
> including _libraries (if you want to build roughly any bit later), and
> them you can ``make {depend|all} SUBDIR_OVERRIDE=bin/cat'' for each of
> the desired TARGET_ARCH.

Any ETA on when this will be committed?


> I know that the Alpha and sparc64 binaries produced on i386 work.

I thought that the Alpha boot blocks ended up too large in the
cross-build case?  They did, last time I tried it.


> I know that cross-compiling i386 on either Alpha or sparc64 is
> broken (GCC sometimes produces different assembler output than
> the native compiler).  I lack the necessary hardware to actually
> test/fix the issues with cross-releases.

I don't think he was attacking you, personally, to ask you to
fix the problem, I think he was just noting the problem exists.


One thing that would help a lot -- and probably be helpful in
general -- would be a binary compare tool that ignored date
stamps in things like libraries, tar images, etc., so that you
could compare where things differ, easily, allowing someone to
track down differences.

It would be helpful in general to be able to compare what you
built vs. a release version, to assemble binary only delta lists,
for preparations for upgrade tools, etc..

I keep meaning to do this, but I really don't want to have to
release the tool under the GPL, if I don't have to.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: recommended VAIO for ACPI hacking (Re: cvs commit:www/en/releases/5.0R todo.sgml)

[Terry Lambert]

Mitsuru IWASAKI wrote:
> > > Also, development resources are limited.  For example, none of ACPI
> > > developers has VAIO.
> >
> > Well, I don't know enough to be a developper but I do have a VAIO (Z600TEK)
> > and can test things. Just ask.
> 
> BTW, I'm planning to buy VAIO (maybe used one) to improve ACPI support.
> Any recommendations?

While I personally want you to buy a PCG-XG29 (what I have 8-)),
I think the most problems have been reported on the Z505 and
Z5xx series.

If you are going to buy used, the Z5?? and PCG-XG2? (especially
the PCG-XG28, not 29) are probably what will be available to you.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Terry Lambert]

John Baldwin wrote:
> On 21-Nov-2002 Scott Sipe wrote:
> > On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
> >> Hmm, is this from a GENERIC kernel?
> >
> > This is from straight from DP2 iso image cd install, X-Developer install,
> > first boot after the install finished, generic kernel etc.
> 
> Ok, generic kernel is the only really important part. :)  Can you
> do me a favor and see if you have a /boot/kernel.GENERIC/kernel.debug
> or a /boot/kernel/kernel.debug?  If so, can you please do
> 'gdb -k kernel.debug' and then at the prompt do 'l *'
> where  is the second part of the instruction pointer
> from the panic message?  (I.e., w/o the leading '0x8:' part.)

It's the PSE and PGE, John.  Are you sure you won't agree to
not disclose, so I can tell you what's happening?

Bosko has a patch which he will give you if you ask him for it
that (mostly) works around the problem.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[John Baldwin]

On 21-Nov-2002 Terry Lambert wrote:
> John Baldwin wrote:
>> On 21-Nov-2002 Scott Sipe wrote:
>> > On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
>> >> Hmm, is this from a GENERIC kernel?
>> >
>> > This is from straight from DP2 iso image cd install, X-Developer install,
>> > first boot after the install finished, generic kernel etc.
>> 
>> Ok, generic kernel is the only really important part. :)  Can you
>> do me a favor and see if you have a /boot/kernel.GENERIC/kernel.debug
>> or a /boot/kernel/kernel.debug?  If so, can you please do
>> 'gdb -k kernel.debug' and then at the prompt do 'l *'
>> where  is the second part of the instruction pointer
>> from the panic message?  (I.e., w/o the leading '0x8:' part.)
> 
> It's the PSE and PGE, John.  Are you sure you won't agree to
> not disclose, so I can tell you what's happening?
> 
> Bosko has a patch which he will give you if you ask him for it
> that (mostly) works around the problem.

DP2 shipped with DISABLE_PSE and DISABLE_PG_G in GENERIC.  I know
because I put them there.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Asking for tester (small patch to chown(8)/chgrp(1))

[David Schultz]

Thus spake Tim Robbins <[EMAIL PROTECTED]>:
> On Wed, Nov 20, 2002 at 01:27:43PM +0100, Alexander Leidinger wrote:
> 
> > On Tue, 19 Nov 2002 10:27:00 -0800
> > David Schultz <[EMAIL PROTECTED]> wrote:
> > 
> > > > > I'm concerned about the used character: "-r" is similiar to "-R"
> > > > 
> > > > Yes, `-r' would be a very poor choice for the reason you state.
> > > 
> > > Agreed, but the precedent has already been set by touch(1) and
> > > truncate(1).  If we're going to get it wrong some of the time, we
> > > might as well be consistent about it.
> > 
> > When we don't look at the fact that neither touch nor truncate operate
> > recursivly... what about changing touch and truncate to allow the
> > proposed -c (or -i) too and mark -r as deprecated (if it isn't covered
> > by a standard)?
> 
> I'd really rather that we didn't change this at all, even if it seems
> "inconsistent". Changing it would just lead to more confusion.
> 
> I am also against adding new options to chown to copy ownership from
> existing files.
> 
> Copy ownership:   chown `stat -f%Su file1` file2
> Copy group:   chgrp `stat -f%Sg file1` file2
> Copy both:chown `stat -f%Su:%Sg file1` file2
> 
> These could easily be made into shell functions or whatever...

Admittedly it *is* creeping featurism, but there's already
creeping featurism all over the place if you're going to be that
strict about it.  You might as well reimplement ls(1) as a shell
script and remove 30 of its 33 documented options.  I think -r is
a specific case that happens to be useful and convenient for
chown.  Most of this discussion has been bogged down in the choice
of option name, which is really silly.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Bluetooth questions

[Vladimir B.]

÷ Thu, 21.11.2002, × 22:28, Maksim Yevmenkin ÎÁÐÉÓÁÌ:

Another bluetooth question:

Is Nokia 6310(i) cell phone supported by FreeBSD bluetooth stack ?
(of course most interesting as cell modem)

What bluetooth adapters (USB/PCMCI/CF) known as work well with FreeBSD.

-- 
Vladimir B. Grebenschikov <[EMAIL PROTECTED]>
SWsoft Inc.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Vallo Kallaste]

On Thu, Nov 21, 2002 at 03:03:48PM -0500, John Baldwin
<[EMAIL PROTECTED]> wrote:

> > It's the PSE and PGE, John.  Are you sure you won't agree to
> > not disclose, so I can tell you what's happening?
> > 
> > Bosko has a patch which he will give you if you ask him for it
> > that (mostly) works around the problem.
> 
> DP2 shipped with DISABLE_PSE and DISABLE_PG_G in GENERIC.  I know
> because I put them there.

Is it any help to know that my problems on P4 stopped after enabling
DISABLE_PSE? Initially I had both of these enabled, but seems that
one is enough. Just FYI.
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[John Baldwin]

On 21-Nov-2002 Vallo Kallaste wrote:
> On Thu, Nov 21, 2002 at 03:03:48PM -0500, John Baldwin
> <[EMAIL PROTECTED]> wrote:
> 
>> > It's the PSE and PGE, John.  Are you sure you won't agree to
>> > not disclose, so I can tell you what's happening?
>> > 
>> > Bosko has a patch which he will give you if you ask him for it
>> > that (mostly) works around the problem.
>> 
>> DP2 shipped with DISABLE_PSE and DISABLE_PG_G in GENERIC.  I know
>> because I put them there.
> 
> Is it any help to know that my problems on P4 stopped after enabling
> DISABLE_PSE? Initially I had both of these enabled, but seems that
> one is enough. Just FYI.

If we can verify that DISABLE_PG_G has no effect then that would be
nice.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Scott Sipe]

On Thursday 21 November 2002 01:58 pm, John Baldwin wrote:
> On 21-Nov-2002 Scott Sipe wrote:
> > On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
> >> Hmm, is this from a GENERIC kernel?
> >
> > This is from straight from DP2 iso image cd install, X-Developer install,
> > first boot after the install finished, generic kernel etc.
>
> Ok, generic kernel is the only really important part. :)  Can you
> do me a favor and see if you have a /boot/kernel.GENERIC/kernel.debug
> or a /boot/kernel/kernel.debug?  If so, can you please do
> 'gdb -k kernel.debug' and then at the prompt do 'l *'
> where  is the second part of the instruction pointer
> from the panic message?  (I.e., w/o the leading '0x8:' part.)

I am able to login as root (sh) in single user mode, but login as root on a 
normal boot dies (starting tcsh from single user mode traps too).

There is a file /boot/kernel/kernel.debug but when I do the gdb command (the 
l) it gives an error about no symbols, use the file command.  I did:
cd /boot/kernek
gdb -k kernel.debug
(in gdb)
l *0xc031f044

sorry if this is a stupid mistake on my part.

Secondly, I'm able to boot ok from the debug kernel.  I did "boot DEBUG" and I 
can then login as my user (tcsh) ok and can run X successfully.  I imagine I 
can recompile the kernel, would this be useful? (disabling PSE or the PGE 
options?)

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

alpha tinderbox failure

[Dag-Erling Smorgrav]

Thu Nov 21 13:00:11 PST 2002
...
U share/man/man8/Makefile
U share/man/man8/rc.8
U share/man/man8/rc.subr.8
? sys/alpha/conf/LINT
U sys/dev/amr/amr_pci.c
U sys/i386/acpica/acpi_machdep.c
U sys/kern/kern_proc.c
U sys/kern/sched_4bsd.c
U sys/modules/Makefile
cvs [update aborted]: cannot make directory include: File exists

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: /proc ( procfs ) DP2

[Kris Kennaway]

On Thu, Nov 21, 2002 at 03:44:08PM +0200, Vallo Kallaste wrote:
> On Thu, Nov 21, 2002 at 12:15:42AM -0800, Kris Kennaway
> <[EMAIL PROTECTED]> wrote:
> 
> > On Thu, Nov 21, 2002 at 08:36:19AM +0100, Christophe Yayon wrote:
> > > Hi all,
> > > 
> > > i am new to CURRENT, i have just installed DP2 and i saw that /proc is not
> > > mounted... Could i create in fstab and mount it or is it not necessary ?
> > 
> > You could if you like, but it's not necessary for most things (it's
> > omitted because it's historically a big security risk).
> 
> The OpenOffice suite crashes at startup without /proc mounted.
> OpenOffice docs say that /proc is only needed for initial install
> program and does not say it's needed afterwards. Still, it's needed.
> Am I missing something? In case it's unavoidable the docs should be
> modified.

You should probably ask the FreeBSD/OpenOffice developers.

Kris



msg47118/pgp0.pgp
Description: PGP signature

Re: DP2 Fatal Trap

[John Baldwin]

On 21-Nov-2002 Scott Sipe wrote:
> On Thursday 21 November 2002 01:58 pm, John Baldwin wrote:
>> On 21-Nov-2002 Scott Sipe wrote:
>> > On Thursday 21 November 2002 01:36 pm, John Baldwin wrote:
>> >> Hmm, is this from a GENERIC kernel?
>> >
>> > This is from straight from DP2 iso image cd install, X-Developer install,
>> > first boot after the install finished, generic kernel etc.
>>
>> Ok, generic kernel is the only really important part. :)  Can you
>> do me a favor and see if you have a /boot/kernel.GENERIC/kernel.debug
>> or a /boot/kernel/kernel.debug?  If so, can you please do
>> 'gdb -k kernel.debug' and then at the prompt do 'l *'
>> where  is the second part of the instruction pointer
>> from the panic message?  (I.e., w/o the leading '0x8:' part.)
> 
> I am able to login as root (sh) in single user mode, but login as root on a 
> normal boot dies (starting tcsh from single user mode traps too).
> 
> There is a file /boot/kernel/kernel.debug but when I do the gdb command (the 
> l) it gives an error about no symbols, use the file command.  I did:
> cd /boot/kernek
> gdb -k kernel.debug
> (in gdb)
> l *0xc031f044
> 
> sorry if this is a stupid mistake on my part.
> 
> Secondly, I'm able to boot ok from the debug kernel.  I did "boot DEBUG" and I 
> can then login as my user (tcsh) ok and can run X successfully.  I imagine I 
> can recompile the kernel, would this be useful? (disabling PSE or the PGE 
> options?)

Erm, well, PSE and PGE are already disabled in GENERIC on DP2.  Hmm.
Can you try doing gdb -k kernel.debug in multiuser under DEBUG and
see if gdb behaves any better?  Another idea might be to use addr2line
instead like so:

addr2line -e kernel.debug -f 0xc031f044

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcc 3.2.1 release import?

[David Schultz]

Thus spake David O'Brien <[EMAIL PROTECTED]>:
> On Wed, Nov 20, 2002 at 05:57:41PM +0100, Marc Recht wrote:
> > Hi!
> > 
> > Will gcc 3.2.1/release be imported before 5.0R ? Just curious..
> 
> There will be no more GCC imports before 5.0-R.  It is just too much code
> churn with too little "road testing" before 5.0-R.

As I recall, the original plan was to import GCC 3.3 for 5.0-R.
At the time, there were concerns about ABI changes between 3.2 and
3.3 that people wanted to get in before 5.0.  What is the new
plan?  GCC 3.3 for 5.1-R?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Call for testers: acpica-unix-20021118.tar.gz

[Juli Mallett]

* De: Mitsuru IWASAKI <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
[ Subjecte: Call for testers: acpica-unix-20021118.tar.gz ]
> Hi all,
> 
> I've made patches for the latest ACPI CA snapshot between 20021002 and
> 20021118.
> http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff
> 
> A lot of bugs are fixed, please check the change log at:
> http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt
> 
> Please test them and feedback to [EMAIL PROTECTED] if you find any
> problems.  I'll import them into src tree before RC1.

Well, my ACPI still doesn't work, here's a dmesg.  But I do now get a longer
error.

%%%
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #45: Thu Nov 21 15:36:15 CST 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/LUNA
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0547000.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 474888664 Hz
CPU: AMD-K6(tm) 3D processor (474.89-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
  Features=0x8021bf
  AMD Features=0x8800
real memory  = 67043328 (63 MB)
avail memory = 59457536 (56 MB)
Security policy loaded: TrustedBSD MAC/None (trustedbsd_mac_none)
Initializing GEOMetry subsystem
K6-family MTRR support enabled (2 registers)
acpi0:  on motherboard
ACPI-0483: *** Error: GPE0 block (GPE 0 to 15) overlaps the GPE1 block (GPE 0 to 
15)
acpi0: could not enable ACPI: AE_BAD_VALUE
device_probe_and_attach: acpi0 attach returned 6
npx0:  on motherboard
npx0: INT 16 interface
Using $PIR table, 6 entries at 0xc00fdf60
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
agp0:  mem 0xe000-0xe3ff at device 0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
cbb0:  mem 0x8800-0x88000fff irq 11 at device 4.0 on 
pci0
cardbus0:  on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb1:  mem 0x88001000-0x88001fff irq 11 at device 4.1 on 
pci0
cardbus1:  on cbb1
pccard1: <16-bit PCCard bus> on cbb1
isab0:  at device 7.0 on pci0
isa0:  on isab0
pcm0:  mem 0xfedf-0xfedf,0xfeddf000-0xfedd 
irq 5 at device 8.0 on pci0
atapci0:  port 0xfcf0-0xfcff at device 15.0 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0:  at device 16.0 (no driver attached)
pci0:  at device 17.0 (no driver attached)
ohci0:  mem 0xfedde000-0xfeddefff irq 9 at 
device 19.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0:  on ohci0
usb0: USB revision 1.0
uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
orm0:  at iomem 0xc-0xcb7ff on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
fdc0:  at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: parallel port not found.
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
fb0 at vga0
speaker0:  at port 0x61 on isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
psmcpnp0: irq resource info is missing; assuming irq 12
unknown:  can't assign resources (port)
Timecounters tick every 10.000 msec
wi0:  at port 0x100-0x13f irq 11 function 0 config 1 on pccard1
wi0: 802.11 address: 00:30:ab:14:0a:60
wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163-SST-flash
wi0: Intersil Firmware: Primary 0.03.00, Station 1.03.04
ad0: 4126MB  [8944/15/63] at ata0-master UDMA33
Mounting root from ufs:/dev/ad0s1a
%%%

Thanks,
juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: sparc64 tinderbox failure

[Kris Kennaway]

On Thu, Nov 21, 2002 at 09:20:41AM +, Mike Barcroft wrote:
> Thu Nov 21 09:15:00 GMT 2002
> ...
> U sys/kern/kern_thread.c
> U sys/kern/sched_4bsd.c
> U sys/modules/netgraph/bluetooth/bluetooth/Makefile
> U sys/modules/netgraph/bluetooth/bt3c/Makefile
> U sys/modules/netgraph/bluetooth/h4/Makefile
> U sys/modules/netgraph/bluetooth/hci/Makefile
> U sys/modules/netgraph/bluetooth/l2cap/Makefile
> U sys/modules/netgraph/bluetooth/socket/Makefile
> U sys/modules/netgraph/bluetooth/ubt/Makefile
> cvs [update aborted]: cannot make directory include: File exists

Looks like this (and the alpha tinderbox) needs manual intervention
following the bluetooth re-import (there was repo surgery after the
first failed import).

Kris



msg47122/pgp0.pgp
Description: PGP signature

Re: mbuf header bloat ?

[Andre Oppermann]

Luigi Rizzo wrote:
> 
> [Bcc to -net because it is relevant there. This email has been
> triggered by a private discussion i was having with other committers
> (who will easily recognise themselves :) which suggested the
> possibility of adding more fields to mbuf headers]
> 
> Just recently came up to my attention that we have the following
> code in 
> 
> #define MAC_MAX_POLICIES4
> struct label {
> int l_flags;
> union {
> void*l_ptr;
> long l_long;
> }   l_perpolicy[MAC_MAX_POLICIES];
> };
> 
> (what are l_perpolicy[], ints ? Could this be written a bit better ?)
> and then in 
> 
> struct pkthdr {
> struct  ifnet *rcvif;   /* rcv interface */
> int len;/* total packet length */
> /* variables for ip and tcp reassembly */
> void*header;/* pointer to packet header */
> /* variables for hardware checksum */
> int csum_flags; /* flags regarding checksum */
> int csum_data;  /* data field used by csum routines */
> SLIST_HEAD(packet_tags, m_tag) tags; /* list of packet tags */
> struct  label label;/* MAC label of data in packet */
> };
> 
> The label is 5 ints, the pkthdr a total of 11 ints (and m_hdr takes
> another 6, for a total of 136 bytes of header info on 64-bit architectures).
> 
> Of the pkthdr, only 3 fields (rcvif, len, tags) are of really general
> use, the rest being used only in certain cases and for very specific
> purposes (e.g. reassembly of fragments, or hw capabilities, or MAC).
> 
> Now that Sam has done the excellent work of integrating packet tags
> to carry annotations around, i really believe that we should try
> to move out of the pkthdr all non-general fields, and move them to
> m_tags so we only pay the cost when needed and not in all cases.
> Also this pays a lot in terms of ABI compatibility and extensibility.
> I understand that for 5.0 it is a bit late to act, but i do hope
> that we can reconsider this issue for 5.1 and pull out of the pkthdr
> at least the MAC label, and possibly also the csum_* fields, much
> in the same way it has been done for VLAN labels.

Sounds good to me.

-- 
Andre

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Bluetooth questions

[Maksim Yevmenkin]

Hello

Vladimir B. Grebenschikov" wrote:
> 
> ÷ Thu, 21.11.2002, × 22:28, Maksim Yevmenkin ÎÁÐÉÓÁÌ:
> 
> Another bluetooth question:
> 
> Is Nokia 6310(i) cell phone supported by FreeBSD bluetooth stack ?
> (of course most interesting as cell modem)

You have got to try it for yourself :) I have received
successful reports about Nokia 7650, so there is a
pretty good chance you can make it work :) You most 
likely can use your Bluetooth enabled cell phone as
a wireless modem. You need to download and install
rfcommd from ports/.

I have recently get Ericsson T68 and the basic stuff
works. I did not try wireless modem because I do not
have this service with my provider. It is still somewhat
expensive  +$8 a month + traffic.
 
> What bluetooth adapters (USB/PCMCI/CF) known as work well with FreeBSD.

USB dongles: 3COM, EPoX, Mitsumi, MSI and TDK. also
if your USB dongle has CSR chip in it then it pretty
much guaranteed to be supported.

PCCARD: 3COM and Xircom(*). Xircom card is a 16550A
UART based card and may not work very well because of
"sio" driver issues. The same is true for any 16550A
UART based card. However if you can convince your
system give separate IRQ for PCCARD and "sio" driver
uses fast interrupts then this card might work well
for you. I managed to do so on my not so -current
and OLDCARD.

max


 
> --
> Vladimir B. Grebenschikov <[EMAIL PROTECTED]>
> SWsoft Inc.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Why isn't NOCLEAN the default? (was: Re: Cross-Development with NetBSD)

[David Schultz]

Thus spake John Baldwin <[EMAIL PROTECTED]>:
> Make release is a very poor example b/c make release goes to great
> efforts to create a clean-room environment for a release.  make
> rerelease is quite helpful though and does do what you want to
> restart a previous release. :)  Also, make buildworld -DNOCLEAN
> isn't too shabby, though if I could do make TARGET_ARCH=alpha
> everything I would prefer that.

I have long wondered why NOCLEAN isn't the default.  There seem to
be a few cases where it doesn't DTRT for kernel builds, but it
seems a bit conservative to make incremental world builds require
that an undocumented variable be defined.  Any ideas?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: [acpi-jp 1961] Re: Call for testers: acpica-unix-20021118.tar.gz

[Moore, Robert]

>>ACPI-0483: *** Error: GPE0 block (GPE 0 to 15) overlaps the GPE1 block
(GPE 0 to 15)

It appears that in your machine's FADT:
 
1) There is a GPE1 block defined (GPE1_BLK, GPE1_BLK_LEN)
2) The GPE1_BASE is set to zero.

One of these is wrong.

Bob


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Call for testers: acpica-unix-20021118.tar.gz

[John Baldwin]

On 21-Nov-2002 Juli Mallett wrote:
> * De: Mitsuru IWASAKI <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
>   [ Subjecte: Call for testers: acpica-unix-20021118.tar.gz ]
>> Hi all,
>> 
>> I've made patches for the latest ACPI CA snapshot between 20021002 and
>> 20021118.
>> http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff
>> 
>> A lot of bugs are fixed, please check the change log at:
>> http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt
>> 
>> Please test them and feedback to [EMAIL PROTECTED] if you find any
>> problems.  I'll import them into src tree before RC1.
> 
> Well, my ACPI still doesn't work, here's a dmesg.  But I do now get a longer
> error.
> 
> %%%
> Copyright (c) 1992-2002 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>   The Regents of the University of California. All rights reserved.
> FreeBSD 5.0-CURRENT #45: Thu Nov 21 15:36:15 CST 2002
> [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LUNA
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0547000.
> Timecounter "i8254"  frequency 1193182 Hz
> Timecounter "TSC"  frequency 474888664 Hz
> CPU: AMD-K6(tm) 3D processor (474.89-MHz 586-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
>   Features=0x8021bf
>   AMD Features=0x8800
> real memory  = 67043328 (63 MB)
> avail memory = 59457536 (56 MB)
> Security policy loaded: TrustedBSD MAC/None (trustedbsd_mac_none)
> Initializing GEOMetry subsystem
> K6-family MTRR support enabled (2 registers)
> acpi0:  on motherboard
> ACPI-0483: *** Error: GPE0 block (GPE 0 to 15) overlaps the GPE1 block (GPE 0 to 
>15)
> acpi0: could not enable ACPI: AE_BAD_VALUE
> device_probe_and_attach: acpi0 attach returned 6

Could you provide just the RSDT portion of your acpidump?  Specifically the
section that srts with DSDT= and includes INT_MODEL=, etc.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mbuf header bloat ?

[Archie Cobbs]

Luigi Rizzo wrote:
> Now that Sam has done the excellent work of integrating packet tags
> to carry annotations around, i really believe that we should try
> to move out of the pkthdr all non-general fields, and move them to
> m_tags so we only pay the cost when needed and not in all cases.
> Also this pays a lot in terms of ABI compatibility and extensibility.
> I understand that for 5.0 it is a bit late to act, but i do hope
> that we can reconsider this issue for 5.1 and pull out of the pkthdr
> at least the MAC label, and possibly also the csum_* fields, much
> in the same way it has been done for VLAN labels.

You got my vote :-)

-Archie

__
Archie Cobbs * Packet Design * http://www.packetdesign.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Searching for users of netncp and nwfs to help debug 5.0 problems

[Robert Watson]

The build of netncp is currently broken on 5.0-CURRENT, and I'd like to
see this fixed before 5.0-RELEASE.  Unfortunately, we're having a lot of
trouble finding a test environment, which is the natural and immediate
follow-on to the compile fixes :-).  Was wondering if anyone with FreeBSD
kernel debugging experience and some time on their hands was interested in
helping resolve this issue over the next week or two. 

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Searching for users of netncp and nwfs to help debug 5.0 problems

[Robert Watson]

On Thu, 21 Nov 2002, Robert Watson wrote:

> The build of netncp is currently broken on 5.0-CURRENT, and I'd like to
> see this fixed before 5.0-RELEASE.  Unfortunately, we're having a lot of
> trouble finding a test environment, which is the natural and immediate
> follow-on to the compile fixes :-).  Was wondering if anyone with
> FreeBSD kernel debugging experience and some time on their hands was
> interested in helping resolve this issue over the next week or two.

(And, you have to bring your own test environment, as the second sentence
suggests, but doesn't actually state).

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Scott Sipe]

On Thursday 21 November 2002 04:26 pm, John Baldwin wrote:
>
> Erm, well, PSE and PGE are already disabled in GENERIC on DP2.  Hmm.
> Can you try doing gdb -k kernel.debug in multiuser under DEBUG and
> see if gdb behaves any better?  Another idea might be to use addr2line
> instead like so:
>
> addr2line -e kernel.debug -f 0xc031f044

in gdb the line I get when I do l * is 'No symbol table is loaded.  Use the 
"file" command.' -- (multiuser too).  Am I doing something wrong?

addr2line displays:
getpeername1
/usr/src/sys/kern/uipc_syscalls.c:1453

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Why isn't NOCLEAN the default? (was: Re: Cross-Development with NetBSD)

[Kris Kennaway]

On Thu, Nov 21, 2002 at 02:02:20PM -0800, David Schultz wrote:
> Thus spake John Baldwin <[EMAIL PROTECTED]>:
> > Make release is a very poor example b/c make release goes to great
> > efforts to create a clean-room environment for a release.  make
> > rerelease is quite helpful though and does do what you want to
> > restart a previous release. :)  Also, make buildworld -DNOCLEAN
> > isn't too shabby, though if I could do make TARGET_ARCH=alpha
> > everything I would prefer that.
> 
> I have long wondered why NOCLEAN isn't the default.  There seem to
> be a few cases where it doesn't DTRT for kernel builds, but it
> seems a bit conservative to make incremental world builds require
> that an undocumented variable be defined.  Any ideas?

It often causes problems during upgrades (but is usually fine when
just rebuilding a non-updated tree)

Kris



msg47132/pgp0.pgp
Description: PGP signature

Re: gcc 3.2.1 release import?

[Harald Arnesen]

David Schultz <[EMAIL PROTECTED]> writes:

>> > Will gcc 3.2.1/release be imported before 5.0R ? Just curious..
>> 
>> There will be no more GCC imports before 5.0-R.  It is just too much code
>> churn with too little "road testing" before 5.0-R.
>
> As I recall, the original plan was to import GCC 3.3 for 5.0-R.
> At the time, there were concerns about ABI changes between 3.2 and
> 3.3 that people wanted to get in before 5.0.  What is the new
> plan?  GCC 3.3 for 5.1-R?

There is neither a gcc 3.2.1 nor a gcc 3.3 yet, so I would't use any of
them in a stable release.
-- 
Hilsen Harald.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Why isn't NOCLEAN the default? (was: Re: Cross-Development with NetBSD)

[David Schultz]

Thus spake Kris Kennaway <[EMAIL PROTECTED]>:
> > I have long wondered why NOCLEAN isn't the default.  There seem to
> > be a few cases where it doesn't DTRT for kernel builds, but it
> > seems a bit conservative to make incremental world builds require
> > that an undocumented variable be defined.  Any ideas?
> 
> It often causes problems during upgrades (but is usually fine when
> just rebuilding a non-updated tree)

Sounds reasonable.  Maybe it should be documented in build(7), though.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Call for testers: acpica-unix-20021118.tar.gz

[Juli Mallett]

* De: John Baldwin <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
[ Subjecte: Re: Call for testers: acpica-unix-20021118.tar.gz ]
> 
> On 21-Nov-2002 Juli Mallett wrote:
> > * De: Mitsuru IWASAKI <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
> >   [ Subjecte: Call for testers: acpica-unix-20021118.tar.gz ]
> >> Hi all,
> >> 
> >> I've made patches for the latest ACPI CA snapshot between 20021002 and
> >> 20021118.
> >> http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff
> >> 
> >> A lot of bugs are fixed, please check the change log at:
> >> http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt
> >> 
> >> Please test them and feedback to [EMAIL PROTECTED] if you find any
> >> problems.  I'll import them into src tree before RC1.
> > 
> > Well, my ACPI still doesn't work, here's a dmesg.  But I do now get a longer
> > error.
> > 
> > acpi0:  on motherboard
> > ACPI-0483: *** Error: GPE0 block (GPE 0 to 15) overlaps the GPE1 block (GPE 0 
>to 15)
> > acpi0: could not enable ACPI: AE_BAD_VALUE
> > device_probe_and_attach: acpi0 attach returned 6
> 
> Could you provide just the RSDT portion of your acpidump?  Specifically the
> section that srts with DSDT= and includes INT_MODEL=, etc.

DSDT=0x3ffbf77
INT_MODEL=PIC
SCI_INT=9
SMI_CMD=0xb1, ACPI_ENABLE=0xf0, ACPI_DISABLE=0xf1, S4BIOS_REQ=0x0
PM1a_EVT_BLK=0x1000-0x1003
PM1a_CNT_BLK=0x1004-0x1005
PM2_CNT_BLK=0x1030-0x1030
PM2_TMR_BLK=0x1008-0x100b
PM2_GPE0_BLK=0x1018-0x101b
P_LVL2_LAT=200ms, P_LVL3_LAT=2000ms
FLUSH_SIZE=0, FLUSH_STRIDE=0
DUTY_OFFSET=1, DUTY_WIDTH=3
DAY_ALRM=72, MON_ALRM=73, CENTURY=50
Flags={WBINVD,PROC_C1,SLP_BUTTON,TMR_VAL_EXT}

Thanks!
juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: [acpi-jp 1964] Re: Call for testers: acpica-unix-20021118.tar.gz

[Moore, Robert]

DSDT=0x3ffbf77
INT_MODEL=PIC
SCI_INT=9
SMI_CMD=0xb1, ACPI_ENABLE=0xf0, ACPI_DISABLE=0xf1, S4BIOS_REQ=0x0
PM1a_EVT_BLK=0x1000-0x1003
PM1a_CNT_BLK=0x1004-0x1005
PM2_CNT_BLK=0x1030-0x1030
PM2_TMR_BLK=0x1008-0x100b
PM2_GPE0_BLK=0x1018-0x101b
P_LVL2_LAT=200ms, P_LVL3_LAT=2000ms
FLUSH_SIZE=0, FLUSH_STRIDE=0
DUTY_OFFSET=1, DUTY_WIDTH=3
DAY_ALRM=72, MON_ALRM=73, CENTURY=50
Flags={WBINVD,PROC_C1,SLP_BUTTON,TMR_VAL_EXT}

Juli, John,

This is interesting that no GPE1 information shows up.

It may be the case that GPE1_BLK is zero, but GPE1_BLK_LEN is not zero in
the FADT.

According to the ACPI spec, only (GPE1_BLK == 0) indicates that there is no
GPE1 block;  It may be that if GPE1_BLK_LEN is non-zero, but GPE1_BLK is
zero, the CA code is not handling this correctly.  I will investigate and
report back.

Bob


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

cron fork bomb/hang -- more info

[Nate Lawson]

Just to recap, the system is running but cannot fork anymore procs.  This
means I can't login.  Cron does a make -j3 buildworld each night and it
appears this is triggering it.  Sys is uniprocessor.  Please let me know
if you need more info.

db> ps
  pid   proc addruid  ppid  pgrp  flag   stat  wmesgwchan  cmd
66984 c24efa80 cddf70000 1 1 800 norm[SLPQ  thrd_sleep
c0b740b4][SLP] init
66983 c24efc40 cddf80002 66982 66983 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66982 c24efe00 cddf90000   420   420 000 norm[SLPQ  ppwait
c24efe00][SLP] cron
66981 c24d5e00 cdca70002 66980 66981 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66980 c24d5c40 cdca60000   420   420 000 norm[SLPQ  ppwait
c24d5c40][SLP] cron
66979 c24d6000 cdca80002 66978 66979 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66978 c24c3540 cdb4a0000   420   420 000 norm[SLPQ  ppwait
c24c3540][SLP] cron
66977 c24c3700 cdb4b0002 66976 66977 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66976 c24c38c0 cdb4c0000   420   420 000 norm[SLPQ  ppwait
c24c38c0][SLP] cron
66975 c24c3a80 cdb4d0002 66973 66975 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66974 c24c3c40 cdb4e0000 66972 66974 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66973 c24c3e00 cdb4f0000   420   420 000 norm[SLPQ  ppwait
c24c3e00][SLP] cron
66972 c24d1000 cdc240000   420   420 000 norm[SLPQ  ppwait
c24d1000][SLP] cron
66971 c24d11c0 cdc250002 66970 66971 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66970 c24d1380 cdc980000   420   420 000 norm[SLPQ  ppwait
c24d1380][SLP] cron
66969 c24d1540 cdc990002 66968 66969 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66968 c24d1700 cdc9a0000   420   420 000 norm[SLPQ  ppwait
c24d1700][SLP] cron
66967 c24d18c0 cdc9b0002 66966 66967 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66966 c24d1a80 cdc9c0000   420   420 000 norm[SLPQ  ppwait
c24d1a80][SLP] cron
66965 c24d1c40 cdc9d0002 66964 66965 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
[... more pages of the same ...]
66780 c1a21000 cd37d0000   420   420 000 norm[SLPQ  ppwait
c1a21000][SLP] cron
66779 c1a2cc40 cd2f80002 66778 66779 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66778 c1b62e00 cd3c70000   420   420 000 norm[SLPQ  ppwait
c1b62e00][SLP] cron
66777 c1a2c380 cd2f30002 66776 66777 8000110 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cron
66776 c19d1700 cd3340000   420   420 000 norm[SLPQ  ppwait
c19d1700][SLP] cron
66775 c1e62c40 cd45e0000 66768  1431 0004000 norm[SLPQ  thrd_sleep
c0b740b4][SLP] as
66774 c1a21a80 cd3bc0000 66768  1431 800 norm[SLPQ ufs
c226168c][SLP] cc
66773 c19cda80 cd3190000 66769  1431 0004000 norm[SLPQ ufs
c220d1ec][SLP] as
66772 c19d1380 cd3320000 66769  1431 0004000 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cc1
66771 c1a2ca80 cd2f70000 66767  1431 800 norm[SLPQ  thrd_sleep
c0b740b4][SLP] cc
66770 c19cd8c0 cd3180000 66767  1431 0004000 norm[SLPQ ufs
c226168c][SLP] cc1
66769 c19271c0 cce490000 66766  1431 0004000 norm[SLPQwait
c19271c0][SLP] cc
66768 c1a2ce00 cd2f90000 66764  1431 0004000 norm[SLPQwait
c1a2ce00][SLP] cc
66767 c19d1540 cd3330000 66765  1431 0004000 norm[SLPQwait
c19d1540][SLP] cc
66766 c1b62000 cd3bf0000 66763  1431 0004000 norm[SLPQwait
c1b62000][SLP] sh
66765 c1e62e00 cd45f0000 66763  1431 0004000 norm[SLPQwait
c1e62e00][SLP] sh
66764 c1a21c40 cd3bd0000 66763  1431 0004000 norm[SLPQwait
c1a21c40][SLP] sh
66763 c1e62540 cd45a0000 42503  1431 0004000 norm[CVQ  select
c03c4fc4][SLP] make
42503 c19d18c0 cd3350000 42502  1431 0004000 norm[SLPQwait
c19d18c0][SLP] sh
42502 c1b621c0 cd3c0 37343  1431 0004000 norm[CVQ  select
c03c4fc4][SLP] make
37343 c1927380 cce4a0000 37337  1431 0004000 norm[SLPQwait
c1927380][SLP][SWAP] sh
37337 c19d1c40 cd3370000 17464  1431 0004000 norm[CVQ  select
c03c4fc4][SLP] make
17464 c19cd700 cd3170000 17459  1431 0004000 norm[SLPQwait
c19cd700][SLP][SWAP] sh
17459 c19cd380 cd3090000 17458  1431 0004000 norm[CVQ  select
c03c4fc4][SLP]
17458 c1a21e00 cd3be0000  1451  1431 0004000 norm[SLPQwait
c1a21e00][SLP][SWAP] sh
 1451 c19cd1c0 cd3080000  1450  1431 0004000 norm[CVQ  select
c03c4fc4][SLP] make
 1450 c19d11c0 cd3290000  1436  1431 0004000 norm[SLPQwait
c19d11c0][SLP][SWAP] sh
 1436 c19d1000 cd3280000  1433  1431 0004000 norm[CVQ  select
c03c4fc4][SLP] make
 1433 c1a2c540 cd2f40000  1431  1431 0004000 norm[SLPQwait
c1a2c540][SLP][SWAP] sh
 1431 c1924380 cce080000  1429  1431 0004000 norm[SLPQwait
c1924380][SLP][SWAP] sh
 1429 c19cde00 cd3270000   420   420 000 norm[SLPQ  piperd
c18aaa50][SLP] cron
  420 c19241c0 cce070000 1   420 000 norm[SLPQ  nanslp
c03f9bd4][SLP] cron

db> tr 66770
mi_switch(c1a2d410,50,c037b496,cc,1) at mi_switch+

Re: Searching for users of netncp and nwfs to help debug5.0 problems

[Brad Knowles]

At 5:23 PM -0500 2002/11/21, Robert Watson wrote:


 (And, you have to bring your own test environment, as the second sentence
 suggests, but doesn't actually state).


	Over on -chat, we're in the process of putting together a list of 
volunteers, hardware, organizational talent, etc... to help test out 
-DP2.  Mark Murray is involved, but I personally would like to see at 
least one or two more core team members committed to making this 
happen.

	If we can get a suitable group of people together, with suitable 
hardware, and get the coordination effort done correctly, I believe 
that we can help make this a much more successful project.


	Your assistance in this effort would be greatly appreciated.

--
Brad Knowles, <[EMAIL PROTECTED]>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E W+++(--) N+ !w---
O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: recommended VAIO for ACPI hacking (Re: cvs commit: www/en/releases/5.0R todo.sgml)

[Ollivier Robert]

According to Mitsuru IWASAKI:
> Thanks.

Here is the result. The first check is there and there are several others
in acpidump output. Full dump at



-=-=-=-
Method(_PTS, 1) {
If(LNot(LLess(Arg0, 0x2))) {
Store(0x1, \_SB_.PCI0.CRST)
}
Else {
Store(0x0, \_SB_.PCI0.CRST)
}
If(LEqual(Arg0, 0x4)) {
Store(\_SB_.PCI0.ISA_.SPIC._CRS(), \_SB_.PCI0.ISA_.SPIC.SSRC)
If(LEqual(SCMP(\_OS_, "Microsoft Windows NT"), Zero)) {
PHS_(0xe3)
PHS_(0xe5)
}
Else {
If(LNot(LEqual(SCMP(\_OS_, "Microsoft Windows"), Zero))) {
PHS_(0xe3)
PHS_(0xe5)
}
}
}
Return(0x0)
}
-=-=-=-
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun  4 22:44:19 CEST 2000

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Searching for users of netncp and nwfs to help debug5.0problems

[Julian Elischer]

As the person who broke it I'd like to help.. The problem was that it
referenced teh proc structure all over the place in several different
ways, and it was not obvious, without knowing the protocol which should
become thread references and which should stay proc references.

On Fri, 22 Nov 2002, Brad Knowles wrote:

> At 5:23 PM -0500 2002/11/21, Robert Watson wrote:
> 
> >  (And, you have to bring your own test environment, as the second sentence
> >  suggests, but doesn't actually state).
> 
>   Over on -chat, we're in the process of putting together a list of 
> volunteers, hardware, organizational talent, etc... to help test out 
> -DP2.  Mark Murray is involved, but I personally would like to see at 
> least one or two more core team members committed to making this 
> happen.
> 
>   If we can get a suitable group of people together, with suitable 
> hardware, and get the coordination effort done correctly, I believe 
> that we can help make this a much more successful project.
> 
> 
>   Your assistance in this effort would be greatly appreciated.
> 
> -- 
> Brad Knowles, <[EMAIL PROTECTED]>
> 
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
>  -Benjamin Franklin, Historical Review of Pennsylvania.
> 
> GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E W+++(--) N+ !w---
> O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
> tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Why isn't NOCLEAN the default?

[M. Warner Losh]

In message: <[EMAIL PROTECTED]>
David Schultz <[EMAIL PROTECTED]> writes:
: Thus spake John Baldwin <[EMAIL PROTECTED]>:
: > Make release is a very poor example b/c make release goes to great
: > efforts to create a clean-room environment for a release.  make
: > rerelease is quite helpful though and does do what you want to
: > restart a previous release. :)  Also, make buildworld -DNOCLEAN
: > isn't too shabby, though if I could do make TARGET_ARCH=alpha
: > everything I would prefer that.
: 
: I have long wondered why NOCLEAN isn't the default.  There seem to
: be a few cases where it doesn't DTRT for kernel builds, but it
: seems a bit conservative to make incremental world builds require
: that an undocumented variable be defined.  Any ideas?

Because the number of times that NOCLEAN screws you is high enough
that we don't want to hear the noise from novice users

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Searching for users of netncp and nwfs to help debug 5.0 problems

[Robert Watson]

On Fri, 22 Nov 2002, Brad Knowles wrote:

> At 5:23 PM -0500 2002/11/21, Robert Watson wrote:
> 
> >  (And, you have to bring your own test environment, as the second sentence
> >  suggests, but doesn't actually state).
> 
>   Over on -chat, we're in the process of putting together a list
> of volunteers, hardware, organizational talent, etc... to help test out
> -DP2.  Mark Murray is involved, but I personally would like to see at
> least one or two more core team members committed to making this happen. 
> 
>   If we can get a suitable group of people together, with suitable
> hardware, and get the coordination effort done correctly, I believe that
> we can help make this a much more successful project.
> 
>   Your assistance in this effort would be greatly appreciated. 

I appreciate the effort, and am interested in the idea, but in this case
it was as much a solicitation for a developer as for the testing
environment itself.  This won't just be "testing" of netncp and nwfs, this
will probably require a developer to have local access to a netware
configuration that they can do nasty things to in order to exercise the
code properly.  Unfortunately, those seem to be in short supply.

If I might suggest: there's a freebsd-qa mailing list.  It's a great place
to organize QA efforts, whereas freebsd-chat is notorious for its lack of
signal (it's where dead signals go to rot).  That's why I read it about
once a month.  If you moving the conversation there and get a bunch of
people subscribed and interested, they'll be able to look there for the
stream of bug fixes associated with the install process, and get easy
access to the testing guide as it evolves, since we usually pass drafts
through there, etc.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: smbfs install option questions

[Robert Watson]

In terms of where to take this: there are many reported problems with
smbfs on 5.0-CURRENT.  It's not clear whether this is left over from the
KSE imports, the Apple-derived fixes that might not have fixed things,
etc.  In any case, before we can look at smbfs install, we really need
smbfs working.  People who feel moved to debug this should feel free :-).

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

On Tue, 5 Nov 2002, David Yeske wrote:

> I got a smbfs install option working a while ago before drivers.flp came around, but 
>there was no
> space on the floppies.  Since drivers.flp came out, there is more space.  I was 
>wondering how I
> should go about making this usable, and which files should be on kern.flp, 
>mfsroot.flp,
> drivers.flp, or somewhere else.  Also I am generally looking for feedback...
> 
> The following patch is NOT up to date though.  The diff to GENERIC is NOT implying I 
>think GENERIC
> should be modifed.  I did that just to have those things added to GENERIC so they 
>would make it
> onto BOOTMFS.  The smbfs install option is based of the nfs install option, but it 
>does not use
> dns.
>  
> http://pigseye.kennesaw.edu/~dyeske/freebsd/smbfs_current.patch
> 
> http://pigseye.kennesaw.edu/~dyeske/freebsd/smbfs.c
> 
>  
> Regards,
> David Yeske
> 
> __
> Do you Yahoo!?
> HotJobs - Search new jobs daily now
> http://hotjobs.yahoo.com/
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-qa" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

5.0 DP2 on Vaio Z600

[Richard Tobin]

I'm trying to install DP2 on a Sony Vaio Z600TEK laptop, but it hangs
at "Probing devices, please wait (this can take a while)...".

It's not completely hung, in that I can switch to the second console
and back.  The last message there is

  DEBUG: Add mapping for /dev/cuaa0 to sl0

and this is after a bunch of errors about da0:umass-sim0 (the memory
stick slot, which doesn't have a card in it).

Changing the BIOS setting for PnP OS doesn't help.

I've been running 4.2 and 4.5 successfully.

Any suggestions?

-- Richard

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcc 3.2.1 release import?

[Marc Recht]

There is neither a gcc 3.2.1 nor a gcc 3.3 yet, so I would't use any of
them in a stable release.

gcc 3.2.1 has been uploaded on ftp.gnu.org at Nov. 19th.

Marc


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: [acpi-jp 1965] RE: Call for testers: acpica-unix-20021118.tar .gz

[Moore, Robert]

Unfortunately, the ACPI specification also says this:

"Each register block contains two registers of equal length: GPEx_STS and
GPEx_EN (where x is 0 or 1). The length of the GPE0_STS and GPE0_EN
registers is equal to half the GPE0_LEN. The length of the GPE1_STS and
GPE1_EN registers is equal to half the GPE1_LEN. If a generic register block
is not supported then its respective block pointer and block length values
in the FADT table contain zeros. The GPE0_LEN and GPE1_LEN do not need to be
the same size."


I guess that we will have to code it this way -- if EITHER the GPE1_BLK or
GPE1_BLK_LEN is zero, there is no GPE1.  Likewise with the GPE0 block.


Bob



-Original Message-
From: Moore, Robert [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, November 21, 2002 3:00 PM
To: '[EMAIL PROTECTED]'; John Baldwin
Cc: [EMAIL PROTECTED]; Mitsuru IWASAKI
Subject: [acpi-jp 1965] RE: Call for testers: acpica-unix-20021118.tar .gz



DSDT=0x3ffbf77
INT_MODEL=PIC
SCI_INT=9
SMI_CMD=0xb1, ACPI_ENABLE=0xf0, ACPI_DISABLE=0xf1, S4BIOS_REQ=0x0
PM1a_EVT_BLK=0x1000-0x1003
PM1a_CNT_BLK=0x1004-0x1005
PM2_CNT_BLK=0x1030-0x1030
PM2_TMR_BLK=0x1008-0x100b
PM2_GPE0_BLK=0x1018-0x101b
P_LVL2_LAT=200ms, P_LVL3_LAT=2000ms
FLUSH_SIZE=0, FLUSH_STRIDE=0
DUTY_OFFSET=1, DUTY_WIDTH=3
DAY_ALRM=72, MON_ALRM=73, CENTURY=50
Flags={WBINVD,PROC_C1,SLP_BUTTON,TMR_VAL_EXT}

Juli, John,

This is interesting that no GPE1 information shows up.

It may be the case that GPE1_BLK is zero, but GPE1_BLK_LEN is not zero in
the FADT.

According to the ACPI spec, only (GPE1_BLK == 0) indicates that there is no
GPE1 block;  It may be that if GPE1_BLK_LEN is non-zero, but GPE1_BLK is
zero, the CA code is not handling this correctly.  I will investigate and
report back.

Bob

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: recommended VAIO for ACPI hacking (Re: cvs commit: www/en/releases/5.0Rtodo.sgml)

[Nate Lawson]

On Fri, 22 Nov 2002, Ollivier Robert wrote:
> According to Mitsuru IWASAKI:
> > Thanks.
> 
> Here is the result. The first check is there and there are several others
> in acpidump output. Full dump at
> 
> 
> 
> -=-=-=-
> Method(_PTS, 1) {
> If(LNot(LLess(Arg0, 0x2))) {
> Store(0x1, \_SB_.PCI0.CRST)
> }
> Else {
> Store(0x0, \_SB_.PCI0.CRST)
> }
> If(LEqual(Arg0, 0x4)) {
> Store(\_SB_.PCI0.ISA_.SPIC._CRS(), \_SB_.PCI0.ISA_.SPIC.SSRC)
> If(LEqual(SCMP(\_OS_, "Microsoft Windows NT"), Zero)) {
> PHS_(0xe3)
> PHS_(0xe5)
> }
> Else {
> If(LNot(LEqual(SCMP(\_OS_, "Microsoft Windows"), Zero))) {
> PHS_(0xe3)
> PHS_(0xe5)
> }
> }
> }
> Return(0x0)
> }

I also have similar problems in my ASL from the IBM T23.
http://www.root.org/~nate/acpi/ibm.asl

Scope(\_SB_) {
Method(_INI) {
If(LEqual(\SCMP(\_OS_, "Microsoft Windows"), Zero)) {
Store(0x1, \W98F)
}
Else {
If(CondRefOf(_OSI, Local0)) {
If(\_OSI) {
"Windows 2001"
Store(0x2, \WNTF)
}
}
Else {
If(LEqual(\SCMP(\_OS_, "Microsoft Windows NT"), Zero)) {
Store(0x1, \WNTF)
}
Else {
If(LEqual(\SCMP(\_OS_, "Microsoft WindowsME: Millennium Edition"), 
Zero)) {
Store(0x1, \WMEF)
Store(0x1, \W98F)
}
}
}
}
If(LNot(LLess(\_REV, 0x2))) {
Store(0x1, \H8DR)
}
Store(0x1, \OSIF)
}

-Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: sparc64 tinderbox failure

[Mike Barcroft]

Kris Kennaway <[EMAIL PROTECTED]> writes:
> On Thu, Nov 21, 2002 at 09:20:41AM +, Mike Barcroft wrote:
> > Thu Nov 21 09:15:00 GMT 2002
> > ...
> > U sys/kern/kern_thread.c
> > U sys/kern/sched_4bsd.c
> > U sys/modules/netgraph/bluetooth/bluetooth/Makefile
> > U sys/modules/netgraph/bluetooth/bt3c/Makefile
> > U sys/modules/netgraph/bluetooth/h4/Makefile
> > U sys/modules/netgraph/bluetooth/hci/Makefile
> > U sys/modules/netgraph/bluetooth/l2cap/Makefile
> > U sys/modules/netgraph/bluetooth/socket/Makefile
> > U sys/modules/netgraph/bluetooth/ubt/Makefile
> > cvs [update aborted]: cannot make directory include: File exists
> 
> Looks like this (and the alpha tinderbox) needs manual intervention
> following the bluetooth re-import (there was repo surgery after the
> first failed import).

The sparc64 tinderbox should be fixed now.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Terry Lambert]

John Baldwin wrote:
> > It's the PSE and PGE, John.  Are you sure you won't agree to
> > not disclose, so I can tell you what's happening?
> >
> > Bosko has a patch which he will give you if you ask him for it
> > that (mostly) works around the problem.
> 
> DP2 shipped with DISABLE_PSE and DISABLE_PG_G in GENERIC.  I know
> because I put them there.

And dynamically tuned maxfiles?  Or a large static maxfiles?

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: DP2 Fatal Trap

[Terry Lambert]

John Baldwin wrote:
> > Is it any help to know that my problems on P4 stopped after enabling
> > DISABLE_PSE? Initially I had both of these enabled, but seems that
> > one is enough. Just FYI.
> 
> If we can verify that DISABLE_PG_G has no effect then that would be
> nice.

It has an effect: writing CR3 or a TSS resulting in a changed CR3
will not invalidate TLB entries with the G flag set, if PGE is set
in CR4.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0 DP2 on Vaio Z600

[Terry Lambert]

Richard Tobin wrote:
> I'm trying to install DP2 on a Sony Vaio Z600TEK laptop, but it hangs
> at "Probing devices, please wait (this can take a while)...".

[ ... ]

> Any suggestions?

Tell it to not load ACPI.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcc 3.2.1 release import?

[Terry Lambert]

Marc Recht wrote: 
> > There is neither a gcc 3.2.1 nor a gcc 3.3 yet, so I would't use any of
> > them in a stable release.
> gcc 3.2.1 has been uploaded on ftp.gnu.org at Nov. 19th.

So it's been extensively tested by the full user base for the
last two days, and you should have known about it before you
posted.  8-) 8-).

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

VM locking problem... And doscmd(8)

[Juli Mallett]

I'm getting a giant owned assertion failure in the vm_map code,
simply by running "doscmd something.exe" where something.exe is
a self-extracting ZIP file (of BIOS upgrade stuff, FWIW), which
leads trivially to tripping over it.  I still don't have a good
way to get the trace output from the box in question to here,
but I've been able to reproduce it every time, so it shouldn't
be hard for someone else.

I rebuilt my kernel today from CVSup, but hadn't tried before
that.

Thanks,
juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: About gbde questions

[kai ouyang]

Hi Everybody,

Poul-Henning Kamp write:

Right.  By "cold disk" we mean that the pass-phrase and key-material
is not available.  A laptop which is only suspended does _not_ meet
this criteria.

Thank you.

Yes, you want to newfs and mount /dev/da0s1f.bde
I think the "-l" is a mistake in the usage, it should be "-L".

you mean that I must newfs /dev/da0s1f again, but it is my '/var' 
partition.
And I do not find the '/dev/da0s1f.bde' in the '/dev/'. In DEVFS model, I 
do not know how to create a new device name in '/dev/'. And what is the 
'da0s1f.bde'?
I have some puzzles about 'newfs', 'gbde' should protect the whole disk. I 
do not know the relationship of the 'gbde' and the partition.

Best Regards
 Ouyang Kai




_
Ãâ·ÑÏÂÔØ MSN Explorer:  http://explorer.msn.com/lccn/ 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcc 3.2.1 release import?

[Marc Recht]

So it's been extensively tested by the full user base for the
last two days, and you should have known about it before you
posted.  8-) 8-).

My original question was only if it will be imported before 5.0R. David 
O'Brien already answered it with "no". That's fine with me.

Marc


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Weird 'ps aux' output in DP2

[Dhee Reddy]

Hello all.
When I run 'ps aux' I can see STARTED field having dates as 31Dec69 for
some processes. the (idle) process's TIME field also seems strange to me. 
The output is pasted below. 

---snip---
USERPID %CPU %MEM   VSZ  RSS  TT  STAT STARTED  TIME COMMAND
root 11 97.4  0.0 0   12  ??  RL   31Dec69 1300:56.54  (idle)
root 10  0.0  0.0 0   12  ??  DL   31Dec69   0:00.00  (ktrace)
root  1  0.0  0.4   696  244  ??  ILs  31Dec69   0:00.04 /sbin/init --
root 12  0.0  0.0 0   12  ??  WL   31Dec69   1:25.47  (swi1: net)
root 13  0.0  0.0 0   12  ??  WL   31Dec69   2:20.15  (swi6: tty:sio cl
root  2  0.0  0.0 0   12  ??  DL   31Dec69   0:08.93  (g_event)
root  3  0.0  0.0 0   12  ??  DL   31Dec69   0:08.86  (g_up)
root  4  0.0  0.0 0   12  ??  DL   31Dec69   0:11.06  (g_down)
root 15  0.0  0.0 0   12  ??  DL   31Dec69   0:18.86  (random)
root 18  0.0  0.0 0   12  ??  WL   31Dec69   0:03.09  (irq14: ata0)
root 20  0.0  0.0 0   12  ??  WL   31Dec69   3:35.29  (irq11: ed0)
root 21  0.0  0.0 0   12  ??  WL   31Dec69   0:01.64  (irq1: atkbd0)
root 22  0.0  0.0 0   12  ??  WL   31Dec69   0:00.00  (irq6: fdc0)
root 23  0.0  0.0 0   12  ??  WL   31Dec69   0:00.00  (irq7: ppc0)
root 24  0.0  0.0 0   12  ??  WL   31Dec69   0:00.02  (swi0: tty:sio)
root 27  0.0  0.0 0   12  ??  WL   31Dec69   0:07.78  (irq5: sbc0)
root  5  0.0  0.0 0   12  ??  DL   31Dec69   0:02.61  (pagedaemon)
root  6  0.0  0.0 0   12  ??  DL   31Dec69   0:00.00  (vmdaemon)
root  7  0.0  0.0 0   12  ??  DL   31Dec69   0:08.86  (pagezero)
root  8  0.0  0.0 0   12  ??  DL   31Dec69   0:00.91  (bufdaemon)
root  9  0.0  0.0 0   12  ??  DL   31Dec69   0:00.52  (vnlru)
root 31  0.0  0.0 0   12  ??  DL   31Dec69   0:38.27  (syncer)
root 32  0.0  0.0 0   12  ??  IL   31Dec69   0:00.00  (nfsiod 0)
root 33  0.0  0.0 0   12  ??  IL   31Dec69   0:00.00  (nfsiod 1)
root 34  0.0  0.0 0   12  ??  IL   31Dec69   0:00.00  (nfsiod 2)
root 35  0.0  0.0 0   12  ??  IL   31Dec69   0:00.00  (nfsiod 3)
root117  0.0  0.1   220   76  ??  Is   Wed05PM   0:00.00 adjkerntz -i
root228  0.0  1.1  1148  664  ??  Is   10:33PM   0:00.88 /usr/sbin/syslogd 
root400  0.0  2.2  2560 1332  ??  Is   10:33PM   0:03.00 /usr/sbin/sshd
root405  0.0  2.9  2996 1804  ??  Ss   10:33PM   0:06.97 sendmail: acceptin
smmsp   408  0.0  2.7  2900 1640  ??  Is   10:33PM   0:00.19 sendmail: Queue ru
root432  0.0  0.9  1116  548  ??  Is   10:33PM   0:00.08 /usr/sbin/moused -
root465  0.0  1.2  1208  756  ??  Is   10:33PM   0:01.24 /usr/sbin/cron
root475  0.0  1.1  1160  664  v2  Is+  10:33PM   0:00.02 /usr/libexec/getty
root476  0.0  1.1  1160  664  v3  Is+  10:33PM   0:00.02 /usr/libexec/getty
root477  0.0  1.1  1160  664  v4  Is+  10:33PM   0:00.02 /usr/libexec/getty
root479  0.0  1.1  1160  664  v5  Is+  10:33PM   0:00.02 /usr/libexec/getty
root480  0.0  1.1  1160  664  v6  Is+  10:33PM   0:00.02 /usr/libexec/getty
root481  0.0  1.1  1160  664  v7  Is+  10:33PM   0:00.02 /usr/libexec/getty
root   2279  0.0  1.5  1512  932  v1  Is   10:28AM   0:00.10 login -p dhee
dhee   3129  0.0  1.8  1520 1080  v1  I 5:11PM   0:00.18 -tcsh (tcsh)
dhee   3134  0.0  5.6  4324 3448  v1  S+5:12PM   7:47.45 BitchX irc.criten.
root   3557  0.0  1.7  1512 1032  v0  Is8:27PM   0:00.10 login -p root
root   3558  0.0  1.8  1524 1080  v0  S 8:27PM   0:00.20 -csh (csh)
root  0  0.0  0.0 0   12  ??  DLs  31Dec69   0:00.31  (swapper)
root   3583  0.0  0.5   632  304  v0  R+8:35PM   0:00.00 ps aux

---snip---

truely
-- 
dhee

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message