On Wed, May 29, 2013 at 08:47:14AM +0900, Hiroki Sato wrote:
YongHyeon PYUN pyu...@gmail.com wrote
in 20130528023300.ga3...@michelle.cdnetworks.com:
py I'll have access to the other box on Wednesday and will try the other
test.
py
py Here is patch I'm testing and it seems to work with
On Tue, May 28, 2013 at 03:34:00PM -0400, Michael L. Squires wrote:
Short answer: it didn't work.
[...]
Patch did not solve the problem on the home NAT box. I'll try it on the
Hmm, I can't reproduce it on my box. I double checked every
possible controller initialization sequences in driver
Short answer: it didn't work.
On Tue, 28 May 2013, YongHyeon PYUN wrote:
On Mon, May 27, 2013 at 01:02:14PM -0400, Michael L. Squires wrote:
On Mon, 27 May 2013, YongHyeon PYUN wrote:
On Sun, May 26, 2013 at 08:38:41PM +0900, YongHyeon PYUN wrote:
On Fri, May 24, 2013 at 04:36:46PM
YongHyeon PYUN pyu...@gmail.com wrote
in 20130528023300.ga3...@michelle.cdnetworks.com:
py I'll have access to the other box on Wednesday and will try the other
test.
py
py Here is patch I'm testing and it seems to work with dhclient on
py CURRENT.
py Mike, could you try attached patch?
On
On Mon, 27 May 2013, YongHyeon PYUN wrote:
On Sun, May 26, 2013 at 08:38:41PM +0900, YongHyeon PYUN wrote:
On Fri, May 24, 2013 at 04:36:46PM +0900, Hiroki Sato wrote:
Hiroki Sato h...@freebsd.org wrote
in 20130524.162926.395058052118975996@allbsd.org:
hr YongHyeon PYUN
On Fri, May 24, 2013 at 04:36:46PM +0900, Hiroki Sato wrote:
Hiroki Sato h...@freebsd.org wrote
in 20130524.162926.395058052118975996@allbsd.org:
hr YongHyeon PYUN pyu...@gmail.com wrote
hr in 20130524054720.ga1...@michelle.cdnetworks.com:
hr
hr A workaround is specifying the
On Fri, May 24, 2013 at 03:32:29AM -0400, Charles Sprickman wrote:
On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote:
On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM
On Sun, May 26, 2013 at 08:38:41PM +0900, YongHyeon PYUN wrote:
On Fri, May 24, 2013 at 04:36:46PM +0900, Hiroki Sato wrote:
Hiroki Sato h...@freebsd.org wrote
in 20130524.162926.395058052118975996@allbsd.org:
hr YongHyeon PYUN pyu...@gmail.com wrote
hr in
On May 24, 2013 1:58 AM, Jeremy Chadwick j...@koitsu.org wrote:
I can't test anything without an ISO -- the system in question is truly
bare-bones (no hard disk, can't boot USB memsticks, etc.). I'm not a
good test subject for changes on this one, I'm afraid.
On another system, if you can
YongHyeon PYUN pyu...@gmail.com wrote
in 20130524054720.ga1...@michelle.cdnetworks.com:
py On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
py On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
py On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
py
On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote:
On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy
Hiroki Sato h...@freebsd.org wrote
in 20130524.162926.395058052118975996@allbsd.org:
hr YongHyeon PYUN pyu...@gmail.com wrote
hr in 20130524054720.ga1...@michelle.cdnetworks.com:
hr
hr A workaround is specifying the following line in rc.conf:
hr
hr ifconfig_fxp0=DHCP media 100baseTX
YongHyeon PYUN pyu...@gmail.com wrote
in 20130524054720.ga1...@michelle.cdnetworks.com:
py On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
py On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
py On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
py
On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote:
On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy
I'll have access to the test box on Tuesday, will test a fixed IP number
then. I'm unable to test that here since reinstalling 8.4 on the NAT box
will require eventually reinstalling 8.3-RELEASE and I'm not the only one
using the NAT box for Internet access.
The test box had 8.3-RC3
Hiroki Sato wrote this message on Fri, May 24, 2013 at 16:36 +0900:
Hiroki Sato h...@freebsd.org wrote
in 20130524.162926.395058052118975996@allbsd.org:
hr YongHyeon PYUN pyu...@gmail.com wrote
hr in 20130524054720.ga1...@michelle.cdnetworks.com:
hr
hr A workaround is specifying
I agree that this seems to be a problem only experienced by those still
using the fxp interface and DHCP on a certain subset of Supermicro
systems, which has to be a very small group.
This isn't entirely correct. The test box I used has an Intel Pro 100 pci card
plugged into an Intel
I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh
installation of 8.4-RC3. I had problems with the installation, wouldn't
boot until I used a Windows 98 FDISK to write a master boot record (no
idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X board with two
On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote:
I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh
installation of 8.4-RC3. I had problems with the installation, wouldn't
boot until I used a Windows 98 FDISK to write a master boot record
(no idea
On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote:
I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh
installation of 8.4-RC3. I had problems with the installation, wouldn't
boot until
On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote:
I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh
installation of
On Thu, May 23, 2013 at 08:03:51PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote:
I've just tested 8.4-RC3
On Thu, May 23, 2013 at 11:13:03PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:03:51PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 08:18:33PM
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
If someone wants me to test DHCP via fxp(4) on the above system (I can
do so with both NICs), just let me know; it should only take me half an
hour or so.
I'll politely wait for someone to say please do so else won't bother.
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
If someone wants me to test DHCP via fxp(4) on the above system (I can
do so with both NICs), just let me know; it should only take me half an
hour or so.
I'll
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
If someone wants me to test DHCP via fxp(4) on the above system (I can
do so with both NICs), just
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
[...]
So if someone wants to take a stab at this, they'll need to do so and
make me an ISO. Sorry that I can't make things easier. :-(
This definitely needs to get fixed before 8.4-RELEASE.
*sigh*
At this point, it is
On May 24, 2013, at 12:40 AM, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
If someone wants me to test DHCP via fxp(4) on the above system (I can
do so with both NICs), just let me know; it
On Fri, May 24, 2013 at 12:56:20AM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
[...]
So if someone wants to take a stab at this, they'll need to do so and
make me an ISO. Sorry that I can't make things easier. :-(
This definitely needs
Speaking entirely on behalf of myself now...
On Thu, May 23, 2013 at 10:11:39PM -0700, Jeremy Chadwick wrote:
I think this will likely be included in errata notes for the release.
I urge you to meet with others in Release Engineering and discuss this
fully. This is major enough that, once
At this point fxp hardware is over a decade old. I'm loath to introduce delays
at the end of the runway for this issue.
Keep in mind that delays to 8.4 are pushed directly on to delays for 9.2, which
won't be started until 8.4 is completed, and is desperately needed. (9.1
doesn't have drivers
Jeremy Chadwick j...@koitsu.org wrote
in 20130524044035.ga40...@icarus.home.lan:
jd On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
jd On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
jd If someone wants me to test DHCP via fxp(4) on the above system (I can
jd
On Fri, May 24, 2013 at 01:24:24AM -0400, Glen Barber wrote:
Speaking entirely on behalf of myself now...
On Thu, May 23, 2013 at 10:11:39PM -0700, Jeremy Chadwick wrote:
I think this will likely be included in errata notes for the release.
I urge you to meet with others in Release
On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
If someone wants me to test DHCP
On Fri, May 24, 2013 at 02:47:20PM +0900, YongHyeon PYUN wrote:
On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
On Thu, May 23, 2013 at
The problem is not with the kernel/motherboard combination but with the
world/motherboard combination.
8.3-R p8 with the 8.3R p8 world works fine.
8.4-Prerelease (what I get using cvsup 8_4) works fine.
8.3R p8 with the 8.4 Pre world has DHCP problems (see example below)
8.4 Pre with the 8.4
I'm not sure this is a kernel issue.
I re-installed 8.3Release p8 (have to get work done!) and then installed a
8.4 Prerelease kernel (I'm still running cvsup, going to svn is a number
of crisis problems down from the list of things to fix today).
Booted with the 8.4 Prerelease kernel but
On Sat, May 11, 2013 at 7:57 PM, Michael L. Squires mi...@siralan.orgwrote:
I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp driver on
an older Supermicro single CPU single core Xeon motherboard.
I know that 8.3-Release does not have this issue, but don't know when in
the
On Sat, May 11, 2013 at 10:57:44PM -0400, Michael L. Squires wrote:
I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp
driver on an older Supermicro single CPU single core Xeon
motherboard.
[...]
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983,
Here is pciconf -lvbc under 8.3-RELEASE p8:
hostb0@pci0:0:0:0: class=0x06 card=0x chip=0x00171166 rev=0x32
hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'CMIC-SL'
class = bridge
subclass = HOST-PCI
hostb1@pci0:0:0:1:
On Sun, 12 May 2013, Glen Barber wrote:
On Sat, May 11, 2013 at 10:57:44PM -0400, Michael L. Squires wrote:
I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp
driver on an older Supermicro single CPU single core Xeon
motherboard.
[...]
Copyright (c) 1992-2013 The FreeBSD
On Sun, May 12, 2013 at 09:50:18PM -0400, Michael L. Squires wrote:
I installed RELENG_8_4 using cvsup (yes, I'm planning on updating)
and got 8.4-BETA; this had the same behavior as 8-STABLE.
Right. releng/8.4 is not exported to cvsup. Please update your tree
with svn or svnup (net/svnup
On Sat, May 11, 2013 at 10:57:44PM -0400, Michael L. Squires wrote:
I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp driver on
an older Supermicro single CPU single core Xeon motherboard.
I know that 8.3-Release does not have this issue, but don't know when in
the updates to
43 matches
Mail list logo
