Re: No/weird mixer in -CURRENT

[Damian Gerow]

On Sun, 21 Sep 2003 23:19:12 -0400, thus spake Damian Gerow <[EMAIL PROTECTED]>:
: This is a fairly new machine, using a DFI PS83-BL motherboard.  pcm0
: is picked up as an Intel ICH5 (82801EB), and a C-Media Electronics
: CMI9739 AC97 Codec.
: 
: Does pcm not fully understand my audio device, am I lacking a mixer,
: or is it something else
: entirely?

(Apologies for horrible wrapping the first time.)

I just went through and applied a one-line patch to ich.c -- looks like
it was saying to treat ICH5 like ICH4.  This didn't make a difference.

Does anyone have any suggestions or pointers?  As much as I like
listening to something at full volume, it would be nice to be able to
turn it down without turning it off.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Something is wrong with the fxp network driver

[Mike Tancsa]

At 11:32 PM 26/09/2003, Glenn Johnson wrote:
On Fri, Sep 26, 2003 at 08:07:38PM -0400, Mike Tancsa wrote:

> Are they Tyan motherboards by chance ? There was a thread in stable
> about this a few weeks ago.  The problems seem specific to those
> motherboards.  Someone posted a potential workaround as well.
No, five of them are MSI dual Athlon-MP boards (can not remember the


what does pciconf -v -l show for the cards ?  Are all on the same switch ? 
Is it a flow control issue perhaps ?

---Mike 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Something is wrong with the fxp network driver

[Glenn Johnson]

On Fri, Sep 26, 2003 at 08:07:38PM -0400, Mike Tancsa wrote:

> Are they Tyan motherboards by chance ? There was a thread in stable
> about this a few weeks ago.  The problems seem specific to those
> motherboards.  Someone posted a potential workaround as well.

No, five of them are MSI dual Athlon-MP boards (can not remember the
exact model and am not near the machines now), and one is an Epox
Athlon-XP board.  The five MSI boards are using a built-in LAN interface
and the Epox is using a PCI card. I do have some machines with Tyan
motherboards but they have 3Com xl interfaces in them.

> On Fri, 26 Sep 2003 11:40:08 -0500, in sentex.lists.freebsd.current
> you wrote:
>
> >I am having a problem with recent builds of -current with the fxp
> >driver.  A couple of days ago, the 6 machines in my cluster with fxp
> >interfaces all died at about the same time with fxp timeout errors.
> >The machines with 3Com xl interfaces kept on going. Today, I am
> >observing that the throughput is about half of what I am seeing on my
> >machines with a 3Com xl interface.  Is anybody else observing this?
> >What other information do I need to provide?
> >
> >Thanks.

-- 
Glenn Johnson
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

problems with Intel pro/100 VE

[Richard Coleman]

I did a search on the FreeBSD web site, as well as a google search, but 
didn't see an answer to this.  I apologize if this has been discussed 
before.

I've tried to installing FreeBSD 4.8 and 5.1.  But neither of these 
recognize my network card (Intel PRO/100 VE running on new Dell computer).

Has something for this card been added after 5.1, or is this too new a 
card for anyone to have added the necessary code?

Richard Coleman
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: recent changes prohibit vinum swap.

[Greg 'groggy' Lehey]

On Friday, 26 September 2003 at 22:08:25 -0400, David Gilbert wrote:
>> "Greg" == Greg Lehey  writes:
>
> Greg> Don't hold your breath.  This will probably happen in the course
> Greg> of migrating Vinum functionality to GEOM.
>
> So... is vinum-as-we-know-it going to disappear into the GEOM
> monster?

I suppose that depends on how you know it :-)

> There seems to be cross purposes here.

I'm not sure what you mean.  GEOM is a generalized framework which
fits around Vinum.  It also does a lot of the same things that Vinum
does.  There's no reason to have duplicated effort, so Vinum is going
to have to adapt.

Greg
--
See complete headers for address and phone numbers.
NOTE: Due to the currently active Microsoft-based worms, I am limiting
all incoming mail to 131,072 bytes.  This is enough for normal mail,
but not for large attachments.  Please send these as URLs.


pgp0.pgp
Description: PGP signature

Re: Tonight's current breaks IPFILTER

[Philip Paeps]

On 2003-09-26 21:56:08 (-0400), David Gilbert <[EMAIL PROTECTED]> wrote:
> Tonight's current breaks compiling IPFILTER.  It complains that it can't
> find the 'PFIL_OUT' symbol.

The top entry in UPDATING insists that you stick PFIL_HOOKS in your
configuration.  I've just rebuilt a kernel with that option and the IPFILTER
bits and it works perfectly.

Cheers,

 - Philip

-- 
Philip Paeps  Please don't CC me, I am
   subscribed to the list.

  If you have a difficult task give it to a lazy man, he
  will find an easier way to do it.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: recent changes prohibit vinum swap.

[David Gilbert]

> "Greg" == Greg Lehey  writes:

Greg> Don't hold your breath.  This will probably happen in the course
Greg> of migrating Vinum functionality to GEOM.

So... is vinum-as-we-know-it going to disappear into the GEOM monster?
There seems to be cross purposes here.

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tonight's current breaks IPFILTER

[Sam Leffler]

> Tonight's current breaks compiling IPFILTER.  It complains that it
> can't find the 'PFIL_OUT' symbol.

Read UPDATING; you need PFIL_HOOKS in your kernel config file.

Sam

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tonight's current breaks IPFILTER

[Kris Kennaway]

On Fri, Sep 26, 2003 at 09:56:08PM -0400, David Gilbert wrote:
> Tonight's current breaks compiling IPFILTER.  It complains that it
> can't find the 'PFIL_OUT' symbol.

Did you read UPDATING?

Kris


pgp0.pgp
Description: PGP signature

Tonight's current breaks IPFILTER

[David Gilbert]

Tonight's current breaks compiling IPFILTER.  It complains that it
can't find the 'PFIL_OUT' symbol.

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: recent changes prohibit vinum swap.

[Greg 'groggy' Lehey]

On Friday, 26 September 2003 at 19:28:45 -0400, David Gilbert wrote:
>> "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:
>
> Robert> On Fri, 26 Sep 2003, David Gilbert wrote:
>
>>> Recent changes to -CURRENT prohibit vinum swap:
>>>
>>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon:
>>> /dev/vinum/swapmu: Operation not supported by device
>
> Robert> In order to support swapping, Vinum will need to be modified
> Robert> to use struct disk and the disk(9) API, rather than exposing
> Robert> its storage devices directly via struct cdevsw and
> Robert> make_dev(9).  I.e., Vinum probably needs to start approaching
> Robert> things as "disks" rather than "devices", a distinction that's
> Robert> becoming more mature in -CURRENT.
>
>>> From a quick read of vinumconfig.c, I'm guessing this wouldn't be
>>> hard to
> Robert> implement.  Some subset of struct sd, struct plex, and struct
> Robert> volume will need to start holding a struct disk instance which
> Robert> would be passed to disk_create() instead of a call to
> Robert> make_dev().  Much of the remainder will just consist of a bit
> Robert> of tweaking to make Vinum extract its data from
> bp-> bio_disk->d_drv1 instead of bp->b_dev, replacing the ioctl dev_t
> Robert> argument with a disk argument, etc.
>
> Is this something that someone can help me with quickly, or should I
> downgrade the machine until it's been done? 

Don't hold your breath.  This will probably happen in the course of
migrating Vinum functionality to GEOM.

> Is there a quick hack to make it work for now?

None that I know of.

