Melco LPC4-CLX-CB support in 5.0-Current NEWCARD
Dear all, Does anyone have tested whether this card works with current 5.0 NEWCARD? I tried it on a Thinkpad 600X with current 5.0 cvsupped yestersday and received a kernel: pccbb0: card inserted: event=0x, state=3920 kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] kernel: pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] kernel: found->vendor=0x10ec, dev=0x8138, revid=0x10 kernel: class=02-00-00, hrdtype=0x00, mfdev=0 kernel: cmdreg=0x, statreg=0x0290, cachelnsz=0 (dwords) kernel: lattimer=0xa8 (5040 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) kernel: intpin=a, irq=128 kernel: cardbus0: Expecting link target, got 0xff kernel: cardbus0: Resource not specified in CIS: id=10, size=100 kernel: cardbus0: Resource not specified in CIS: id=14, size=200 kernel: cardbus0: Non-prefetchable memory at 8400-840001ff kernel: cardbus0: Non-prefetable memory rid=14 at 8400-840001ff (200) kernel: cardbus0: IO port at 1000-10ff kernel: cardbus0: IO port rid=10 at 1000-10ff kernel: cardbus0: (vendor=0x10ec, dev=0x8138) at 0.0 irq 11. kernel: pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Any idea on how I can move forward? __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Melco LPC4-CLX-CB support in 5.0-Current NEWCARD
> "Shizuka" == Shizuka Kudo <[EMAIL PROTECTED]> writes: Shizuka> Does anyone have tested whether this card works with current 5.0 Shizuka> NEWCARD? I already tested it on NEWCARD. Melco LPC4-CLX-CB is using Realtek's chip. So, we need to add vendor/device ID to rl driver if we want to use Melco LPC4-CLX-CB. #but rl driver is hang up when I testing it. does rl driver have bugs? Thanks, --- YAMAMOTO ShigeruInternet Initiative Japan Inc. <[EMAIL PROTECTED]> Network Engineering Div. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Melco LPC4-CLX-CB support in 5.0-Current NEWCARD
At Tue, 15 Jan 2002 03:08:53 -0800 (PST), Shizuka Kudo wrote: > > Dear all, > > Does anyone have tested whether this card works with > current 5.0 NEWCARD? I tried it on a Thinkpad 600X > with current 5.0 cvsupped yestersday and received a > > kernel: found->vendor=0x10ec, dev=0x8138, > revid=0x10 (snip) It may work with device rl. (see /sys/pci/if_rlreg.h) -- YAMAMOTO, Taku <[EMAIL PROTECTED]> Member of Advanced Computer and Communication Studies Society (ACCESS for short), Information Processing Center, Saitama Univ. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
World broken again?
Hi guys, Yet again, building the world is broken again for me. I am using freshly cvsupped sources as of yesterday evening (CET that is) For good measure, output from uname: FreeBSD azazel.ipv6.hackerheaven.org 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Mon Jan 7 16:28:34 CET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AZAZEL i386 I am also having other problems rebooting the machine. Somehow my /usr filesystem has a bad superblock, drops to single user, where I do a fsck -y and when I reboot the same thing happens again. I would like to capture it to the serial port, can anyone point me to some docs on how to do that? Furthermore, I made a script(1) of a 'make buildworld', which is attached to this mail. Cheers, Emiel -- "I'd love to go out with you, but I'm attending the opening of my garage door." typescript.gz Description: application/gunzip
Re: World broken again?
On Tue, Jan 15, 2002 at 02:10:45PM +0100, Emiel Kollof wrote: [share/man/man3/Makefile breakage] Already fixed in src/share/man/man3/Makefile,v 1.21. Cheers, -- Ruslan Ermilov Oracle Developer/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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rpcbind panic
I can second this. I have seen the same panic, but was too lazy to hand copy it. Ken On Mon, 14 Jan 2002, Michael McGoldrick wrote: > Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from > cvsup.freebsd.org. > The panic message is hand copied. Please send me a mail if other details (eg dme > sg) are required. > > Kernel trap 12 with interrupts disabled > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x28 > fault code= supervisor read, page not present > instruction pointer = 0x8:0xc01d9f07 > stack pointer = 0x10:0xcb5b8b4c > frame pointer = 0x10:0xcb5b8b5c > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 178 (rpcbind) > kernel: type 12 trap, code = 0 > stopped at _mtx_unlock_sleep+0x9f : cmpl $0,0x28(%ebx) > > > 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: Trace for rpcbind panic
This is the same backtrace I got when I tried it too... The system would get all the way through booting, then fam (I'm assuming) sent something to rpcbind, which then caused this panic. Ken On Mon, 14 Jan 2002, Michael McGoldrick wrote: > The trace was short, so I wrote the whole thing down. > > _mtx_unlock_sleep(c232c834,0,0,0) at _mtx_unlock_sleep+0x9f > unp_externalize(c0b6ab00,c0b6ac00,cb5d3ccc,cb5d3c8c,cb5d3ccc) at unp_externalize > +0x38e > soreceive(ca29d420,cb5d3c18,cb5d3c44,0,cb5d3c1c) at soreceive+0x376 > recvit(ca284304,b,cb5d3ccc,0,ca284200) at recvit+0x121 > recvmsg(ca284304,cb5d3d20,281221c8,bfbfd550,2328) at recvmsg+0xdb > syscall(2f,2f,2f,2328,bfbfd550) at syscall+0x2d4 > syscall_with_err_pushed() at syscall_with_err_pushed+0x1b > --- syscall(27, FreeBSD ELF, recvmsg), eip=0x280c0657, esp=0xbfbfd500, ebp=0xbfb > fd5cc --- > > 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: Melco LPC4-CLX-CB support in 5.0-Current NEWCARD
In message: <[EMAIL PROTECTED]> Shizuka Kudo <[EMAIL PROTECTED]> writes: : kernel: found->vendor=0x10ec, dev=0x8138, revid=0x10 ... : kernel: cardbus0: (vendor=0x10ec, dev=0x8138) at 0.0 irq 11. Try adding this ID to the dc driver? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Melco LPC4-CLX-CB support in 5.0-Current NEWCARD
In message: <[EMAIL PROTECTED]> "M. Warner Losh" <[EMAIL PROTECTED]> writes: : In message: <[EMAIL PROTECTED]> : Shizuka Kudo <[EMAIL PROTECTED]> writes: : : kernel: found->vendor=0x10ec, dev=0x8138, revid=0x10 : ... : : kernel: cardbus0: (vendor=0x10ec, dev=0x8138) at 0.0 irq 11. : : Try adding this ID to the dc driver? Obviously I wasn't paying attention to the rest of the thread. Please ignore this. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvsup7.freebsd.org down until further notice
CVSup7.freebsd.org is having hardware problems. It will be down until further notice -- probably at least 2 weeks. For a list of mirror sites, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Netatalk broken in current? Lock order reversal?
My kernel compile from fresh CURRENT sources bombed today with this: linking kernel.debug ddp_input.o: In function `atintr': /usr/src/sys/netatalk/ddp_input.c:51: multiple definition of `atintrq1_present' intrq.o(.data+0x0):/usr/src/sys/net/intrq.c: first defined here ddp_input.o: In function `atintr': /usr/src/sys/netatalk/ddp_input.c:51: multiple definition of `atintrq2_present' intrq.o(.data+0x4):/usr/src/sys/net/intrq.c: first defined here *** Error code 1 So that leaves Appletalk right out (which I use. I do own macs...). It compiles fine if I leave options NETATALK out of my config I also had some strange panics and these messages appear once in a while: lock order reversal 1st 0xc185e934 filedesc structure @ /usr/src/sys/kern/kern_descrip.c:925 2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959 The panics moan about a kernel trap and some mutex stuff involving Giant. It only happens when I start Samba. Any leads? Cheers, Emiel -- Demographic polls show that you have lost credibility across the board. Especially with those 14 year-old Valley girls. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Netatalk broken in current? Lock order reversal?
On 15-Jan-02 Emiel Kollof wrote: > My kernel compile from fresh CURRENT sources bombed today with this: > > linking kernel.debug ddp_input.o: In function `atintr': > /usr/src/sys/netatalk/ddp_input.c:51: multiple definition of > `atintrq1_present' intrq.o(.data+0x0):/usr/src/sys/net/intrq.c: first defined > here > ddp_input.o: In function `atintr': /usr/src/sys/netatalk/ddp_input.c:51: > multiple definition of `atintrq2_present' > intrq.o(.data+0x4):/usr/src/sys/net/intrq.c: first defined here > *** Error code 1 > > So that leaves Appletalk right out (which I use. I do own macs...). It > compiles fine if I leave options NETATALK out of my config > > I also had some strange panics and these messages appear once in a while: > > lock order reversal 1st 0xc185e934 filedesc structure @ > /usr/src/sys/kern/kern_descrip.c:925 > 2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959 This one is due to not releasing the filedesc lock when grabbing Giant to free oldofile in fdalloc(). > The panics moan about a kernel trap and some mutex stuff involving > Giant. It only happens when I start Samba. Having the actual panic messages would be very helpful here. -- 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
LINT not compiling:
../../../dev/usb/uhci.c: In function `uhci_dump_all': ../../../dev/usb/uhci.c:694: structure has no member named `hlink' ../../../dev/usb/uhci.c: At top level: ../../../dev/usb/uhci.c:1270: warning: `uhci_reset' defined but not used ../../../dev/usb/uhci.c:261: warning: `uhci_dump_ii' used but never defined *** Error code 1 (continuing) cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -DGPROF -DGPROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg -mprofiler-epilogue ../../../netatm/atm_subr.c ../../../netatm/atm_subr.c: In function `atm_initialize': ../../../netatm/atm_subr.c:137: `atmintrq_present' undeclared (first use in this function) ../../../netatm/atm_subr.c:137: (Each undeclared identifier is reported only once ../../../netatm/atm_subr.c:137: for each function it appears in.) *** Error code 1 (continuing) cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -DGPROF -DGPROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg -mprofiler-epilogue ../../../netipx/spx_usrreq.c ../../../netipx/spx_usrreq.c: In function `spx_input': ../../../netipx/spx_usrreq.c:226: incompatible type for argument 3 of `ipx_pcbconnect' *** Error code 1 (continuing) cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -DGPROF -DGPROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg -mprofiler-epilogue ../../../compat/svr4/svr4_fcntl.c ../../../compat/svr4/svr4_fcntl.c: In function `fd_truncate': ../../../compat/svr4/svr4_fcntl.c:298: `uap' undeclared (first use in this function) ../../../compat/svr4/svr4_fcntl.c:298: (Each undeclared identifier is reported only once ../../../compat/svr4/svr4_fcntl.c:298: for each function it appears in.) ../../../compat/svr4/svr4_fcntl.c:291: warning: unused variable `ft' ../../../compat/svr4/svr4_fcntl.c:287: warning: unused variable `length' ../../../compat/svr4/svr4_fcntl.c:287: warning: unused variable `start' ../../../compat/svr4/svr4_fcntl.c: At top level: ../../../compat/svr4/svr4_fcntl.c:311: warning: type defaults to `int' in declaration of `length' ../../../compat/svr4/svr4_fcntl.c:311: `vattr' undeclared here (not in a function) ../../../compat/svr4/svr4_fcntl.c:311: warning: data definition has no type or storage class ../../../compat/svr4/svr4_fcntl.c:313: syntax error before `switch' ../../../compat/svr4/svr4_fcntl.c:94: warning: `svr4_to_bsd_flags' defined but not used ../../../compat/svr4/svr4_fcntl.c:68: warning: `svr4_to_bsd_cmd' defined but not used ../../../compat/svr4/svr4_fcntl.c:246: warning: `fd_revoke' defined but not used../../../compat/svr4/svr4_fcntl.c:283: warning: `fd_truncate' defined but not used ../../../compat/svr4/svr4_fcntl.c:114: warning: `bsd_to_svr4_flags' defined but not used ../../../compat/svr4/svr4_fcntl.c:135: warning: `bsd_to_svr4_flock' defined but not used ../../../compat/svr4/svr4_fcntl.c:163: warning: `svr4_to_bsd_flock' defined but not used ../../../compat/svr4/svr4_fcntl.c:190: warning: `bsd_to_svr4_flock64' defined but not used ../../../compat/svr4/svr4_fcntl.c:218: warning: `svr4_to_bsd_flock64' defined but not used *** Error code 1 (continuing) cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -DGPROF -DGPROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg -mprofiler-epilogue ../../../compat/svr4/svr4_misc.c ../../../compat/svr4/svr4_misc.c:625: warning: type defaults to `int' in declaration of `vref' ../../../compat/svr4/svr4_misc.c:625: warning: parameter names (without types) in function declaration ../../../compat/svr4/svr4_misc.c:625: conflicting types for `vref' ../../../sys/vnode.h:675: previous declaration of `vref' ../../../compat/svr4/svr4_misc.c:625: warning: redundant redeclaration of `vref' in same scope ../../../sys/vnode.h:675: warning: previous declaration of `v
-CURRENT as of 14 Jan seems slow
I've been tracking -CURRENT daily, both on a dual-833 MhZ "build
machine" and on my laptop. I still do the bulk of my "real work"
while running -STABLE, so the main workout I give -CURRENT is
in building the following day's -CURRENT.
I mention this in order to provide a bit of perspective in what follows.
After ensuring that the update to my local CVS repository is complete,
I do a "cvs update" against the sources for the OS, checking for
anything weird (especially conflicts with local patches, which I
resolve), then, as root, under script (well, and screen, too), I
issue a crude little csh alias. On the build box, it looks like
(with escapes to avoid the wrapping):
whoami && mount && cd /usr/src && uname -a && \
date && make -j8 buildworld && \
date && make kernel KERNCONF=FREEBEAST && \
date && make installworld && \
date && mergemaster -u 0022 -i && \
date && df -k
(On the laptop, the kernel name changes, and I use -j4 for the "make
buildworld"; it is otherwise identical.)
For grins, I am in the habit of keeping as many as 2 of the resulting
"script" output files. And this works out nicely for quantifying the
observation that yesterday's -CURRENT was considerably slower than
usual:
freebeast(4.5-RC)[2] grep '^... Jan 1[45]' current{,.?}
current:Tue Jan 15 05:42:01 PST 2002
current:Tue Jan 15 11:02:31 PST 2002
current:Tue Jan 15 12:06:17 PST 2002
current:Tue Jan 15 12:29:18 PST 2002
current:Tue Jan 15 12:51:16 PST 2002
current.0:Mon Jan 14 05:23:25 PST 2002
current.0:Mon Jan 14 07:07:11 PST 2002
current.0:Mon Jan 14 07:27:03 PST 2002
current.0:Mon Jan 14 08:34:55 PST 2002
current.0:Mon Jan 14 08:43:45 PST 2002
current.0:Mon Jan 14 08:44:40 PST 2002
(That was the "build machine"; here's the laptop)
g1-7(4.5-RC)[1] grep '^... Jan 1[45]' current{,.?}
current:Tue Jan 15 06:36:02 PST 2002
current:Tue Jan 15 11:52:14 PST 2002
current:Tue Jan 15 12:39:47 PST 2002
current:Tue Jan 15 12:58:32 PST 2002
current:Tue Jan 15 13:00:15 PST 2002
current.0:Mon Jan 14 06:42:15 PST 2002
current.0:Mon Jan 14 08:37:31 PST 2002
current.0:Mon Jan 14 08:58:35 PST 2002
current.0:Mon Jan 14 09:09:22 PST 2002
current.0:Mon Jan 14 09:10:10 PST 2002
So, on the build machine, the "make -j8 buildworld" took 1:43:46 on
Monday, but today, it took 5:20:30. On the laptop, the times were
1:55:16 and 5:16:12, respectively. Even I noticed *those* differences!
(And part of the "make buildworld" on the laptop was on battery power,
while I was driving in to work It's actually even worse than that,
because of what I needed to do to the laptop's AC adapter after I got
in to work, but that's rather beside the point for this note.)
Now, I'm not doing anything to try to cut corners -- I don't mount any
file systems noatime; I'm not using -DNOCLEAN; none of that stuff. And
I certainly didn't change /etc/make.conf between the runs. And neither
machine was doing anything else at the time: I build -STABLE before
building -CURRENT, so by the time the build machine was building
-CURRENT, it wasn't doing anything else.
I've made a list of the files that got updated in Monday's cvs update,
but this message is rather long enough without adding 88 more lines. I
can trim off obviously unrelated files, I suppose -- then again, it
could well be that changes that went in this morning have already
addressed the issue. In any case, here's a summary of recent CVSup
activity:
freebeast(4.5-RC)[4] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Fri Jan 11 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Fri Jan 11 03:53:28 PST 2002
CVSup begin from cvsup14.freebsd.org at Sat Jan 12 03:47:05 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Jan 12 03:54:10 PST 2002
CVSup begin from cvsup14.freebsd.org at Sun Jan 13 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Sun Jan 13 03:54:02 PST 2002
CVSup begin from cvsup14.freebsd.org at Mon Jan 14 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Mon Jan 14 03:53:27 PST 2002
CVSup begin from cvsup14.freebsd.org at Tue Jan 15 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Jan 15 03:54:00 PST 2002
(After updating the CVS repository on the build machine, I use that as a
source and update a CVS repository on the laptop, so save for various
kernel options, the base OS should be pretty close between the two.)
So... is this worth pursuing a bit more?
Thanks,
david (http://www.catwhisker.org/~david/resume.{ps,pdf,html,txt})
--
David H. Wolfskill [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Netatalk broken in current? Lock order reversal?
* John Baldwin ([EMAIL PROTECTED]) wrote: > > > The panics moan about a kernel trap and some mutex stuff involving > > Giant. It only happens when I start Samba. > > Having the actual panic messages would be very helpful here. Hmm, I will proceed to crash my machine again and have a go in hand copying them... I'll be back in a flash :-) Cheers, Emiel -- Anyone who uses the phrase "easy as taking candy from a baby" has never tried taking candy from a baby. -- Robin Hood To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -CURRENT as of 14 Jan seems slow
On 16-Jan-02 David Wolfskill wrote: > So... is this worth pursuing a bit more? Two questions: 1) Do you have WITNESS on in your kernel config? 2) If yes, have you tried building with a kernel without witness? -- 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: -CURRENT as of 14 Jan seems slow
>Date: Tue, 15 Jan 2002 16:46:17 -0800 (PST) >From: John Baldwin <[EMAIL PROTECTED]> >On 16-Jan-02 David Wolfskill wrote: >> So... is this worth pursuing a bit more? >Two questions: >1) Do you have WITNESS on in your kernel config? Yes, in both the build machine & the laptop -- since before I made a "local" hierarchy within my CVS repository (September 9, 2001). >2) If yes, have you tried building with a kernel without witness? No, not since I put it in to re-sync with GENERIC. I could try that, I suppose -- but as noted, I've had WITNESS in there for a while; something seems to have changed during that one 24-hr. period that affected things rather radically. And I thought it notable. :-} I gather no one else has noticed this? Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netatalk broken in current? Lock order reversal?
* John Baldwin ([EMAIL PROTECTED]) wrote:
>
> > lock order reversal 1st 0xc185e934 filedesc structure @
> > /usr/src/sys/kern/kern_descrip.c:925
> > 2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959
>
> This one is due to not releasing the filedesc lock when grabbing Giant to free
> oldofile in fdalloc().
Is that going to cause data loss? I also saw messages like these:
/var: lost blocks 62 files 8
> > The panics moan about a kernel trap and some mutex stuff involving
> > Giant. It only happens when I start Samba.
>
> Having the actual panic messages would be very helpful here.
It crashed very reproducable with this panic (hand copied):
exclusive (sleep mutex) Giant (0xc0462c00) locked @ /usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning with mutex(s) held
Debugger("panic")
panic: kernel trap doesn't have ucred
Cheers,
Emiel
--
So far as I can remember, there is not one word in the Gospels in
praise of intelligence.
-- Bertrand Russell
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT as of 14 Jan seems slow
On Tue, Jan 15, 2002 at 04:56:03PM -0800, David Wolfskill wrote: [...] > > I gather no one else has noticed this? Not here at least (timestamps are CET): note% ls -l /var/log/build/buildworld.log* -rw-r--r-- 1 root wheel 5728428 15 Jan 22:58 /var/log/build/buildworld.log -rw-r--r-- 1 root wheel 5727901 12 Jan 15:14 /var/log/build/buildworld.log.0 -rw-r--r-- 1 root wheel 5728013 11 Jan 04:35 /var/log/build/buildworld.log.1 -rw-r--r-- 1 root wheel 5701184 5 Jan 18:34 /var/log/build/buildworld.log.2 -rw-r--r-- 1 root wheel 5701184 5 Jan 18:34 /var/log/build/buildworld.log.3 note% egrep ' real.* user.* sys' /var/log/build/buildworld.log* /var/log/build/buildworld.log: 3860,96 real 2480,12 user 513,99 sys /var/log/build/buildworld.log.0: 4310,09 real 2948,09 user 560,00 sys /var/log/build/buildworld.log.1: 8044,91 real 2941,55 user 555,54 sys /var/log/build/buildworld.log.2: 4099,63 real 2935,31 user 562,73 sys /var/log/build/buildworld.log.3: 4099,63 real 2935,31 user 562,73 sys > david Cheers, Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -CURRENT as of 14 Jan seems slow
On 16-Jan-02 David Wolfskill wrote: >>Date: Tue, 15 Jan 2002 16:46:17 -0800 (PST) >>From: John Baldwin <[EMAIL PROTECTED]> > >>On 16-Jan-02 David Wolfskill wrote: >>> So... is this worth pursuing a bit more? > >>Two questions: > >>1) Do you have WITNESS on in your kernel config? > > Yes, in both the build machine & the laptop -- since before I made a > "local" hierarchy within my CVS repository (September 9, 2001). > >>2) If yes, have you tried building with a kernel without witness? > > No, not since I put it in to re-sync with GENERIC. I could try that, I > suppose -- but as noted, I've had WITNESS in there for a while; something > seems to have changed during that one 24-hr. period that affected things > rather radically. And I thought it notable. :-} > > I gather no one else has noticed this? Alfred added several more locks for file I/O stuff that could be the hit you are seeing. -- 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: Netatalk broken in current? Lock order reversal?
On 16-Jan-02 Emiel Kollof wrote: > * John Baldwin ([EMAIL PROTECTED]) wrote: >> >> > lock order reversal 1st 0xc185e934 filedesc structure @ >> > /usr/src/sys/kern/kern_descrip.c:925 >> > 2nd 0xc0419b00 Giant @ /usr/src/sys/kern/kern_descrip.c:959 >> >> This one is due to not releasing the filedesc lock when grabbing Giant to >> free >> oldofile in fdalloc(). > > Is that going to cause data loss? I also saw messages like these: > > /var: lost blocks 62 files 8 No, that's softupdates stuff. I think releasing filedesc is ok this case, but usually I would recode it to move malloc's and free's around to avoid having to drop and reacquire locks. >> Having the actual panic messages would be very helpful here. > > It crashed very reproducable with this panic (hand copied): > > exclusive (sleep mutex) Giant (0xc0462c00) locked @ > /usr/src/sys/i386/i386/trap.c:1102 > panic: system call pwrite returning with mutex(s) held Hmm, erm, go kick Alfred really hard. :) This function locks Giant and then doesn't ever unlock it. This looks to be breakage from his fget() changes perhaps. -- 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: Netatalk broken in current? Lock order reversal?
* John Baldwin ([EMAIL PROTECTED]) wrote: > > /var: lost blocks 62 files 8 > > No, that's softupdates stuff. I think releasing filedesc is ok this case, > but usually I would recode it to move malloc's and free's around to avoid > having to drop and reacquire locks. Ah right... Good to know... > > exclusive (sleep mutex) Giant (0xc0462c00) locked @ > > /usr/src/sys/i386/i386/trap.c:1102 > > panic: system call pwrite returning with mutex(s) held > > Hmm, erm, go kick Alfred really hard. :) This function locks Giant and then > doesn't ever unlock it. This looks to be breakage from his fget() changes > perhaps. Ah... Alfred? You will be let off easy this one time. Next time I'll send the Beastie after you. Right after you finish cramping that box of CAT5 cable over there in 30 cm long pieces, oh and you have to repeat "I will never leave my locks on Giant unfreed" too every time you finish one. Right. got that? Good. ;-) Oh, on another note, is someone working at that netatalk breakage? Who do I have to discipline for that? :-) Cheers, Emiel -- Too much of a good thing is WONDERFUL. -- Mae West To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netatalk broken in current? Lock order reversal?
In message <[EMAIL PROTECTED]>, Emiel Kollof writes:
>
>Oh, on another note, is someone working at that netatalk breakage? Who
>do I have to discipline for that? :-)
Could you try the following patch in src/sys/netatalk? The problem
was caused by the -fno-common compiler option that was added to
the kernel build flags recently.
This compiles for me, but I haven't checked that it actually works.
Ian
Index: ddp_input.c
===
RCS file: /dump/FreeBSD-CVS/src/sys/netatalk/ddp_input.c,v
retrieving revision 1.12
diff -u -r1.12 ddp_input.c
--- ddp_input.c 13 Feb 2000 03:31:58 - 1.12
+++ ddp_input.c 16 Jan 2002 01:30:50 -
@@ -27,8 +27,6 @@
static struct ddpstat ddpstat;
static struct routeforwro;
-const int atintrq1_present = 1, atintrq2_present = 1;
-
static void ddp_input(struct mbuf *, struct ifnet *, struct elaphdr *, int);
/*
Index: ddp_usrreq.c
===
RCS file: /dump/FreeBSD-CVS/src/sys/netatalk/ddp_usrreq.c,v
retrieving revision 1.22
diff -u -r1.22 ddp_usrreq.c
--- ddp_usrreq.c17 Nov 2001 03:07:08 - 1.22
+++ ddp_usrreq.c16 Jan 2002 01:32:34 -
@@ -14,6 +14,7 @@
#include
#include
#include
+#include
#include
#include
@@ -547,6 +548,8 @@
{
atintrq1.ifq_maxlen = IFQ_MAXLEN;
atintrq2.ifq_maxlen = IFQ_MAXLEN;
+atintrq1_present = 1;
+atintrq2_present = 1;
mtx_init(&atintrq1.ifq_mtx, "at1_inq", MTX_DEF);
mtx_init(&atintrq2.ifq_mtx, "at2_inq", MTX_DEF);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Netatalk broken in current? Lock order reversal?
* Ian Dowse ([EMAIL PROTECTED]) wrote: > >Oh, on another note, is someone working at that netatalk breakage? Who > >do I have to discipline for that? :-) > > Could you try the following patch in src/sys/netatalk? The problem > was caused by the -fno-common compiler option that was added to > the kernel build flags recently. Right... Applied it. Building as I mail this. > This compiles for me, but I haven't checked that it actually works. I will test it. (run netatalk and transfer some files to and fro) Cheers, Emiel -- "Gee, Toto, I don't think we are in Kansas anymore." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Melco LPC4-CLX-CB support in 5.0-Current NEWCARD
All, Thank you for your support. The card should have been recognized in NEWCARD. It is my fault that I thought my Thinkpad was running NEWCARD but in fact was a custom kernel without rl support. In addition, I did not experience the hang that was mentioned by another YAMAMOTO san. --- Taku YAMAMOTO <[EMAIL PROTECTED]> wrote: > At Tue, 15 Jan 2002 03:08:53 -0800 (PST), > Shizuka Kudo wrote: > > > > Dear all, > > > > Does anyone have tested whether this card works > with > > current 5.0 NEWCARD? I tried it on a Thinkpad 600X > > with current 5.0 cvsupped yestersday and received > a > > > > kernel: found->vendor=0x10ec, dev=0x8138, > > revid=0x10 > (snip) > > It may work with device rl. > (see /sys/pci/if_rlreg.h) > -- > YAMAMOTO, Taku <[EMAIL PROTECTED]> > Member of Advanced Computer and Communication > Studies Society > (ACCESS for short), Information Processing Center, > Saitama Univ. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of > the message __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netatalk broken in current? Lock order reversal?
* Emiel Kollof ([EMAIL PROTECTED]) wrote: > > This compiles for me, but I haven't checked that it actually works. > > I will test it. (run netatalk and transfer some files to and fro) It compiled, and after making a connection with Appletalk with one of my macs, file transfers went off without a hitch. I copied some big files (several MB's) from my CURRENT machine and my mac, and after checking with cmp(1) the files seemed to have no corruption. So basically, it does work. Hope that helped a bit... Now let's hope Alfred will fix my kernel trap when I run Samba... I tend to need it around here :-( Cheers, Emiel -- SCORPIO (Oct 23 - Nov 21) You are shrewd in business and cannot be trusted. You will achieve the pinnacle of success because of your total lack of ethics. Most Scorpio people are murdered. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LIVE TEENS GETTING WILD, free signup!
Below is the result of your feedback form. It was submitted by ([EMAIL PROTECTED]) on Tuesday, January 15, 19102 at 23:13:47 --- : If you want live, wild teens on their webcams you should check http://12.26.191.9";>this out , signup is free just use your credit card to :verify your age and you're in. And best of all they're real people, you can enter a :1 on 1 session and might meet the someone to fulfill all your fantasies. If it's celebs you're looking for, look no farther than http://12.26.191.9/celebs/index.html";>here , We even have the rare Brittany/Justin video set, No credit card required!!! You received this e-mail because you were added to our monthly mailing list, if you want to be removed simply e-mail [EMAIL PROTECTED] with the subject "REMOVE". --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -CURRENT as of 14 Jan seems slow
On Tue, 15 Jan 2002, David Wolfskill wrote: > >Date: Tue, 15 Jan 2002 16:46:17 -0800 (PST) > >From: John Baldwin <[EMAIL PROTECTED]> > >Two questions: > > >1) Do you have WITNESS on in your kernel config? > > Yes, in both the build machine & the laptop -- since before I made a > "local" hierarchy within my CVS repository (September 9, 2001). > > >2) If yes, have you tried building with a kernel without witness? > > No, not since I put it in to re-sync with GENERIC. I could try that, I > suppose -- but as noted, I've had WITNESS in there for a while; something > seems to have changed during that one 24-hr. period that affected things > rather radically. And I thought it notable. :-} > > I gather no one else has noticed this? File locking seems to cause only the usual few percent of slowdown for each round of major locking changes. I haven't completed benchmarking the file locking pessimizations. I don't use WITNESS or INVARIANTS for benchmarking of course. Maybe the file locking changes cause much larger pessimizations when WITNESS is turned on than most locking changes. I can see how they might: WITNESS seemed to slow down creation and destruction of mutexes more than most mutex operations last time I checked, and there is a descriptor for each file and each file descriptor. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
size of /usr/src
Hi, I created a separate partition for /usr/src (around 420MB) and cvsup ran out of space. Can someone give me a rough idea of how big it is? Also, I should be able to use growfs (after booting off of a floppy) to increase the size of the partition (if the slice has space), right? How about moving partitions - is there an easier way than creating a partition at the end of the slice and copying partitions down? Thanks, Arvind To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
