I think I've found a bug in fsck. Some invalid values in cylinder groups
don't get fixed.
>From pass5.c:
if (cg->cg_rotor < newcg->cg_ndblk)
newcg->cg_rotor = cg->cg_rotor;
else
newcg->cg_rotor = 0;
It seems Matthew Dillon wrote:
> Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've
> been trying to track down a crash in nfs_node that Nils Holland
> has been having - he appears to have the same chipset and could
> have the same problem, and he can reproduce the pan
It seems Matthew Dillon wrote:
> Soren, if you post a patch for 4.x I will be happy to follow-up
> with Brady. I've been working with Brady for several days now trying
> to track down corruption in the vm_page array. I *really* want to know
> if a VIA chipset patch solves his p
It seems Danny Braniss wrote:
> > It seems Matthew Gilbert wrote:
> > > > So, general question to everyone having crashes during heavy
> > > > IDE workloads: Please post your /var/run/dmesg.boot
> > > > output.
> >
> > > atapci0: port 0xd000-0xd00f at device 7.1 on
> >
> > You hav
On Thu, Dec 27, 2001 at 02:34:40AM -0600, Kevin Day wrote:
You might want to file this as a PR (using send-pr)
so that it can be looked at by the filesystem gurus. I am not to sure
that Kirk keeps up with -hackers
Wilko
> I think I've found a bug in fsck. Some invalid values in cylinder groups
On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> It seems Matthew Gilbert wrote:
> > > So, general question to everyone having crashes during heavy
> > > IDE workloads: Please post your /var/run/dmesg.boot
> > > output.
>
> > atapci0: port 0xd000-0xd00f at device 7.1
It seems Wilko Bulte wrote:
> On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> > It seems Matthew Gilbert wrote:
> > > > So, general question to everyone having crashes during heavy
> > > > IDE workloads: Please post your /var/run/dmesg.boot
> > > > output.
> >
> > >
On Thu, Dec 27, 2001 at 02:07:22PM +0100, Søren Schmidt wrote:
> It seems Wilko Bulte wrote:
> > On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> > > It seems Matthew Gilbert wrote:
> > > > > So, general question to everyone having crashes during heavy
> > > > > IDE workloa
> Anyhow since this is not always the case I did the fix for -current,
> granted it should not be in the ATA driver, but since nobody else
> really cared at the time
Does this mean that if you dont have the ATA drivers in the kernel then
you wont get the fix ? As the bug occurs under high PCI
It seems Pete French wrote:
> > Anyhow since this is not always the case I did the fix for -current,
> > granted it should not be in the ATA driver, but since nobody else
> > really cared at the time
>
> Does this mean that if you dont have the ATA drivers in the kernel then
> you wont get th
There are a couple known issues going on with the VIA Chipset line (Some
acknowledge by VIA partially, some not.) beyond just the 686B bug.
Here's a couple sites with details. Myself, I think it's a BIOS writer's
problem as well, but unfortunatly with most VIA boards, their goal is
performance o
It seems Søren Schmidt wrote:
> > Does this mean that if you dont have the ATA drivers in the kernel then
> > you wont get the fix ? As the bug occurs under high PCI loads then this
> > can potentially affect people with large amounts of PCI activity on
> > SCSI drives too surely ? Granted I've ne
On Thu, Dec 27, 2001 at 03:15:15PM +0100, Søren Schmidt wrote:
> It seems Pete French wrote:
> > > Anyhow since this is not always the case I did the fix for -current,
> > > granted it should not be in the ATA driver, but since nobody else
> > > really cared at the time
> >
> > Does this mean
On Thu, Dec 27, 2001 at 10:45:01AM +0100, Søren Schmidt stood up and spoke:
>
> OK, here goes the VIA 686b patch, it is hand cut out from the bulk patches
> to go into 4.5 so beware :)
Well, as Matt has said, I reported a crash that he's trying to debug. Since
I have the 686b in my machine, I ap
Les raisons de mon départ ne sont nullement dues aux conditions de travail, ni aux
rapports humains que je qualifierai plutôt de profitables en ce qui me concerne.
Simplement, je ressens le besoin daller voir plus loin..
Dans un souci de bon accord, jaimerais toutefois, si cela vous est po
Hi all,
I hope this list will be the right list to ask this question, but any help
will be appreciated.
I am looking for a way that I can distribute FreeBSD on a huge cluster; 26
machines, but the problem I am running into, is if I used a sysinstall
scripts, then that would allow me to install a
Hassan Halta <[EMAIL PROTECTED]> types:
> I am looking for a way that I can distribute FreeBSD on a huge cluster; 26
> machines, but the problem I am running into, is if I used a sysinstall
> scripts, then that would allow me to install a basic FreeBSD distribution,
> and in the future, when I nee
This is great news! I'm crossing my fingers and hoping that Nils can't
reproduce the crash any more with Soren's fix.
Just to let you all know, Nils has been working his ass off helping me
track his crash down. I've been pulling my hair out... I gave him patch
after patch to
Hassan Halta writes:
> Hi all,
>
> I hope this list will be the right list to ask this question, but any help
> will be appreciated.
>
> I am looking for a way that I can distribute FreeBSD on a huge cluster; 26
> machines, but the problem I am running into, is if I used a sysinstall
> scripts,
I got a PCI based 802.11b card that is not recognized by FreeBSD. They
claim the card used to have a MX98713, and that the newer cards have a
MX98315, but I cannot find a thing (even on the Macronix site) about the
MX98315, does anybody know anything about it, like how similar it is to
the 713 (o
On Thu, Dec 27, 2001 at 12:10:32PM -0700, Chad David wrote:
> I got a PCI based 802.11b card that is not recognized by FreeBSD. They
> claim the card used to have a MX98713, and that the newer cards have a
> MX98315, but I cannot find a thing (even on the Macronix site) about the
> MX98315, does
It seems Matthew Dillon wrote:
> This is great news! I'm crossing my fingers and hoping that Nils can't
> reproduce the crash any more with Soren's fix.
Me too :)
I have a small change that can be used if performace suffers too badly,
it has not provoked the problem again on any of the
This patchset fixes a race in the nfs_node code. Basically the
issue is that it is possible for the nfsnode (and the vnode) to
get ripped out from under us if vget() sleeps, so we have to retry
the operation.
I'd like to MFC this one to -stable.
SXren Schmidt wrote:
>
> It seems Matthew Dillon wrote:
> > Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've
> > been trying to track down a crash in nfs_node that Nils Holland
> > has been having - he appears to have the same chipset and could
> > have the same prob
Just an update:
userland probram panic's FBSD 4.3-REL, FBSD 4.4-REL and FBSD 4.4-STABLE.
its not hardware (unless two completly identicle systems have some type of
chip problem not known yet)
its not thermal problem (I can do make buildworld's all day long)
If I do find it, its easy to tell: I c
* Michael Scheidell <[EMAIL PROTECTED]> [011227 14:26] wrote:
> Just an update:
> userland probram panic's FBSD 4.3-REL, FBSD 4.4-REL and FBSD 4.4-STABLE.
> its not hardware (unless two completly identicle systems have some type of
> chip problem not known yet)
Can you provide this program or a k
- Original Message -
From: "Alfred Perlstein" <[EMAIL PROTECTED]>
To: "Michael Scheidell" <[EMAIL PROTECTED]>
Cc: "David Malone" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, December 27, 2001 3:31 PM
Subject: Re: userland program panics freebsd 4.3
> * M
* Michael Scheidell <[EMAIL PROTECTED]> [011227 14:34] wrote:
>
> > * Michael Scheidell <[EMAIL PROTECTED]> [011227 14:26] wrote:
> > > Just an update:
> > > userland probram panic's FBSD 4.3-REL, FBSD 4.4-REL and FBSD 4.4-STABLE.
> > > its not hardware (unless two completly identicle systems hav
- Original Message -
From: "Alfred Perlstein" <[EMAIL PROTECTED]>
To: "Michael Scheidell" <[EMAIL PROTECTED]>
Cc: "David Malone" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, December 27, 2001 3:31 PM
Subject: Re: userland program panics freebsd 4.3
> * M
* Michael Scheidell <[EMAIL PROTECTED]> [011227 14:48] wrote:
>
> same place as before:
>
> 0 fstatfs (p=0xce1bd260, uap=0xce216f80) at ../../kern/vfs_syscalls.c:684
> 684 error = VFS_STATFS(mp, sp, p);
> 680 if ((error = getvnode(p->p_fd, SCARG(uap, fd), &fp)) != 0)
> 6
- Original Message -
From: "Alfred Perlstein" <[EMAIL PROTECTED]>
To: "Michael Scheidell" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 27, 2001 4:00 PM
Subject: Re: userland program panics freebsd 4.3
> *mp, *sp, *p, *((struct vnode *)fp->f_data)
print *mp:
$1 =
* Michael Scheidell <[EMAIL PROTECTED]> [011227 15:11] wrote:
>
> - Original Message -
> From: "Alfred Perlstein" <[EMAIL PROTECTED]>
> To: "Michael Scheidell" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, December 27, 2001 4:00 PM
> Subject: Re: userland program panics
On Thu, 2001-12-27 at 15:20, ian j hart wrote:
> Myself and others have had IDE related problems. Search
> the stable and hardware mail archives for
> UDMA and ICRC [and ianjhart] for examples.
>
> There is also the "only supports 16MxN RAM" feature.
Maybe I should toss in that I've had spontane
It seems Brandon S. Allbery KF8NH wrote:
> On Thu, 2001-12-27 at 15:20, ian j hart wrote:
> > Myself and others have had IDE related problems. Search
> > the stable and hardware mail archives for
> > UDMA and ICRC [and ianjhart] for examples.
> >
> > There is also the "only supports 16MxN RAM" f
In article <005101c18ee1$9b5d66e0$fa01a8c0@ABERRATION>, Predius
<[EMAIL PROTECTED]> writes
>There are a couple known issues going on with the VIA Chipset line (Some
>acknowledge by VIA partially, some not.) beyond just the 686B bug.
>
>Here's a couple sites with details. Myself, I think it's a BI
Hey,
It is great if you are finding a solution for the VIA-chipset.
Do you have any idea if it is a simular problem that I am experiencing?
I am not enough into chip code to have a clue what exactly the patch
is doing - but maybe it is just decreasing the load on the kernel/system in
a
way that
:Hey,
:
:It is great if you are finding a solution for the VIA-chipset.
:Do you have any idea if it is a simular problem that I am experiencing?
:
:I am not enough into chip code to have a clue what exactly the patch
:is doing - but maybe it is just decreasing the load on the kernel/system in
:a
:In article <005101c18ee1$9b5d66e0$fa01a8c0@ABERRATION>, Predius
:<[EMAIL PROTECTED]> writes
:>There are a couple known issues going on with the VIA Chipset line (Some
:>acknowledge by VIA partially, some not.) beyond just the 686B bug.
:>
:>Here's a couple sites with details. Myself, I think it'
Hi,
I've sort of asked this before but maybe was too verbose.
In short, has anyone been able to develope apps for palm
with the palm sdk, prc-tools-*, and palm emulation (e.g., pose)
on freebsd?
I tried starting with pose and got immediately stumped with
core dumps.
Is there some tried/true wa
Thanks, and here you are.
The last crash I had was while trying to compile Mozilla from the
port-collection, e.g.
concentrated high activity:
root@jkkn:/var/crash# gdb -k /usr/src/sys/compile/JKKN_KRNL/kernel.debug
vmcore.4
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free s
On Thu, Dec 27, 2001 at 11:31:43AM -0800, Brooks Davis wrote:
> On Thu, Dec 27, 2001 at 12:10:32PM -0700, Chad David wrote:
>
> What you'll want to do is edit src/sys/dev/wi/if_wi.c, add an appropriate
> entry to the definition of pci_ids for your card, and recompile your
> kernel. If that works
I was reading TCP/IP Vol 2 by douglas comer. In that
he has one queue for each interface from which the IP
layer processes the incoming datagrams. He has used
round-robin for fairness. I checked up the BSD code
and it seems to use only one queue 'ipintrq'. The
ethernet driver places the mbuf
Hi,
FreeBSD uses a single queue, but as long as you make sure that you
do not fill the queue with packets coming from a single interface,
you can still give some fairness to the system. Recent "DEVICE_POLLING"
code in -current (hopefully going into -stable at some point) does
exactly this -- an al
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an Athlon XP 1700. Last August, though, I bought a machine which gave
me a lot of trouble, the
44 matches
Mail list logo
