On 16-Aug-01 Michael Lucas wrote:
> [cc's trimmed]
>
> John,
>
> Thanks for the suggestion, I appreciate it. I did as you suggested
> (diff below).
>
> It paniced again, but this time savecore said "dump time is unreasonable."
>
> The short panic message was:
>
> panicstr: bremfree: bp 0xcc
[cc's trimmed]
John,
Thanks for the suggestion, I appreciate it. I did as you suggested
(diff below).
It paniced again, but this time savecore said "dump time is unreasonable."
The short panic message was:
panicstr: bremfree: bp 0xcc2a1ae4 not locked
Looks like the same thing to me, sorry.
On 15-Aug-01 Michael Lucas wrote:
> On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
>> To help localize this problem, could you please try this same thing on
>> a kernel without devfs? The dump you sent me did not look like a
>> Vinum bug, as I said in my reply.
>
> Sorry, it happen
On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
> To help localize this problem, could you please try this same thing on
> a kernel without devfs? The dump you sent me did not look like a
> Vinum bug, as I said in my reply.
Sorry, it happens on a non-devfs kernel as well. Since it d
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>the lack of subdirectory support is a pitty.
There is support for subdirectories:
ls -la /dev/fd
>it was a primary design goal in the previous devfs and its
>disappearance caught me by surprise. (the support I mean)
The abilit
the lack of subdirectory support is a pitty.
it was a primary design goal in the previous devfs and its
disappearance caught me by surprise. (the support I mean)
On Wed, 15 Aug 2001, Andrew Kenneth Milton wrote:
> +---[ Poul-Henning Kamp ]--
> | In message <[EMAIL PROTECT
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
| >+---[ Poul-Henning Kamp ]--
| >| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| >| writes:
| >|
| >| >The problem turns up most violently wit
On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
> On Tuesday, 14 August 2001 at 19:26:09 -0400, Michael Lucas wrote:
> > Before I start generating crash dumps & etc., are there any gotchas
> > with Vinum & -current? I'm using devfs on a SMP system, upgraded 3
> > days ago. I get a pa
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>+---[ Poul-Henning Kamp ]--
>| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
>| writes:
>|
>| >The problem turns up most violently within the XFree86 DRI Module, since
>| >it now uses make_dev, and no
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
|
| >The problem turns up most violently within the XFree86 DRI Module, since
| >it now uses make_dev, and not mknod as it used to.
| >
| >The DRI Module first attempts to mkdir
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>The problem turns up most violently within the XFree86 DRI Module, since
>it now uses make_dev, and not mknod as it used to.
>
>The DRI Module first attempts to mkdir /dev/dri/, and then for each card
>it supports attempts to use mak
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
| >+---[ Greg Lehey ]--
| >|
| >
| >[snip]
| >
| >| whether it's been fixed. Basically, devfs as supplied in CURRENT had
| >| a 16 character limit on devi
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>> I'm working on the 16char limit problem as well, but I want to avoid
>> allocating memory in incovenient circumstances if at all possible.
>
>The problem is that I kept having problems with the devfs/vinum
>combination even after increasing th
On Wednesday, 15 August 2001 at 7:16:02 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
> writes:
>> +---[ Greg Lehey ]--
>>>
>>
>> [snip]
>>
>>> whether it's been fixed. Basically, devfs as supplied in CURRENT had
>>> a 16 charact
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>+---[ Greg Lehey ]--
>|
>
>[snip]
>
>| whether it's been fixed. Basically, devfs as supplied in CURRENT had
>| a 16 character limit on device names, and it didn't understand
>| subdirectories: it treated the /
+---[ Greg Lehey ]--
|
[snip]
| whether it's been fixed. Basically, devfs as supplied in CURRENT had
| a 16 character limit on device names, and it didn't understand
| subdirectories: it treated the / as a part of the device name.
The subdir part bit me about a week ag
16 matches
Mail list logo
