Re: CURRENT: re(4) crashing system

2016-11-20 Thread O. Hartmann
Am Sun, 20 Nov 2016 16:43:52 +0900 YongHyeon PYUN schrieb: > On Sat, Nov 19, 2016 at 07:44:35PM +0100, O. Hartmann wrote: > > Am Mon, 7 Nov 2016 11:16:23 +0900 > > YongHyeon PYUN schrieb: > > > > > On Sun, Nov 06, 2016 at 01:20:36PM +0100, Hartmann, O. wrote: > > > > On Mon, 31 Oct 2016 11:

Re: CURRENT: re(4) crashing system

2016-11-19 Thread YongHyeon PYUN
On Sat, Nov 19, 2016 at 07:44:35PM +0100, O. Hartmann wrote: > Am Mon, 7 Nov 2016 11:16:23 +0900 > YongHyeon PYUN schrieb: > > > On Sun, Nov 06, 2016 at 01:20:36PM +0100, Hartmann, O. wrote: > > > On Mon, 31 Oct 2016 11:12:22 +0900 > > > YongHyeon PYUN wrote: > > > > > > > On Fri, Oct 28, 201

Re: CURRENT: re(4) crashing system

2016-11-19 Thread O. Hartmann
Am Mon, 7 Nov 2016 11:16:23 +0900 YongHyeon PYUN schrieb: > On Sun, Nov 06, 2016 at 01:20:36PM +0100, Hartmann, O. wrote: > > On Mon, 31 Oct 2016 11:12:22 +0900 > > YongHyeon PYUN wrote: > > > > > On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > > > > On Thu, 27 Oct 2016 10:0

Re: CURRENT: re(4) crashing system

2016-11-06 Thread YongHyeon PYUN
On Sun, Nov 06, 2016 at 01:20:36PM +0100, Hartmann, O. wrote: > On Mon, 31 Oct 2016 11:12:22 +0900 > YongHyeon PYUN wrote: > > > On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > > > On Thu, 27 Oct 2016 10:00:04 +0900 > > > YongHyeon PYUN wrote: > > > > > > > On Tue, Oct 25, 201

Re: CURRENT: re(4) crashing system

2016-11-06 Thread Hartmann, O.
On Mon, 31 Oct 2016 11:12:22 +0900 YongHyeon PYUN wrote: > On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > > On Thu, 27 Oct 2016 10:00:04 +0900 > > YongHyeon PYUN wrote: > > > > > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > > > On Tue, 25 Oct 2016 11:05

Re: CURRENT: re(4) crashing system

2016-11-03 Thread O. Hartmann
Am Mon, 31 Oct 2016 11:12:22 +0900 YongHyeon PYUN schrieb: > On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > > On Thu, 27 Oct 2016 10:00:04 +0900 > > YongHyeon PYUN wrote: > > > > > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > > > On Tue, 25 Oct 2016 11:

Re: CURRENT: re(4) crashing system

2016-10-30 Thread YongHyeon PYUN
On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > On Thu, 27 Oct 2016 10:00:04 +0900 > YongHyeon PYUN wrote: > > > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > > On Tue, 25 Oct 2016 11:05:38 +0900 > > > YongHyeon PYUN wrote: > > > > > > > [...] > > > > > >

Re: CURRENT: re(4) crashing system

2016-10-28 Thread Hartmann, O.
On Thu, 27 Oct 2016 10:00:04 +0900 YongHyeon PYUN wrote: > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > On Tue, 25 Oct 2016 11:05:38 +0900 > > YongHyeon PYUN wrote: > > > > [...] > > > > I'm not sure but it's likely the issue is related with EEE/Green > > > Ethernet han

Re: CURRENT: re(4) crashing system

2016-10-27 Thread O. Hartmann
Am Thu, 27 Oct 2016 10:00:04 +0900 YongHyeon PYUN schrieb: > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > On Tue, 25 Oct 2016 11:05:38 +0900 > > YongHyeon PYUN wrote: > > > > [...] > > > > I'm not sure but it's likely the issue is related with EEE/Green > > > Ethernet h

Re: CURRENT: re(4) crashing system

2016-10-26 Thread YongHyeon PYUN
On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > On Tue, 25 Oct 2016 11:05:38 +0900 > YongHyeon PYUN wrote: > [...] > > I'm not sure but it's likely the issue is related with EEE/Green > > Ethernet handling. EEE is negotiated feature with link partner. If > > you directly connect

Re: CURRENT: re(4) crashing system

2016-10-24 Thread Hartmann, O.
On Tue, 25 Oct 2016 11:05:38 +0900 YongHyeon PYUN wrote: > On Mon, Oct 24, 2016 at 02:03:37PM +0200, O. Hartmann wrote: > > On Mon, 24 Oct 2016 14:14:00 +0900 > > YongHyeon PYUN wrote: > > > > > On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote: > > > > I tried to report earlier

Re: CURRENT: re(4) crashing system

2016-10-24 Thread YongHyeon PYUN
On Mon, Oct 24, 2016 at 02:03:37PM +0200, O. Hartmann wrote: > On Mon, 24 Oct 2016 14:14:00 +0900 > YongHyeon PYUN wrote: > > > On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote: > > > I tried to report earlier here that CURRENT does have some serious > > > problems right now and one o

Re: CURRENT: re(4) crashing system

2016-10-24 Thread O. Hartmann
On Mon, 24 Oct 2016 14:14:00 +0900 YongHyeon PYUN wrote: > On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote: > > I tried to report earlier here that CURRENT does have some serious > > problems right now and one of those problems seems to be triggered by > > the recent re(4) driver. Th

Re: CURRENT: re(4) crashing system

2016-10-23 Thread YongHyeon PYUN
On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote: > I tried to report earlier here that CURRENT does have some serious > problems right now and one of those problems seems to be triggered by > the recent re(4) driver. The problem is also present in recen 11-STABLE! > > Below, you'll fi

CURRENT: re(4) crashing system

2016-10-23 Thread Hartmann, O.
I tried to report earlier here that CURRENT does have some serious problems right now and one of those problems seems to be triggered by the recent re(4) driver. The problem is also present in recen 11-STABLE! Below, you'll find pciconf-output reagrding the device on a Lenovo E540 Laptop I can tes