Re: ata drivers

On Tue, 21 Sep 1999, David Krinsky wrote: > On Mon, Sep 20, 1999 at 12:05:38AM +, Gary Hampton ([EMAIL PROTECTED]) >wrote: > > On Mon, 20 Sep 1999, Adam Strohl wrote: > > > > > Remake your acd device, I think you may need a patch to do it. I had the > > > same problem, until I rm-ed the de

Re: ata drivers

On Mon, Sep 20, 1999 at 12:05:38AM +, Gary Hampton ([EMAIL PROTECTED]) wrote: > On Mon, 20 Sep 1999, Adam Strohl wrote: > > > Remake your acd device, I think you may need a patch to do it. I had the > > same problem, until I rm-ed the device and remade it. > > > > - ( Adam Strohl )

Re: DANGER: login and friends with libscrypt/libdescrypt

> - /usr/bin/login and friends are now linked against libscrypt > instead of libcrypt. This is a link bug. The Makefile says "-lcrypt". JDP? i M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebs

Re: 2xPIIIx450 results & NFS results

Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Mike Smith writes: > >> >Use a watchdog timeout like you should for any device that may hang. > >> >Don't waste time running it every clock tick. > >> > > >> >ISTR that we thought that the bug might be caused by a bug in unwanted > >> >SMI

Re: Wierd su/vnc issue

Well, is there a work around, telneting out does the same thing, using the -l option used to allow me to log into remote hosts, not anymore, same with loopback telneting and suing. I can hear Jordan already: "TAKE IT LIKE A MAN!" ;'D - ( Adam Strohl )

Re: Wierd su/vnc issue

On Mon, Sep 20, 1999 at 09:16:13PM +, Adam Strohl wrote: > adams@nightfall(21:13:30)$ su > Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k > > As soon as I hit enter I get more: > load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k I saw that, too. That might be a strange side e

Wierd su/vnc issue