> If I must downgrade, what date would be appropriate?

Sorry, I can't help there.  Maybe phk can give you some indication.

> Robert> I also noticed that the vinum commandline tool is a bit
> Robert> devfs-unfriendly, or at least, it gets pretty verbose about
> Robert> how all the files/directories it wants to create are already
> Robert> present.  It could be that a test for devfs conditionally
> Robert> causing a test for EEXIST would go a long way in muffling the
> Robert> somewhat loud complaining :-).
>
> Well... vinum is fragile in a whole bunch of ways.  vinum rm often
> leaves things in an inconsistant state.  I almost always reboot now
> after using it.  vinum rename doesn't change the devfs vinum directory
> ... which then also requires a reboot to correct.

Hmm.  That's another one to look at.

> Another thing that's very fragile is resetconfig.  It blanks memory,
> but not disk.

It should do.  It leaves the device names, though.  That's arguably a
bug.

Greg
--
See complete headers for address and phone numbers.
NOTE: Due to the currently active Microsoft-based worms, I am limiting
all incoming mail to 131,072 bytes.  This is enough for normal mail,
but not for large attachments.  Please send these as URLs.


pgp0.pgp
Description: PGP signature

Re: recent changes prohibit vinum swap.

[David Gilbert]

> "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:

Robert> On Fri, 26 Sep 2003, David Gilbert wrote:

>> Recent changes to -CURRENT prohibit vinum swap:
>> 
>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon:
>> /dev/vinum/swapmu: Operation not supported by device

Robert> In order to support swapping, Vinum will need to be modified
Robert> to use struct disk and the disk(9) API, rather than exposing
Robert> its storage devices directly via struct cdevsw and
Robert> make_dev(9).  I.e., Vinum probably needs to start approaching
Robert> things as "disks" rather than "devices", a distinction that's
Robert> becoming more mature in -CURRENT.

>> From a quick read of vinumconfig.c, I'm guessing this wouldn't be
>> hard to
Robert> implement.  Some subset of struct sd, struct plex, and struct
Robert> volume will need to start holding a struct disk instance which
Robert> would be passed to disk_create() instead of a call to
Robert> make_dev().  Much of the remainder will just consist of a bit
Robert> of tweaking to make Vinum extract its data from
bp-> bio_disk->d_drv1 instead of bp->b_dev, replacing the ioctl dev_t
Robert> argument with a disk argument, etc.

Is this something that someone can help me with quickly, or should I
downgrade the machine until it's been done?  Is there a quick hack to
make it work for now?  If I must downgrade, what date would be
appropriate?

Robert> I also noticed that the vinum commandline tool is a bit
Robert> devfs-unfriendly, or at least, it gets pretty verbose about
Robert> how all the files/directories it wants to create are already
Robert> present.  It could be that a test for devfs conditionally
Robert> causing a test for EEXIST would go a long way in muffling the
Robert> somewhat loud complaining :-).

Well... vinum is fragile in a whole bunch of ways.  vinum rm often
leaves things in an inconsistant state.  I almost always reboot now
after using it.  vinum rename doesn't change the devfs vinum directory
... which then also requires a reboot to correct.

Another thing that's very fragile is resetconfig.  It blanks memory,
but not disk.  It's often hard to get things running after that.  Many
times, I've had to resetconfig, reboot without loading vinum, dd to
blank the disk, reboot, load vinum and start again.

That all said, I see raidframe has been sucked in.  Are there plans
with that?

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: recent changes prohibit vinum swap.

[Robert Watson]

On Sat, 27 Sep 2003, Greg 'groggy' Lehey wrote:

> > I recently noticed that Vinum may be averse to blocksizes other than
> > 512 bytes.
> 
> It shouldn't be.  There's never been any dependency on it.

I've attached the output from trying to use a swap md set below the malloc
md set.

> > I also noticed that the vinum commandline tool is a bit
> > devfs-unfriendly, or at least, it gets pretty verbose about how all
> > the files/directories it wants to create are already present.  It
> > could be that a test for devfs conditionally causing a test for
> > EEXIST would go a long way in muffling the somewhat loud complaining
> > :-).
> 
> I'm not sure I understand this.  Can you give me a concrete example?

none# vinum
vinum -> quit
none# mdconfig -a -t malloc -s 4m
md0
none# mdconfig -a -t malloc -s 4m
md1
none# mdconfig -a -t malloc -s 4m
md2
none# mdconfig -a -t malloc -s 4m
md3
none# vinum
vinum -> concat -v /dev/md0 /dev/md1 /dev/md2 /dev/md3
volume vinum0
  plex name vinum0.p0 org concat
drive vinumdrive0 device /dev/md0
sd name vinum0.p0.s0 drive vinumdrive0 size 0
drive vinumdrive1 device /dev/md1
sd name vinum0.p0.s1 drive vinumdrive1 size 0
drive vinumdrive2 device /dev/md2
sd name vinum0.p0.s2 drive vinumdrive2 size 0
drive vinumdrive3 device /dev/md3
sd name vinum0.p0.s3 drive vinumdrive3 size 0
Can't create /dev/vinum/vinum0: File exists
Can't create /dev/vinum/vol/vinum0: No such file or directory
Can't create /dev/vinum/vol/vinum0.plex: No such file or directory
Can't create /dev/vinum/plex/vinum0.p0: File exists
Can't create /dev/vinum/vol/vinum0.plex/vinum0.p0: No such file or directory
Can't create /dev/vinum/vol/vinum0.plex/vinum0.p0.sd: No such file or directory
Can't create /dev/vinum/sd/vinum0.p0.s0: File exists
Can't create /dev/vinum/sd/vinum0.p0.s1: File exists
Can't create /dev/vinum/sd/vinum0.p0.s2: File exists
Can't create /dev/vinum/sd/vinum0.p0.s3: File exists
V vinum0State: up   Plexes:   1 Size: 15 MB
P vinum0.p0   C State: up   Subdisks: 4 Size: 15 MB
S vinum0.p0.s0  State: up   D: vinumdrive0  Size:   3963 kB
S vinum0.p0.s1  State: up   D: vinumdrive1  Size:   3963 kB
S vinum0.p0.s2  State: up   D: vinumdrive2  Size:   3963 kB
S vinum0.p0.s3  State: up   D: vinumdrive3  Size:   3963 kB

Just to demonstrate it's not because of -v:

none# vinum
vinum -> concat /dev/md0 /dev/md1 /dev/md2 /dev/md3
Can't create /dev/vinum/vinum0: File exists
Can't create /dev/vinum/vol/vinum0: No such file or directory
Can't create /dev/vinum/vol/vinum0.plex: No such file or directory
Can't create /dev/vinum/plex/vinum0.p0: File exists
Can't create /dev/vinum/vol/vinum0.plex/vinum0.p0: No such file or directory
Can't create /dev/vinum/vol/vinum0.plex/vinum0.p0.sd: No such file or directory
Can't create /dev/vinum/sd/vinum0.p0.s0: File exists
Can't create /dev/vinum/sd/vinum0.p0.s1: File exists
Can't create /dev/vinum/sd/vinum0.p0.s2: File exists
Can't create /dev/vinum/sd/vinum0.p0.s3: File exists

Attached below is the swap-backed version.  Previously when I've bumped
into compatability problems involving different types of md devices, it's
come down to the blocksize on swap-backed nodes.  Doesn't have to be the
actual cause, but it might be a good place to start.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

