So the patch works, and this problem seems serious and easy to encounter, i
vote for moving it to stable.
- Original Message -
From: "Tobias Ulmer" <[EMAIL PROTECTED]>
To: "Otto Moerbeek" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, August 03, 2007 3:37 PM
Subj
On Thu, Jul 19, 2007 at 08:09:58PM +0200, Otto Moerbeek wrote:
> [...]
>
> I misdiagnosed the problem. In the meantime I got another report with
> a dd of the partition which enabled me to diagnose the problem and
> make a fix for 4.1. Please test and report back. I'll be on vacation
> from Saturda
INOPB(&sblock));
sblock.fs_inopb = sblock.fs_bsize / sizeof(struct
ufs1_dinode);
--
Will this work?
Regards,
Marcos
- Original Message -
From: "Otto Moerbeek" <[EMAIL PROTECTED]>
To: "Marcos Laufer" <[EMAIL PROTECTED]>
Cc:
Sent: Frid
arcos
- Original Message -
From: "Otto Moerbeek" <[EMAIL PROTECTED]>
To: "Marcos Laufer" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, July 20, 2007 4:02 PM
Subject: Re: fsck Segmentation fault on 4.1
On Fri, 20 Jul 2007, Marcos Laufer wrote:
> Will this b
; From: "Otto Moerbeek" <[EMAIL PROTECTED]>
> To: "Marcos Laufer" <[EMAIL PROTECTED]>
> Cc:
> Sent: Thursday, July 19, 2007 3:09 PM
> Subject: Re: fsck Segmentation fault on 4.1
>
>
> On Fri, 13 Jul 2007, Otto Moerbeek wrote:
>
> >
Will this be moved to -stable, or is it an uncommon thing ?
- Original Message -
From: "Otto Moerbeek" <[EMAIL PROTECTED]>
To: "Marcos Laufer" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, July 19, 2007 3:09 PM
Subject: Re: fsck Segmentation fault on 4.1
On
On Fri, 13 Jul 2007, Otto Moerbeek wrote:
> On Fri, 13 Jul 2007, Marcos Laufer wrote:
>
> > Otto ,
> >
> > This is the error i get:
> > It starts booting , and it starts fsck , it fails with /dev/rwd0e and rwd0h,
> >
> > (i could see once that when it finished it says:)
> > fsck_ffs in free():
On Sun, 15 Jul 2007, Niko Itajarvi wrote:
> Otto Moerbeek drijf.net> writes:
>
> >
> > On Fri, 13 Jul 2007, Marcos Laufer wrote:
> >
> > > Otto,
> > >
> > > I know the cables are allright, i'm using them with other hard drive .
> > > And the hard drive is new , but i will format it and check
Otto Moerbeek drijf.net> writes:
>
> On Fri, 13 Jul 2007, Marcos Laufer wrote:
>
> > Otto,
> >
> > I know the cables are allright, i'm using them with other hard drive .
> > And the hard drive is new , but i will format it and check if it
> > shows up some errors.
> > I hope it is hardware rel
> Regards,
> Marcos
>
> - Original Message -
> From: "Otto Moerbeek" <[EMAIL PROTECTED]>
> To: "Marcos Laufer" <[EMAIL PROTECTED]>
> Cc:
> Sent: Friday, July 13, 2007 4:46 PM
> Subject: Re: fsck Segmentation fault on 4.1
>
ystem?
Regards,
Marcos
- Original Message -
From: "Otto Moerbeek" <[EMAIL PROTECTED]>
To: "Marcos Laufer" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, July 13, 2007 4:46 PM
Subject: Re: fsck Segmentation fault on 4.1
On Fri, 13 Jul 2007, Marcos Laufer wrote:
>
splay0
> pmsi0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pmsi0 mux 0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0:
> spkr0 at pcppi0
> lm0 at isa0 port 0x290/8: W83627THF
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> b
> I want to report a problem i experienced while testing OpenBSD 4.1 .
> I've installed it, increased VM_PHYSSEG_MAX to 16
> in /usr/src/sys/arch/i386/include/vmparam.h to make
> it work with this particular motherboard and made a
> stable release.
Fluffy!!!
There be dragons..
t; <[EMAIL PROTECTED]>
To: "Marcos Laufer" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, July 13, 2007 3:38 PM
Subject: Re: fsck Segmentation fault on 4.1
On Fri, 13 Jul 2007, Marcos Laufer wrote:
> Hello,
>
> I want to report a problem i experienced while testing OpenBSD
On Fri, 13 Jul 2007, Marcos Laufer wrote:
> Hello,
>
> I want to report a problem i experienced while testing OpenBSD 4.1 .
> I've installed it, increased VM_PHYSSEG_MAX to 16
> in /usr/src/sys/arch/i386/include/vmparam.h to make
> it work with this particular motherboard and made a
> stable rele
Hello,
I want to report a problem i experienced while testing OpenBSD 4.1 .
I've installed it, increased VM_PHYSSEG_MAX to 16
in /usr/src/sys/arch/i386/include/vmparam.h to make
it work with this particular motherboard and made a
stable release.
Installed a server with it and it's working fine as
16 matches
Mail list logo