On Monday 09 March 2009 21:00:20 ian j hart wrote:
On Monday 09 March 2009 06:08:41 Pyun YongHyeon wrote:
On Sun, Mar 08, 2009 at 05:05:12PM +, ian j hart wrote:
On Sunday 08 March 2009 02:36:42 Pyun YongHyeon wrote:
On Sat, Mar 07, 2009 at 05:17:57PM +, ian j hart wrote:
On
On Mon, Mar 09, 2009 at 02:51:41PM +1000, Gavin Stone-Tolcher wrote:
Have you tried re(4) in HEAD?
I had one report that re(4) in HEAD still does not fix the issue so
I posted a possible workaround for that. Unfortunately he didn't
report back so I don't know whether it was right
On Sun, Mar 08, 2009 at 05:05:12PM +, ian j hart wrote:
On Sunday 08 March 2009 02:36:42 Pyun YongHyeon wrote:
On Sat, Mar 07, 2009 at 05:17:57PM +, ian j hart wrote:
On Tuesday 20 January 2009 02:45:19 Pyun YongHyeon wrote:
On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim
On Mon, Mar 09, 2009 at 03:03:46PM +0900, Pyun YongHyeon wrote:
...
Thanks a lot! This is the report I had been waiting for. I've
committed the patch to HEAD(r189555).
As long as you're thinking about the re/rl driver, I have been
meaning to report to you that the patch you've posted for
On Sun, Mar 08, 2009 at 08:41:45PM -1000, Clifton Royston wrote:
On Mon, Mar 09, 2009 at 03:03:46PM +0900, Pyun YongHyeon wrote:
...
Thanks a lot! This is the report I had been waiting for. I've
committed the patch to HEAD(r189555).
As long as you're thinking about the re/rl driver, I
On Sun, 8 Mar 2009 11:36:42 +0900 Pyun YongHyeon pyu...@gmail.com wrote
about Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers:
PY Have you tried re(4) in HEAD?
PY I had one report that re(4) in HEAD still does not fix the issue so
PY I posted a possible workaround
On Mon, 9 Mar 2009 14:51:41 +1000 Gavin Stone-Tolcher
g.stone-tolc...@its.uq.edu.au wrote about RE: FreeBSD 7.1 Breaks re and
rl Network Interface Drivers:
GST Hi, Just some more feedback on your patch.
GST I have a Jetway J7F4K1G2E board with dual embedded
GST RealteK RTL8110SC. I tried using
On Mon, Mar 09, 2009 at 09:21:31AM +0100, Gerrit K?hn wrote:
On Sun, 8 Mar 2009 11:36:42 +0900 Pyun YongHyeon pyu...@gmail.com wrote
about Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers:
PY Have you tried re(4) in HEAD?
PY I had one report that re(4) in HEAD still does not fix
Pyun YongHyeon wrote:
Thanks a lot! This is the report I had been waiting for. I've
committed the patch to HEAD(r189555).
Hi,
with the files in HEAD i could also fix the occasional:
re0: watchdog timeout (missed Tx interrupts) -- recovering
on a rented server. Any chance this will be
On Monday 09 March 2009 06:08:41 Pyun YongHyeon wrote:
On Sun, Mar 08, 2009 at 05:05:12PM +, ian j hart wrote:
On Sunday 08 March 2009 02:36:42 Pyun YongHyeon wrote:
On Sat, Mar 07, 2009 at 05:17:57PM +, ian j hart wrote:
On Tuesday 20 January 2009 02:45:19 Pyun YongHyeon wrote:
On Sunday 08 March 2009 02:36:42 Pyun YongHyeon wrote:
On Sat, Mar 07, 2009 at 05:17:57PM +, ian j hart wrote:
On Tuesday 20 January 2009 02:45:19 Pyun YongHyeon wrote:
On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim wrote:
On Monday 19 January 2009 04:33 pm, Jung-uk Kim
Have you tried re(4) in HEAD?
I had one report that re(4) in HEAD still does not fix the issue so
I posted a possible workaround for that. Unfortunately he didn't
report back so I don't know whether it was right workaround or not.
If re(4) in HEAD does not fix the issue, would you try
On Tuesday 20 January 2009 02:45:19 Pyun YongHyeon wrote:
On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim wrote:
On Monday 19 January 2009 04:33 pm, Jung-uk Kim wrote:
I found something interesting. I have another RTL8169SC that works
perfectly fine without the patch. The
On Sat, Mar 07, 2009 at 05:17:57PM +, ian j hart wrote:
On Tuesday 20 January 2009 02:45:19 Pyun YongHyeon wrote:
On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim wrote:
On Monday 19 January 2009 04:33 pm, Jung-uk Kim wrote:
I found something interesting. I have another
Pyun YongHyeon pisze:
On Wed, Jan 14, 2009 at 03:18:16PM +0100, Bartosz Stec wrote:
Walter Venable pisze:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER
On Mon, Jan 19, 2009 at 09:31:36AM +0100, Bartosz Stec wrote:
Pyun YongHyeon pisze:
On Wed, Jan 14, 2009 at 03:18:16PM +0100, Bartosz Stec wrote:
Walter Venable pisze:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at
Pyun YongHyeon wrote:
On Tue, Jan 13, 2009 at 03:53:59PM +0100, Sascha Holzleiter wrote:
Jung-uk Kim wrote:
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Hi,
i see similar problems with a re card:
r...@pci0:4:7:0: class=0x02 card=0x816710ec chip=0x816710ec
On Friday 16 January 2009 11:47 pm, Pyun YongHyeon wrote:
On Tue, Jan 13, 2009 at 03:53:59PM +0100, Sascha Holzleiter wrote:
Jung-uk Kim wrote:
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Hi,
i see similar problems with a re card:
r...@pci0:4:7:0:
On Monday 19 January 2009 04:33 pm, Jung-uk Kim wrote:
I found something interesting. I have another RTL8169SC that works
perfectly fine without the patch. The hardware revision is
0x1800. After reading Linux driver (drivers/net/r8169c), I
realised they use different masks for hardware
On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim wrote:
On Monday 19 January 2009 04:33 pm, Jung-uk Kim wrote:
I found something interesting. I have another RTL8169SC that works
perfectly fine without the patch. The hardware revision is
0x1800. After reading Linux driver
On Sat, Jan 17, 2009 at 06:04:37PM +0100, Dimitry Andric wrote:
On 2009-01-17 05:54, Pyun YongHyeon wrote:
I think the initial setup time issue of 8169SC is different one.
Did re(4) of 7.0-RELEASE also have the same issue?
Sometimes, and sometimes not. :) It was flaky, to say the
Pyun YongHyeon wrote:
On Tue, Jan 13, 2009 at 03:53:59PM +0100, Sascha Holzleiter wrote:
Jung-uk Kim wrote:
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Hi,
i see similar problems with a re card:
r...@pci0:4:7:0: class=0x02 card=0x816710ec chip=0x816710ec
On 2009-01-17 05:54, Pyun YongHyeon wrote:
I think the initial setup time issue of 8169SC is different one.
Did re(4) of 7.0-RELEASE also have the same issue?
Sometimes, and sometimes not. :) It was flaky, to say the least...
Also would you try attached patch? It doesn't fix initial setup
On Wed, Jan 14, 2009 at 03:18:16PM +0100, Bartosz Stec wrote:
Walter Venable pisze:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE
On Tue, Jan 13, 2009 at 03:53:59PM +0100, Sascha Holzleiter wrote:
Jung-uk Kim wrote:
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Hi,
i see similar problems with a re card:
r...@pci0:4:7:0: class=0x02 card=0x816710ec chip=0x816710ec
rev=0x10 hdr=0x00
On Thu, Jan 15, 2009 at 09:10:11PM +0100, Dimitry Andric wrote:
On 2009-01-14 00:05, Jung-uk Kim wrote:
Can you try one of the following patches?
-CURRENT: http://people.freebsd.org/~jkim/re/re.current.diff
-STABLE: http://people.freebsd.org/~jkim/re/re.stable.diff
These
On 2009-01-14 00:05, Jung-uk Kim wrote:
Can you try one of the following patches?
-CURRENT: http://people.freebsd.org/~jkim/re/re.current.diff
-STABLE: http://people.freebsd.org/~jkim/re/re.stable.diff
These patches contain all patches suggested by me and yongari and an
Walter Venable pisze:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE make installworld. I think
this implies it's a kernel driver issue.
I'm on 7.1-RELEASE/amd64 with the following card:
r...@pci0:2:0:0: class=0x02 card=0x368c1462 chip=0x816810ec rev=0x01
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
class = network
subclass = ethernet
And luckey
On Tue, Jan 13, 2009 at 08:59:41AM +, Oliver Peter wrote:
I'm on 7.1-RELEASE/amd64 with the following card:
r...@pci0:2:0:0: class=0x02 card=0x368c1462 chip=0x816810ec rev=0x01
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit
Jung-uk Kim wrote:
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Hi,
i see similar problems with a re card:
r...@pci0:4:7:0:class=0x02 card=0x816710ec chip=0x816710ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169/8110 Family
Pyun YongHyeon a écrit :
On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is
On 2009-01-13 06:02, Pyun YongHyeon wrote:
I'm also having problems with re's, in my case the interfaces take about
10 seconds to come up, if they come up at all. After the interfaces are
up, half the time no packets go out at all. Usually it helps to bring
them down via the console,
On Tuesday 13 January 2009 10:27 am, Dimitry Andric wrote:
Reverting r180519 seems to solve the problem of not being able to
send any packets. It does not solve the other problem, which is
that the interfaces can take a very long time to come up at boot
time, e.g:
Setting hostuuid:
On Tue, Jan 13, 2009 at 10:17:54AM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009,
Pyun YongHyeon a écrit :
On Tue, Jan 13, 2009 at 10:17:54AM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
On 2009-01-12 07:41, Pyun YongHyeon wrote:
I see, Unfortunately the issue was fixed in the end of 7.1-R
release process so I wanted to get more exposure before MFC.
I'll make sure to MFC to stable/7 after more testing.
I'm also having problems with re's, in my case the interfaces take about
10
Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE make installworld. I think
this implies it's a kernel driver issue.
Pyun,
I was able to perform a full source downgrade to 7.0 and all the
problems went away. Curiously, re0 and re1 have reversed names --
what was re0 is now re1, and vice versa. I need my box to be up and
working so I can't throw 7.1 on it again. If I can offer any data
from 7.0, please let me
Pyun YongHyeon a écrit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
WV problems. I believe this roundly confirms that this is
On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is 7.0-RELEASE-p7 completely
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE
On Mon, Jan 12, 2009 at 05:37:39PM +0100, Dimitry Andric wrote:
On 2009-01-12 07:41, Pyun YongHyeon wrote:
I see, Unfortunately the issue was fixed in the end of 7.1-R
release process so I wanted to get more exposure before MFC.
I'll make sure to MFC to stable/7 after more testing.
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
WV problems. I believe this roundly confirms that this is a bug in the
WV 7.1-RELEASE re kernel drivers.
Does kern/130011 look similar?
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
WV problems. I believe this roundly confirms that this is a bug in the
WV
On Mon, Jan 12, 2009 at 09:32:20AM +0300, eug...@donpac.ru wrote:
EG Does kern/130011 look similar?
EG http://www.freebsd.org/cgi/query-pr.cgi?pr=130011
Do you have RTL8168C controller? If not, it's not related with
Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C.
EG Does kern/130011 look similar?
EG http://www.freebsd.org/cgi/query-pr.cgi?pr=130011
Do you have RTL8168C controller? If not, it's not related with
Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C.
Look into kern/130011. As far as I can see I do have RTL8168C.
EG The re
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE make installworld. I think
this implies it's a kernel driver issue.
On Wed, 2009-01-07 at 09:39 -0500, Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE make installworld. I think
this
On Wed, Jan 7, 2009 at 1:34 PM, Brian Duke br...@box201.com wrote:
Walter,
I too have these two interfaces and was forced to disconnect my rl0 in order
for my static ip on re0 to route correctly. If both interfaces are up on the
same network even if both are different IPs all routing stopped.
I was on cvsup tag RELENG_7_0 and I upgraded to RELENG_7_1. All that
and more details are in the URL I provided.
On Wed, Jan 7, 2009 at 11:47 AM, Gavin Atkinson ga...@freebsd.org wrote:
On Wed, 2009-01-07 at 09:39 -0500, Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access,
Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
problems. I believe this roundly confirms that this is a bug in the
7.1-RELEASE re kernel drivers.
On Wed, Jan 7, 2009 at 9:39 AM, Walter Venable w...@relnor.com wrote:
FreeBSD 7.1 upgrade broke my network access, machine is
On Wed, Jan 07, 2009 at 06:50:40PM -0500, Walter Venable wrote:
Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
problems. I believe this roundly confirms that this is a bug in the
7.1-RELEASE re kernel drivers.
Please show me full dmesg output.
On Wed, Jan 7,
On Wed, Jan 07, 2009 at 09:39:32AM -0500, Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE make installworld. I
On Wed, Jan 7, 2009 at 8:50 PM, Pyun YongHyeon pyu...@gmail.com wrote:
Please show me full dmesg output.
Hi Pyun,
I have attached the full dmesg output.
dmesg
Description: Binary data
___
freebsd-stable@freebsd.org mailing list
On Wed, Jan 07, 2009 at 09:20:05PM -0500, Walter Venable wrote:
On Wed, Jan 7, 2009 at 8:50 PM, Pyun YongHyeon pyu...@gmail.com wrote:
Please show me full dmesg output.
Hi Pyun,
I have attached the full dmesg output.
Walter, I need dmesg output of 7.1-RELEASE.
--
Regards,
Pyun
56 matches
Mail list logo