none# mdconfig -a -t swap -s 4m
md0
none# mdconfig -a -t swap -s 4m
md1
none# mdconfig -a -t swap -s 4m
md2
none# mdconfig -a -t swap -s 4m
md3
none# vinum
vinum -> concat -v /dev/md0 /dev/md1 /dev/md2 /dev/md3
volume vinum0
  plex name vinum0.p0 org concat
drive vinumdrive0 device /dev/md0
sd name vinum0.p0.s0 drive vinumdrive0 size 0
drive vinumdrive1 device /dev/md1
sd name vinum0.p0.s1 drive vinumdrive1 size 0
drive vinumdrive2 device /dev/md2
sd name vinum0.p0.s2 drive vinumdrive2 size 0
drive vinumdrive3 device /dev/md3
sd name vinum0.p0.s3 drive vinumdrive3 size 0
Can't create /dev/vinum/vinum0: File exists
Can't create /dev/vinum/vol/vinum0: No such file or directory
Can't create /dev/vinum/vol/vinum0.plex: No such file or directory
Can't create /dev/vinum/plex/vinum0.p0: File exists
Can't create /dev/vinum/vol/vinum0.plex/vinum0.p0: No such file or directory
Can't create /dev/vinum/vol/vinum0.plex/vinum0.p0.sd: No such file or directory
Can't create /dev/vinum/sd/vinum0.p0.s0: File exists
Can't create /dev/vinum/sd/vinum0.p0.s1: File exists
Can't create /dev/vinum/sd/vinum0.p0.s2: File exists
Can't create /dev/vinum/sd/vinum0.p0.s3: File exists
V vinum0State: down Plexes:   1 Size: 15 MB
P vinum0.p0   C State: faulty   Subdisks: 4 Size: 15 MB
S vinum0.p0.s0  State: crashed  D: vinumdrive0  Size:   3963 kB
S vinum0.p0.s1  State: crashed  D: vinumdrive1  Size:   3963 kB
S vinum0.p0.

Re: recent changes prohibit vinum swap.

[Greg 'groggy' Lehey]

On Friday, 26 September 2003 at 18:38:48 -0400, Robert Watson wrote:
>
> On Fri, 26 Sep 2003, David Gilbert wrote:
>
>> Recent changes to -CURRENT prohibit vinum swap:
>>
>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon: /dev/vinum/swapmu:
>> Operation not supported by device
>
> In order to support swapping, Vinum will need to be modified to use struct
> disk and the disk(9) API, rather than exposing its storage devices
> directly via struct cdevsw and make_dev(9).  I.e., Vinum probably needs to
> start approaching things as "disks" rather than "devices", a distinction
> that's becoming more mature in -CURRENT.
>
> From a quick read of vinumconfig.c, I'm guessing this wouldn't be hard to
> implement.  Some subset of struct sd, struct plex, and struct volume will
> need to start holding a struct disk instance which would be passed to
> disk_create() instead of a call to make_dev().  Much of the remainder will
> just consist of a bit of tweaking to make Vinum extract its data from
> bp->bio_disk->d_drv1 instead of bp->b_dev, replacing the ioctl dev_t
> argument with a disk argument, etc.

I'll take a look at this soon.  If somebody else wants to look first,
please let me know.  The introduction of GEOM means quite a shake-up
in the Vinum structure.

> I recently noticed that Vinum may be averse to blocksizes other than
> 512 bytes.

It shouldn't be.  There's never been any dependency on it.

> Or at least, I can get Vinum mirrors up and running on md devices
> backed to memory, but not to swap, and the usual reason for problems
> on that front is the 4k blocksize for swap-backed md devices.

I've had a number of problems with md devices.  This one may be that
Vinum is presenting a 512 byte block size upwards instead of the 4 kB
that it should be showing.  Again, I'll take a look.

> I also noticed that the vinum commandline tool is a bit
> devfs-unfriendly, or at least, it gets pretty verbose about how all
> the files/directories it wants to create are already present.  It
> could be that a test for devfs conditionally causing a test for
> EEXIST would go a long way in muffling the somewhat loud complaining
> :-).

I'm not sure I understand this.  Can you give me a concrete example?

Greg
--
See complete headers for address and phone numbers.
NOTE: Due to the currently active Microsoft-based worms, I am limiting
all incoming mail to 131,072 bytes.  This is enough for normal mail,
but not for large attachments.  Please send these as URLs.


pgp0.pgp
Description: PGP signature

Re: Something is wrong with the fxp network driver

[Derek Ragona]

This worked until I went beyond p4 on 5.1 release

I found a PR that suggested adding:
 { 0x1050,  "Intel 82801EB (ICH5) Pro/100 Ethernet" },
line to the if_fxp.c file, in the struct:
/*
 * Claim various Intel PCI device identifiers for this driver.  The
 * sub-vendor and sub-device field are extensively used to identify
 * particular variants, but we don't currently differentiate between
 * them.
 */
 static struct fxp_ident fxp_ident_table[] = {
{ 0x1029,   "Intel 82559 PCI/CardBus Pro/100" },
{ 0x1030,   "Intel 82559 Pro/100 Ethernet" },
{ 0x1031,   "Intel 82801CAM (ICH3) Pro/100 VE Ethernet" },
{ 0x1032,   "Intel 82801CAM (ICH3) Pro/100 VE Ethernet" },
{ 0x1033,   "Intel 82801CAM (ICH3) Pro/100 VM Ethernet" },
{ 0x1034,   "Intel 82801CAM (ICH3) Pro/100 VM Ethernet" },
{ 0x1035,   "Intel 82801CAM (ICH3) Pro/100 Ethernet" },
{ 0x1036,   "Intel 82801CAM (ICH3) Pro/100 Ethernet" },
{ 0x1037,   "Intel 82801CAM (ICH3) Pro/100 Ethernet" },
{ 0x1038,   "Intel 82801CAM (ICH3) Pro/100 VM Ethernet" },
{ 0x1039,   "Intel 82801DB (ICH4) Pro/100 VE Ethernet" },
{ 0x103A,   "Intel 82801DB (ICH4) Pro/100 Ethernet" },
{ 0x103B,   "Intel 82801DB (ICH4) Pro/100 VM Ethernet" },
{ 0x103C,   "Intel 82801DB (ICH4) Pro/100 Ethernet" },
{ 0x103D,   "Intel 82801DB (ICH4) Pro/100 VE Ethernet" },
{ 0x103E,   "Intel 82801DB (ICH4) Pro/100 VM Ethernet" },
{ 0x1050,  "Intel 82801EB (ICH5) Pro/100 Ethernet" },
{ 0x1059,   "Intel 82551QM Pro/100 M Mobile Connection" },
{ 0x1209,   "Intel 82559ER Embedded 10/100 Ethernet" },
{ 0x1229,   "Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet" },
{ 0x2449,   "Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet" },
{ 0,NULL },
 };
-Derek

At 07:15 PM 9/26/2003 -0500, Derek Ragona wrote:
Mine is an Intel® Server Board S875WP1-E, I was using a patch but it quite 
working on the fxp0 interface.

-Derek

At 08:07 PM 9/26/2003 -0400, Mike Tancsa wrote:

Are they Tyan motherboards by chance ? There was a thread in stable
about this a few weeks ago.  The problems seem specific to those
motherboards.  Someone posted a potential workaround as well.
---Mike

On Fri, 26 Sep 2003 11:40:08 -0500, in sentex.lists.freebsd.current
you wrote:
>I am having a problem with recent builds of -current with the fxp
>driver.  A couple of days ago, the 6 machines in my cluster with fxp
>interfaces all died at about the same time with fxp timeout errors.  The
>machines with 3Com xl interfaces kept on going. Today, I am observing
>that the throughput is about half of what I am seeing on my machines
>with a 3Com xl interface.  Is anybody else observing this?  What other
>information do I need to provide?
>
>Thanks.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Something is wrong with the fxp network driver

