Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Wilko Bulte
On Fri, Nov 02, 2001 at 12:21:22AM +0100, Wilko Bulte wrote: I forgot to mention that I had the same config running fine on the same Abit MB using 4.3-stable. And that PII-266 is a VIA chipset of some sort, not an Intel like I write below Wilko > Hi > > I'm looking for comments on the follow

system hung with runnable processes

2001-11-02 Thread Jeff Fellin
I didn't see anything like this in the archives, so I'm sending this to the questions list and hackers list for assistance. I am running FreeBSD 4.3 on a L440GX+ motherboard with dual PCI buses: 32/33 and 32/66 dual Pentium III @ 700MHz with 256KB L2 cache. The system is running in Uniprocessor m

Re: head(1) speedup

2001-11-02 Thread Greg Shenaut
In message <[EMAIL PROTECTED]>, Alfred Perlstein cleopede: >can someone please check this out, it makes "head -n" about five >times faster. (also nukes a 'register', sorry :)) I'm curious--does using fgetln here always result in a win, or just with short lines? I'm thinking of the impact of rea

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Wilko Bulte
On Fri, Nov 02, 2001 at 07:26:48AM -0700, Justin T. Gibbs wrote: > >On Fri, Nov 02, 2001 at 12:21:22AM +0100, Wilko Bulte wrote: > > > >I forgot to mention that I had the same config running fine > >on the same Abit MB using 4.3-stable. > > In 4.3-stable, we ignored the parity errors due to a log

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Lorenzo Iania
  Hi,I believe that this is the same problem I have booting the 4.4 on mynotebook: everthing is all right using 4.3 stable, but it is impossible toboot it using a 4.4 kernel and the solution proposed by Warner Losh did notresolve my problem because the code he sent me is the same I have in m

Re: head(1) speedup

2001-11-02 Thread Alfred Perlstein
* Greg Shenaut <[EMAIL PROTECTED]> [011102 08:42] wrote: > In message <[EMAIL PROTECTED]>, Alfred Perlstein cleopede: > >can someone please check this out, it makes "head -n" about five > >times faster. (also nukes a 'register', sorry :)) > > I'm curious--does using fgetln here always result in

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Gary Jennejohn
On Friday 02 November 2001 00:21, Wilko Bulte wrote: [snip problem description] > I ran the same systemdisk & all expansion cards in a PII-266 > with Intel chipset without any issue. The K7V is rock stable > as long as I keep my fingers from fxtv. > > Suggestions on how to analyse/workaround this

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Wilko Bulte
On Fri, Nov 02, 2001 at 09:52:28AM +0100, Gary Jennejohn wrote: > On Friday 02 November 2001 00:21, Wilko Bulte wrote: > [snip problem description] > > I ran the same systemdisk & all expansion cards in a PII-266 > > with Intel chipset without any issue. The K7V is rock stable > > as long as I kee

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Mike Silbersack
On Fri, 2 Nov 2001, Wilko Bulte wrote: > On Fri, Nov 02, 2001 at 12:21:22AM +0100, Wilko Bulte wrote: > > I forgot to mention that I had the same config running fine > on the same Abit MB using 4.3-stable. > > And that PII-266 is a VIA chipset of some sort, not an Intel like I > write below > >

Re: head(1) speedup

2001-11-02 Thread Chris Costello
On Friday, November 02, 2001, Alfred Perlstein wrote: > > I'm curious--does using fgetln here always result in a win, or just > > with short lines? I'm thinking of the impact of realloc and memcpy > > on speed. > > Ugh, I should have checked that, my guess is that performance > isn't going ot be

Re: ep0 driver oddity

2001-11-02 Thread Leo Bicknell
Thanks to all who had suggestions. Turned out the card had tossed it's cookies, rerunning the 3com setup showed bogus values for the port and IRQ, and simply resetting it and rebooting fixed the problem. -- Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440 PGP keys at http://www.ufp.

No Subject

