On Sun, 17 Dec 2006 17:15:47 +0300
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 29, 2006 at 08:29:48AM +0300, Evgeniy Polyakov ([EMAIL
> PROTECTED]) wrote:
> > > > > > > > > > > Here is link to discussion:
> > > > > > > > > > > http://marc.theaimsgroup.com/?l=linux-netdev&m=116227512
On Mon, Dec 18, 2006 at 09:17:28AM -0800, Stephen Hemminger ([EMAIL PROTECTED])
wrote:
> > Bug with freeze also exists in 2.6.18-3 (package version 2.6.18-7) - no
> > messages in dmesg, no interrupts.
> > It is dual lan board with only one port being used.
> > rmmod/modprobe sequence brings NIC ba
On Wed, Nov 29, 2006 at 08:29:48AM +0300, Evgeniy Polyakov ([EMAIL PROTECTED])
wrote:
> > > > > > > > > > Here is link to discussion:
> > > > > > > > > > http://marc.theaimsgroup.com/?l=linux-netdev&m=116227512815783&w=2
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > can you try the lin
On Sat, Nov 18, 2006 at 02:25:27PM +0300, Evgeniy Polyakov ([EMAIL PROTECTED])
wrote:
> On Sat, Nov 18, 2006 at 12:21:34PM +0100, maximilian attems ([EMAIL
> PROTECTED]) wrote:
> > > > > > > > > Bug was filled against 2.6.17-9, but was fixed in recent git
> > > > > > > > > (2.6.19-rc3), probably
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Followup-For: Bug #396185
Bug was filled against 2.6.17-9, but was fixed in recent git (2.6.19-rc3),
probably also
fixed in 2.6.18.1
Here is link to discussion:
http://marc.theaimsgroup.com/?l=linux-netdev&m=116227512815783&w=2
-- System Infor
On Tue, Oct 31, 2006 at 10:30:30AM +0300, Evgeniy Polyakov wrote:
> Package: linux-image-2.6.17-2-686
> Version: 2.6.17-9
> Followup-For: Bug #396185
>
> Bug was filled against 2.6.17-9, but was fixed in recent git (2.6.19-rc3),
> probably also
> fixed in 2.6.18.1
>
> Here is link to discussion:
On Tue, Oct 31, 2006 at 10:34:55AM +0100, maximilian attems ([EMAIL PROTECTED])
wrote:
> On Tue, Oct 31, 2006 at 12:30:55PM +0300, Evgeniy Polyakov wrote:
> > On Tue, Oct 31, 2006 at 09:57:16AM +0100, maximilian attems ([EMAIL
> > PROTECTED]) wrote:
> > > On Tue, Oct 31, 2006 at 10:30:30AM +0300,
On Tue, Oct 31, 2006 at 12:30:55PM +0300, Evgeniy Polyakov wrote:
> On Tue, Oct 31, 2006 at 09:57:16AM +0100, maximilian attems ([EMAIL
> PROTECTED]) wrote:
> > On Tue, Oct 31, 2006 at 10:30:30AM +0300, Evgeniy Polyakov wrote:
> > > Package: linux-image-2.6.17-2-686
> > > Version: 2.6.17-9
> > > F
On Tue, Oct 31, 2006 at 09:57:16AM +0100, maximilian attems ([EMAIL PROTECTED])
wrote:
> On Tue, Oct 31, 2006 at 10:30:30AM +0300, Evgeniy Polyakov wrote:
> > Package: linux-image-2.6.17-2-686
> > Version: 2.6.17-9
> > Followup-For: Bug #396185
> >
> > Bug was filled against 2.6.17-9, but was fix
On Tue, Oct 31, 2006 at 12:44:25PM +0300, Evgeniy Polyakov wrote:
>
> I'm installing it right now, although package is called 2.6.18-1, but
> actual version is 2.6.18-3, so if it was based on 2.6.18.2+ then bug
> should be fixed. I will add more details if this situation appeares
> again, since I
On Thu, 16 Nov 2006 20:35:32 +0300
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 31, 2006 at 12:44:25PM +0300, Evgeniy Polyakov ([EMAIL
> PROTECTED]) wrote:
> > > > > > Bug was filled against 2.6.17-9, but was fixed in recent git
> > > > > > (2.6.19-rc3), probably also
> > > > > > fi
On Thu, Nov 16, 2006 at 09:38:21AM -0800, Stephen Hemminger ([EMAIL PROTECTED])
wrote:
> Please retest with 2.76.18.2 or 2.6.19-rc6, there were some fixes
> already there.
I will install that kernel, but I can not test it right now.
If there will be any problem I will report it.
Thank you.
> --
On Sat, Nov 18, 2006 at 12:21:34PM +0100, maximilian attems ([EMAIL PROTECTED])
wrote:
> > > > > > > > Bug was filled against 2.6.17-9, but was fixed in recent git
> > > > > > > > (2.6.19-rc3), probably also
> > > > > > > > fixed in 2.6.18.1
> > > > > > > >
> > > > > > > > Here is link to discus
On Thu, 16 Nov 2006, Stephen Hemminger wrote:
> On Thu, 16 Nov 2006 20:35:32 +0300
> Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> > On Tue, Oct 31, 2006 at 12:44:25PM +0300, Evgeniy Polyakov ([EMAIL
> > PROTECTED]) wrote:
> > > > > > > Bug was filled against 2.6.17-9, but was fixed in recent
14 matches
Mail list logo