[Derek Ragona]

Mine is an Intel® Server Board S875WP1-E, I was using a patch but it quite 
working on the fxp0 interface.

-Derek

At 08:07 PM 9/26/2003 -0400, Mike Tancsa wrote:

Are they Tyan motherboards by chance ? There was a thread in stable
about this a few weeks ago.  The problems seem specific to those
motherboards.  Someone posted a potential workaround as well.
---Mike

On Fri, 26 Sep 2003 11:40:08 -0500, in sentex.lists.freebsd.current
you wrote:
>I am having a problem with recent builds of -current with the fxp
>driver.  A couple of days ago, the 6 machines in my cluster with fxp
>interfaces all died at about the same time with fxp timeout errors.  The
>machines with 3Com xl interfaces kept on going. Today, I am observing
>that the throughput is about half of what I am seeing on my machines
>with a 3Com xl interface.  Is anybody else observing this?  What other
>information do I need to provide?
>
>Thanks.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Something is wrong with the fxp network driver

[Mike Tancsa]

Are they Tyan motherboards by chance ? There was a thread in stable
about this a few weeks ago.  The problems seem specific to those
motherboards.  Someone posted a potential workaround as well.

---Mike

On Fri, 26 Sep 2003 11:40:08 -0500, in sentex.lists.freebsd.current
you wrote:

>I am having a problem with recent builds of -current with the fxp
>driver.  A couple of days ago, the 6 machines in my cluster with fxp
>interfaces all died at about the same time with fxp timeout errors.  The
>machines with 3Com xl interfaces kept on going. Today, I am observing
>that the throughput is about half of what I am seeing on my machines
>with a 3Com xl interface.  Is anybody else observing this?  What other
>information do I need to provide?
>
>Thanks.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: recent changes prohibit vinum swap.

[Robert Watson]

On Fri, 26 Sep 2003, David Gilbert wrote:

> Recent changes to -CURRENT prohibit vinum swap: 
> 
> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon: /dev/vinum/swapmu:
> Operation not supported by device

In order to support swapping, Vinum will need to be modified to use struct
disk and the disk(9) API, rather than exposing its storage devices
directly via struct cdevsw and make_dev(9).  I.e., Vinum probably needs to
start approaching things as "disks" rather than "devices", a distinction
that's becoming more mature in -CURRENT.

>From a quick read of vinumconfig.c, I'm guessing this wouldn't be hard to
implement.  Some subset of struct sd, struct plex, and struct volume will
need to start holding a struct disk instance which would be passed to
disk_create() instead of a call to make_dev().  Much of the remainder will
just consist of a bit of tweaking to make Vinum extract its data from
bp->bio_disk->d_drv1 instead of bp->b_dev, replacing the ioctl dev_t
argument with a disk argument, etc.

I recently noticed that Vinum may be averse to blocksizes other than 512
bytes.  Or at least, I can get Vinum mirrors up and running on md devices
backed to memory, but not to swap, and the usual reason for problems on
that front is the 4k blocksize for swap-backed md devices.

I also noticed that the vinum commandline tool is a bit devfs-unfriendly,
or at least, it gets pretty verbose about how all the files/directories it
wants to create are already present.  It could be that a test for devfs
conditionally causing a test for EEXIST would go a long way in muffling
the somewhat loud complaining :-). 

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

5.1 p7 to 5.1 p8 compile problems

[Derek Ragona]

I am trying to update a server from RELENG_5_1 p7 to RELENG_5_1 p8 for the 
last security advisory.  I had no problem building the p7.

I cvsup'd but the compile breaks.  I tried other mirrors, and even 
completely repopulated /usr/src.  But it still breaks.  The latest 
breakdown is:



building static objc library
ranlib libobjc.a
===> gnu/lib/libg2c
cc -O -pipe -march=pentiumpro -DHAVE_CONFIG_H=1 -DSTDC_HEADERS=1 
-DHAVE_TEMPNAM=1 -DNO_EOF_CHAR_CHECK=1 -DRETSIGTYPE=void 
-DSkip_f2c_Undefs=1 -DIEEE_drem=1 -DAllow_TYQUAD -DPedantic 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/libF77 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/libI77 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/libU77 
-I/usr/src/gnu/lib/libg2c  -c -DLabort -o abort.o 
/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/f2cext.c
cc -O -pipe -march=pentiumpro -DHAVE_CONFIG_H=1 -DSTDC_HEADERS=1 
-DHAVE_TEMPNAM=1 -DNO_EOF_CHAR_CHECK=1 -DRETSIGTYPE=void 
-DSkip_f2c_Undefs=1 -DIEEE_drem=1 -DAllow_TYQUAD -DPedantic 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/libF77 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/libI77 
-I/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/libU77 
-I/usr/src/gnu/lib/libg2c  -c -DLaccess -o access.o 
/usr/src/gnu/lib/libg2c/../../../contrib/libf2c/f2cext.c
Segmentation fault (core dumped)
*** Error code 139

Stop in /usr/src/gnu/lib.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in 
/usr/src.===
Any ideas on how to fix this?



-Derek
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

recent changes prohibit vinum swap.

[David Gilbert]

Recent changes to -CURRENT prohibit vinum swap:

