On Thu, 2 Feb 2006, Enrique Ayesta Perojo wrote:
> Hello, i'm trying to install FreeBSD6 on an old PowerEdge 4200. But i cannot
> even get to sysinstall, when it's booting from the cd it gets to a point
> where the system reboots, these are the messages i can see on the console:
>
> ...
> amr0: p
On Fri, Feb 03, 2006 at 09:55:49PM -0700, Warner Losh wrote..
> From: Scott Long <[EMAIL PROTECTED]>
> Subject: Re: [releng_6 tinderbox] failure on sparc64/sparc64
> Date: Fri, 03 Feb 2006 19:40:42 -0700
>
> > Warner Losh wrote:
> > > From: [EMAIL PROTECTED] (Dag-Erling Smørgrav)
> > > Subject: Re
On Sat, 4 Feb 2006, Wilko Bulte wrote:
[snip]
WB> > My point is that it is unreasonable to get bitched at for tinerbox
WB> > breakages that don't show up when building lint because the tinderbox
WB> > person is too stubborn to not use non-standard flags.
WB>
WB> I would think that the tinderboxe
On Sat, Feb 04, 2006 at 01:54:14PM +0300, Dmitry Morozovsky wrote..
> On Sat, 4 Feb 2006, Wilko Bulte wrote:
>
> [snip]
>
> WB> > My point is that it is unreasonable to get bitched at for tinerbox
> WB> > breakages that don't show up when building lint because the tinderbox
> WB> > person is too
Warner Losh <[EMAIL PROTECTED]> writes:
> Can we not have special flags for tinderbox builds? It make
> pre-commit testing a big pita. How about just -O on both head and
> in RELENG_6?
As I have repeatedly pointed out in the past, -O2 catches more bugs
because it enables optimizations which requ
In message: <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Dag-Erling Smørgrav) writes:
: Warner Losh <[EMAIL PROTECTED]> writes:
: > Can we not have special flags for tinderbox builds? It make
: > pre-commit testing a big pita. How about just -O on both head and
: > in RELENG_6?
:
: As I ha
IIRC, at NetApp -O2 was the default for all builds. I think it is safe to
say that the generated code is quite stable. If -O2 allows the compiler to
catch errors earlier it should be the default.
-Kip
On 2/4/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
>
> In message: <[EMAIL PROTECTED]>
On Sat, February 4, 2006 3:45 am, Stephen Montgomery-Smith wrote:
> I have a Crucial 1GB USB 2.0 Gizmo memory stick. It does work, but not
> without its problems.
>
> When I insert it into the USB port, the kernel spits out a large number
> of bad looking messages - I'll copy them below. /dev/da0
Giorgos Kapetanakis wrote:
On Sat, February 4, 2006 3:45 am, Stephen Montgomery-Smith wrote:
I have a Crucial 1GB USB 2.0 Gizmo memory stick. It does work, but not
without its problems.
When I insert it into the USB port, the kernel spits out a large number
of bad looking messages - I'll copy
On Saturday 04 February 2006 12:01, [EMAIL PROTECTED] wrote:
> many aspects of the network interface configuration
> process were overhauled.
Which, I suppose, explains the yo-yo effect of my two xe (4) PC Cards, amongst
others, and why my wi (4) card no longer behaves itself.
Up-down-up-dow
I would think that the tinderboxes should run 100% the same flags as
what normal release builds use. Nothing more, nothing less.
What I would like to see is a pointer to a procedure and tools to make
sure builds aren't broken.
I've been refreshing my memory about email going back about 5
In message: <[EMAIL PROTECTED]>
Kip Macy <[EMAIL PROTECTED]> writes:
: IIRC, at NetApp -O2 was the default for all builds. I think it is safe to
: say that the generated code is quite stable. If -O2 allows the compiler to
: catch errors earlier it should be the default.
If things have
"M. Warner Losh" <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > As I have repeatedly pointed out in the past, -O2 catches more
> > bugs because it enables optimizations which require more extensive
> > coverage analysis.
> Then it should be the default, standard f
"M. Warner Losh" <[EMAIL PROTECTED]> writes:
> If things have really changed, then we should change the default and
> remove the kludges. My main objection is the mismatch, not the actual
> value. Did you remove the kludges in the mk files at netapp to remove
> the -fno-strict-alias?
Most of the
Matthew Jacob <[EMAIL PROTECTED]> writes:
> a) The tinderbox breakage is being treated as bad as stop ship type of
> bug rather than being informative as it should be. I feel I got
> roasted and slammed for what should have been simply a "hey- Matt-
> come fix this please!".
Not really. You were
Actually, in my tree, 19 files don't compile. In all of the files I've
looked at PCPU_SET is the offender. My guess is that the issue could be
fixed by passing the type as an argument.
On 2/4/06, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
>
> Matthew Jacob <[EMAIL PROTECTED]> writes:
> > a) Th
On Fri, Feb 03, 2006 at 11:50:54AM -0800, Sean Bruno wrote:
> Just curious if I should even bother trying to compile 4.11's kernel
> under Release 6.
>
> Just tried and couldn't successfully 'config MYKERNEL_CONF':
>
> [EMAIL PROTECTED] config MIRALINK.serial_console
> config: ../compile/MIRALINK
On Sat, Feb 04, 2006 at 09:03:13PM +0100, Dag-Erling Sm?rgrav wrote:
> "M. Warner Losh" <[EMAIL PROTECTED]> writes:
> > Dag-Erling Sm?rgrav <[EMAIL PROTECTED]> writes:
> > > As I have repeatedly pointed out in the past, -O2 catches more
> > > bugs because it enables optimizations which require more
In message: <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Dag-Erling Smørgrav) writes:
: "M. Warner Losh" <[EMAIL PROTECTED]> writes:
: > If things have really changed, then we should change the default and
: > remove the kludges. My main objection is the mismatch, not the actual
: > value.
In message: <[EMAIL PROTECTED]>
Ruslan Ermilov <[EMAIL PROTECTED]> writes:
: On Sat, Feb 04, 2006 at 09:03:13PM +0100, Dag-Erling Sm?rgrav wrote:
: > "M. Warner Losh" <[EMAIL PROTECTED]> writes:
: > > Dag-Erling Sm?rgrav <[EMAIL PROTECTED]> writes:
: > > > As I have repeatedly pointed o
On Sat, 4 Feb 2006 08:48:28 -0800
Kip Macy <[EMAIL PROTECTED]> wrote:
> IIRC, at NetApp -O2 was the default for all builds. I think it is safe to
> say that the generated code is quite stable. If -O2 allows the compiler to
> catch errors earlier it should be the default.
>
I concur.
--
Tom Rho
In message: <[EMAIL PROTECTED]>
Kip Macy <[EMAIL PROTECTED]> writes:
: Actually, in my tree, 19 files don't compile. In all of the files I've
: looked at PCPU_SET is the offender. My guess is that the issue could be
: fixed by passing the type as an argument.
In the drivers there's a l
"M. Warner Losh" <[EMAIL PROTECTED]> writes:
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> > I mean, I don't see a reason not to remove -fno-strict-aliasing
> > from the kernel builds now. Perhaps it's still needed for some
> > platforms that aren't covered by tinderbox, not sure... Can be
> > e
I need to get a Proliant machine with 2 P3 processors running FreeBSD 6.
I don't know much about the machine, I think it's ML 380 G2 or close to
that, but I have physical access. So far, everything is fine (once the
inability to boot from CD-ROM is circumvented), except one "detail":
horrible w
Hi,
I'm running FreeBSD 6.1-prerelease on my laptop and it is running really
great, except my SD/MMC Cardreader. Its a Texas Instrumens Chip, I'l
paste the interesting from pciconf:
[EMAIL PROTECTED]:9:3: class=0x018000 card=0x300717c0 chip=0x8033104c rev=0x00
hdr=0x00
vendor = 'Texas
Not sure if this is standard, but on an idle machine (ie. just set it up,
nothing running on it yet), with RAID1+0 across 4 drives:
Writing the 853 Megabyte file, 'iozone.tmp'...15.656250 seconds
Reading the file...3.921875 seconds
IOZONE performance measurements:
57129601 bytes/secon
On Sunday 05 February 2006 01:42, Daniel Bond wrote:
> Hi,
>
> I'm running FreeBSD 6.1-prerelease on my laptop and it is running really
> great, except my SD/MMC Cardreader. Its a Texas Instrumens Chip, I'l
> paste the interesting from pciconf:
>
> [EMAIL PROTECTED]:9:3: class=0x018000 card=0x300
> From: Matt Dawson <[EMAIL PROTECTED]>
> Date: Sat, 4 Feb 2006 18:08:02 +
> Sender: [EMAIL PROTECTED]
>
> On Saturday 04 February 2006 12:01, [EMAIL PROTECTED] wrot> e:
> > many aspects of the network interface configuration process
> > were overhauled.
>
> Which, I suppose, explains the yo-
28 matches
Mail list logo
