Re: xmms broken by either libc_r or sound
In the last episode (Jun 14), Otter said: > On Wed, 14 Jun 2000, Chris Piazza wrote: > > Yes backout recent changes to sys/dev/sound/pcm/channel.c. (a few days) > > How does one backout changes? I thought once it was committed, and > the make world process is complete, it was just that: committed. You make another commit, undoing what your first commit did. That way there is a record of what you did, and hopefully why it was backed out. For more info: info -n "(cvs)Merging two revisions" -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xmms broken by either libc_r or sound
oh good, I thought it was somehow something I did on my last upgrade and was just about to hit the list archives to make sure I hadn't missed something :) On Wed, 14 Jun 2000, Alfred Perlstein wrote: > xmms is a really good test for libc_r and the sound system. > > xmms no longer plays back mp3s, other mp3 players are working > fine. > > Any ideas? > > -Alfred > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xmms broken by either libc_r or sound
For now I'm just using mpg123 (gqmpeg works too of course, as a front-end, but I hate it's list manager).. mpg123 seems to work fine on all of my -current machines. thomas r. stromberg [EMAIL PROTECTED] senior systems administratorhttp://www.afterthought.org/ research triangle commerce, inc.1.919.657.1317 'FreeBSD - the power to serve' 'Perl - the power to hack' On Wed, 14 Jun 2000, Alfred Perlstein wrote: > xmms is a really good test for libc_r and the sound system. > > xmms no longer plays back mp3s, other mp3 players are working > fine. > > Any ideas? > > -Alfred > > > 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: xmms broken by either libc_r or sound
On Wed, 14 Jun 2000, Chris Piazza wrote: > On Wed, Jun 14, 2000 at 05:41:39PM -0700, Alfred Perlstein wrote: > > xmms is a really good test for libc_r and the sound system. > > > > xmms no longer plays back mp3s, other mp3 players are working > > fine. > > > > Any ideas? > > Yes backout recent changes to sys/dev/sound/pcm/channel.c. (a few days) > How does one backout changes? I thought once it was committed, and the make world process is complete, it was just that: committed. -Otter > There was a large-ish thread about this on -committers too... > > -Chris > -- > [EMAIL PROTECTED] | yawn. > [EMAIL PROTECTED]| Abbotsford, BC, Canada > > > 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: xmms broken by either libc_r or sound
On Wed, Jun 14, 2000 at 05:51:01PM -0700, Chris Piazza wrote: > On Wed, Jun 14, 2000 at 05:41:39PM -0700, Alfred Perlstein wrote: > > xmms is a really good test for libc_r and the sound system. > > > > xmms no longer plays back mp3s, other mp3 players are working > > fine. > > > > Any ideas? > > Yes backout recent changes to sys/dev/sound/pcm/channel.c. (a few days) > > There was a large-ish thread about this on -committers too... Before you do, it would be interesting to check whether the pcm driver is getting dma interrupts. Either try to play some sound and check vmstat -i, or add a printf to chn_wrintr in channel.c. Lots of the reportable problems with the pcm driver can be reproduced here when the driver does not get dma interrupts. However, it may be unique to my setup. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Re: xmms broken by either libc_r or sound
On Wed, Jun 14, 2000 at 05:41:39PM -0700, Alfred Perlstein wrote: > xmms is a really good test for libc_r and the sound system. > > xmms no longer plays back mp3s, other mp3 players are working > fine. > > Any ideas? Yes backout recent changes to sys/dev/sound/pcm/channel.c. (a few days) There was a large-ish thread about this on -committers too... -Chris -- [EMAIL PROTECTED] | yawn. [EMAIL PROTECTED]| Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xmms broken by either libc_r or sound
xmms is a really good test for libc_r and the sound system. xmms no longer plays back mp3s, other mp3 players are working fine. Any ideas? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: establish tcp connection slowness
Matthew Dillon scribbled this message on Jun 13: > Typically time delays like this are due to the reverse DNS lookup > failing. Make sure the dns resolver is working properly on the > machine. You should be able to test it by running nslookup on > the IP addresses connecting into the machine. not if the time delay is between Trying x.x.x.x... and the Connected to line... also, the time delay is being seen w/ a simple /bin/echo service.. this shouldn't do any reverse lookup of the connecting host.. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking"I say all sorts of useless things." -- cmc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons rebooting when going to 80x50
* Kazutaka YOKOTA <[EMAIL PROTECTED]> [000614 17:00] wrote: > > >After taking the patches for config and booting my box reboots > > Which patch is it? I'm sorry, I should have been more clear, no patches, just the 5.0 sources from ~noon PST. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons rebooting when going to 80x50
>After taking the patches for config and booting my box reboots Which patch is it? Kazu >because I have: > >#allscreens_flags="-m on 80x50" >#saver="logo" >#font8x8="cp437-8x8" >#font8x14="cp437-8x14" >#font8x16="cp437-8x16" > >enabled in my rc.conf, a kernel from ~2 days ago is fine with this. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
syscons rebooting when going to 80x50
After taking the patches for config and booting my box reboots because I have: #allscreens_flags="-m on 80x50" #saver="logo" #font8x8="cp437-8x8" #font8x14="cp437-8x14" #font8x16="cp437-8x16" enabled in my rc.conf, a kernel from ~2 days ago is fine with this. thanks, -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Remote GDB *still* buggy...
On Wednesday, 14 June 2000 at 11:05:41 -0600, Justin T. Gibbs wrote: > I still can't get remote GDB to work correctly in a 5.0-current > environment at speeds greater than 9600bps. Is anyone else > experiencing similar results? I thought that grog had fixed this... So did I. Are you just getting hangs? What kind of UART? Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Remote GDB *still* buggy...
On Wednesday, 14 June 2000 at 12:27:27 -0600, Justin T. Gibbs wrote: >> On Wednesday, 14 June 2000 at 11:05:41 -0600, Justin T. Gibbs wrote: >>> I still can't get remote GDB to work correctly in a 5.0-current >>> environment at speeds greater than 9600bps. Is anyone else >>> experiencing similar results? I thought that grog had fixed this... >> >> So did I. Are you just getting hangs? What kind of UART? > > On which side of the connection? Debug machine. > I'm using my Thinkpad 770X as the GDB host and it says: > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > > On the machine I'm trying to debug, a Dell Precision 410, I have: > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > > I suppose I could rip open the case to try and find what part they > put on the motherboard for the 16550 support, but I'm had similar > results with other machines. Hmm. > In GDB, you see some message about "malformed messages" and you > can't seem to do anything. The other odd part is that speeds up to > even 115200 work just fine up until the point that interrupt > services are enabled. Then your hosed. That's pretty much the symptoms I had been seeing until the fix. I don't understand why you're still seeing them; they were gone in a flash on my system. Are you sure you're using this revision? /* $FreeBSD: src/sys/i386/i386/i386-gdbstub.c,v 1.15 2000/05/18 02:29:23 grog Exp $ */ If so, try changing the two spltty()s to splhigh() and see if that makes the problem go away. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
syscons scrolling broken
Hello! My old kernel is from May 25th. Syscons scrolling works (scroll-lock, scrolling with page up/down). With my new kernel from today: FreeBSD cichlids.cichlids.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jun 14 22:25:49 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/cichlids i386 it does not. It seems, as if screen output is still being deactivated, but scrolling does just not work. Anyone else? Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Hello Peter! I just have things running. I see that the kernel boots _much_ faster now. I don't know, if you wanted that or if this is a nice side-effect. However, a few comments, which might be of interest. Some of those are probably planned by you already. a) the device.hints file: It will probably be copied to /sys/compile by config(8) in future and installed by make install :) Good. b) Setting apm 0 at to nexus (string) Setting apm 0 disabled to 1 (int) Setting apm 0 flags to 32 (int) ... Can this be moved to verbose boot only? c) is much more interesting: With the new kernel my syscons scrolling stopped working. However, this could also be jake's fault, I'll ask him. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Peter Wemm wrote: > > The only change in /boot is /boot/defaults/loader.conf: > > diff -r1.26 -r1.27 > 24c24 > < loader_conf_files="/boot/loader.conf /boot/loader.conf.local" > --- > > loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local" > > ie: /boot/device.hints is searched for. > > If you override loader_conf_files in your own loader.conf, you will need to > take care of it (or use static hints). loader_conf_files is not overridable. If that variable has a new value after a conf file has been read, it will process it recursively, an restore the original value afterwards. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "He is my minion, so he doesn't need a name." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: res_init.c 1.20 broke non-INET6 kernel!
> On Wed, 14 Jun 2000 12:21:48 -0700 > "Andrey A. Chernov" <[EMAIL PROTECTED]> said: ache> All nameservers are initialized to AF_INET6 which cause socket() to return -1 ache> in non-INET6 kernel. ache> All names lookups fails as result. Oops, sorry. I'll backout previous commit right now. ache> I think IPV6 support is optional, isn't? Yes, of couece. It's just my mistake. Sorry again. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ppp is broken now
On Wed, Jun 14, 2000 at 06:46:07PM +0400, Andrey A. Chernov wrote: > Fresh -current, "ppp -auto system" not react on outgoing packets and not > dial, it seems they routed to dead end. Direct "dial system" command > dials in, but packets not routed too. Restoring ppp from 8 Jun fix it. Forget it, it is not ppp problem at all, it is resolver damaged by IPV6 support, see my next message about res_init.c -- Andrey A. Chernov <[EMAIL PROTECTED]> http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADSUP: bioops patch.
This patch virtualizes & untangles the bioops operations vector. Background: The bioops operation vector is a list of OO-like operations which can be performed on struct buf. They are used by the softupdates code to handle dependencies. Ideally struct buf should have had a real OO like operations vector like vnodes have it, and struct bioops is the first step towards that. One of the reasons we should have OO-like struct buf, is that as long as bwrite(bp) "knows" that the buffer is backed by a disk device, we cannot use the UFS layer on top of a storage manager which isn't based on disk-devices: When UFS modifies a directory inode, it will call bwrite(bp) on the buffer with the data. This would not work if the backing were based on malloc(9) or anonymous swap-backed VM objects for instance. In other words: this is the main reason why we don't have a decent tmpfs in FreeBSD. Instead of just assuming that it works on a disk, bwrite(bp) should do a "bp->b_ops->bwrite(bp)" so that each buffer could have its own private idea of how to write itself, depending on what backing it has. So in order to move bioops closer to become a bp->b_ops, this patch takes two entries out of bioops: the "sync" and the "fsync" items and virtualizes the rest of the elements a bit. The "sync" item is called only from the syncer, and is a call to the softupdates code to do what it needs to do for periodic syncing. The real way of doing that would be to have an event-handler for this since other code could need to be part of the sync trafic, raid5 private parity caches could be one example. I have not done this yet, since currently softupdates is the only client. The fsync item really doesn't belong in the fsync system call, it belongs in ffs_fsync, and has been moved there. To give the right behaviour when SOFTUPDATES is not compiled in, stubs for both of these functions have been added to ffs_softdep_stub.c Finally all the checks to see if the bioops vector is populated has been centralized in in-line functions in thereby paving the road for the global bioops to become bp->b_ops. Comments, reviews, tests please Poul-Henning Index: contrib/softupdates/ffs_softdep.c === RCS file: /home/ncvs/src/sys/contrib/softupdates/ffs_softdep.c,v retrieving revision 1.64 diff -u -r1.64 ffs_softdep.c --- contrib/softupdates/ffs_softdep.c 2000/05/26 02:01:59 1.64 +++ contrib/softupdates/ffs_softdep.c 2000/06/14 19:26:46 @@ -222,8 +222,6 @@ softdep_disk_io_initiation, /* io_start */ softdep_disk_write_complete,/* io_complete */ softdep_deallocate_dependencies,/* io_deallocate */ - softdep_fsync, /* io_fsync */ - softdep_process_worklist, /* io_sync */ softdep_move_dependencies, /* io_movedeps */ softdep_count_dependencies, /* io_countdeps */ }; Index: kern/vfs_bio.c === RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.258 diff -u -r1.258 vfs_bio.c --- kern/vfs_bio.c 2000/05/26 02:04:39 1.258 +++ kern/vfs_bio.c 2000/06/14 19:00:56 @@ -616,8 +616,8 @@ newbp->b_flags &= ~B_INVAL; /* move over the dependencies */ - if (LIST_FIRST(&bp->b_dep) != NULL && bioops.io_movedeps) - (*bioops.io_movedeps)(bp, newbp); + if (LIST_FIRST(&bp->b_dep) != NULL) + buf_movedeps(bp, newbp); /* * Initiate write on the copy, release the original to @@ -673,10 +673,10 @@ /* * Process dependencies then return any unfinished ones. */ - if (LIST_FIRST(&bp->b_dep) != NULL && bioops.io_complete) - (*bioops.io_complete)(bp); - if (LIST_FIRST(&bp->b_dep) != NULL && bioops.io_movedeps) - (*bioops.io_movedeps)(bp, origbp); + if (LIST_FIRST(&bp->b_dep) != NULL) + buf_complete(bp); + if (LIST_FIRST(&bp->b_dep) != NULL) + buf_movedeps(bp, origbp); /* * Clear the BX_BKGRDINPROG flag in the original buffer * and awaken it if it is waiting for the write to complete. @@ -939,8 +939,8 @@ * cache the buffer. */ bp->b_flags |= B_INVAL; - if (LIST_FIRST(&bp->b_dep) != NULL && bioops.io_deallocate) - (*bioops.io_deallocate)(bp); + if (LIST_FIRST(&bp->b_dep) != NULL) + buf_deallocate(bp); if (bp->b_flags & B_DELWRI) { --numdirtybuffers; numdirtywakeup(); @@ -1570,8 +1570,8 @@ crfree(bp->b_wcred); bp->b_wcred = NOCRED; } - if (LIST_FIRST(
Re: res_init.c 1.20 broke non-INET6 kernel!
On Wed, Jun 14, 2000 at 12:21:48PM -0700, Andrey A. Chernov wrote: > All nameservers are initialized to AF_INET6 which cause socket() to return -1 > in non-INET6 kernel. > > All names lookups fails as result. Returning res_init.c to 1.19 and res_send.c to 1.32 solve this thing. -- Andrey A. Chernov <[EMAIL PROTECTED]> http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
res_init.c 1.20 broke non-INET6 kernel!
All nameservers are initialized to AF_INET6 which cause socket() to return -1 in non-INET6 kernel. All names lookups fails as result. I think IPV6 support is optional, isn't? Moreover, this code is very strange looking by itself, because res_update() reinitialize all nameservers back to AF_INET -- Andrey A. Chernov <[EMAIL PROTECTED]> http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Remote GDB *still* buggy...
>On Wednesday, 14 June 2000 at 11:05:41 -0600, Justin T. Gibbs wrote: >> I still can't get remote GDB to work correctly in a 5.0-current >> environment at speeds greater than 9600bps. Is anyone else >> experiencing similar results? I thought that grog had fixed this... > >So did I. Are you just getting hangs? What kind of UART? On which side of the connection? I'm using my Thinkpad 770X as the GDB host and it says: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A On the machine I'm trying to debug, a Dell Precision 410, I have: sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A I suppose I could rip open the case to try and find what part they put on the motherboard for the 16550 support, but I'm had similar results with other machines. In GDB, you see some message about "malformed messages" and you can't seem to do anything. The other odd part is that speeds up to even 115200 work just fine up until the point that interrupt services are enabled. Then your hosed. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
At 01:20 AM 6/14/2000 -0700, Peter Wemm wrote: >Peter Wemm wrote: > >> # update /boot/loader.conf >> cd src/sys/boot; make obj depend all install > >Of course, it would be just my luck that there is a loader bug right now, >and this command will throw you into the fire. ;-( If your loader >complains about not being version 0.3+ or later and aborting, comment the >version tests out of /boot/loader.4th as an interim. > >I have also just committed a last-minute introduced bug that prevented >static hints files with full-line comments in them from working properly. > >Cheers, >-Peter Peter I got this to work after some tweaking. I was getting syntax errors from the hints file when booting. I cut and pasted out of GENERIC.hints into my.hints and now it seems to boot without any errors. I noticed I now have a new link in the / directory :: lrwxr-xr-x 1 root wheel 10 Jun 14 11:18 ttyv0@ -> /dev/ttyv0 is this normal ? Also it seems that there is a order in the hints file that needs to be followed. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Remote GDB *still* buggy...
I still can't get remote GDB to work correctly in a 5.0-current environment at speeds greater than 9600bps. Is anyone else experiencing similar results? I thought that grog had fixed this... -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ppp is broken now
Fresh -current, "ppp -auto system" not react on outgoing packets and not dial, it seems they routed to dead end. Direct "dial system" command dials in, but packets not routed too. Restoring ppp from 8 Jun fix it. -- Andrey A. Chernov <[EMAIL PROTECTED]> http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Peter Wemm wrote: > # update /boot/loader.conf > cd src/sys/boot; make obj depend all install Of course, it would be just my luck that there is a loader bug right now, and this command will throw you into the fire. ;-( If your loader complains about not being version 0.3+ or later and aborting, comment the version tests out of /boot/loader.4th as an interim. I have also just committed a last-minute introduced bug that prevented static hints files with full-line comments in them from working properly. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message