[1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu
swapon: /dev/vinum/swapmu: Operation not supported by device

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: cannot boot -s

[Jonathan Fosburgh]

>
> Try to pull in the commit I just did to syscons, I looks like I messed
> something up somewhere :-(

That seems to have fixed it. I get the startup and shutdown messages.  I 
didn't make it back to my console soon enough after rebooting to go straight 
to singule-user mode, but I was able to shutdown now to get there.
-- 
Jonathan Fosburgh
AIX and Storage Administrator
UT MD Anderson Cancer Center
Houston, TX 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

DANGER! broken /dev/console

[Poul-Henning Kamp]

I seem to have messed up /dev/console.  If you have any console
related problems with -current from today, please upgrade to
after this commit before sending me your error report!

Poul-Henning

phk 2003/09/26 12:35:50 PDT

  FreeBSD src repository

  Modified files:
sys/alpha/tlsb   zs_tlsb.c 
sys/dev/ofw  ofw_console.c 
sys/dev/sab  sab.c 
sys/dev/zs   zs.c 
sys/kern tty_cons.c 
sys/pc98/pc98sio.c 
sys/sys  cons.h 
  Log:
  OK, I messed up /dev/console with what I had hoped would be compat
  code.  Convert remaining console drivers and hope for the best.
  
  Revision  ChangesPath
  1.39  +4 -3  src/sys/alpha/tlsb/zs_tlsb.c
  1.15  +4 -4  src/sys/dev/ofw/ofw_console.c
  1.20  +1 -1  src/sys/dev/sab/sab.c
  1.14  +1 -1  src/sys/dev/zs/zs.c
  1.115 +0 -5  src/sys/kern/tty_cons.c
  1.195 +21 -16src/sys/pc98/pc98/sio.c
  1.31  +0 -1  src/sys/sys/cons.h


--- End of Forwarded Message

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: cannot boot -s

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Jonathan Fosburgh writes:
>On Friday 26 September 2003 01:13 pm, Cameron Murdoch wrote:
>> I have the same here from this morning's -current but I also see this on
>> boot up:
>>
>> *snip*
>> mounting root from ufs:/dev/ad0s2a
>> pid 87 (fsck_ufs), uid 0: exited on signal 8
>> pid 88 (fsck_ufs), uid 0: exited on signal 8
>>
>
>I noticed the same thing when I did not try to boot into single-user mode.

Try to pull in the commit I just did to syscons, I looks like I messed
something up somewhere :-(

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: cannot boot -s

[Jonathan Fosburgh]

On Friday 26 September 2003 01:13 pm, Cameron Murdoch wrote:
> I have the same here from this morning's -current but I also see this on
> boot up:
>
> *snip*
> mounting root from ufs:/dev/ad0s2a
> pid 87 (fsck_ufs), uid 0: exited on signal 8
> pid 88 (fsck_ufs), uid 0: exited on signal 8
>

I noticed the same thing when I did not try to boot into single-user mode.

-- 
Jonathan Fosburgh
AIX and Storage Administrator
UT MD Anderson Cancer Center
Houston, TX 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: CF image building script (for soekris etc)

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, "masta" writes:
>Thanks phk,
>
>May I use this in wifibsd without any copywrite dramma?

Absolutely, go right ahead.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: CF image building script (for soekris etc)

[masta]

Thanks phk,

May I use this in wifibsd without any copywrite dramma?
Your beer-ware license, or bsd license, is asumed.
I was engineering my own script that does the same job, if you care to
colaborate, you may see it at:
http://masta.yazzy.org/wifibsd/bin/mkimage.sh

Mine is still a work in progress. ;)


Poul-Henning Kamp wrote:
> To: [EMAIL PROTECTED]
> Subject: CF image building script (for soekris etc)
> From: "Poul-Henning Kamp" <[EMAIL PROTECTED]>
> Date: Sun, 21 Sep 2003 21:22:59 +0200
> Message-ID: <[EMAIL PROTECTED]>
>
>
> I promised various people to post my shellscript for building a CF
> image for my soekris boxes:
>
>   http://phk.freebsd.dk/misc/build_cf.sh
>


 __  __   _
|  \/  | __ _ ___| |_ __ _
| |\/| |/ _` / __| __/ _` |
| |  | | (_| \__ \ || (_| |
|_|  |_|\__,_|___/\__\__,_|

unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep


[EMAIL PROTECTED]
http://wifibsd.org



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: boot -s change in -current?

[Cameron Murdoch]

On Fri, 2003-09-26 at 19:42, Scott Long wrote:
> On Fri, 26 Sep 2003, Aaron Wohl wrote:
> 
> > I just cvsuped -current/build/install.  Now boot -s doesnt work, it
> > ignores the -s.  Do I need to do something to enable -s nowadays?  Or how
> > to get into standalone now?
> 
> I have no idea what the cause is, but does the 'boot single user' option
> of the loader work?
> 
> Scott

No it has the same result.

Cam


signature.asc
Description: This is a digitally signed message part

Re: boot -s change in -current?

[Scott Long]

On Fri, 26 Sep 2003, Aaron Wohl wrote:

> I just cvsuped -current/build/install.  Now boot -s doesnt work, it
> ignores the -s.  Do I need to do something to enable -s nowadays?  Or how
> to get into standalone now?

I have no idea what the cause is, but does the 'boot single user' option
of the loader work?

Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

boot -s change in -current?

[Aaron Wohl]

I just cvsuped -current/build/install.  Now boot -s doesnt work, it
ignores the -s.  Do I need to do something to enable -s nowadays?  Or how
to get into standalone now?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: cannot boot -s

[Cameron Murdoch]

I have the same here from this morning's -current but I also see this on
boot up:

*snip*
mounting root from ufs:/dev/ad0s2a
pid 87 (fsck_ufs), uid 0: exited on signal 8
pid 88 (fsck_ufs), uid 0: exited on signal 8

The machine then displays the login prompt, but not the missing startup
messages.

Cam

On Fri, 2003-09-26 at 17:16, Jonathan Fosburgh wrote:
> On Friday 26 September 2003 10:32 am, Shin-ichi Yoshimoto wrote:
> > Hi, After new kernel installing, I cannot boot -s.
> > This kernel always runs multiuser mode.
> >
> > What's happen ??
> I have the same thing from this morning's sources.  Also, shutdown -s just 
> brings me back up into single-user mode.   Also, the output from startup and 
> shutdown scripts is no longer being echoed to the console.  Now, the system 
> so far appears to be running fine and everything does seem to have started.  
> Still, seems a little strange ...


signature.asc
Description: This is a digitally signed message part

Re: Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)

[Terry Lambert]

"Jeroen C.van Gelderen" wrote:
> On Friday, Sep 26, 2003, at 13:29 US/Eastern, Terry Lambert wrote:
> > Which begs the question... is 5.2 going to ship with WITH_LIBMAP
> > enabled by default?
> 
> http://www.google.com/search?q=libmap+default+WITH_LIBMAP&ie=UTF-
> 8&oe=UTF-8
> 
> http://people.freebsd.org/~bmah/relnotes/CURRENT/relnotes-i386.txt
> 
> rtld(1) now includes ``libmap'' functionality by default; the
> WITH_LIBMAP compile knob is unnecessary and has been retired. More
> information can be found in libmap.conf(5).

I saw that in the release notes; but people are still posting to
-current about problems that require it, and other are posting
about how to use it, so either their -current isn't, or the code
doesn't match the release notes.  I suspect the former, but I
wanted to make sure (5.2 is going to be my next big "upgrade
the old boxes" release).

-- Terry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)

[Daniel Eischen]

On Fri, 26 Sep 2003, Terry Lambert wrote:

> Claus Guttesen wrote:
> > Before the 'make world/kernel' these two apps would
> > crash at regular intervals, and I had to make these
> > addititions to /etc/libmap.conf so they wouldn't go
> > down:
> > 
> > [/usr/X11R6/bin/firebird]
> > libc_r.so.5  libthr.so.1
> > libc_r.solibthr.so
> 
> Which begs the question... is 5.2 going to ship with WITH_LIBMAP
> enabled by default?

It's already enabled by default, so I'd think so:


revision 1.25
date: 2003/09/13 21:50:35;  author: mdodd;  state: Exp;  lines: +1 -10
Retire the WITH_LIBMAP compile knob; libmap is now a standard feature.


-- 
Dan Eischen

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)

[Jeroen C . van Gelderen]

On Friday, Sep 26, 2003, at 13:29 US/Eastern, Terry Lambert wrote:
Which begs the question... is 5.2 going to ship with WITH_LIBMAP
enabled by default?
http://www.google.com/search?q=libmap+default+WITH_LIBMAP&ie=UTF- 
8&oe=UTF-8

http://people.freebsd.org/~bmah/relnotes/CURRENT/relnotes-i386.txt

rtld(1) now includes ``libmap'' functionality by default; the  
WITH_LIBMAP
   compile knob is unnecessary and has been retired. More information  
can be
   found in libmap.conf(5).

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)

[Terry Lambert]

Claus Guttesen wrote:
> Before the 'make world/kernel' these two apps would
> crash at regular intervals, and I had to make these
> addititions to /etc/libmap.conf so they wouldn't go
> down:
> 
> [/usr/X11R6/bin/firebird]
> libc_r.so.5  libthr.so.1
> libc_r.solibthr.so

Which begs the question... is 5.2 going to ship with WITH_LIBMAP
enabled by default?

-- Terry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ThinkPad R40 hangs during ACPI power down

[Don Lewis]

On 26 Sep, To: [EMAIL PROTECTED] wrote:
> On 25 Sep, Nate Lawson wrote:

>> To debug this, please boot a newer kernel with the ACPI_DEBUG option with
>> the following options in loader.conf:
>> 
>> debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS"
>> debug.acpi.level="ACPI_LV_FUNCTIONS"
>> 
>> You'll get spammed with way too many messages on boot but just ignore
>> these.
> 
> You're not kidding.  I gave up after 2 hours and 7.5 MB of output.  It
> looks like it's looping, see below ...

I let it run overnight and it spewed 25 MB of output before I killed it.
It didn't get very far into the boot, just after the CPU is probed.  I
uploaded the full trace to
.

The system boots ok if I remove these two debug options.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Something is wrong with the fxp network driver

[Lanny Baron]

Hi Glenn,
We have several FreeBSD boxes here. Some run -current and some run -5.1-P4
and all have fxp* and em*

You must have something else going wrong that is causing you the grief.
fxp0: flags=8843 mtu 1500
options=3
inet6 fe80::202:b3ff:fe96:c64b%fxp0 prefixlen 64 scopeid 0x1
ether 00:02:b3:96:c6:4b
media: Ethernet autoselect (10baseT/UTP)
status: active

The above is on:

gw-tor# uname -a
FreeBSD gw-tor.FreeBSDsystems.COM 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed
Sep 24 11:07:47 EDT 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/GW-TOR  i386

Because of our network setup, fxp0 does not have any ip address bound to it.

Check your logs, like I said, something else is causing the problem.

Lanny

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Lanny Baron
Proud to be 100% FreeBSD
http://www.FreeBSDsystems.COM
Toll Free: 1.877.963.1900
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=


- Original Message -
From: "Glenn Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 26, 2003 12:40 PM
Subject: Something is wrong with the fxp network driver


> I am having a problem with recent builds of -current with the fxp
> driver.  A couple of days ago, the 6 machines in my cluster with fxp
> interfaces all died at about the same time with fxp timeout errors.  The
> machines with 3Com xl interfaces kept on going. Today, I am observing
> that the throughput is about half of what I am seeing on my machines
> with a 3Com xl interface.  Is anybody else observing this?  What other
> information do I need to provide?
>
> Thanks.
>
> --
> Glenn Johnson
> USDA, ARS, SRRC Phone: (504) 286-4252
> New Orleans, LA 70124 e-mail: [EMAIL PROTECTED]
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Something is wrong with the fxp network driver

[Glenn Johnson]

I am having a problem with recent builds of -current with the fxp
driver.  A couple of days ago, the 6 machines in my cluster with fxp
interfaces all died at about the same time with fxp timeout errors.  The
machines with 3Com xl interfaces kept on going. Today, I am observing
that the throughput is about half of what I am seeing on my machines
with a 3Com xl interface.  Is anybody else observing this?  What other
information do I need to provide?

Thanks.

-- 
Glenn Johnson
USDA, ARS, SRRC  Phone: (504) 286-4252
New Orleans, LA 70124   e-mail: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: cannot boot -s

[Jonathan Fosburgh]

On Friday 26 September 2003 10:32 am, Shin-ichi Yoshimoto wrote:
> Hi, After new kernel installing, I cannot boot -s.
> This kernel always runs multiuser mode.
>
> What's happen ??
I have the same thing from this morning's sources.  Also, shutdown -s just 
brings me back up into single-user mode.   Also, the output from startup and 
shutdown scripts is no longer being echoed to the console.  Now, the system 
so far appears to be running fine and everything does seem to have started.  
Still, seems a little strange ...
-- 
Jonathan Fosburgh
AIX and Storage Administrator
UT MD Anderson Cancer Center
Houston, TX 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

cannot boot -s

[Shin-ichi Yoshimoto]

Hi, After new kernel installing, I cannot boot -s.
This kernel always runs multiuser mode.

What's happen ?? 

-- 
Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]>
http://diary.waishi.jp/~yosimoto/diary/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: re,rl and BURN_BRIDGES

