Re: panic during fdisk'ing a md(4) device

2002-01-18 Thread Bruce Evans
On Fri, 18 Jan 2002, Michael Reifenberger wrote: > On Fri, 18 Jan 2002, Bruce Evans wrote: > ... > > devfs still leaks 2 DEVFS allocations and 6 devbuf allocations for every > > iteration of the script. > ... > Does this mean that your latest patch removes the panic but leaks some > resources. N

Re: panic during fdisk'ing a md(4) device

2002-01-18 Thread Michael Reifenberger
On Fri, 18 Jan 2002, Bruce Evans wrote: ... > It somehow worked here, but after fixing the non-removal of the > /dev/md11*, I got back what is probably the original panic too. At > least with my fixed changes, the panic is caused by not clearing > pointers in destroy_dev(). The pointers come bac

Re: panic during fdisk'ing a md(4) device

2002-01-18 Thread Bruce Evans
On Thu, 17 Jan 2002, Michael Reifenberger wrote: > On Thu, 17 Jan 2002, Bruce Evans wrote: > ... > > Oops. There should be no alias for md10c. Try this version. It fixes > > the "may want an alias case" in dkmodminor() and moves all the dk inlines > > to subr_diskslice.c. > This patch works be

Re: panic during fdisk'ing a md(4) device

2002-01-17 Thread Michael Reifenberger
On Thu, 17 Jan 2002, Bruce Evans wrote: ... > Oops. There should be no alias for md10c. Try this version. It fixes > the "may want an alias case" in dkmodminor() and moves all the dk inlines > to subr_diskslice.c. This patch works better. This brings us back to the original problem :-) Now it d

Re: panic during fdisk'ing a md(4) device

2002-01-16 Thread Bruce Evans
On Mon, 14 Jan 2002, Michael Reifenberger wrote: > On Tue, 15 Jan 2002, Bruce Evans wrote: > ... > > Try this version. Only disklabel.h has many changes. The code for > > avoiding creation of bogus 'c' partitions didn't work at all. > > This works during startup but the following commands cases

Re: panic during fdisk'ing a md(4) device

2002-01-14 Thread Michael Reifenberger
On Tue, 15 Jan 2002, Bruce Evans wrote: ... > Yes, it is a bit confusing. sys/types.h gives the userland version. Only as confusing as the rest of the dk* code :-) > > Try this version. Only disklabel.h has many changes. The code for > avoiding creation of bogus 'c' partitions didn't work at

Re: panic during fdisk'ing a md(4) device

2002-01-14 Thread Bruce Evans
On Mon, 14 Jan 2002, Michael Reifenberger wrote: > Hi, > more food: > The kernel startup is: > ... > vga: ... > makedev(116,65538) > make_dev(maj=116,min=65538,name=ad0) > ad0: ... > makedev(116,65546) > make_dev(maj=116,min=65546,name=ad1) > ad1: ... > acd0: ... > Mounting root from ufs:/dev/ad0

Re: panic during fdisk'ing a md(4) device

2002-01-14 Thread Michael Reifenberger
Hi, more food: The kernel startup is: ... vga: ... makedev(116,65538) make_dev(maj=116,min=65538,name=ad0) ad0: ... makedev(116,65546) make_dev(maj=116,min=65546,name=ad1) ad1: ... acd0: ... Mounting root from ufs:/dev/ad0s3a makedev(116,65538) (?!?!? Why, where) makedev(116,26

Re: panic during fdisk'ing a md(4) device

2002-01-13 Thread Bruce Evans
On Sat, 12 Jan 2002, Michael Reifenberger wrote: > Hi, > more input: > The panic occurs in dsname() while dereferencing devsw(dev)->d_name. > devsw(dev) gives NULL. This was fairly clear from the panic message (the low fault address is almost certainly for a null pointer + offset, and it's fairl

Re: panic during fdisk'ing a md(4) device

2002-01-12 Thread Michael Reifenberger
Hi, more input: The panic occurs in dsname() while dereferencing devsw(dev)->d_name. devsw(dev) gives NULL. The call to dsname() occurs from dkmodminor() defined in disklabel.h I've seen two calls to dsname, only the second one panics. Any thoughts? Bye! Michael Reifenberger ^.*Plaut.*$, IT,

Re: panic during fdisk'ing a md(4) device

2002-01-10 Thread Michael Reifenberger
Hi, > Hmm. I used an old set of patches to avoid filtering out local changes > again. Try the enclosed up to date patches. Hmmm. Fresh -current, fresh patch. (Hunk 2 still doesnt apply cleanly, but this seems to be irrelevant for the problem) Old symptom: ... mounting root from ufs:/dev/ad0s3a

Re: panic during fdisk'ing a md(4) device

2002-01-09 Thread Bruce Evans
On Wed, 9 Jan 2002, Michael Reifenberger wrote: > On Wed, 9 Jan 2002, Bruce Evans wrote: > ... > > This seems to be just another null pointer panic caused by the dk macros > > creating half-baked devices with null devswitches. I sent the following > > quick fixes for this to the devfs maintainer

Re: panic during fdisk'ing a md(4) device

2002-01-09 Thread Michael Reifenberger
On Wed, 9 Jan 2002, Bruce Evans wrote: ... > This seems to be just another null pointer panic caused by the dk macros > creating half-baked devices with null devswitches. I sent the following > quick fixes for this to the devfs maintainer a couple of weeks ago. They > also fix the non-creation o

Re: panic during fdisk'ing a md(4) device

2002-01-09 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Bruce Evans writes: >This seems to be just another null pointer panic caused by the dk macros >creating half-baked devices with null devswitches. I sent the following >quick fixes for this to the devfs maintainer a couple of weeks ago. They >also fix the non-crea

Re: panic during fdisk'ing a md(4) device

2002-01-09 Thread Bruce Evans
On Tue, 8 Jan 2002, Michael Reifenberger wrote: > Hi, > the following script panics my system when executed twice: > (uncomment the dd lines for the first time or do it manually) > > > ## > > #!bin/sh > > block_size=512 > blocks=$((120 * 1024 * 1024 / $block_size)) > heads=16