In article <[EMAIL PROTECTED]>,
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
>
> Woops, I have the KASSERT bungled up. Please change
> KASSERT(to < *hiwat && uip != NULL,
> to
> KASSERT(to >= *hiwat || uip != NULL,
It seems to be fixed now. I've had a script pounding o
In article <[EMAIL PROTECTED]>,
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
>
> Woops, I have the KASSERT bungled up. Please change
> KASSERT(to < *hiwat && uip != NULL,
> to
> KASSERT(to >= *hiwat || uip != NULL,
Thanks. The system comes up OK now. I'll try to provo
On Sun, 27 Aug 2000, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
> > If this is a problem with sbsize, this should take care of any possibility
> > ever of there being a problem...
>
> I tried your patch, but it panics reliably on
In article <[EMAIL PROTECTED]>,
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
> If this is a problem with sbsize, this should take care of any possibility
> ever of there being a problem...
I tried your patch, but it panics reliably on start-up:
Automatic boot in progress...
/dev/da0s1a:
If this is a problem with sbsize, this should take care of any possibility
ever of there being a problem...
Index: kern/kern_proc.c
===
RCS file: /usr2/ncvs/src/sys/kern/kern_proc.c,v
retrieving revision 1.69
diff -u -r1.69 kern_proc
* Archie Cobbs <[EMAIL PROTECTED]> [000824 14:52] wrote:
> I don't know if this is related to the problems you guys are looking at,
> but I have a box that every so often (every couple of months) panics
> with a "panic: recieve 1" panic. This panic happens when the socket
> character count is bogu
I don't know if this is related to the problems you guys are looking at,
but I have a box that every so often (every couple of months) panics
with a "panic: recieve 1" panic. This panic happens when the socket
character count is bogus during a recv(2), etc. system call.
So several months ago I ca
Try making them small critical sections. If it makes it easier,
which it probably will, try this: pass the pointer to sb_hiwat as an
argument to chgsbsize and make that the only way to modify it (sockbuf
creation would have to be a place where it's initialized manually to
0 ;) I'd say stick the h
* Brian Fundakowski Feldman <[EMAIL PROTECTED]> [000823 22:05] wrote:
> On Wed, 23 Aug 2000, Alfred Perlstein wrote:
>
> > * Alfred Perlstein <[EMAIL PROTECTED]> [000823 14:29] wrote:
> > >
> > > I have a feeling that this is related to missing spl protection around
> > > the chgsbsize subsystem
On Wed, 23 Aug 2000, Alfred Perlstein wrote:
> * Alfred Perlstein <[EMAIL PROTECTED]> [000823 14:29] wrote:
> >
> > I have a feeling that this is related to missing spl protection around
> > the chgsbsize subsystem, this was probably an issue before I touched it
> > but since I touched it last I
In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
>
> more paranioa:
>
>
> Index: uipc_socket.c
> ===
> RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
> retrieving revision 1.80
> diff -u -u -r1.80 uip
* John Polstra <[EMAIL PROTECTED]> [000823 15:55] wrote:
> In article <[EMAIL PROTECTED]>,
> Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> > > Nope, that doesn't fix it. I got the same panic on the very first
> > > try.
> >
> > hmm, when does it happen? During the transfer or at the end of the
In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> > Nope, that doesn't fix it. I got the same panic on the very first
> > try.
>
> hmm, when does it happen? During the transfer or at the end of the
> transfer?
The first time I reported the problem it had happened d
* John Polstra <[EMAIL PROTECTED]> [000823 15:39] wrote:
> In article <[EMAIL PROTECTED]>,
> Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> >
> > Let's take a more paraniod approach (back out my spl in chgsbsize):
> >
> >
> > Index: uipc_socket2.c
>
> Nope, that doesn't fix it. I got the same
In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
>
> Let's take a more paraniod approach (back out my spl in chgsbsize):
>
>
> Index: uipc_socket2.c
Nope, that doesn't fix it. I got the same panic on the very first
try.
John
--
John Polstra
* John Polstra <[EMAIL PROTECTED]> [000823 15:03] wrote:
> In article <[EMAIL PROTECTED]>,
> Alfred Perlstein <[EMAIL PROTECTED]> wrote:
>
> > John can you try this patch and let us know if you still experiance
> > crashes?
>
> Will do. I'll let you know what happens.
Let's take a more parani
In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> John can you try this patch and let us know if you still experiance
> crashes?
Will do. I'll let you know what happens.
John
--
John Polstra [EMAIL PROTECTED]
John
* Alfred Perlstein <[EMAIL PROTECTED]> [000823 14:29] wrote:
>
> I have a feeling that this is related to missing spl protection around
> the chgsbsize subsystem, this was probably an issue before I touched it
> but since I touched it last I'll have a look-see.
>
> Brian, does that makes sense?
* John Polstra <[EMAIL PROTECTED]> [000823 13:46] wrote:
> I got the above panic in a -current kernel from August 19 with
> INVARIANTS and INVARIANT_SUPPORT compiled in. I also saw it once
> before on a kernel from a few weeks ago. In both cases the panic
> occurred when receiving a 25 MB file w
I got the above panic in a -current kernel from August 19 with
INVARIANTS and INVARIANT_SUPPORT compiled in. I also saw it once
before on a kernel from a few weeks ago. In both cases the panic
occurred when receiving a 25 MB file with FTP over a gigabit Ethernet
link (wx driver). Here is the re
20 matches
Mail list logo
