On Fri, Mar 14, 2003 at 10:00:18AM -0800, Wade Klaver wrote:
> OK, I cvsup'd about 1 hour ago. I get an error when building. Any Ideas?
>
It's a must to read src/UPDATING before posting to this list.
You're probably looking for the 20030125 entry.
Cheers,
--
Ruslan Ermilov Sysadmin an
OK, I cvsup'd about 1 hour ago. I get an error when building. Any Ideas?
cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys
-I/u
I have a Dell Latitude CPi notebook, and recently ran into some nastiness
involving the boot process. The machine is using an April 24th world, and
up until now had been using an April 24th kernel. Leaving aside problems
with pcm hanging the kernel at boot, things seemed to work largely fine.
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>:Greg,
>:
>:4K is probably too conservative, it only applies if you have a
>:swap-backed vn device at the bottom, which would be a truly
>:weird thing to do with vinum.
>:
>:Don't spend too much time on tracking the sector size yet. I think
:Greg,
:
:4K is probably too conservative, it only applies if you have a
:swap-backed vn device at the bottom, which would be a truly
:weird thing to do with vinum.
:
:Don't spend too much time on tracking the sector size yet. I think
:the si_bsize stuff needs some thinking before we do more with
On Friday, 27 August 1999 at 8:55:04 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>> On Thursday, 26 August 1999 at 16:25:14 -0700, Matthew Dillon wrote:
>> int devminor; /* minor number */
>>
>>
Greg,
4K is probably too conservative, it only applies if you have a
swap-backed vn device at the bottom, which would be a truly
weird thing to do with vinum.
Don't spend too much time on tracking the sector size yet. I think
the si_bsize stuff needs some thinking before we do more with it.
P
On Thursday, 26 August 1999 at 16:25:14 -0700, Matthew Dillon wrote:
int devminor; /* minor number */
devminor = minor(dev);
+dev->si_bsize_phys = DEV_BSIZE;
+dev->si_bsize_best = BLKDEV_IOSIZE;
+dev->si_bsize_
Hi,
Sorry for taking so long to reply. I have an isdn line to my office
which has been acting up lately (or should I say acting down?).
Anyways, yes, I am using a ccd. I also have a machine with a
dpt raid4 controller that I probably need to check to see if
it still works
My setup
On Thursday, 26 August 1999 at 22:35:27 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>>That fixes a problem with ccd, but not the one causing John's failures.
>>
>>You will note that with John's failure's the I/O is properly page-aligned.
>>T
unsubscribe freebsd-current
-Original Message-
From: Matthew Dillon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 26, 1999 6:25 PM
To: Poul-Henning Kamp
Cc: Christopher Masto; [EMAIL PROTECTED]; John W. DeBoskey;
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: -current kernel
:>> int devminor; /* minor number */
:>>
:>> devminor = minor(dev);
:>> +dev->si_bsize_phys = DEV_BSIZE;
:>> +dev->si_bsize_best = BLKDEV_IOSIZE;
:>> +dev->si_bsize_max = MAXBSIZE;
:>
:>Bingo! Thank you.
:
:Cool, I expect grog will comm
In message <[EMAIL PROTECTED]>, Christopher Masto writes:
>> Index: vinum.c
>> ===
>> RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v
>> retrieving revision 1.29
>> diff -u -r1.29 vinum.c
>> --- vinum.c 1999/08/24 02:18:55 1.29
On Thu, Aug 26, 1999 at 11:04:44PM +0200, Poul-Henning Kamp wrote:
> Ok, I havn't touched vinum (grog generally want to do this himself),
> the fix is probably something like this:
>
> Index: vinum.c
> ===
> RCS file: /home/ncvs/src/
In article <[EMAIL PROTECTED]>,
John W. DeBoskey <[EMAIL PROTECTED]> wrote:
>
>I need to figure out why my 11:30am EST cvsup didn't pick
> this file up. It's 44 minutes infront of cvsup...
Most mirror sites update themselves hourly from cvsup-master, which
updates itself every 6 minutes from
On Thu, Aug 26, 1999 at 11:04:44PM +0200, Poul-Henning Kamp wrote:
> >Well, I just had much the same blowup with source from last night
> >and I'm using vinum, (and not vn or ccd).
> >
> >Recompiling now to see if it's still there.
>
> Ok, I havn't touched vinum (grog generally want to do this hi
In message <[EMAIL PROTECTED]>, Christopher Masto writes:
>On Thu, Aug 26, 1999 at 10:35:27PM +0200, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>> >That fixes a problem with ccd, but not the one causing John's failures.
>> >
>> >You will note that wi
On Thu, Aug 26, 1999 at 10:35:27PM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
> >That fixes a problem with ccd, but not the one causing John's failures.
> >
> >You will note that with John's failure's the I/O is properly page-aligned.
> >Th
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>That fixes a problem with ccd, but not the one causing John's failures.
>
>You will note that with John's failure's the I/O is properly page-aligned.
>The fix to ccd deals with a misalignment problem.
No it doesn't. johns failur
In message <[EMAIL PROTECTED]>, Jul
ian Elischer writes:
>
>
>On Thu, 26 Aug 1999, Poul-Henning Kamp wrote:
>
>>
>> The size and resid of 0 is because it decides to use a sectorsize of
>> zero due to the si_bsize fields being empty.
>
>yes, but didn't I just see you commit a fix for that?
To ccd
The first part of this patch is not yet part of my multipatch at
http://www.backplane.com/FreeBSD4/
This is a tentative fix, but I believe it to be correct. Until
yesterday I was testing swap-backed VN with only one swap partition,
otherwise this would have been found and fi
That fixes a problem with ccd, but not the one causing John's failures.
You will note that with John's failure's the I/O is properly page-aligned.
The fix to ccd deals with a misalignment problem.
But I believe I have found the problem... it is a bug in vm/swap_pager.c
that o
Ah my mistake, it was ccd. I remembered vn. I guess vinum, vn,
and ccd need all have the correct bisize code..
On Thu, 26 Aug 1999, John W. DeBoskey wrote:
> which would be this commit...
>
> phk 1999/08/26 07:46:11 PDT
>
> Modified files:
> sys/dev/ccd ccd.c
>
which would be this commit...
phk 1999/08/26 07:46:11 PDT
Modified files:
sys/dev/ccd ccd.c
Log:
Initialize the dev->si_bsize fields.
Submitted by: tegge
Reviewed by: phk
Revision ChangesPath
1.53 +5 -1 src/sys/dev/ccd/ccd.c
I need t
On Thu, 26 Aug 1999, Poul-Henning Kamp wrote:
>
> The size and resid of 0 is because it decides to use a sectorsize of
> zero due to the si_bsize fields being empty.
yes, but didn't I just see you commit a fix for that?
>
> In message <[EMAIL PROTECTED]>, Jul
> ian Elischer writes:
> >swapp
I am positive that I just saw a checkin from phk that
initialised the initial default transfer size.
On Thu, 26 Aug 1999, Matthew Dillon wrote:
> :swapping on a vn device?
> :the 'size' and 'resid' of 0 looks suspicious.
> :
> :a fix was just committed to teh vn code that may fix this if that'
The size and resid of 0 is because it decides to use a sectorsize of
zero due to the si_bsize fields being empty.
In message <[EMAIL PROTECTED]>, Jul
ian Elischer writes:
>swapping on a vn device?
>the 'size' and 'resid' of 0 looks suspicious.
>
>a fix was just committed to teh vn code that may
:swapping on a vn device?
:the 'size' and 'resid' of 0 looks suspicious.
:
:a fix was just committed to teh vn code that may fix this if that's your
:problem.
A fix was? When? Where? What?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECT
swapping on a vn device?
the 'size' and 'resid' of 0 looks suspicious.
a fix was just committed to teh vn code that may fix this if that's your
problem.
On Thu, 26 Aug 1999, John W. DeBoskey wrote:
> Hi,
>
>Following up my own mail on sig 11 problems, I beleive the
> problem is kernel re
fixed earlier today...
On Thu, 26 Aug 1999, John W. DeBoskey wrote:
> Hi,
>
>Following up my own mail on sig 11 problems, I beleive the
> problem is kernel related. Running a kernel with sources current
> as of 11:30am EST, I get the following during a make world:
>
> spec_getpages: I/O r
Hi,
Following up my own mail on sig 11 problems, I beleive the
problem is kernel related. Running a kernel with sources current
as of 11:30am EST, I get the following during a make world:
spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000
size: 0, resid
31 matches
Mail list logo
