On Wed, May 02, 2007 at 11:35:32AM +0200, Andi Kleen wrote:
>
> > Looks like you hit:
> > BUG_ON(flags & ~(GFP_DMA | GFP_LEVEL_MASK | __GFP_NO_GROW));
> >
> > I guess this was due to the vmalloc_32() change now passing in
> > GFP_DMA32. Looks like that could be a problem with the
> > x86_64-m
On Wed, May 02, 2007 at 11:35:32AM +0200, Andi Kleen wrote:
> Does this patch help?
So far so good :-)
Thank you very much.
> Index: linux/mm/vmalloc.c
> ===
> --- linux.orig/mm/vmalloc.c
> +++ linux/mm/vmalloc.c
> @@ -431,7 +431,7
> Looks like you hit:
> BUG_ON(flags & ~(GFP_DMA | GFP_LEVEL_MASK | __GFP_NO_GROW));
>
> I guess this was due to the vmalloc_32() change now passing in
> GFP_DMA32. Looks like that could be a problem with the
> x86_64-mm-vmalloc-32 patch. Andi?
Does this patch help?
Index: linux/mm/vmallo
On Tue, 2007-05-01 at 11:41 +0200, Gregoire Favre wrote:
> Hello again,
>
> just forgot this :
>
> ksymoops 2.4.11 on x86_64 2.6.21. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.6.21/ (default)
> -m /usr/src/linu
On Tue, May 01, 2007 at 05:58:42PM +0200, Oliver Endriss wrote:
> Has anyone a problem with this patch?
> If not I'll apply it tomorrow...
The patch seems fine, but incomplete : it allows budget-ci to work, but
don't allow cx88 cards to works.
--
Grégoire FAVRE http://gregoire.favre.googlepages
Jon Burgess wrote:
> It appears the problem is that the driver is using streamed PCI and
> needs to explicitly sync the data otherwise it breaks when the SWIOTLB
> is in use. A call to pci_unmap_sg() was missing too.
>
> This patch is against the current v4l-dvb HG tree.
>
> I've only tested the
Hello again,
just forgot this :
ksymoops 2.4.11 on x86_64 2.6.21. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.21/ (default)
-m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol inf
On Mon, Apr 30, 2007 at 07:05:16PM +0100, Jon Burgess wrote:
> I'm currently using 2.6.21 + x86_64-mm-vmalloc-32.patch with the v4l-dvb
> drivers. I need to use the v4l-dvb tree in order to get the IR remote
> working reliably. This combination compiles and works OK for me.
You are lucky :)
They
On Mon, 2007-04-30 at 18:52 +0200, Gregoire Favre wrote:
> On Sat, Apr 28, 2007 at 09:14:37PM +0100, Jon Burgess wrote:
>
> > While the above patch works, it seems the underlying causes is that
> > vmalloc_32() is providing memory above 4Gb on x86-64 which is not what
> > the driver expects. This
On Sat, Apr 28, 2007 at 09:14:37PM +0100, Jon Burgess wrote:
> While the above patch works, it seems the underlying causes is that
> vmalloc_32() is providing memory above 4Gb on x86-64 which is not what
> the driver expects. This same issue came up a few weeks ago with regards
> to DRM on radeon
Jon Burgess wrote:
> On Sat, 2007-04-28 at 18:17 +0100, Jon Burgess wrote:
> > On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> > > On 4/27/07, Jon Burgess <[EMAIL PROTECTED]> wrote:
> > > > Interesting - I see similar symptoms after upgrading my PC:
> > > > * old PC was AMD Athlon 64 3000 w/
On Sat, Apr 28, 2007 at 09:14:37PM +0100, Jon Burgess wrote:
> While the above patch works, it seems the underlying causes is that
> vmalloc_32() is providing memory above 4Gb on x86-64 which is not what
> the driver expects. This same issue came up a few weeks ago with regards
> to DRM on radeon
On Sat, 2007-04-28 at 18:17 +0100, Jon Burgess wrote:
> On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> > On 4/27/07, Jon Burgess <[EMAIL PROTECTED]> wrote:
> > > Interesting - I see similar symptoms after upgrading my PC:
> > > * old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issu
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> On 4/27/07, Jon Burgess <[EMAIL PROTECTED]> wrote:
> > Interesting - I see similar symptoms after upgrading my PC:
> > * old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
> > * new PC is a Intel Core 2 Duo w/ 4GB of RAM and fails
14 matches
Mail list logo