[M. Warner Losh]

In message: <[EMAIL PROTECTED]>
Jiri Mikulas <[EMAIL PROTECTED]> writes:
: when i use BURN_BRIDGES in kernel config,
: it seems that there is resubmited old part of code
: in function suspend and resume - PCIR_MAPS symbol
: i made diff for me  - see attachment
: please could anybody submit corrected version into cvs tree?
: i'm not maintainer ...

But the suspend/resume routines shouldn't be defined to do these
things when BURN_BRIDGES is defined.

Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Fixing -pthreads (Re: ports and -current)

[Garrett Wollman]

< said:

> think '-pthread' is a good thing. It's nice to have a portable way to say
> that I want to compile POSIX code. What good is a standard if there's no
> standard way to get to it?

The Standard way to do it is:

c99 foo.c -l pthread

-GAWollman

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: yep, umass still broken

[Wesley Morgan]

On Fri, 26 Sep 2003, Brian Fundakowski Feldman wrote:

> I can get fdisk to read the MBR, but when I try mdir, I get this trace back
> (of course, no crash dump because those haven't worked for me in a year):
> trap 0xc
> memcpy()
> ohci_softintr()
> usb_schedsoftintr()
> ohci_intr1()
> ohci_intr()
> ithread_loop()
>
> Anyone have any clued?  I'll include my dmesg, of course.

It was unbroken for a while, but has been broken for at least a month
(seem my earlier post about it). The umass driver has been a constant
source of frustation for me and suffers from constant breakage and
neglect.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

re,rl and BURN_BRIDGES

[Jiri Mikulas]

Hello
when i use BURN_BRIDGES in kernel config,
it seems that there is resubmited old part of code
in function suspend and resume - PCIR_MAPS symbol
i made diff for me  - see attachment
please could anybody submit corrected version into cvs tree?
i'm not maintainer ...
Thanks for help  :)
Jiri
--- sys/pci/if_rl.c Thu Sep 11 06:05:01 2003
+++ sys/pci/if_rl.c Tue Sep 23 16:09:10 2003
@@ -1915,7 +1915,7 @@
rl_stop(sc);
 
for (i = 0; i < 5; i++)
-   sc->saved_maps[i] = pci_read_config(dev, PCIR_MAPS + i * 4, 4);
+   sc->saved_maps[i] = pci_read_config(dev, PCIR_BAR(i), 4);
sc->saved_biosaddr = pci_read_config(dev, PCIR_BIOS, 4);
sc->saved_intline = pci_read_config(dev, PCIR_INTLINE, 1);
sc->saved_cachelnsz = pci_read_config(dev, PCIR_CACHELNSZ, 1);
@@ -1944,7 +1944,7 @@
 
/* better way to do this? */
for (i = 0; i < 5; i++)
-   pci_write_config(dev, PCIR_MAPS + i * 4, sc->saved_maps[i], 4);
+   pci_write_config(dev, PCIR_BAR(i), sc->saved_maps[i], 4);
pci_write_config(dev, PCIR_BIOS, sc->saved_biosaddr, 4);
pci_write_config(dev, PCIR_INTLINE, sc->saved_intline, 1);
pci_write_config(dev, PCIR_CACHELNSZ, sc->saved_cachelnsz, 1);
--- sys/dev/re/if_re.c  Sat Sep 20 23:18:27 2003
+++ sys/dev/re/if_re.c  Tue Sep 23 16:06:35 2003
@@ -2423,7 +2423,7 @@
re_stop(sc);
 
