Current Locking up... Re: possibly related data point - (was) Re: Current Broken!

[Steven E. Ames]

-CURRENT as of yesterday was still causing my system to lock (with
'make -j8 world'). Lock=no possibility of debugger.

I have two of these systems and they behave identically. If someone with
lots more debugging experience would benefit from borrowing one of the
machines I'd happily send it to you. I'd really like to be use SMP
stabily.

-Steve

- Original Message -
From: "John Baldwin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Andrew
[SKY:ET95:EXCH]" <[EMAIL PROTECTED]>
Sent: Friday, December 08, 2000 1:49 PM
Subject: RE: possibly related data point - (was) Re: Current Broken!


>
> On 08-Dec-00 [EMAIL PROTECTED] wrote:
> >
> > I hit on it by accident (I normally compile with -O). That said,
your
> > claim that gcc with no optimization generates incorrect code is
> > kind of counter-intuitive, wouldn't you say ?
>
> I've seen it do weird things with -O0 (mostly with C++). :)  It's just
another
> program.  Nothing is keeping it from having bugs. :)
>
> > I think you missed my point, I was just illustrating that optimizer
seems
> > to affect (in my case apparently negate) the processing of
constraints.
>
> I am back now to thinking that it is a gcc bug in the -O case now as
well.  The
> constraings I removed were in fact valid, so I've put them back in,
but just
> disabled the macros for now until gcc is fixed.
>
> > What you take from that is up to you - I was just trying to be
helpful :)
>
> Sorry if I came across as if I was biting your head off, that was not
the
> intent.
>
> > Cheers,
> >
> > A.
>
> --
>
> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
> PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
> "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CURRENT is freezing again ...

[Steven E. Ames]

It seems to only do it SMP... the same machine built with a non-SMP
kernel (same source code) runs just fine for extended periods.

-Steve

- Original Message -
From: "Soren Schmidt" <[EMAIL PROTECTED]>
To: "Boris Popov" <[EMAIL PROTECTED]>
Cc: "Valentin Chopov" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, November 16, 2000 12:17 PM
Subject: Re: CURRENT is freezing again ...


> It seems Boris Popov wrote:
> > On Thu, 16 Nov 2000, Soren Schmidt wrote:
> >
> > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing
again in
> > > > 10 min after boot...
> > >
> > > You mean "is still freezing" right ?
> > >
> > > Current has been like this for longer than I care to think about,
it
> > > seems those in charge doesn't take these problems seriously
(enough)...
> >
> > I think info about where/how it freezing would be more helpful.
>
> No idea, the system just freezes, no drob to DDB no remote gdb no
> nothing, so its really hard to tell where...
> As to how, just boot current on a fairly fast machine, make a kernel
> and it'll hang in minutes if not less, or just leave it alone and
> it will hang in 10-30 mins...
>
> -Søren
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: NFS /usr/src and /usr/obj?

[Steven E. Ames]

Sure. This can be done with no problems. It is, in fact, a good way to
put the same OS on multiple machines.

-Steve

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 26, 2000 5:26 PM
Subject: NFS /usr/src and /usr/obj?


> I'm wondering how one can do a buildworld on a machine, and then NFS
> mount /usr/src and /usr/obj on a client machine and do an installworld
> of the freshly built sources?  I've been looking in the archives
without
> much success, and haven't figured it out by reading the makefiles yet.
> Can anyone shed some light on this?
>
> --
> Kyle Mestery | Ancor Communications
> [EMAIL PROTECTED] | http://www.freebsd.org/
> [EMAIL PROTECTED] | http://www.netwinder.org/
> Protect your right to privacy: www.freecrypto.org
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADSUP: wd driver will be retired!

[Steven E. Ames]

> >Next month it'll be -RELEASE.  This isn't the time to remove such
> >significant functionality.  If it weren't for that, I'd agree with
> >you.
>
> Think about that some more.

Ditto :)

The idea that seems to be here is to definately make ATA the default
driver. Definately it should be the default driver for 4.0... but leave
the 'wd' driver there as a fallback. After we've had a wide test
audience of 4.0 users using the ATA driver it will likely cover every
bit of hardware that 'wd' already does and do a better job.