adams@nightfall(21:13:30)$ su Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k As soon as I hit enter I get more: load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k (hit enter 3 t

DANGER: login and friends with libscrypt/libdescrypt

I've just been bitten by the following, so I figured I might as well warn others. From a quick glance it doesn't seem to have been mentioned, or not clearly enough, in this list. - libscrypt/libdescrypt major number has been bumped a few days ago. - /usr/bin/login and fr

Re: Testers please!

In reply: > If you have a PIIX4 based SMP system and run current, could you > please try out this patch: > > http://phk.freebsd.dk/piix/ > > I'm very interested in hearing if there are any measurable difference > apart from clock granularity being 3 times better. just cvsupped, added your

is this a f77 issue, egcs issue, or os issue?

Just for kicks, while waiting for my phones to be hooked up at the new address, I ran some heavy duty benchmarks to see if the systems transported fine. i think they did arrive undamaged in the move, but i ran pitest at the maximum rated precision. apparently, this is not a /usr/bin/time issue,

Re: ep0 etherlink III breakage

> WHAT am I supose to do with this? I don't even understand what you > are trying to tell me. You booted single user and got a hang. What > is the #'ed line supose to be? Last time *_I_* booted single user I > didn't see such output. Actually I don't really care what you do wi

Re: ep0 etherlink III breakage

I'm not certain what the problem is, but the ep0 changes that generated the HEADS UP messages affect _only_ PC Cards. The other sections of code are untouched. Further, I'm 99% sure the only card that could possibly have been broken by the probe change is the 3C574 PC Card (not 3C574B). Jason Y

Re: request for review, patch to specfs to fix EOF condition alignment with buffer

> This problem was first found by Tor. Tor's example creates > an oddly-sized VN partition and then dd's from it. Without the > patch the dd believes that it can read 2880 sectors. With the > patch it correctly reads the last (truncated) block. Actually, the problem was discus

ports/net/kicq problem

Hello ppl, i have installed latest (1.1.2) kde11-i18n based on qt-i18-1.44a library. kde itself works fine but, now i'm experiencing another problem: old binaries that were built with older qt do not run. but the worst thing is impossibility to re-build that binaries with new qt using ports (kic

Re: ep0 etherlink III breakage

On Mon, Sep 20, 1999 at 11:58:28AM -0700, David O'Brien wrote: > > Sequence of events boot -s > > # ifconfig ep0 inet 192.168.18.200 > > (PC hangs) > \begin{wpaul} Dunno, you seem too mellow. > WHAT am I supose to do with this? I don't even understa

Re: request for review, patch to specfs to fix EOF condition alignment with buffer

>Once this patch is committed, the only problem we will have is >in recognizing the write-EOF case, which I will have a >recommendation for after this patch goes in. ...and the lack of error code returns on write. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROT

request for review, patch to specfs to fix EOF condition alignment with buffer

This is a request for a review. This patch fixes a bug in specfs relating to dealing with the EOF condition of a block device. If the EOF occurs in the middle of a block, specfs was not properly calculating the truncation for the I/O. This problem was first found by Tor. To

Re: ep0 etherlink III breakage

On Mon, Sep 20, 1999 at 12:28:27PM -0500, Mark Hittinger wrote: > Hey per request I'm reporting some ep0 breakage in today's -current. I have > an etherlink III 3c509B and the probing appears correct. > > Sequence of events boot -s ># ifconfig ep0 inet 192.168.18.200 >

Re: Page fault with ethernet xl0

Of all the gin joints in all the towns in all the world, Stephan van Beerschoten had to walk into mine and say: > I have experienced something nasty. After cvs'ing my tree 3 hours > ago which would be approx 16:00 CET, I did a buildworld, installed > it, compiled a new kernel. Dammit. You didn'

Page fault with ethernet xl0

I have experienced something nasty. After cvs'ing my tree 3 hours ago which would be approx 16:00 CET, I did a buildworld, installed it, compiled a new kernel. This was right after the announcement that improvements had been made to the xl device driver. I wanted to try... The Result: Pagefault

ep0 etherlink III breakage

Hey per request I'm reporting some ep0 breakage in today's -current. I have an etherlink III 3c509B and the probing appears correct. Sequence of events boot -s # ifconfig ep0 inet 192.168.18.200 (PC hangs) More later... Mark Hittinger Mindspring/Net

Re: 2xPIIIx450 results & NFS results

Hi, > Use a watchdog timeout like you should for any device that may hang. > Don't waste time running it every clock tick. > > ISTR that we thought that the bug might be caused by a bug in unwanted > SMI interrupt handling. Upgrading the BIOS to Rev. 1010 does solve the problem for me without the

Web page w/ postmark results so far...

Folks, I haven't put everything online that I've gotten so far, but I have started putting my information online. See . The tables were taken directly from Network Appliance, and then extended to include the additional entries

Re: 2xPIIIx450 results & NFS results

In message <[EMAIL PROTECTED]>, Mike Smith writes: >> >Use a watchdog timeout like you should for any device that may hang. >> >Don't waste time running it every clock tick. >> > >> >ISTR that we thought that the bug might be caused by a bug in unwanted >> >SMI interrupt handling. >> >> If anybod

Re: 2xPIIIx450 results & NFS results

> >Use a watchdog timeout like you should for any device that may hang. > >Don't waste time running it every clock tick. > > > >ISTR that we thought that the bug might be caused by a bug in unwanted > >SMI interrupt handling. > > If anybody can reproduce this reliably on a *BX chipset I have > co

Re: 2xPIIIx450 results & NFS results

In message <[EMAIL PROTECTED]>, Bruce E vans writes: >> I remember this one too. I think the problem is that we fail to >> service the RTC intr for some reason. This patch was only a >> workaround, and received a verbal broadside from Bruce if I >> remember right. >> >> Maybe it should be add

Re: 2xPIIIx450 results & NFS results

> I remember this one too. I think the problem is that we fail to > service the RTC intr for some reason. This patch was only a > workaround, and received a verbal broadside from Bruce if I > remember right. > > Maybe it should be added under a sysctl until a better solution > is know. > > -

Re: Testers please!

In message <[EMAIL PROTECTED]>, Peter Wemm writes : >Poul-Henning Kamp wrote: >> >> Ok, noted. I changed to to fail the probe but still use the hardware. > >If intpm is probed first (the smbus driver), your probe won't even get >called. I think we need an early quirks or hooks handler in the pci

Re: Testers please!

Poul-Henning Kamp wrote: > > Ok, noted. I changed to to fail the probe but still use the hardware. If intpm is probed first (the smbus driver), your probe won't even get called. I think we need an early quirks or hooks handler in the pci probes to handle stuff like this. For example, we have h

Re: newpcm and Vibra16X

I don;t need it back...so I don't mind... Peter Wemm also had an idea, of setting up a clean installed box here allowing certain hosts into the network and giving a serial console to work from. I don;t mind doing this either. Let me know. If you want me to ship it, give me your address and I'll

Re: newpcm and Vibra16X

On Sun, 19 Sep 1999, Pat Lynch wrote: > I have an extra Vibra16X if you haven't gotten one yet, I'm dying to have > my sound working again. -Pat If you don't mind shipping it to the UK, I can give you my address. Cameron is in the process of moving and I don't have his new address. I'm very keen

Re: Testers please!

Ok, noted. I changed to to fail the probe but still use the hardware. Poul-Henning In message <[EMAIL PROTECTED]>, Peter Wemm writes : >Poul-Henning Kamp wrote: >> >> If you have a PIIX4 based SMP system and run current, could you >> please try out this patch: >> >> http://phk.freebsd.d