for (i = 0; i < 5; i++)
-   sc->saved_maps[i] = pci_read_config(dev, PCIR_MAPS + i * 4, 4);
+   sc->saved_maps[i] = pci_read_config(dev, PCIR_BAR(i), 4);
sc->saved_biosaddr = pci_read_config(dev, PCIR_BIOS, 4);
sc->saved_intline = pci_read_config(dev, PCIR_INTLINE, 1);
sc->saved_cachelnsz = pci_read_config(dev, PCIR_CACHELNSZ, 1);
@@ -2452,7 +2452,7 @@
 
/* better way to do this? */
for (i = 0; i < 5; i++)
-   pci_write_config(dev, PCIR_MAPS + i * 4, sc->saved_maps[i], 4);
+   pci_write_config(dev, PCIR_BAR(i), sc->saved_maps[i], 4);
pci_write_config(dev, PCIR_BIOS, sc->saved_biosaddr, 4);
pci_write_config(dev, PCIR_INTLINE, sc->saved_intline, 1);
pci_write_config(dev, PCIR_CACHELNSZ, sc->saved_cachelnsz, 1);

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Where is my SLIP interface

[Bernd Walter]

On Fri, Sep 26, 2003 at 01:29:30PM +0200, Willem Jan Withagen wrote:
> Don't ask why, but running 'slattach -l /dev/cuaa0' works
> No modem is connect now so it could be the -l stuff.
> And slattach would be waiting for my modem to signal things.

Possible - I never used anything else, because I completly trust
TCP to care for data loss in my microcontroller applications.
If the controller can't keep up with the serial transmission it
normaly also can't keep up with the content.

-- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Where is my SLIP interface

[Willem Jan Withagen]

Don't ask why, but running 'slattach -l /dev/cuaa0' works
No modem is connect now so it could be the -l stuff.
And slattach would be waiting for my modem to signal things.

it created sl1 but who am I to complain.

Thanx for getting me on my way again...
--WjW

- Original Message - 
From: "Bernd Walter" <[EMAIL PROTECTED]>
To: "Willem Jan Withagen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, September 26, 2003 1:19 PM
Subject: Re: Where is my SLIP interface


> On Fri, Sep 26, 2003 at 12:47:53PM +0200, Willem Jan Withagen wrote:
> > From: "Bernd Walter" <[EMAIL PROTECTED]>
> > > On Thu, Sep 25, 2003 at 07:49:18PM +1000, Peter Jeremy wrote:
> > But am I to understand that running slattach creates the sl0 device?? by
> > something like 'ifconfig sl0 create'?
> > Or is slattach just loading the module which makes sl0 appear?
>
> slattach creates and removes the device.
> It doesn't make much sense to have a slip device alone IMO.
>
> [51]cicely13# kldstat -v | grep sl
> 88 if_sl
> [52]cicely13# ifconfig sl0
> ifconfig: interface sl0 does not exist
> Exit 1
> [53]cicely13# slattach -l /dev/cuaa0
> /var/run/slattach.cuaa0.pid
> [54]cicely13# ifconfig sl0
> sl0: flags=8011 mtu 552
> [55]cicely13# kill `cat /var/run/slattach.cuaa0.pid`
> [56]cicely13# ifconfig sl0
> ifconfig: interface sl0 does not exist
> Exit 1
>
> -- 
> B.Walter   BWCThttp://www.bwct.de
> [EMAIL PROTECTED]  [EMAIL PROTECTED]
>
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Where is my SLIP interface

[Bernd Walter]

On Fri, Sep 26, 2003 at 12:47:53PM +0200, Willem Jan Withagen wrote:
> From: "Bernd Walter" <[EMAIL PROTECTED]>
> > On Thu, Sep 25, 2003 at 07:49:18PM +1000, Peter Jeremy wrote:
> But am I to understand that running slattach creates the sl0 device?? by
> something like 'ifconfig sl0 create'?
> Or is slattach just loading the module which makes sl0 appear?

slattach creates and removes the device.
It doesn't make much sense to have a slip device alone IMO.

[51]cicely13# kldstat -v | grep sl
88 if_sl
[52]cicely13# ifconfig sl0
ifconfig: interface sl0 does not exist
Exit 1
[53]cicely13# slattach -l /dev/cuaa0
/var/run/slattach.cuaa0.pid
[54]cicely13# ifconfig sl0
sl0: flags=8011 mtu 552
[55]cicely13# kill `cat /var/run/slattach.cuaa0.pid`
[56]cicely13# ifconfig sl0
ifconfig: interface sl0 does not exist
Exit 1

-- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Where is my SLIP interface

[Willem Jan Withagen]

From: "Bernd Walter" <[EMAIL PROTECTED]>
> On Thu, Sep 25, 2003 at 07:49:18PM +1000, Peter Jeremy wrote:
> > On Thu, Sep 25, 2003 at 02:43:21PM +0930, Greg 'groggy' Lehey wrote:
> > >> Perhaps 'The Complete FreeBSD' by Greg Lehey will help out.
> > >
> > >Not any more.  I removed that chapter from the book.  The chapter's
> > >available (also covers UUCP) if anybody wants it; just ask.  But it
> > >seems that Willem has already had SLIP up and running.
> >
> > I can (mostly) understand removing SLIP, but I though UUCP still
> > had a niche as a way to implement e-mail "pull" delivery without
> > losing the envelope - even when you don't have/want IP connectivity.
>
> Slip is still the ideal protocol to interface microntrollers because
> of its simplicity.
> PPP just wastes space for this purpose.
> Unfortunately neither IPv6 nor USB serials were working with the
> -current I use.
> You can connect using ucom device but may expirience hangings, which
> might already be solved.
> Mmm - and acording to this thread there is a new problem.
>
> At least it still works with my (old) system:
> /var/run/slattach.cuaa0.pid
> [78]cicely13# ps -ax | grep sla
> 18680  p0  R+ 0:00.01 grep sla
> 18678  a0  Ss+0:00.01 slattach -l /dev/cuaa0
> [79]cicely13# ifconfig sl0
> sl0: flags=8011 mtu 552
> [80]cicely13# uname -a
> FreeBSD cicely13.cicely.de 5.1-CURRENT FreeBSD 5.1-CURRENT #15: Sun Jun 15
06:26:51 CEST 2003
[EMAIL PROTECTED]:/var/d7/builder/FreeBSD-2003-06-05-cicely13/src/sys
/i386/compile/CICELY13  i386

I have more or less the same reason to use SLIP.
It's a simple dedicated line (IP-only) between my router and an Portmaster
on a fixed line.
No reason to do anything as complicated as PPP: no logins, no IPX .

But am I to understand that running slattach creates the sl0 device?? by
something like 'ifconfig sl0 create'?
Or is slattach just loading the module which makes sl0 appear?

--WjW

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

CF image building script (for soekris etc)

[Poul-Henning Kamp]

To: [EMAIL PROTECTED]
Subject: CF image building script (for soekris etc)
From: "Poul-Henning Kamp" <[EMAIL PROTECTED]>
Date: Sun, 21 Sep 2003 21:22:59 +0200
Message-ID: <[EMAIL PROTECTED]>


I promised various people to post my shellscript for building a CF
image for my soekris boxes:

http://phk.freebsd.dk/misc/build_cf.sh

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Geom and Gbde slides

[Poul-Henning Kamp]

To: [EMAIL PROTECTED]
Subject: Geom and Gbde slides
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
Date: Sun, 21 Sep 2003 21:19:52 +0200
Message-ID: <[EMAIL PROTECTED]>


As promised, but somewhat delayed, I have uploaded my slides from
BSDcon03 to my web-server:

http://phk.freebsd.dk/pubs

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: KSE howto?

[Claus Guttesen]