At that point 'wd' can be scrapped for 4.1-RELEASE.

Big changes that have been little tested shouldn't be made just before
RELEASE... not without a safety net.

-Steve

>
> After that it will be 4.1.  Nice to give people a driver and then rip
it
> out when 4.1 comes when Soren fixes the last of the things people
> needed to have into the ata driver.
>
> I was already testing the ata driver and even procured some more info
> for Soren than he already had.  Same goes for a bunch of other people.
> But the opposite goes for a lot of people.
>
> People running CURRENT to be cutting edge as in being elite with the
> latest FreeBSD thus get bitten.
>
> I'd say, cut loose the wd driver.  (VoxWare removed would be cool
too.)
>
> --
> Jeroen Ruigrok van der Werven/Asmodai
asmodai@[wxs.nl|bart.nl]
> Documentation nutter.  *BSD: Technical excellence at its
best...
> The BSD Programmer's Documentation Project

> Atone me to my throes curtail...
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: boot stops after "Mounting root from ufs:/dev/ad0s2a"

[Steven E. Ames]

> > ad0:  ATA-3 disk at ata0 as master
> > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
> > ad0: 16 secs/int, 1 depth queue, DMA
> > acd0:  CDROM drive at ata1 as master
> > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO
> > acd0: supported read types: CD-R, CD-DA
> > acd0: Audio: play, 256 volume levels
> > acd0: Mechanism: ejectable tray
> > acd0: Medium: no/blank disc inside, unlocked
> > Mounting root from ufs:/dev/ad0s2a
>
> It's difficult to mount your root if there's no disk in the drive.

What? He's mounting /dev/ad0s2a... ad0 was detected as a Quantum
Fireball. acd0 has no disc inside. Agreed.

-Steve



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADSUP: wd driver will be retired!

[Steven E. Ames]

Agreed. -CURRENT is all about development. New ideas will be tried,
sometimes (sometimes a lot :) things are going to be broke.

I switched to the new ATA driver on Monday. Seems to work but I have
some questions.

Could someone (sos?) post a quick primer on how to read the probe
messages? With the old wd driver I understood the messages and it was
readily apparent when something wasn't using DMA, large blocks, etc...

The new ATA driver is here to stay. Yep. It needs some serious testing.
Yep. If someone would post a quick how-to of stuff to do/look-for I'm
sure more people would be willing to test with a smile on their face.

Here's the relevant portion of my probe:

ata-pci0:  irq 0 at device
1.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
.
.
ad0:  ATA-? disk at ata0 as master
ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, PIO
ad1:  ATA-? disk at ata0 as slave
ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S
ad1: 16 secs/int, 1 depth queue, PIO
acd0:  CDROM drive at ata1 as master
acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO
acd0: supported read types:
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
ata_command: timeout waiting for interrupt

I have no idea what have of these messages mean. This is less clear to
me (probably because I'm used to the old messages) than the 'wd'
messages.

Also, like others, I'm getting that 'ata_command: timeout waiting for
interrupt' at the end.

-Steve

- Original Message -
From: Mike Smith <[EMAIL PROTECTED]>
To: Julian Elischer <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 08, 1999 1:56 PM
Subject: Re: HEADSUP: wd driver will be retired!


> >
> > because it doesn't support the chipsets that the old one does.
> > (namely the 200 or so lines of support in pci_ide.c needed for the
Cyrix
> > GXM series).
> >
> > You shouldn't remove a function until it has been properly replaced.
> > A very simple concept some people seem to have trouble grasping.
>
> Actually, that's not at all correct.  We've demonstrated a number of
> times now that you reach a point where a brutal cutover is required.
> Failure to do so leaves people clutching the old security blanket for
> years, and massively impedes further development.
>
> This is a good time for this particular cutover.  A little more public
> announcement would perhaps have been nice, but that's probably asking
> more of our axe-wielding friends than we're ever going to get.
>
> The right attitude to be taking now is "here is where the ata drivers
> still fall down" or "here are patches to them to replace this
> functionality".  Think about the longer-term goals here folks.
>
> --
> \\ Give a man a fish, and you feed him for a day. \\  Mike Smith
> \\ Tell him he should learn how to fish himself,  \\
[EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message