Wes Peters wrote:
>
> This might be the new 82559ER; I'm downloading the datasheet now. Have
> a peek at:
>
> http://developer.intel.com/design/network/datashts/index.htm
Nope, that one is apparently device ID 0x1209. Too bad they don't have
a PCI device ID cross-reference on the web
David Greenman wrote:
>
> >
> >Sorry, I forgot to say about the above. Since Wes Peters suggested that it
> >might be a 82558, it put the above name. Please correct it to whatever the
> >name should be.
>
>From your other email it sounds like it has an 82559. Intel has been
> shipping that f
Here's a reimplementation of my earlier per cpu time keeping patch
on SMP. The attached patch is against a 11/20/99 -current that I
cvsup'ed.
1. On UP,
sys_time is a global and contains the system wide stats
cpu_time is a global and is essentially the same as sys_time.
2. On S
>
> If you can't find the id on the chip, I'll see what I can track down at
> Intel tomorrow.
>
I am looking up the Intel website. The chip indeed is 82559. Also
there doesn't seem to be a correlation between the chip and the PCI device_id.
I have two network cards (I mentioned them in my l
Mohit Aron wrote:
>
> >
> > > #define FXP_VENDORID_INTEL 0x8086
> > > #define FXP_DEVICEID_i825570x1229
> > >+#define FXP_DEVICEID_i825580x1030
> >
> >This wouldn't be correct. The 82558 has been used for years on Pro/100+
> > boards and they ID as 0x1229.
> >
>
> Sorry, I forgot
>
>From your other email it sounds like it has an 82559. Intel has been
> shipping that for more than a year as well on boards that ID as 0x1229,
> so apparantly the chip being used doesn't correlate with the ID number.
I mentioned another similar card in my last posting. That one I got fro
>
>>
>> > #define FXP_VENDORID_INTEL 0x8086
>> > #define FXP_DEVICEID_i825570x1229
>> >+#define FXP_DEVICEID_i825580x1030
>>
>>This wouldn't be correct. The 82558 has been used for years on Pro/100+
>> boards and they ID as 0x1229.
>>
>
>
>Sorry, I forgot to say about the above.
>
> Bah. It sounds like an Intel ploy so that they can trivially identify
> these cards and put the "right" name up in the Windows network setup box.
> This isn't quite what the idea was with PCI IDs originally. 8(
Probably. One of our faculty actually bought what seems like a slightly
diffe
>
> > #define FXP_VENDORID_INTEL 0x8086
> > #define FXP_DEVICEID_i825570x1229
> >+#define FXP_DEVICEID_i825580x1030
>
>This wouldn't be correct. The 82558 has been used for years on Pro/100+
> boards and they ID as 0x1229.
>
Sorry, I forgot to say about the above. Since Wes P
> #define FXP_VENDORID_INTEL 0x8086
> #define FXP_DEVICEID_i825570x1229
>+#define FXP_DEVICEID_i825580x1030
This wouldn't be correct. The 82558 has been used for years on Pro/100+
boards and they ID as 0x1229.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project
On Sun, 05 Dec 1999, you wrote:
>
> > The question: Why doesn't this work... it seem so straight forward...
>
> I'm not sure about the code in question, but the basic assumptions you're
> making about PCI's behaviour are flawed. To achieve the goal you're
> trying to, you need to reduce the va
>
> It's probably an 82558 chip. Does it support Wake-on-LAN?
>
Not sure what Wake-on-LAN means. I believe there are some cards out there
now that support some kind of network management. This is not that if that
helps.
>
> Add the device IDs to the list in the driver and recompile. If it
>
> > Er, you should read the sio(4) manpage too. tty-level buffer overflows
> > have nothing to do with interrupt latency/execution time.
>
> You mean this:
>
> sio%d: tty-level buffer overflow. Problem in the application. Input has
> arrived faster than the given module could pr
> I got some new Intel 10/100Mbps network interfaces recently, but
> unfortunately found that FreeBSD (version 4.0-19990827-CURRENT) doesn't
> recognize them. These are called the "Intel InBusiness 10/100 PCI Network
> Adaptor". Unfortunately, these are the only ones supported in the stores
> Question,
>
> I am a graduate student at Duke University. Currently, I am part of a team to
> build a terabit router using a cluster connected with Myrinet. One aspect of
> the project is to tune the devices & drivers to perform cooperatively... In a
> routing situation, the 1500B dma takes r
On Mon, 6 Dec 1999, Leif Neland wrote:
>
> >
> > If it already hasn't been done, we should capture the procedure that
> > Jordan posted, added to by Matt and maybe post it to the troubleshooting
> > part of the guide(s).
> >
> >
> > Unlike some of us who've been fooling with computers since
Sorry I missed this question. Check www.acl.lanl.gov/~rminnich for v9fs
and see if you can use it.
ron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, 6 Dec 1999, Darren Reed wrote:
> How reliable should the ep0 driver be with 3c389d pcmcia cards ? It gets
> detected by pccardd without any problems and a driver is attached to it,
> but I'm not getting much in the way of performance from it with "link2"
> selected for UTP (doesn't work w
Mike,
So I'm to blame that my project schedule didn't happen to coincide
with the FreeBSD release schedule? Give me a break. The project hasn't
even gone into production yet. And I think you'll find that your apparent
assumption that no one was told about the problems is equally rash. I
poste
%Nick Hibma wrote:
%>
%> Being multi-threaded has almost nothing to do with being
%> multi-processor. Multi-threading means that your application has
%> multiple threads of execution that are able to run simultaneously.
%>
%> The multi-processing capability of your box means that 2 threads of
%>
ejecting a modem pcmcia card caused 3.3 to do the following:
/kernel: sio2 unload,gone
/kernel: Return IRQ=11
/kernel: Card removed, slot 1
/kernel: Card inserted, slot 0
and then it was frozen.
Will there be a 3.4 with things like this fixed ?
Darren
To Unsubscribe: send mail to [EMAIL PRO
How reliable should the ep0 driver be with 3c389d pcmcia cards ? It gets
detected by pccardd without any problems and a driver is attached to it,
but I'm not getting much in the way of performance from it with "link2"
selected for UTP (doesn't work with "media 10baset/utp"). It's being
used in
Matthew Dillon wrote:
> :
> :All running software has serious problems, that's why it is never considered
> :done. Taking the time to enumerate specific problems that are currently
> :plaguing an installation is the only way anyone can possibly hope to help.
> :Problems reports of "It don't work"
Mohit Aron wrote:
>
> Hi,
> I got some new Intel 10/100Mbps network interfaces recently, but
> unfortunately found that FreeBSD (version 4.0-19990827-CURRENT) doesn't
> recognize them. These are called the "Intel InBusiness 10/100 PCI Network
> Adaptor". Unfortunately, these are the only
Nick Hibma wrote:
>
> Being multi-threaded has almost nothing to do with being
> multi-processor. Multi-threading means that your application has
> multiple threads of execution that are able to run simultaneously.
>
> The multi-processing capability of your box means that 2 threads of
> executi
oh, one more thing... (replying to myself)
On Sun, 5 Dec 1999, Alfred Perlstein wrote:
>
> I've been trying to workout mega-clusters for NFS, since afaik the
> vfs_cluster code will only do 64k chunks and we can benifit greatly
> by compacting ranges for commit RPCs.
My code seems to have the
I've been trying to workout mega-clusters for NFS, since afaik the
vfs_cluster code will only do 64k chunks and we can benifit greatly
by compacting ranges for commit RPCs.
The problem, is that it seems that NFS has been having issues, doing
large appends on my box (lptest 80 10 > /nfsmount/
Brian Dean writes:
> No dropped packets, but definitely some occasional long delays before
> I get the echo. However, I must concede, based on other respondants,
> that something else must be going on and I cannot necessarily
> attribute this to divert/firewall/natd.
>
> However, the above numbe
> On a recent project I encountered two show-stopping bugs with 3.3-release
> that did not exist in 2.2.8-release:
>
> 1) Random crashes in FXP interrupt or low-level IP code. Something is
>clobbering the kernel stack--possibly the NCR driver, since using an
>Adaptec made the problem sto
>
> If it already hasn't been done, we should capture the procedure that
> Jordan posted, added to by Matt and maybe post it to the troubleshooting
> part of the guide(s).
>
>
> Unlike some of us who've been fooling with computers since pre-1985, this
> standard operating procedure may not be
Hi,
I got some new Intel 10/100Mbps network interfaces recently, but
unfortunately found that FreeBSD (version 4.0-19990827-CURRENT) doesn't
recognize them. These are called the "Intel InBusiness 10/100 PCI Network
Adaptor". Unfortunately, these are the only ones supported in the stores no
At 3:17 PM -0500 12/4/99, Robert Watson wrote:
>On 4 Dec 1999, Assar Westerlund wrote:
>
> > Garance A Drosihn <[EMAIL PROTECTED]> writes:
> > > In the case of AFS, I think you'd want to expand the size of st_dev.
> > > All files in an AFS volume are "one device", I would think. If the
> > > "dev
Hi,
> >and disable natd and the firewall code, these delays go away so I am
> >assuming that it is natd/firewall/divert that is responsible for this
> >delay.
>
> I think that is a bad assumption.
[snip]
> I'm running FreeBSD 3.3 with IPFIREWALL, IPDIVERT, and natd also over a
> 56k modem, and
In message <[EMAIL PROTECTED]>,
Kelly Yancey <[EMAIL PROTECTED]> wrote:
>>
>>3b) Examination of the drive(s) in question for any cooling or
>>mounting deficiencies. Depending on the SCSI errors in question,
>>I might even investigate firmware updates for the drive(s).
>>
> Another interesting cause for problems is duff powersupplies. As the
> proverb goes "every machine is as good as it's PSU". E.g. I just struggeled
> with a DLT tape unit that inexplicable reset itself. After examining the
> 5Volts rail with a scope I found glitches on it whenever the drive did
As Kelly Yancey wrote ...
> >
> >3b) Examination of the drive(s) in question for any cooling or
> >mounting deficiencies. Depending on the SCSI errors in question,
> >I might even investigate firmware updates for the drive(s).
> >
>
> I actually used to get these *exact*
On Sat, 04 Dec 1999 15:44:49 -0800, "Ronald F. Guilmette" <[EMAIL PROTECTED]> wrote:
>Specifically, I'm planning a large mail server... which will use Sendmail...
>and I'd really like to allocate the Sendmail queue files... which typically
>have a rather short lifespan... on/in some sort of filesy
On Mon, Dec 06, 1999 at 09:15:55AM +1300, Joe Abley wrote:
> I've just noticed that (on STABLE, at least) it doesn't seem possible
> to run an NFS server on a machine, and have it service requests from
> clients talking to anything other than the base address.
We've some patches which Matt Dillo
> >1. It's quite possible that the drive and/or the cabling in this
> > system has been defective all along.
>
> I suspect not, based upon the history.
>
> I think that the drive and/or controler has just developed this sickness
> within the past 24 hours.
>
> >2. It's equally possible that
Question,
I am a graduate student at Duke University. Currently, I am part of a team to
build a terabit router using a cluster connected with Myrinet. One aspect of
the project is to tune the devices & drivers to perform cooperatively... In a
routing situation, the 1500B dma takes roughly 11us
In message <[EMAIL PROTECTED]>,
"Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote:
>> "... even though I used it on Linux for several months."
>>
>> I read that as meaning "the drive worked despite the fact that it was on
>> Linux".
>
>Well, just to inject a note of reality into this discussion:
>
On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
>
> In message <[EMAIL PROTECTED]>, you
> P.S. The other reference you gave:
>
> >http://www.ece.cmu.edu/~ganger/CSE-TR-254-95/
>
> seem to no longer be useful/functional.
That is because it should be ~ganger/CSE-TR-254-95/
>
>
To Unsubsc
In message <[EMAIL PROTECTED]>,
Bill Fumerola <[EMAIL PROTECTED]> wrote:
>On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
>
>> The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
>> Viking 4.5GB SCSI. I have never had any problem with this drive before,
>> even though I used it
> 3. Any system I saw spitting out errors like this would get the following
>treatment, in roughly this order:
>
>3a) Complete check of all cables and the seating of connectors.
>
>3b) Examination of the drive(s) in question for any cooling or
>mounting deficiencies. Dependi
>
>3b) Examination of the drive(s) in question for any cooling or
>mounting deficiencies. Depending on the SCSI errors in question,
>I might even investigate firmware updates for the drive(s).
>
I actually used to get these *exact* errors a couple of years ago on
various
> "... even though I used it on Linux for several months."
>
> I read that as meaning "the drive worked despite the fact that it was on
> Linux".
Well, just to inject a note of reality into this discussion:
1. It's quite possible that the drive and/or the cabling in this
system has been defe
In message <[EMAIL PROTECTED]>, you
wrote:
>See src/sys/ufs/ffs/README.softupdates, which tells you what you need to get
>them to work
Thank you. I'll definitely be looking at that.
P.S. The other reference you gave:
>http://www.ece.cmu.edu/~ganger/CSE-TR-254-95/
seem to no longer be usef
In the last episode (Dec 05), Ronald F. Guilmette said:
> Matthew Dillon <[EMAIL PROTECTED]> wrote:
> > Mail queue files are persistant enough (upwards of 5 days if a
> > destination is down) that you run a real risk of losing something
> > important if you crash and wipe. I would not use MFS at
Hi,
I've just noticed that (on STABLE, at least) it doesn't seem possible
to run an NFS server on a machine, and have it service requests from
clients talking to anything other than the base address.
For example, if I
ifconfig fxp0 inet 192.168.0.11
ifconfig fxp0 inet 192.168.0.16 alias
an
On Sun, 5 Dec 1999, Bill Fumerola wrote:
> On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
>
> > The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
> > Viking 4.5GB SCSI. I have never had any problem with this drive before,
> > even though I used it on Linux for several mo
On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
> The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
> Viking 4.5GB SCSI. I have never had any problem with this drive before,
> even though I used it on Linux for several months.
>
> This (FreeBSD) system has been running just f
My apologies for posting this digression from the usual weighty
matters that are discussed here on -hackers, but I'm really in
a tizzy about this.
Going through my waiting mail this morning (on my personal desktop
system named `segfault.monkeys.com') I found the following message
from the nightl
On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
> > Normal
> > filesystems with softupdates turned on make pretty good mail spools though
>
> OK, I've seen several mentions now of `softupdates', and I think that I
> have a general (vague?) notion of what `softupdates' is all about, but
> allow
In message <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>So, I think it *IS* possible to make FreeBSD sufficiently bug-free that
>people become 'surprised' when they are able to crash a box running it.
FYI - Part of the reason that _I_ jumped onto the FreeBSD bandwago
You write:
: we can not identify the specific problem from this message.
: without sufficient information to indentify and hopefully reproduce
: the problem, we can not address it. please provide this information
: if it is available to you. if it is not, please provide us contact
: informa
On Mon, 6 Dec 1999, Dennis wrote:
> The "issue" that i first cited is that the core people in FreeBSD seemed
> disinterested in 3.x soon after its release. Development on 4.0 shouldnt
> even have begun until 3.x was stabilized. 3.0 wasnt ready for prime time
> when it was released and the work n
In message <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>Mail queue files are persistant enough (upwards of 5 days if a destination
>is down) that you run a real risk of losing something important if
>you crash and wipe. I would not use MFS at all and I would on
On Thursday, 2 December 1999 at 22:32:44 -0500, David Gilbert wrote:
> I can grep through the vmcore.x file and find the offset of the string
> I put on the stack by
>
> strings -t x
> ... but how do I associate that back with an address inside gdb -k?
With utmost difficult.
> My problem is th
The "issue" that i first cited is that the core people in FreeBSD seemed
disinterested in 3.x soon after its release. Development on 4.0 shouldnt
even have begun until 3.x was stabilized. 3.0 wasnt ready for prime time
when it was released and the work needed to get it there hasnt been done
due t
[snip]
> I am a good programmer and can fix things :-). But I've had to deal with
> a number of nightmare situations by commercial entities deploying FreeBSD
> and at least three (including one very recently) where commercial entities
> have refused to upgrade past 2.2.x due to perceiv
Being multi-threaded has almost nothing to do with being
multi-processor. Multi-threading means that your application has
multiple threads of execution that are able to run simultaneously.
The multi-processing capability of your box means that 2 threads of
execution, be it a process or a thread
> I think openbsd asks users to email them the output of 'dmesg',
> so they can tell which drivers are really of interest to the
> greatest number of their users. Seems like a reasonable idea.
You might want to include the list of packages installed from the base
CD's as well to prime the packag
> Nice serial server, anyone working for serial support on USB ?
> Have an 8 port and could help getting support for it or testing
> drivers.
If you are or someone else is willing to write a driver under NDA I can
give you the e-mail address of a guy who can give you the specifications
for it.
I
63 matches
Mail list logo
