Re: problem with vnconfig -s labels ...

1999-08-22 Thread Luigi Rizzo
About the vnconfig/disklabel problem, i don't understand one thing: the sequence that causes the reboot is the same used to produce the boot floppy images. How comes that it is still possible to produce snapshots for -current ? Are they cross-built on an older version of the system ? che

Re: problem with vnconfig -s labels ...

1999-08-22 Thread Julian Elischer
On Sat, 21 Aug 1999, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Bruce Evans writes: > >>Hmmm, I know this is your code, but are you sure? 8-). My understanding of > >>dkmodslice() and friends is that they manipulate dev_t entries, but don't > >>actually initialise them. Since th

Re: problem with vnconfig -s labels ...

1999-08-20 Thread John Birrell
On Sat, Aug 21, 1999 at 04:30:57PM +1000, Bruce Evans wrote: > >Hmmm, I know this is your code, but are you sure? 8-). My understanding of > >dkmodslice() and friends is that they manipulate dev_t entries, but don't > >actually initialise them. Since the subr_diskslice code takes a dev_t > > dkmo

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Bruce Evans writes: >>Hmmm, I know this is your code, but are you sure? 8-). My understanding of >>dkmodslice() and friends is that they manipulate dev_t entries, but don't >>actually initialise them. Since the subr_diskslice code takes a dev_t > >dkmodslice() once

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, John Birrell writes: >On Sat, Aug 21, 1999 at 07:30:46AM +0200, Poul-Henning Kamp wrote: >> >but I'm still looking for the place >> >where the dev1 entry is supposed to be initialised. >> >> In dkmodslice() (and friends). > >Hmmm, I know this is your code, but are

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Bruce Evans
>Hmmm, I know this is your code, but are you sure? 8-). My understanding of >dkmodslice() and friends is that they manipulate dev_t entries, but don't >actually initialise them. Since the subr_diskslice code takes a dev_t dkmodslice() once just manipulated bits in dev_t scalars. Now that dev_t i

Re: problem with vnconfig -s labels ...

1999-08-20 Thread John Birrell
On Sat, Aug 21, 1999 at 07:30:46AM +0200, Poul-Henning Kamp wrote: > >but I'm still looking for the place > >where the dev1 entry is supposed to be initialised. > > In dkmodslice() (and friends). Hmmm, I know this is your code, but are you sure? 8-). My understanding of dkmodslice() and friends

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, John Birrell writes: >The problem is that disklabel executes code in subr_diskslice.c which >does: > >dev1 = dkmodslice(dkmodpart(dev, RAW_PART), slice); > >The 'dev' structure has s_drv1 set correctly, but the 'dev1' entry >has s_drv1 NULL. When vnstrategy() is ca

Re: problem with vnconfig -s labels ...

1999-08-20 Thread John Birrell
On Sat, Aug 21, 1999 at 04:22:46AM +0200, Luigi Rizzo wrote: > Hi, > > > I've found panics are more likely to occur if the command pair is > > executed in a script vs. from the command line. This may suggest some > > sort of race is occurring. > > no idea... i have always managed to panic

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Luigi Rizzo
Hi, > I've found panics are more likely to occur if the command pair is > executed in a script vs. from the command line. This may suggest some > sort of race is occurring. no idea... i have always managed to panic the system even running the commands from the command line one at a time,

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Andrew Atrens
> > Someone also sent me a report on that, so it's a real problem. I have a > traceback, but without debugging symbols. Doh! Sorry about that :) I'll rebuild my kernel later today... Cheers, Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Andrew Atrens
Luigi, I've been seeing the same thing for about 6 weeks now :) I, too can reproduce the panic _at will_. If anyone's interested I've got a large selection of kernel cores to choose from :) ... Andrew. Some comments below ... On Fri, 20 Aug 1999, Luigi Rizzo wrote: > Hi, > > trying to bu

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Luigi Rizzo writes: >> > can someone investigate this ? the code seems to work fine on 3.x >> >> Someone also sent me a report on that, so it's a real problem. I have a >> traceback, but without debugging symbols. > >it's so easy to reproduce that i hope the vm/vn

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Andrzej Bialecki
On Fri, 20 Aug 1999, Luigi Rizzo wrote: > > > can someone investigate this ? the code seems to work fine on 3.x > > > > Someone also sent me a report on that, so it's a real problem. I have a > > traceback, but without debugging symbols. > > it's so easy to reproduce that i hope the vm/vn gurus

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Luigi Rizzo
> > can someone investigate this ? the code seems to work fine on 3.x > > Someone also sent me a report on that, so it's a real problem. I have a > traceback, but without debugging symbols. it's so easy to reproduce that i hope the vm/vn gurus will not require too much effort to find the bug. i

Re: problem with vnconfig -s labels ...

1999-08-20 Thread Andrzej Bialecki
On Fri, 20 Aug 1999, Luigi Rizzo wrote: > Hi, > > trying to build picobsd on 19990816snap of -current, i am consistently > hitting a problem, which is totally reproducible from the command line. > The following sequence > > vnconfig -s labels -c /dev/rvn0 fs.PICOBSD > disklabel -rw /dev

problem with vnconfig -s labels ...

1999-08-20 Thread Luigi Rizzo
Hi, trying to build picobsd on 19990816snap of -current, i am consistently hitting a problem, which is totally reproducible from the command line. The following sequence vnconfig -s labels -c /dev/rvn0 fs.PICOBSD disklabel -rw /dev/rvn0 fd1440 causes a panic with a page fault accessing