![]() | |||||||||||||
Messages in this thread |
On 04/08/06, Andrew Morton <akpm@osdl.org> wrote: > On Fri, 4 Aug 2006 11:04:36 +0200> "Jesper Juhl" <jesper.juhl@gmail.com> wrote: > > > On 04/08/06, Greg KH <gregkh@suse.de> wrote: > > > This is the start of the stable review cycle for the 2.6.17.8 release. > > > There are 23 patches in this series, all will be posted as a response to > > > this one. If anyone has any issues with these being applied, please let > > > us know. If anyone is a maintainer of the proper subsystem, and wants > > > to add a Signed-off-by: line to the patch, please respond with it. > > >> > > These patches are sent out with a number of different people on the Cc: > > > line. If you wish to be a reviewer, please email stable@kernel.org to > > > add your name to the list. If you want to be off the reviewer list, > > > also email us.> > >> > > Responses should be made by Sunday, August 6, 05:00:00 UTC. Anything > > > received after that time might be too late.> > >> > > I've also posted a roll-up patch with all changes in it if people want > > > to test it out. It can be found at:> > >> > > kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.17.8-rc1.gz > > > > > > > Any chance that the fixes in the (latest) e1000 driver version > > 7.1.9-k4 will get backported? > > The post-2.6.17 e1000 changes are massive. > I know, I tried backporting the new driver but gave up. > > I can't run 2.6.17.7 on at least one of my servers due to bugs in the > > driver that are fixed in the latest e1000 version.> > I looked through the -stable patches but didn't find anything that > > would fix my problem.> > I get messages along the lines of "kernel: Virtual device XXX asks to > > queue packet!" and the device then refuses to work. > > The last kernel where I know for a fact that it worked OK is 2.6.11, > > so that's what the server is currently running. > > > > Getting the fix for that problem backported to -stable would really make my day.>>> Perhaps the e1000 developers can help us to identify the particular fix for > this problem.> That's what I was hoping for... > That's assuming that it is actually fixed. Does 2.6.18-current fix the bug? > I tested 2.6.18-rc3-git3 and that did indeed fix the e1000 bug, but I can't run that kernel since xfs crashes :-( (I've send a sepperate bug report for that) -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-08-04 09:25 [from the cache] ©2003-2008 | |||||||||||||