2001-11-02 Thread îÏ×ÙÅ ÂÁÚÙ ÄÁÎÎÙÈ 2001-2002
éÚ×ÉÎÉÔÅ, ÅÓÌÉ ÷Ù ÎÅ ÚÁËÁÚÙ×ÁÌÉ ÜÔÕ ÉÎÆÏÒÍÁÃÉÀ, ÎÏ ×ÏÚÍÏÖÎÏ ÜÔÏ ÔÏ, ÞÔÏ ÷Ù ÔÁË ÄÏÌÇÏ ÉÓËÁÌÉ! ðÒÅÄÌÁÇÁÅÍ ÷ÁÍ ÓÌÅÄÕÀÝÉÅ ÐÒÏÇÒÁÍÍÙ É ÎÏ×ÙÅ âÁÚÙ ÄÁÎÎÙÈ: 1. ðÒÏÇÒÁÍÍÕ "SUBMIT WOLF 3.2" - Á×ÔÏÍÁÔÉÞÅÓËÏÇÏ ÒÁÚÍÅÝÅÎÉÑ ÒÅËÌÁÍÎÙÈ ÓÏÏÂÝÅÎÉÊ ÎÁ 1100 ÒÕÓÓËÏÑÚÙÞÎÙÈ ÜÌÅËÔÒÏÎÎÙÈ ÄÏÓËÁÈ ÏÂßÑ×ÌÅÎÉÊ ÐÏ ×Ó

Re: ep0 driver oddity

2001-11-02 Thread Matthew N. Dodd
On Fri, 2 Nov 2001, Leo Bicknell wrote: > Thanks to all who had suggestions. Turned out the card had tossed > it's cookies, rerunning the 3com setup showed bogus values for the > port and IRQ, and simply resetting it and rebooting fixed the > problem. For the archives; this is -very- common for

Re: About stscasestr() prototyped with string.h of current lib

2001-11-02 Thread Andrey A. Chernov
On Fri, Nov 02, 2001 at 05:50:07 -0500, Thomas David Rivers wrote: > > > > On Fri, Nov 02, 2001 at 17:36:04 +0900, NINOMIYA Hideyuki wrote: > > > > > In implementation with current, even if you implemented it for the > > > reason that Linux included, there is the problem that behavior is > > > d

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Justin T. Gibbs
>On Fri, Nov 02, 2001 at 12:21:22AM +0100, Wilko Bulte wrote: > >I forgot to mention that I had the same config running fine >on the same Abit MB using 4.3-stable. In 4.3-stable, we ignored the parity errors due to a logic bug. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsu

Re: About stscasestr() prototyped with string.h of current lib

2001-11-02 Thread Andrey A. Chernov
On Fri, Nov 02, 2001 at 17:36:04 +0900, NINOMIYA Hideyuki wrote: > In implementation with current, even if you implemented it for the > reason that Linux included, there is the problem that behavior is > different from Linux in about prototyping reference. 1) Our strcasestr() implementation is n

Re: About stscasestr() prototyped with string.h of current lib

2001-11-02 Thread Hajimu UMEMOTO
Hi, > On Fri, 2 Nov 2001 12:01:19 +0300 > "Andrey A. Chernov" <[EMAIL PROTECTED]> said: ache> On Fri, Nov 02, 2001 at 17:36:04 +0900, NINOMIYA Hideyuki wrote: > In implementation with current, even if you implemented it for the > reason that Linux included, there is the problem that beh

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Justin T. Gibbs
>It appears things are more complicated than that. I have swapped >the Adaptec 29160 for a 2940UW. I am now running continous buildworlds, >a 'dd' of the SCSI disk and fxtv in parallel. > >This appears to work like a charm until now. I'll let it run and >see what develops I bet you the aic7892 o

Re: ahc(4) reports PCI parity error interrupt

2001-11-02 Thread Wilko Bulte
On Fri, Nov 02, 2001 at 01:24:59PM -0700, Justin T. Gibbs wrote: > >It appears things are more complicated than that. I have swapped > >the Adaptec 29160 for a 2940UW. I am now running continous buildworlds, > >a 'dd' of the SCSI disk and fxtv in parallel. > > > >This appears to work like a charm

Re: About stscasestr() prototyped with string.h of current lib

2001-11-02 Thread Andrey A. Chernov
On Fri, Nov 02, 2001 at 22:01:13 +0900, Hajimu UMEMOTO wrote: > I think nin said that having strcasestr() in our standard header > breaks existing program. Existen programs must be ported to FreeBSD first. > That is, our header seems not confirm > standard. Use #define _ANSI_SOURCE or _POSI