On 9 Sep 2003 at 17:06, Jesse Guardiani wrote:

>> Howdy list,
>> 
>> Is there a KSE howto guide anywhere?
>> 
>> I'm thinking about updating my FreeBSD 5.1-RELEASE
>> system to -CURRENT and compiling XFree, KDE, MySQL,
>> and Apache2 with KSE support, just for fun.
>> 
>> But I don't know how to enable KSE support at
>> compile time...

> I just enable libkse on 5.1-RELEASE.  Do this:
> 1 - add "WITH_LIBMAP= yes" to /etc/make.conf 
> 2 - do a make clean in src/libexec/rtld-elf and make
all install
> 3 - to /etc/libmap.conf, add: 

> libc_r.so.5 libkse.so.1
> libc_r.so libkse.so

I cvsup'ed with current Sept. 25'th and noticed
changes to libpthread. So I did a 'make world/kernel'
and Firebird (browser) and Thunderbird (mail) haven't
crashed since then.

Before the 'make world/kernel' these two apps would
crash at regular intervals, and I had to make these
addititions to /etc/libmap.conf so they wouldn't go
down:

[/usr/X11R6/bin/firebird]
libc_r.so.5  libthr.so.1
libc_r.solibthr.so

regards
Claus


Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og 
virusscan
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ThinkPad R40 hangs during ACPI power down

[Don Lewis]

On 25 Sep, Nate Lawson wrote:
>> I've got an IBM ThinkPad R40 that hangs when I do a "shutdown -p".  It
>> wedges after printing "Powering system off using ACPI".
>>
>> Attempting to use 'acpiconf -s" to suspend produces similar hangs.
> 
> Your system is halting correctly but powering off is failing.  A cursory
> glance at your ASL shows nothing particularly amiss.  It's very similar to
> my laptop (T23).
> 
>> I tried compiling a version of the kernel with the ACPI_DEBUG option
>> listed in NOTES, but buildkernel dies
> 
> This was fixed on Sept 21 so cvsup and recompile.  Set hw.acpi.verbose=1
> in loader.conf to get more messages.

I didn't get much more ...

acpi_cmbat1: battery initialization failed, giving up  
Waiting (max 60 seconds) for system process `vnlru' to stop...stopped  
Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped  
Waiting (max 60 seconds) for system process `syncer' to stop...stopped  
  
syncing disks, buffers remaining... 11 11   
done  
Uptime: 1m10s  
Powering system off using ACPI 


> To debug this, please boot a newer kernel with the ACPI_DEBUG option with
> the following options in loader.conf:
> 
> debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS"
> debug.acpi.level="ACPI_LV_FUNCTIONS"
> 
> You'll get spammed with way too many messages on boot but just ignore
> these.

You're not kidding.  I gave up after 2 hours and 7.5 MB of output.  It
looks like it's looping, see below ...


> Then do shutdown -p and log the printed messages (hopefully you
> have a serial console).
> 
> I'll map the debugging tunables to a sysctl since it would be better if
> you could just set this just before testing rather than for the full boot.

Yeah, that would be a lot better.



 psscope-0236 [10] PsPushScope   : Entry 0xc402e9a8
   SYNCH-0156 [11] AcpiOsWaitSemaphore   : Entry
   SYNCH-0162 [11] AcpiOsWaitSemaphore   : Exit- AE_OK
   SYNCH-0314 [11] AcpiOsSignalSemaphore : Entry
   SYNCH-0336 [11] AcpiOsSignalSemaphore : Exit- AE_OK
  utmisc-1062 [11] UtPushGenericState: Entry
  utmisc-1070 [11] UtPushGenericState: Exit-
 psscope-0271 [10] PsPushScope   : Exit- AE_OK
   SYNCH-0156 [10] AcpiOsWaitSemaphore   : Entry
   SYNCH-0162 [10] AcpiOsWaitSemaphore   : Exit- AE_OK
   SYNCH-0314 [10] AcpiOsSignalSemaphore : Entry
   SYNCH-0336 [10] AcpiOsSignalSemaphore : Exit- AE_OK
 psparse-0405 [10] PsNextParseState  : Entry 0xc403b128
 psparse-0501 [10] PsNextParseState  : Exit- AE_OK
  psargs-0489 [10] PsGetNextSimpleArg: Entry 0001
  psargs-0562 [10] PsGetNextSimpleArg: Exit-
 psparse-0405 [10] PsNextParseState  : Entry 0xc403b128
 psparse-0501 [10] PsNextParseState  : Exit- AE_OK
 psparse-0231 [10] PsCompleteThisOp  : Entry 0xc403b128
 psparse-0378 [10] PsCompleteThisOp  : Exit-
 psscope-0301 [10] PsPopScope: Entry
  utmisc-1093 [11] UtPopGenericState : Entry
  utmisc-1106 [11] UtPopGenericState : Exit- 0xc40248a8
  utmisc-1333 [11] UtDeleteGenericState  : Entry
   SYNCH-0156 [12] AcpiOsWaitSemaphore   : Entry
   SYNCH-0162 [12] AcpiOsWaitSemaphore   : Exit- AE_OK
   SYNCH-0314 [12] AcpiOsSignalSemaphore : Entry
   SYNCH-0336 [12] AcpiOsSignalSemaphore : Exit- AE_OK
  utmisc-1337 [11] UtDeleteGenericState  : Exit-
 psscope-0334 [10] PsPopScope: Exit-
 nsutils-0982 [10] NsOpensScope  : Entry Integer
 nsutils-0993 [10] NsOpensScope  : Exit-0   0
 psparse-0405 [10] PsNextParseState  : Entry 0xc402e9a8
 psparse-0501 [10] PsNextParseState  : Exit- AE_OK
 psparse-0231 [10] PsCompleteThisOp  : Entry 0xc402e9a8
  pswalk-0340 [11] PsDeleteParseTree : Entry 0xc402e9a8
  utmisc-1165 [12] UtCreateThreadState   : Entry
   SYNCH-0156 [13] AcpiOsWaitSemaphore   : Entry
   SYNCH-0162 [13] AcpiOsWaitSemaphore   : Exit- AE_OK
   SYNCH-0314 [13] AcpiOsSignalSemaphore : Entry
   SYNCH-0336 [13] AcpiOsSignalSemaphore : Exit- AE_OK
  utmisc-1181 [12] UtCreateThreadState   : Exit- 0xc40248a8
dswstate-0950 [12] DsCreateWalkState : Entry
   SYNCH-0156 [13] AcpiOsWaitSemaphore   : Entry
   SYNCH-0162 [13] AcpiOsWaitSemaphore   : Exit- AE_OK
   SYNCH-0314 [13] AcpiOsSignalSemaphore : Entry
   SYNCH-0336 [13] AcpiOsSignalSemaphore : Exit- AE_OK
dsmthdat-0158 [13] DsMethodDataInit  : Entry
dsmthdat-0186 [13] DsMethodDataInit  : Exit-
   SYNCH-0156 [13] AcpiOsWaitSemaphore   : Entry
   SYNCH-0162 [13] AcpiOsWaitSemaphore   : Exit- AE_OK
   SYNCH-0314 [13] AcpiOsSignalSemaphore : Entry
   SYNCH-0336 [13] AcpiOsSignalSemaphore : Exit- AE_OK
  utmisc-1062 [13] UtPushGenericState: Entry
  utmisc-1070 [13] UtPushGenericState: Exit-
dswstate-0872 [13] DsPushWalkState   : Entry
dswstate-0878 [13] DsPushWalkState   :