Re: jerky mouse still in 7.0-RELEASE
Dominic Fandrey wrote: > Kris Kennaway wrote: >> Dominic Fandrey wrote: >>> Kris Kennaway wrote: Well it doesn't rule it out. X may be introducing latencies that are causing your mouse to lose sync or something. >>> >>> It's not the mouse that hangs. >>> It's the only thing that works, >>> everything else hangs when I combine moused/X. This issue doesn't >>> exist on all my systems, though. It existed on my old Thinkpad >>> (Pentium-m 1.3 GHz), it exists on my new notebook (Core2 Duo with >>> 2.4 GHz), but it doesn't exist on my P4 with 1.6 GHz. >>> >>> Key entries, animations, they all just pile up somewhere and happen >>> all at once when I start using the mouse. To watch a movie I have to >>> keep the mouse moving all the time. >>> >>> It's not a general X and mouse problem, because without moused in >>> between everything works fine. I think at some point in time a bug >>> was either introduced in moused, or in my opinion more likely, in >>> the sysmouse protocol implementation in X. >> >> Could also be an interrupt issue. Either way it's still a different >> issue to the ones in this thread. > > I always thought it's about the same thing and people were just > imprecise in their perception. The P4 used to be affected by this, > too. This changed somewhere around RC1, I think. Since all of my > machines had encountered the problem since I switched them to > RELENG_7, I thought my problem was very common and it's the one > everyone is talking about. Perhaps this is related to the CX / cpu idle level problems we've been experiencing on a lot of hardware? What is the output of "sysctl -a | grep cx" on your system? -- Coleman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: cvs commit: src/sys/dev/tdfx tdfx_pci.c]
Hello, I am looking to MFC the above, rather simple, commit. Could anyone take a quick look at it, to make sure that it isn't missing anything RELENG_7-related? -- Coleman Kane --- Begin Message --- cokane 2008-03-13 14:08:41 UTC FreeBSD src repository Modified files: sys/dev/tdfx tdfx_pci.c Log: Add the module dependency on the mem(4) module. This will fix the module failing to load on a kernel that has "nodevice mem" in the config. It will now properly bring in the mem(4) module. Submitted by: antoine Reviewed by:imp MFC after: 1 week Revision ChangesPath 1.40 +1 -0 src/sys/dev/tdfx/tdfx_pci.c --- End Message --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MFC Candidate: convert ffs_softdep.c over to callout(9)
Hi stable users,
Recently I committed revision 1.219 of src/sys/ufs/ffs/ffs_softdep.c to
remove the use of old-style timeout(9) calls in the softdep code and
replace them with the new callout(9) API, to further MPSAFE-ness of the
softdep code.
I am attaching a patch to RELENG_7 that I'd like some people to test,
which is just an MFC of this code. Can I get any testers (so that I can
MFC this)?
--
Coleman Kane
diff --git a/sys/ufs/ffs/ffs_softdep.c b/sys/ufs/ffs/ffs_softdep.c
index 668f08f..f1b01d2 100644
--- sys/ufs/ffs/ffs_softdep.c
+++ sys/ufs/ffs/ffs_softdep.c
@@ -661,7 +661,7 @@ static int maxindirdeps = 50; /* max number of indirdeps before slowdown */
static int tickdelay = 2; /* number of ticks to pause during slowdown */
static int proc_waiting; /* tracks whether we have a timeout posted */
static int *stat_countp; /* statistic to count in proc_waiting timeout */
-static struct callout_handle handle; /* handle on posted proc_waiting timeout */
+static struct callout softdep_callout;
static int req_pending;
static int req_clear_inodedeps; /* syncer process flush some inodedeps */
#define FLUSH_INODES 1
@@ -1392,6 +1392,9 @@ softdep_initialize()
bioops.io_complete = softdep_disk_write_complete;
bioops.io_deallocate = softdep_deallocate_dependencies;
bioops.io_countdeps = softdep_count_dependencies;
+
+ /* Initialize the callout with an mtx. */
+ callout_init_mtx(&softdep_callout, &lk, 0);
}
/*
@@ -1402,6 +1405,7 @@ void
softdep_uninitialize()
{
+ callout_drain(&softdep_callout);
hashdestroy(pagedep_hashtbl, M_PAGEDEP, pagedep_hash);
hashdestroy(inodedep_hashtbl, M_INODEDEP, inodedep_hash);
hashdestroy(newblk_hashtbl, M_NEWBLK, newblk_hash);
@@ -5856,8 +5860,10 @@ request_cleanup(mp, resource)
* We wait at most tickdelay before proceeding in any case.
*/
proc_waiting += 1;
- if (handle.callout == NULL)
- handle = timeout(pause_timer, 0, tickdelay > 2 ? tickdelay : 2);
+ if (callout_pending(&softdep_callout) == FALSE)
+ callout_reset(&softdep_callout, tickdelay > 2 ? tickdelay : 2,
+ pause_timer, 0);
+
msleep((caddr_t)&proc_waiting, &lk, PPAUSE, "softupdate", 0);
proc_waiting -= 1;
return (1);
@@ -5872,14 +5878,15 @@ pause_timer(arg)
void *arg;
{
- ACQUIRE_LOCK(&lk);
+ /*
+ * The callout_ API has acquired mtx and will hold it around this
+ * function call.
+ */
*stat_countp += 1;
wakeup_one(&proc_waiting);
if (proc_waiting > 0)
- handle = timeout(pause_timer, 0, tickdelay > 2 ? tickdelay : 2);
- else
- handle.callout = NULL;
- FREE_LOCK(&lk);
+ callout_reset(&softdep_callout, tickdelay > 2 ? tickdelay : 2,
+ pause_timer, 0);
}
/*
signature.asc
Description: This is a digitally signed message part
Re: MFC Candidate: convert ffs_softdep.c over to callout(9)
Ilya Bakulin spake thusly: > > Hi, > I have an ability to test this patch on RELENG_7 system (there is no > mission-critical data stored on HDD :-) ) > What sould I do? Just apply patch, recompile kernel and produce some disk > load on that system? > > > Hi stable users, > > > > Recently I committed revision 1.219 of src/sys/ufs/ffs/ffs_softdep.c to > > remove the use of old-style timeout(9) calls in the softdep code and > > replace them with the new callout(9) API, to further MPSAFE-ness of the > > softdep code. > > > > I am attaching a patch to RELENG_7 that I'd like some people to test, > > which is just an MFC of this code. Can I get any testers (so that I can > > MFC this)? > > Ilya, Yes just go ahead and apply the patch that was attached. Then rebuild your kernel. Make sure that your softupdates are enabled on the UFS partition(s). Then try hammering it with some sort of file test on that partition (e.g. unpack a somewhat large source tarball and try building it). The kernel did build fine for me when I built it. Unfortunately, due to my hardware, RELENG_7 doesn't "just work" for me from vanilla sources, so I'd like to see some testers on better "supported" hardware. -- Coleman Kane ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adaptec 29160
I have a box running with a 29160 card at 160 MB/s on 4.2-RELEASE. It runs very nicely. Make world is a simple task now... ooo... alex had the audacity to say: > > i have a adaptec 39160 running under freebsd 4.2, no problems. i think this > is the same card, just 2 scsi channels instead one. > > dmesg: > ahc0: port 0xcc00-0xccff mem > 0xdfffd000-0xdfffdfff irq 10 at device 10.0 on pci0 > aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1: port 0xdc00-0xdcff mem > 0xd000-0xdfff irq 11 at device 10.1 on pci0 > aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs > > > --On Montag, 7. Mai 2001 13:32 -0700 Alex M <[EMAIL PROTECTED]> wrote: > > > > > Hello All, > > > > I am currently running FreeBSD on an old box, and planning on to install > > 4.2 on my new server-type box, which has Adaptec 29160 SCSI card, the > > thing is that i've checked the hardware compatibility list and didnt find > > this model in there, nor the official adaptec site offers drivers for > > freebsd. > > Is it true it will not work? If yes, I hope support for this card would > > be available soon. > > Best Regards, > > Alex M. > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > PGP signature
Re: XFree86-4.1.0+mga+dri+FreeBSD-4.3-stable == hang
I thought that dfr was supposed to be taking care of this...maybe not anymore. On Mon, Jun 25, 2001 at 11:06:20AM +0100, Rasputin wrote, and it was proclaimed: > * Glenn Johnson <[EMAIL PROTECTED]> [010614 20:27]: > > On Thu, Jun 14, 2001 at 02:36:00PM -0500, [EMAIL PROTECTED] wrote: > > > > > Say I have a Matrox G400, on FreeBSD-4.3-stable, I have installed the > > > FreeBSD 'port' of XFree86-4.1.0 and I try to enable dri, and it hangs. > > > > The DRI stuff does not work with XF86-4.1 and FreeBSD. > > > > > Do I try to foist blame on XFree86, or do I try to foist blame on > > > FreeBSD? > > > > > > I realize this isn't a well formed bug report, I'm holding off on > > > that, until I understand who wants to be put in the frame. > > > > > > My suspicion is that Its FreeBSD, because it relates to their > > > kernel agp.ko module (which I am guessing is required to support > > > DRI->agp->G400 interrelationships somehow. > > > > The agp.ko module is built with the FreeBSD sources and as far as I know > > works fine for most motherboard chip sets. It is required for DRI but > > not sufficient. The other required kernel modules for DRI with a Matrox > > G400 are the mga.ko and the drm.ko modules. These are [optionally] > > built as part of XFree86. The problem is that nobody is keeping the BSD > > branch of the DRI source tree up to date. > > If you go to > > >http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/XFree86-4/?only_with_tag=RELEASE_4_3_0 > > you'l get a version of the port that *should* build the dri modules you need. > You still need to preload agp.ko and mga.ko from /boot/loader.conf, and load > the dri module in XF86Config , but you should be OK. > > Unlike me ,since that port doesn't appear to build tdfx_dri.so . > > If anyone's got DRi on a Voodoo 3 working, please let me know. > Ta! > -- > Moon, n.: > 1. A celestial object whose phase is very important to > hackers. See PHASE OF THE MOON. 2. Dave Moon (MOON@MC). > Rasputin :: Jack of All Trades - Master of Nuns :: > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RAID spanning over two 2400A's supported?
Yeah, Basically that's it in short form. -- coleman On Sun, Apr 21, 2002 at 03:29:49PM +0300, Vallo Kallaste wrote: > > As I understand it, it's basically SCSI RAID controller with some > special firmware which will translate subset of ATA commands to SCSI > and vice versa. Something similar to ATAPI <-> CAM layer translation > in FreeBSD we're all missing 8-) > -- > > Vallo Kallaste > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Unrecognized CPU Class (and a disc error)
Another thing that may cause this behavior is if the 80-conductor ATA cable is attached backwards, with the master end plugged into the host on the motherboard and the host end plugged into the master drive. On Thu, Oct 31, 2002 at 11:02:30PM -0500, Forrest Aldrich wrote: > > >I believe FreeBSD probes the drives independently from the BIOS.. > > > >I had a problem where I plugged a 2.5" HD in via an adapter and it was > >being detected as a UDMA66 drive when it only did UDMA33 and got a > >similar error to yours. > [ ... ] > > I'll go in to the data center tomorrow and check the cables and BIOS -- I'm > sure they were okay. > > If this is a FreeBSD error (and I'm not certain yet) - what was your fix > for this - will this cause problems with the system? > > > Thanks alot, > Forrest > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- coleman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: AMD 3DNow instructions on FreeBSD
Yes, if you compile the PGCC from the ports, or packages (in ports/lang) it has support for 3dnow. --cokane Randall Hopper had the audacity to say: > > Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow > instruction set? > > Why I ask: I attempted to build GLX/Mesa3.1 with 3DNow support, and it > bombed since our assembler isn't 3DNow-knowledgable (femms, pfmul, > etc. undefined). The assembler in -stable has the same shortcoming AFAICT. > > Facts? Rumors? I'm interested in anything you may know. > > Thanks, > > Randall > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CPU voltage (was Re: load spike strangeness)
I believe that these readings have to do not only with the uneven voltages in the power supply, b ut also the accuracy of the instruments used to record them. --cokane Kip Macy had the audacity to say: > My machine is not overclocked and I get similar results > > > > Motherboard Temp Voltages > > 26C / 78F / 299K Vcore1: +1.953V >Vcore2: +1.953V > Fan Speeds + 3.3V: +3.375V >+ 5.0V: +4.906V > 1: 3013 rpm+12.0V: +12.625V > 2: 3708 rpm-12.0V: -13.562V > 3:0 rpm- 5.0V: -5.584V > > > On Sat, 8 Jan 2000, David Bushong wrote: > > > On Sat, Jan 08, 2000 at 10:03:44PM -0800, R Joseph Wright wrote: > > > Awhile back I was having trouble getting through kernel compiles, the > > > machine would reboot during the compile. Someone on some newsgroup said > > > "are you overclocking?". I checked my settings. No, I wasn't > > > overclocking. But my voltage setting looked wrong. It was set at 2.2 > > > volts or whatever and I thought it was supposed to be at 2.4. So I > > > changed it to 2.4. My problem was solved. I was flying through the > > > compiles. Then I was looking through my motherboard manual and realized > > > that it was supposed to be set at 2.2 after all. I prefer it the way it > > > is though. Do you think there is anything wrong with that? > > > > > Hmm. lmmon -i produces some scary results: > > > >Voltages > > > > Vcore1: +2.781V > > Vcore2: +1.469V > > + 3.3V: +3.312V > > + 5.0V: +4.932V > > +12.0V: +12.250V <-- > > -12.0V: -13.125V <-- > > - 5.0V: -5.532V <-- > > > > Those look disturbingly off.. maybe this much drift is common, I don't know. > > However, I never have any problem with the machine, other than this benign > > occurance.. and I do tend to tax it every now and again (couple ports > > building, world building, mp3 encodes, the usual). Ack, can't believe I > > forgot to mention I'm running with soft updates enabled on both drives > > (and root). While I was reading this thread btw, I got another spike, and > > by measuring pixel widths in xload, came up with 30 pixels @ 10 seconds per > > pixel, or 300 seconds, or exactly 5 minutes, which seems awfully round. > > > > Re: overclocking thing: ok, people, I know it's my machine. Take a chill > > pill. I have a very stable CPU, a well ventilated machine, and a jumperless > > motherboard that makes it very easy to switch settings. However, as I have > > said, this machine has been rock solid (except for during a few of those > > sketchy 3.1 release ;) I'll go ahead and try turning off the overclocking > > and see if > > a) it affects the voltage (which does worry me a bit) > > b) I continue to see this load strangeness (I suspect I will) > > > > --David Bushong > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: When does the 4.x branch go stable?
Well, GCC 2.95.x can be patched for pentium, ppro, and k6 optimization to make your programs run faster and more efficiently. If you could compile the base system with it, you would glean more performance from the box. If you go to http://www.goof.com/pcg/ you can see what I'm talking about, there is also a port in /usr/ports/lang/pgcc. --cokane David O'Brien had the audacity to say: > On Mon, Jan 10, 2000 at 12:40:54AM -0500, Coleman Kane wrote: > > Obviously, you have never tried to make world with the new egcs, it is almost > > WHY do you need to make world with GCC 2.95.2? Gcc 2.7.2 acutally > produces smaller code. For some things even faster code. What is so > glammorous about a Gcc 2.95 built world and kernel? > > Use the base compiler to compile the product and install the `egcs' port > for your own code. The big short falling with Gcc 2.7.2 is a total piece > of crap C++ compiler. Since the only thing written in C++ in /usr/src/ > is groff (and very old style C++), who cares. > > > impossible since there are many violations of ANSI C and C++ in the code right > > now. The kernel does, however, properly compile (minus some ext2fs crap). > > Send patches then, if you are a programmer. > > -- > -- David([EMAIL PROTECTED]) >[maintainer of /usr/src/contrib/gcc, `gcc-devel', `egcs', `pgcc'] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FREE CASH, NO CATCH.........
wtf is this? You can't even use this software on freebsd. --cokane [EMAIL PROTECTED] had the audacity to say: > This message is being send in conjuction with the anti-spam policy of AllAdvantage. > If you received this message unwillingly, please accept my most sincere apologies. > To be taken from this list simply respond to this message. Thank you. > > > Subject: Did I tell you about AllAdvantage.com? > > Hi, > > Maybe I haven't told you yet, but I get paid to surf the Web. Really! > > I recently joined AllAdvantage.com, a new company that pays its members to > surf the Web - and they've been paying out millions of dollars to members > since July. $10,000,000+ in the last three month alone!! > > What's the catch? There is no catch. Membership is totally free and private. > To earn money you agree to download a small message window -- called a > Viewbar - on your desktop. The Viewbar delivers information about products > and services available online. > > AllAdvantage.com is for real: > > Their Web site was the 12th most-visited property on the Web in October. > Last month, more than 30 AllAdvantage.com members earned well over US$1,000 > EACH and the top earner pulled in over US$4,400! > The company has more than 3 million members worldwide, but there are still > 75 million active online users (in the US and Canada alone) who are still > waiting to hear about AllAdvantage.com and become members. Be sure you're > the first to tell them about it! > The sooner you join, the sooner you'll get paid. Please use my referral ID > number (gze543), because I get paid when you sign up and surf. Be sure to > tell all your friends who use the Internet -- the more referrals we get, the > more money we can earn. You can sign up with AllAdvantage.com right away by > following the link below: > > http://www.alladvantage.com/go.asp?refid=gze543 > > This is a really great deal with no strings attached! > > Cheers, > Chris. > Member ID# gze543 > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Multiple IP addresses
Easy. To build a firewall of machines that you still want to map unique internet IPs to. I use a nice AMD 5x86 160 to do the job, with OpenBSD. It works rather nicely. I am given 8 IP#'s by my DSL ISP, after broadcast, network, and router that number goes down to 5. I basically map everything through one box and have a sever on the outside, we have an internal network where nome machines get mapped by NAT and three get a dedicated IP mapping. It's like this: 172.16.0.9 ---\10.131.21.178 --\ 172.16.0.10 --->172.16.0.1 <-> 10.131.21.179 ---> 10.131.21.177 --> Outside 172.16.0.39---/10.131.21.180 --/ ^ 10.131.21.182 -/10.131.21.181 Server, outside firewall All the addresses 10.131.21.177-10.131.21.182 are addresses my ISP maps directly to outside internet addresses. I have the four above mapped to one ethernet port of the firewall, and have it map certain IP's to them, 172.16.0.9-172.16.0.11. Of course, there is no .11 above, but you get the idea. Anything out of that range simply uses NAT. I also have DHCP set up to automatically assign certain IPs based on ethernet HW ID, but that's a story for another time --cokane ROGIER MULHUIJZEN had the audacity to say: > >The scenario I have setup is as follows, the server (xl0) has been > assigned > >the IP address of yyy.yyy.yyy.8 and the I route an entire Class C to > that > >interface in the router, e.g. > >ip route xxx.xxx.xxx.0 255.255.255.0 yyy.yyy.yyy.8 > > BTW, I'm just being curious here, why would you want to bind an entire > class C subnet to a single machine? To me it seems like a total waste of > precious real estate (until IPv6 becomes the standard). > >DocWilco > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stray IRQs
IRQ 15 is typically an interrupt for the second IDE controller. You may be using SCSI and have disabled the wdc on a mobo that doesn't like that too much. The network traffic blockage could be attributed to the PIC not being reset before the requests were handled. IRQs 8-15 are handled by IRQ 2, mid you, so they are higher priority if your netcard is on PIC1. --cokane Mike Smith had the audacity to say: > > A mission-critical production machine of ours seems to be > > having issues with stray irqs. > > > > This is in the dmesg: > > - > > stray irq 15 > > stray irq 15 > > stray irq 15 > > stray irq 15 > > stray irq 15 > > too many stray irq 15's; not logging any more > > > > > > It seems as if the ethernet traffic stops for about a minute > > when it posts that message. > > > > I've searched back in the mailing lists to find that this > > may be caused by the BIOS grabbing the IRQ -- and was just > > wondering if anyone else has seen this problem lately? > > No; this is typically caused by having hardware in the system that's > generating interrupts but isn't handled by a driver. It may be > symptomatic of faulty hardware or a system misconfiguration. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
xl0 packet dropping, still
Well, I switched my xl0 ethernet carc, but I am still recieving messages saying that there are packets being dropped. Sometimes this results in the card being shut down. --cokane PGP signature
Re: K6-MTRRs
Roman Shterenzon had the audacity to say: > What models/revisions seem to be broken? > I *think* that K6-2 mtrr works. > That's the impression I was under. I have gotten no information from AMD to say that the MTRRs on their K6-2 line don't work. The only things I know of is that the first-gen chips didn't have them, and the code checks for that. Are you sure that it isn't some interpretation problem with the tech docs? --cokane > On Mon, 6 Mar 2000, Mike Smith wrote: > > > > Well, I know that they are different form those on the PII/III line, > > > and that there are only two. I think that they are implemented in some > > > windows drivers and programs. Maybe whoever is in charge of it could > > > contact me, I have some AMD tech docs and maybe I could take a crack at > > > it. > > > > I'm not sure I follow you. We have implemented support for the K6 memory > > range registers, and having done so, discovered that they don't behave > > like they should. Thus, support was disabled for these CPUs. There's > > nothing more to do, as far as I'm aware - the hardware itself is broken. > > > > > --cokane > > > > > > Mike Smith had the audacity to say: > > > > > I know that the k6 mtrr code is broken. Who is actively working on > > > > > this? I have been messing with it and know that it screws up the > > > > > framebuffer writes in xfree86 4.0. It prevents the writes of certain > > > > > parts of the pixel values. > > > > > > > > Evidence suggests that the problem is actually in the K6 itself. > > > > > > > > -- > > > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > > > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > > > > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > --Roman Shterenzon, UNIX System Administrator and Consultant > [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: K6-MTRRs
Mike Smith had the audacity to say: > > That's the impression I was under. I have gotten no information from AMD to say > > that the MTRRs on their K6-2 line don't work. The only things I know of is that > > the first-gen chips didn't have them, and the code checks for that. Are you sure > > that it isn't some interpretation problem with the tech docs? > > If the original K6's don't have memory range registers, how could we have > tested them and discovered they didn't work? > > At any rate, you're encouraged to talk to the author/maintainer of the > code, Brian Feldman (copied). If you can make it work, wonderful. > Maybe that's it, the original K6 had them but they were "disabled" or at least ignored. I believe that the new K6-2 cores with CXT core have working MTRRs because I remember that being a big thing as well as the cache pipelining. Maybe I should get in touch with AMD on the matter as well. --cokane PGP signature
Re: 4.0 stable upgrade trouble
For anyone who'd like to know, I was able to successfully upgrade to 4.0-RELEASE by downloading the source tarballs, and unpacking them in my /usr/src directory. I cleared it out of the old 3.4 sources beforehand, and found that you must first compile a 4.0 kernel and reboot before attempting a make world. After you reboot, you can drop in to single-user (for safety), and run yoyur make world. Since it only installs the new gcc at the end, you may want to re-make world a second time, or simply make and install gcc, etc. first. --cokane Kris Kennaway had the audacity to say: > You should have read the UPDATING file before attempting this. It explains > the hoops you need to jump through. I don't know whether you can easily > recover from where you are now, it might be best to restore the system > directories from a backup and start again. > > Kris > > On Wed, 29 Mar 2000, Dale Robson wrote: > > > To anyone who can help, > > I've been trying to upgrade from 3.3 stable to 4.0 stable and I've been > > having trouble getting it to work. I have run make buildworld and that > > worked. Then during make installworld I got an error so that only half > > the files were installed. > > The trouble that I now have is that the newly upgraded 'make' links > > with the old versions of several libraries. When I try to run make it > > says: "Bad sytem call". Is there a way to fix make without being able > > to use make? I've made a couple attempts at running a staticly linked > > version on make compiled on other boxes but they all argue about the > > ".include " lines in the make files. Thank you for any > > help. > > > > Dale Robson > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How stable is the ATA code?
I'd like to say that I have been keeping stable with freebsd 4.0, and I am using ata with an FIC-VA503+ (VIA Apollo MVP3) mobo and a WD Expert 18GB Hard Drive (which I recommend to anyone) with no problems. I have been updating my kernel as large changes come along and have been amazed at the stability of the OS and the filesystem. When I first installed FreeBSD 3.0-RELEASE on an old compaq server, the ncr SCSI driver had some nasty troubles with it that caused the filesystem to corrupt and the kernel to panic whenever the scsi bus was put under more than a moderate load. --cokane To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How stable is the ATA code?
I have heard of trouble trying to get a non-UDMA drive working connected to a UDMA drive. Try Linking the ad1 to your CDROM's channel and disable the UDMA for Master+Slave 2nd controller in BIOS. Also, WDMA wasn't properly implemented on some drives (I have an old maxtor to testify to that, and many nights of wasted time). This problem is just in the nature of how IDE works, if the two drives being linked together is the problem. Also, your UDMA options in BIOS tell the controller what mode to set the drive in on POST. It may help if there is some problem in the driver to have it turned off in BIOS. I do know that an ATA66 drive should never share the channel with another drive. --cokane Matt Heckaman had the audacity to say: > > And to add one of those annoying "me too" posts, I absolutely cannot get > my setup to work. It's as follows: > > 4.0-STABLE as of April 3 2000 > > atapci0: port 0xf000-0xf00f at device 7.1 > on pci0 > > ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 > ad1: 1549MB [3148/16/63] at ata0-slave using WDMA2 > acd0: CDROM at ata1-master using WDMA2 > > ad0 and acd0 work fine, ad1 does not. It bombs with the following error: > > ad1: HARD READ ERROR blk# 0ata0-slave: WARNING: WAIT_READY > active=ATA_ACTIVE_ATA > ad1: HARD READ ERROR blk# 0 status=59 error=04 > ad1: DMA problem fallback to PIO mode > ad1: reading primary partition table: error reading fsbn 0 > > sysctl settings: hw.atamodes: dma,pio,dma,---, > > I know the drive is fine, it works under the wd? drivers but that's a less > than ideal situation. My original posting about this got a reply from > Jordon saying that it was the rollover reason for 4.0-RELEASE, but the bug > is still there and I'm at a loss and quite frustrated. > > Regards, > Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How stable is the ATA code?
Yeah, the chipsets also are all handled by their own code, MVP3 setup isn't the same procedure as PIIX4 setup or ALI1541 setup I know, from my experience that my specific revision of the 586B works fine. Some of it I have noticed is also from cramming three or four drives onto the mobo controllers. I have had DMA33 troubles with two hard drives sharing the same channel, stuff like that. Some of that is chipset specific, but if you really need that many devices you should really look into SCSI, I have one CDROM on my secondary and a hard drive on my primary and it works well. If I wanted to add another hard drive or something, I'd probably save up for a SCSI controller and a SCSI hard drive. You start slaving devices on the IDE bus and it really degrades performance, especially mixing UDMA and non-UDMA drives. Most manuals for them specifically say not to do that. --cokane Warner Losh had the audacity to say: > > In message <[EMAIL PROTECTED]> Coleman Kane writes: > : The original point was that the troubles weren't necessarily > : chipset-specific or mobo specific. There is probably some code that > : needs to be dealt with. > > I got the impression that it was this particular 82C586B plus some > marginal IDE drives. I've not seen other chipsets mentioned as often. > > Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Sound issues
Yeah, the ESS AudioDrives are sb-compatible. Also, try adding a device joy to the config and you can get rid of unknown10. --ck Conrad Sabatier had the audacity to say: > On 17-May-00 Ron 'The InSaNe One' Rosson wrote: > > > > Here is what I have in my kernel configuration file: > > # Sound Card > > ## This Works but spits out a bunch of unknowns > > options PNPBIOS > > device pcm0 > > > > Here is the dmesg output for the sound card: > > > > unknown9: at port 0x800-0x807 on isa0 > > sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,5 > > on > > isa0 > > pcm0: on sbc0 > > unknown10: at port 0x201 on isa0 > > > > > > Anyone have any idea what happened. Before I reinstalled I think the > > date of the last 4.0-STABLE was over a month old. > > It looks like your card may be an SB-compatible. Have you tried adding a > "sbc0" entry in your config file? > > -- > Conrad Sabatier > http://members.home.net/conrads/ > ICQ# 1147270 > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
3dfx driver
I have finished the 3dfx driver for FreeBSD finally. What should I do with it now, the tarball would be a little big to stick on the list I assume. It is basically a device driver that can be compiled as a kld or static kernel driver, and another module that is loaded after the linux module to facilitate the linux ioctl interface (which requires drivers to register their own ioctls for linux). Anyway, is there someone in charge of taking care of this sort of thing, or some testers? -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu PGP signature
kerneld for FreeBSD
Would the person or person(s) interested in developing a kerneld-like, dynamic module (un)loader for FreeBSD please email me. I am really interested in this. It would be very advantageous to begin to move kld module use into the mainstream for all components. I'd like to do what I can to help with it. -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu PGP signature
Re: kerneld for FreeBSD
No, they are technically shareable, as long as you don't attept to expect either of them at the software level to respond at a certain time. This is why you can have COM2 and COM4 on the same interrupt in windows or DOS, as long as you don't use them at the same time. The ISA bus is a very simple interface, and typically nothing at the hardware level causes a system to crash when resources are shared. It is usually a driver expecting information from its device, when another one is already using a certain interrupt. The only counter to this is MIO and PIO, where the result of an input is undefined, and an output is supposed to cause the data to go to both devices. I was actually aiming more towards, memory allocations, and other things like MTRRs and X and stuff. From the MTRR standpoint, most 6th gen processors (for the sake of argument the K6CXT is 6th gen) have MTRRs, registers that can define how memory ranges are utilized in the processor. There are only a finite number of these, therefore if you were to disable them for some hardware that didn't need them you could spread them out. It would also be really great (and I was originally not informed about the current state of autoloading/unloading of modules for fs and net devices) to move completely to loading everything out of klds, rather than compiling the kernel. It may also help some debugging to be able to pull apart the kernel peice by peice, having a basic default "failsafe" kernel to boot from that would subsequently begin to load the necessary modules specified, or to load them in real time and unload them when finished. I really am not sure about the reality of this proposal, and someone brought it up earlier, so I thought I'd stick my head in on it. This email is getting rather lengthy, maybe I'll try fiddling with something tonight... school is over until summer quarter starts. Mike Smith had the audacity to say: > > They're "non shareable" at the hardware level ... like all the "non > shareable" hardware resources. > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu PGP signature
Re: kerneld for FreeBSD
Sorry, been working a strange schedule this week. By resources, I meant kernel resources such as kmem space, from what I have been hearing though, it seems as though the kernel does a lot this stuff already. I dunno, but someone else posted awhile back about this, so I was still interested. Mike Smith had the audacity to say: > > > Well, it would be nice to auto-load or unload any module that is needed. > > not just ethernet and fs types. That's basically the idea. Say, if you > > load a driver that uses some resources that another one can use while the > > first one is off... that's what I'm talking about. > > "Some resources?" Er, no offence, but you're not making any sense. > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu PGP signature
Re: Wierd Log Messages
My roommate had the same problem with his sony VAIO laptop. I pruned the kernel config file and replaced all isa ata entries with 'device ata'. I also removed the ATAPI_STATIC_ID. I can't remember completely what else I may have done, but that was about it, I think. Pat Wendorf had the audacity to say: > > I've been getting some weierd log messages, and random reboots under > heavy swap file load on my laptop. > LICQ, and Netscape are notorious for causing this behaviour. > > Any info on what the problem is would be appreciated > > Pat Wendorf > > > Log Messages: > > Jun 21 18:30:28 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:29 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:29 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 44760, size: 12288 > Jun 21 18:30:29 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 19032, size: 4096 > Jun 21 18:30:29 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:29 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:30 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 32888, size: 4096 > Jun 21 18:30:30 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/ > 0x30001, blkno: 32336, size: 4096 > Jun 21 18:30:30 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:30 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:30 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 44760, size: 12288 > Jun 21 18:30:30 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 19032, size: 4096 > Jun 21 18:30:30 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:31 laptop /kernel: swap_pager: I/O error - pagein failed; > blkno 44760,size 12288, error 5 > Jun 21 18:30:31 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:31 laptop /kernel: vm_fault: pager read error, pid 241 > (licq) > Jun 21 18:30:31 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 32888, size: 4096 > Jun 21 18:30:31 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 12440, size: 8192 > Jun 21 18:30:31 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 32336, size: 4096 > Jun 21 18:30:32 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:32 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:32 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 19032, size: 4096 > Jun 21 18:30:32 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:32 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:32 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 32888, size: 4096 > Jun 21 18:30:32 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 12440, size: 8192 > Jun 21 18:30:32 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 32336, size: 4096 > Jun 21 18:30:33 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:33 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:33 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 6, size: 4096 > Jun 21 18:30:33 laptop /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x30001, blkno: 19032, size: 4096 > Jun 21 18:30:33 laptop /kernel: ad0: READ command timeout - resetting > Jun 21 18:30:33 laptop /kernel: swap_pager: I/O error - pagein failed; > blkno 19032,size 4096, error 5 > Jun 21 18:30:34 laptop /kernel: ata0: resetting devices .. done > Jun 21 18:30:34 laptop /kernel: vm_fault: pager read error, pid 231 > (wmmon) > Jun 21 18:30:34 laptop /kernel: pid 241 (licq), uid 1001: exited on > signal 6 (core dumped) > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: AMD K6-2 / 550
But I thought the P!!! really did make the internet come alive. :) Jeffrey J. Mountin had the audacity to say: > At 05:37 AM 7/5/00 -0700, Mike Harding wrote: > > >Yeah, but does AMD have disco-dancing clean-room technicians and > >animated sock monkeys? Does AMD "improve your internet experience" > >with "brighter colors?" > > The past 2 years Intel has been terrible with the BS it pushes on the > mostly ignorant consumer. Have been rooting for AMD since the K7/Athalon > was in design. Intel's recent problems and refusal of supporting PC133 and > DDRSDRAM to push (or should I say ram) RAMBUS on everyone.. No need to > rant, but AMD has come a long way. My next personal system will be a dual > AMD. The capability is due later this year. With their greatly improved > production capacity Intel best look out, since they will then be able to > start in on the mid-range server market. > > They only question then is SMP support for AMD system. > > >Sorry about the OT, but these ads have bugged me for years. :) > > Intel's policies have PO'd me for ages now, so pardon my OT rant. > > Intel Inside^H^H^H^H^H^HElsewhere. > > > Jeff Mountin - [EMAIL PROTECTED] > Systems/Network Administrator > FreeBSD - the power to serve > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0-20000714-SNAP on 486 DX2-66
Excellent, man. That's totally awesome. I love old hardware that's made use of. Max Khon had the audacity to say: > hi, there! > > yesterday I have succesfully installed 4.0-2714-SNAP > (I have built it by myself) on 486 DX2-66 machine > (3.4/3.5-RELEASE refused to install there -- hangs while installing > probably related to bugs in wd driver) > > everything seems to work fine > generating DSA key takes 20 minutes (no less!) > > /fjoe > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: agp and 3dfx
XFree86-4 has been updated to the newest version. It has a kld named tdfx.ko that must be installed into /modules/. When you load X, it will load dri, agp, and tdfx all for you. There is also a 3dfx.ko to work with /dev/3dfx. This is provided to support device accesses for glide programs, like quake3 and all. It currently has some issues with the Voodoo3 and Banshee hardware, but I could use another tester. It is part of -CURRENT, and will most likely panic your box, but some output sent to me about the crash would be helpful. Actually, if anyone has an old agp 3dfx card they'dl ike to donate for this development, it would be helpful. I have been testing it with my voodoo2 board with much success, but I have had some responses from users with Voodoo3's that say that they haven't gotten it to work. Nawfal M. Rouyan had the audacity to say: > > hi all, >How do one make use of the new agp driver? > Recently, there were discussions on the new 3dfx > driver. Where can i get it? is it in the base system already? > > __ > Do You Yahoo!? > Get Yahoo! Mail ? Free email you can access from anywhere! > http://mail.yahoo.com/ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
