On Sun, Sep 29, 2002 at 12:17:54PM -0700, Eric Anholt wrote:
> On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
> > Does this bug effect -stable? It only showed up in -current recently.
> > Isn't it a bigger chance that something on the FreeBSD side made this bug
> > much more visible?
> >
> > O
if i can help, please let me know!
all im doing is:
newfs /dev/ad0s2a
mount /dev/ad0s2a /mnt-root
rsh dev -n dump 0f - /c/4 | restore rf -
and after a short while it panics.
with today's cvsup, and with this 'fix':
*** vfs_subr.c 2002/09/29 08:16:40 1.1
--- v
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Last call:
Unless somebody with access to this hardware and willing to maintain
these drivers step forward Real Soon Now, I intend to retire them
from -current before 5.0-R.
Poul-Henning
--- Forwarded Message
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
Date: Mon, 30 Sep 2002 06:49:20 -07
On Mon, Sep 30, 2002 at 04:05:40PM +0200, Poul-Henning Kamp wrote:
>
> Unless somebody with access to this hardware and willing to maintain
> these drivers step forward Real Soon Now, I intend to retire them
> from -current before 5.0-R.
For a possible maintainer for the mcd driver i have at lea
Hi!
While local package initilization I get a panic. World and kernel from today.
This I found in messages:
Sep 30 15:49:55 leeloo kernel: panic: lockmgr: locking against myself
Sep 30 15:49:55 leeloo kernel:
Sep 30 15:49:55 leeloo kernel: syncing disks... panic: bremfree: bp 0xd381a080 not
lock
Hi,
> > Index: sys/i386/i386/machdep.c
> > ===
> > RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v
> > retrieving revision 1.532
> > diff -u -r1.532 machdep.c
> > --- sys/i386/i386/machdep.c 7 Sep 2002 19:12:42 - 1.532
>
On 29-Sep-2002 Hanspeter Roth wrote:
> On Sep 29 at 12:25, Mitsuru IWASAKI spoke:
>
>> If you think this is caused by acpi.ko, just disable acpi.ko loading.
>> Please read thru loader(8) and device.hints(5).
>
> Yes, this is it. I've now disabled acpi and the boot process comes
> further.
>
Hello,
I've installed DP1 from CD. It doesn't like the Promise ATA100 TX2.
`boot -c' just behaves exactly like normal boot and stops in the
debugger.
Thus I thought I could install via FTP. But what will I get?
Will I get a `current' current?
Or will I get DP1 from April again?
-Hanspeter
To U
On Sep 30 at 11:59, John Baldwin spoke:
>
> These messages above that you left out are very important. :(
> Also, if you can get a trace by typing 't' at the db> prompt
> that can be very helpful as well.
Ok. I hope there aren't to many mistakes.
vga0: at port 0x3c0-0x3df iomem 0xa-0xbf
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
>
> I went through the FlexeLint output of the LINT kernel on i386 and
> tried to examine all warnings about memoryleaks in central or
> semi-central code.
>
> I this patch I belive addresses the ones I think I could confirm,
> in the following files
Provided nothing terminal pops up in the next 5 days, GEOM will
become default in -current on Saturday 5th of october.
Please test it now on _your_ configuration and tell me if it
fails to work.
There is one known issue on sparc64 which is being worked: On sparc64
nexus_dmamap_create() calls ma
On 30-Sep-2002 Hanspeter Roth wrote:
> On Sep 30 at 11:59, John Baldwin spoke:
>
>>
>> These messages above that you left out are very important. :(
>> Also, if you can get a trace by typing 't' at the db> prompt
>> that can be very helpful as well.
>
> Ok. I hope there aren't to many mistak
On Sep 30 at 15:16, John Baldwin spoke:
> > Fatal trap 12: page fault while in kernal mode
> > fault virtual address = 0xdeadc0de
>
> This means someone is trying to access memory that has been free'd.
How do I make someone not to do such bad things? :-)
> Hmm, unfortunately generic_bcopy()
On Sep 30 at 19:40, Hanspeter Roth spoke:
> Thus I thought I could install via FTP. But what will I get?
> Will I get a `current' current?
> Or will I get DP1 from April again?
I've interrupted after /bin has been downloaded. And what do I see?
mnt/bin # ll
total 7810
-r-xr-xr-x 2 root whee
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
What are the exact steps
In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
>On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
>> Provided nothing terminal pops up in the next 5 days, GEOM will
>> become default in -current on Saturday 5th of october.
>>
>> Please test it now on _your_ configuration
On 30-Sep-2002 Hanspeter Roth wrote:
> On Sep 30 at 15:16, John Baldwin spoke:
>
>> > Fatal trap 12: page fault while in kernal mode
>> > fault virtual address = 0xdeadc0de
>>
>> This means someone is trying to access memory that has been free'd.
>
> How do I make someone not to do such bad
Any problems that one runs into, or things that go boom, or questions should
be directed to me. I've been running almost the exact same stuff under
OpenBSD and FreeBSD (with the notable exception that some things were unworking
in OpenBSD due to relied-upon breakage) both -current and -stable Fre
On Sep 30 at 15:16, John Baldwin spoke:
> Hmm, unfortunately generic_bcopy() is in asm, and so it doesn't have
> a "true" frame and we end up skipping over the frame in execve()
> where it is called from. There are only 3 bcopy's in execve(), but
> I'm not sure which is likely to have been the
On Mon, Sep 30, 2002 at 09:45:39PM +0200, Hanspeter Roth wrote:
> On Sep 30 at 19:40, Hanspeter Roth spoke:
>
> > Thus I thought I could install via FTP. But what will I get?
> > Will I get a `current' current?
> > Or will I get DP1 from April again?
>
> I've interrupted after /bin has been do
At the end is a potentially longer term fix for the ABI
breakage that was introduced when the i386 mcontext_t
was changed/enlarged.
Someone other than I (Bruce?) should vet this. It should
solve the libc_r binary compatibility problem, but it may
not fix everything. Applications that copy ucont
On 30-Sep-2002 Hanspeter Roth wrote:
> On Sep 30 at 15:16, John Baldwin spoke:
>
>> Hmm, unfortunately generic_bcopy() is in asm, and so it doesn't have
>> a "true" frame and we end up skipping over the frame in execve()
>> where it is called from. There are only 3 bcopy's in execve(), but
>>
On Sep 30 at 14:16, Kris Kennaway spoke:
> release bits, or you can just download new installation media from the
> desired snapshot (this is the preferred option) and use that to
> install with.
I can only see /pub/FreeBSD/snapshots/i386/5.0-20020302-PREVIEW.
Is there a more recent snapshot?
On Sep 30 at 17:19, John Baldwin spoke:
>
> On 30-Sep-2002 Hanspeter Roth wrote:
> > 416 and 556 denote linenumbers in kern_exec.c.
>
> Thanks! That's here:
>
> if (ps_arg_cache_limit >= i + sizeof(struct pargs)) {
> bcopy(imgp->stringbase, newargs->ar_args, i);
>
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Daniel Eischen wrote:
> At the end is a potentially longer term fix for the ABI
> breakage that was introduced when the i386 mcontext_t
> was changed/enlarged.
> - ret = set_fpcontext(td, &ucp->uc_mcontext);
> - if (ret != 0)
> - return (ret);
> +
On Mon, 30 Sep 2002, Juli Mallett wrote:
> * De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> [ Subjecte: Re: signal changes ]
> >
> > On Mon, 30 Sep 2002, Juli Mallett wrote:
> >
> > > > What limits are the on the number of signals that are stored?
> > >
> > > It's a Tai
* De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
[ Subjecte: Re: signal changes ]
>
>
> On Mon, 30 Sep 2002, Juli Mallett wrote:
>
> > * De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> > [ Subjecte: Re: signal changes ]
> > >
> > > On Mon, 30 Sep 2002,
On Mon, Sep 30, 2002 at 11:26:50PM +0200, Hanspeter Roth wrote:
> On Sep 30 at 14:16, Kris Kennaway spoke:
>
> > release bits, or you can just download new installation media from the
> > desired snapshot (this is the preferred option) and use that to
> > install with.
>
> I can only see /pub/
cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/dell/imp/p4/newcard/src/lib/libkvm -c
/dell/imp/p4/newcard/src/lib/libkvm/kvm_proc.c -o kvm_proc.o
/dell/imp/p4/newcard/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
/dell/imp/p4/newcard/src/lib/libkvm/kvm_proc.c:201: structure has no member n
cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c
/usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o
/usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
/usr/src/lib/libkvm/kvm_proc.c:201: structure has no member named `p_siglist'
To Unsubscribe: send mail to [EMAIL PROTECTED
On Mon, 30 Sep 2002, Juli Mallett wrote:
>
> Teh same that provides specification for queued signals - posix rts.
hey that's MY typo... get your own! :-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message: <[EMAIL PROTECTED]>
walt <[EMAIL PROTECTED]> writes:
: cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c
: /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o
: /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
: /usr/src/lib/libkvm/kvm_proc.c:201: stru
* De: "M. Warner Losh" <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
[ Subjecte: Re: World broken at libkvm ]
> In message: <[EMAIL PROTECTED]>
> walt <[EMAIL PROTECTED]> writes:
> : cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c
> : /usr/src/lib/libkvm/kvm_proc
Juli Mallett wrote:
> * De: "M. Warner Losh" <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> [ Subjecte: Re: World broken at libkvm ]
> > In message: <[EMAIL PROTECTED]>
> > walt <[EMAIL PROTECTED]> writes:
> > : cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c
> >
Juli Mallett wrote:
> * De: "M. Warner Losh" <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> [ Subjecte: Re: World broken at libkvm ]
>>This has been fixed. But there's other breakages in the kernel that
>>are being worked on.
> And now fixed. All we have to look out for now is someone doin
* De: Peter Wemm <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
[ Subjecte: Re: World broken at libkvm ]
> Juli Mallett wrote:
> > * De: "M. Warner Losh" <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> > [ Subjecte: Re: World broken at libkvm ]
> > > In message: <[EMAIL PROTECTED]>
> > >
In article <[EMAIL PROTECTED]>
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
It fails to c
In article <[EMAIL PROTECTED]>
Takahashi Yoshihiro <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>
> Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>
> > Provided nothing terminal pops up in the next 5 days, GEOM will
> > become default in -current on Saturday 5th of october.
> >
>
I was talking to someone about lightweight interrupt threads
and interactions with KSEs and specifically about
KSE borrowing..
Believe it or not, I can't remember who it was..
if it was you, let me know :-)
Julian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
On 30 Sep, Peter Wemm wrote:
> Juli Mallett wrote:
>> And now fixed. All we have to look out for now is someone doing something
>> that exposes some sort of functional difference, but I don't anticipate it.
> I suggest you turn WITNESS on, and stress the system. If you get *new*
> 'could sleep
Dunno who it was, but my understanding is that we already actually use
lightweight interrupt threads on sparc64, so you might want to peruse
there and look at the approach taken. :-) You might have been talking to
Bosko (possibly at USENIX ATC), as he was maintaining an i386 lightweight
interrup
* De: Don Lewis <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
[ Subjecte: Re: World broken at libkvm ]
> On 30 Sep, Peter Wemm wrote:
> > Juli Mallett wrote:
>
> >> And now fixed. All we have to look out for now is someone doing something
> >> that exposes some sort of functional difference,
Apparently, On Tue, Oct 01, 2002 at 01:46:50AM -0400,
Robert Watson said words to the effect of;
> Dunno who it was, but my understanding is that we already actually use
> lightweight interrupt threads on sparc64, so you might want to peruse
> there and look at the approach taken. :-) Y
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
> System and kernel slice at 1200 GMT 30 Sep 2002 where
> the log showed a whole series of changes to the Adaptec
> drivers: kernel came up, ran for a few minutes, then
> hung.
There have been no major changes to the aic7xxx driver in the last
few days. A few $Id updates, a fix t
Hi
On -current as of yesterday, the kdebase-3.0.3 build fails in
ksysguardd.
source='netdev.c' object='netdev.o' libtool=no \
depfile='.deps/netdev.Po' tmpdepfile='.deps/netdev.TPo' \
depmode=gcc3 /bin/sh ../../../admin/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../../.. -DKSYSGUARDDRCFILE="\"\"" -I
Hello,
I'm looking for a starting point to learn
about support of threads in the current kernel.
I'm intrested in the following things concerning kernel threads:
- design
- implementation
- usage
I'm developing a pseudo driver that performs CPU time consuming
cryptographic operations in Free
49 matches
Mail list logo
