On Mon, May 13, 2002 at 09:19:18PM -0700, Peter Wemm wrote:
> Terry Lambert wrote:
>
> > Has anyone tapped the manufacturer on the shoulder hard enough to
> > get an answer?
>
> "Why are you not using Linux or another supported OS?"
It's not like they support development of the Linux tg3 driver
Peter Wemm wrote:
> Terry Lambert wrote:
> > Has anyone tapped the manufacturer on the shoulder hard enough to
> > get an answer?
>
> "Why are you not using Linux or another supported OS?"
>
> No, they so far have steadfastly refused to supply information about bugs
> and errata in such a way th
Terry Lambert wrote:
> Has anyone tapped the manufacturer on the shoulder hard enough to
> get an answer?
"Why are you not using Linux or another supported OS?"
No, they so far have steadfastly refused to supply information about bugs
and errata in such a way that we could use them in an open s
On Tue, 2002-05-14 at 08:54, Matt wrote:
> I was trying to use FreeBSD4.5 with pppoe to dial through DSL modem. But
> according handbook, there must be through Ethernet interface, yet I found
> the DSL modem used a usb interface. it seems no driver can recognize this
> usb device as Ethernet inter
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00E2_23I34K5M.N2565R76"
* David Greenman-Lawrence <[EMAIL PROTECTED]> [020513 15:40] wrote:
> >* David Greenman-Lawrence <[EMAIL PROTECTED]> [020513 13:10] wrote:
> >>
> >>The card doesn't drop the packet if the IP/TCP checksum is wrong. In my
> >> tests, I did a software checksum on the supposedly bad packet, and f
This tool is wonderful! It almost gives too much information (and that's a
good thing). But the pmap_helper.ko kernel module is a little worrisome from
a "safety" standpoint; just glancing through it, I see how it would be possible
to leave with a LK_SHARED still held on p->p_vmspace->vm_map (sa
I was trying to use FreeBSD4.5 with pppoe to dial through DSL modem. But
according handbook, there must be through Ethernet interface, yet I found
the DSL modem used a usb interface. it seems no driver can recognize this
usb device as Ethernet interface. how will this situation works for FreeBSD
n
>Actually, if you could find one of these, it would probably give
>enough information that we could figure out what kind of error it
>was giving. If it's just the incremental checksum 0x (-0)
>problem from one's complement vs. two's complement, then you could
>be sure that it was only bad pac
Alfred Perlstein wrote:
> * David Greenman-Lawrence <[EMAIL PROTECTED]> [020513 13:10] wrote:
> >The card doesn't drop the packet if the IP/TCP checksum is wrong. In my
> > tests, I did a software checksum on the supposedly bad packet, and found it
> > to be good every time. So it DMA's correc
>* David Greenman-Lawrence <[EMAIL PROTECTED]> [020513 13:10] wrote:
>>
>>The card doesn't drop the packet if the IP/TCP checksum is wrong. In my
>> tests, I did a software checksum on the supposedly bad packet, and found it
>> to be good every time. So it DMA's correctly, the checksum is jus
A process can sleep for various reasons such as memory, I/O etc. Is there
a way to collect statistics about how long it sleeps for different
reasons? Thanks.
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon 2002-05-13 (14:09), Doug White wrote:
> On 13 May 2002, David [ISO-8859-1] Siebörger wrote:
>
> > That's hardly the worst of it. The ServerWorks OSB4 ATA controller
> > has been known to cause data corruption with Seagate drives.
>
> Have you isolated it to Seagates only? our problematic
On 13 May 2002, David [ISO-8859-1] Siebörger wrote:
> That's hardly the worst of it. The ServerWorks OSB4 ATA controller
> has been known to cause data corruption with Seagate drives.
Have you isolated it to Seagates only? our problematic rackables have
seagate drives, but I don't have any othe
On Mon, May 13, 2002 at 09:55:40PM +0100, Dominic Marks wrote:
> Hey,
>
> I've been having panics with RELENG_4 for a few months now at 3 to
> 4 day intervals. I haven't been able to get a meaning debugging data
> from the machine until today. Any clues on what might be the clue of
> this would b
* David Greenman-Lawrence <[EMAIL PROTECTED]> [020513 13:10] wrote:
>
>The card doesn't drop the packet if the IP/TCP checksum is wrong. In my
> tests, I did a software checksum on the supposedly bad packet, and found it
> to be good every time. So it DMA's correctly, the checksum is just cal
Hey,
I've been having panics with RELENG_4 for a few months now at 3 to
4 day intervals. I haven't been able to get a meaning debugging data
from the machine until today. Any clues on what might be the clue of
this would be very gratefully received!
If it helps the machine wasn't doing very much
On Mon, May 13, 2002 at 12:49:44PM -0700, Terry Lambert wrote:
> void wrote:
> > > A: ``I'll give you $200 to add $foo to the base system.''
> > > B: ``No, *I* bid $300 to get someone to work on $bar.''
> > > ...
> >
> > This has been mooted before, and I think people have even made efforts
> "Peter" == Peter Haight <[EMAIL PROTECTED]> writes:
Peter> Of course. What's a good thing to tell them? Is the problem
Peter> that their DNS server isn't correctly responding to a query
Peter> with an unknown QTYPE?
The most common error is for the server to return an authorita
>You would do everyone a favour by notifying those sites that don't
>handle IPv6 DNS queries properly. In many (most) cases the sites aren't
>aware that their DNS software is broken. A quick e-mail will often see
>the problem fixed in short order. (bbc.co.uk is a recent example of
>this.)
Of cour
If memory serves me right, Steve Ames wrote:
> cc1: warnings being treated as errors
> /usr/src/sys/dev/ed/if_ed.c: In function `ed_attach':
> /usr/src/sys/dev/ed/if_ed.c:1653: warning: unknown conversion type character
> `D'
> in format
> /usr/src/sys/dev/ed/if_ed.c:1653: warning: too many arg
>David Greenman-Lawrence wrote:
>> >Was the result a rejected packet that didn't get transferred, or
>> >transferred packets with bad checksums?
>> >
>> >If the latter, then it's workaroundable in software, which might
>> >be worth doing... if only rechecking packets with bad checksums.
>> >I fear
> "Peter" == Peter Haight <[EMAIL PROTECTED]> writes:
Peter> I'm going to try Terry's solution and try and do concurrent
Peter> lookups. Mozilla is already using pthreads, so I should be
Peter> able to just spawn the two requests in separate threads and
Peter> take the one tha
David Greenman-Lawrence wrote:
> >Was the result a rejected packet that didn't get transferred, or
> >transferred packets with bad checksums?
> >
> >If the latter, then it's workaroundable in software, which might
> >be worth doing... if only rechecking packets with bad checksums.
> >I fear the fo
void wrote:
> > A: ``I'll give you $200 to add $foo to the base system.''
> > B: ``No, *I* bid $300 to get someone to work on $bar.''
> > ...
>
> This has been mooted before, and I think people have even made efforts
> to implement, but it's never taken off in a big way.
Or Alfred would be
>> :Can you guys elaborate on the problem? Was it on incoming checksums,
>> :outgoing checksums, or both?
>>
>> It was on incoming checksums I believe.
>
>Was the result a rejected packet that didn't get transferred, or
>transferred packets with bad checksums?
>
>If the latter, then it's wor
On Sat, May 11, 2002 at 01:23:33AM -0700, David Schultz wrote:
>
> I think you're on to something here. Just imagine:
>
> A: ``I'll give you $200 to add $foo to the base system.''
> B: ``No, *I* bid $300 to get someone to work on $bar.''
> ...
This has been mooted before, and I think peo
David Greenman-Lawrence wrote:
> >My local copy of the -STABLE source tree leaves BGE_CSUM_FEATURES set
> >on in the driver; is there a change that needs to be MFC'ed to turn
> >these suckers off?
> ...
> >There's no similar comment in the if_bge.c ...
>
>See rev 1.5 and 1.3.2.5 of if_bge.c.
:> This change was made on 14-December-01 by DG. Anyone with an earlier
:> driver may be running with checksums enabled.
:
:OK... Ugh. Any way to get the word "checksum" into that comment?
:I plead search-blindness.
:
:
:> :Can you guys elaborate on the problem? Was it on incoming chec
Matthew Dillon wrote:
> Yup. Of course I am completely Jaded now after listening to B.P.
> curse the chipset while he was debugging it :-)
I like B.P. 8-).
> :My local copy of the -STABLE source tree leaves BGE_CSUM_FEATURES set
> :on in the driver; is there a change that needs to be
>My local copy of the -STABLE source tree leaves BGE_CSUM_FEATURES set
>on in the driver; is there a change that needs to be MFC'ed to turn
>these suckers off?
...
>There's no similar comment in the if_bge.c ...
See rev 1.5 and 1.3.2.5 of if_bge.c.
-DG
David Greenman-Lawrence
Co-founder, The
> # XXX broken: tconv < has been broken since at
> least 4.4...
> # XXX Use GNU versions: apropos bc dc diff grep ld man patch ptx uucp whatis
> # Moved to secure: bdes
> #
>
> Any idea when this will get fixed? I need this program.
I ran into the same thing a while ag
:This is depressing.
:
:The Dell PowerEdge 2550's use the BGE driver (Tigon III). I'm really
:surprised that the problem exists on the Tigon III. My personal
:experience with Tigon III's was that the hardware checksumming was
:working. Maybe my testing was too lax. 8-(.
Yup. Of course I
Matthew Dillon wrote:
> :>If you aren't using VLAN tagging, you shouldn't care.
> :
> : No, that is absolutely not correct. The checksum problems happend in many
> :situations, depending on the chipset and other factors. The problem that
> :resulted in the commit to disable the receive hardware
On Mon, 13 May 2002, David Greenman-Lawrence wrote:
> >David Greenman-Lawrence wrote:
> >> >If you aren't using VLAN tagging, you shouldn't care.
> >>
> >>No, that is absolutely not correct. The checksum problems happend in many
> >> situations, depending on the chipset and other factors. Th
>David Greenman-Lawrence wrote:
>> >If you aren't using VLAN tagging, you shouldn't care.
>>
>>No, that is absolutely not correct. The checksum problems happend in many
>> situations, depending on the chipset and other factors. The problem that
>> resulted in the commit to disable the receive
Just got this during a kernel build:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W
missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -an
si -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/
dev/acpica -I/us
David Greenman-Lawrence wrote:
> >If you aren't using VLAN tagging, you shouldn't care.
>
>No, that is absolutely not correct. The checksum problems happend in many
> situations, depending on the chipset and other factors. The problem that
> resulted in the commit to disable the receive hardw
Jake Burkholder wrote:
[ ... ]
* The SI_SUB_CONSOLE and SI_SUB_SWAP values represent values used by
* the BSD 4.4Lite but not by FreeBSD; they are maintained in dependent
* order to support porting.
My bad. One of my local machines here is running different console
code, from one of the oth
:>If you aren't using VLAN tagging, you shouldn't care.
:
: No, that is absolutely not correct. The checksum problems happend in many
:situations, depending on the chipset and other factors. The problem that
:resulted in the commit to disable the receive hardware checksum was caused
:by small p
>Jamie Heckford wrote:
>> I read in the mailling lists mentions of hardware checksum problems
>> with the chipset.. did anyone know what the final outcome with
>> this problem was and if any changes had been MFC'd?
>
>The problems were only when coupled with VLAN tagging.
>
>I'm not sure if the 57
Jamie Heckford wrote:
> I read in the mailling lists mentions of hardware checksum problems
> with the chipset.. did anyone know what the final outcome with
> this problem was and if any changes had been MFC'd?
The problems were only when coupled with VLAN tagging.
I'm not sure if the 5701 was s
Miguel Mendez wrote:
> On Mon, May 13, 2002 at 09:36:06AM +0100, Dominic Marks wrote:
> > You do have a good quality heatsink and fan on this, don't you?
> >
> LOL, please, see below...
>
> > > Soyo K7VTA PRO MB
> > > Koolance Water cooled case
> ^^
"I wonder if this
Peter Wemm wrote:
> Would it make you happier if I removed SI_SUB_CONSOLE to prove the point?
> Hmm, I think I will.. It seems to be confusing some people.
That's not productive.
You might as well remove the VM one, as well, so that people think
they can use the allocator before it's initialize
Mike Makonnen wrote:
> On Sun, 2002-05-12 at 14:16, Peter Haight wrote:
> > Hmm. Looking at the FreeBSD resolver code, it doesn't look like there is
> > some convenient way to do this. Maybe something like, try the lookup,
> > but if we don't get any reply in a short timeout, try an A lookup.
I noticed that the tconv command is broken in 4.4 and 4.5.
(See /usr/src/usr.bin/Makefile which says:)
# From: @(#)Makefile 8.3 (Berkeley) 1/7/94
# $FreeBSD: src/usr.bin/Makefile,v 1.144.2.10 2002/02/20 19:08:31 ru Exp
$
# XXX MISSING: deroff diction graph learn plot
# spell spline
Gregory Sutter wrote:
> On 2002-05-11 10:49 +0800, Dinesh Nair <[EMAIL PROTECTED]> wrote:
>> On Fri, 10 May 2002, Doug White wrote:
>>
>> > usually have onboard everything, including dual fxp's nowadays. But they
>> > have the ServerWorks curse.
>> > . Tyan makes some interesting stuff, but as w
Apparently, On Sun, May 12, 2002 at 11:36:27PM -0700,
Terry Lambert said words to the effect of;
> Jake Burkholder wrote:
> > I know that you wrote it and I know that you're wrong.
> >
> > Take sparc64_init() for example, which is called from locore.S before
> > mi_startup():
>
> [ ...
On Thu, 2 May 2002, Matthew D. Fuller wrote:
> I'll see if I can put some time over the next few days into delving into
> it and at least getting the first step (of making the locking work more
> usefully) work.
Hi Matt. Just wondering if you've made any progress on making pw use a
lockfile. I
Hi,
Following cards:
bge0: mem 0xf7fb-0xf7fb irq 5 at device
5.0 on pci1
bge1: mem 0xf7fa-0xf7fa irq 10 at device
6.0 on pci1
Sucessfully got this driver recognised and "working" on
FreeBSD 4.6-PRERELEASE #1: Thu May 9 12:50:45 BST 2000.
Seems to fine.. apart from im noti
On Sat, 11 May 2002, Semen A. Ustimenko wrote:
> DEADLOCK...
Indeed, weird situation. Nice analysis, btw :)
> Make vn_lock() in vrele() lock vnode only LK_THISLAYER. Obviously, the
> NULLFS and other stacking FSes will have to deal with this in their
> VOP_INACTIVE() handlers. This chan
On May 11, at 1:15pm -0700, Ed Hall wrote:
> At Yahoo! we use a lot of shared memory, both in the form of .so's and
> for IPC. It would be very useful to be able to accurately measure the
> amount of shared and private memory associated with a process, the
> number of references to a given share
On Mon, May 13, 2002 at 10:40:31AM +0200, Miguel Mendez wrote:
> On Mon, May 13, 2002 at 09:36:06AM +0100, Dominic Marks wrote:
>
> Hi,
>
> > You do have a good quality heatsink and fan on this, don't you?
> >
> LOL, please, see below...
>
> > > Soyo K7VTA PRO MB
> > > Koolance Water cooled ca
On Mon, May 13, 2002 at 09:36:06AM +0100, Dominic Marks wrote:
Hi,
> You do have a good quality heatsink and fan on this, don't you?
>
LOL, please, see below...
> > Soyo K7VTA PRO MB
> > Koolance Water cooled case
^^
Cheers,
--
Miguel Mendez - [EMAIL
On Sun, May 12, 2002 at 11:09:47PM -0300, V. K. Cody Bumgardner wrote:
> Here is some info I have changed case, mb, ps, and memory but I still
> have this problem.. I get dumps in gcc during compile.
>
> Thanks,
> Cody
>
> !!UNAME!!
> FreeBSD cody.spectechnologies.net
> 4.5-STABLE FreeBSD 4.5-
Terry Lambert wrote:
> Jake Burkholder wrote:
> > Wrong, no cookie. kernel printf uses the low level console which is
> > initialized by cninit, which is called from init386 (etc), before
> > mi_startup.
> >
> > My best guess at what's happening is that the subsystem numbers are
> > "sparse", an
56 matches
Mail list logo
