> > yesterday we came across another MM related problem. This time its related
to> > the bttv-driver. We do very simple things:
>
> Do you trust your kernel build ?
Yes.
> The bt848 drivers are working beautifully
> for me in 2.4.18pre
Well, I had a quick look at the code, and it seems that vmalloc is just
failing, the source line is obvious./proc/meminfo before modprobe and xawtv:
total: used: free: shared: buffers: cached:
Mem: 1054728192 120070144 934658048 0 10420224 65257472
Swap: 1085652992 0 1085652992
MemTotal: 1030008 kB
MemFree: 912752 kB
MemShared: 0 kB
Buffers: 10176 kB
Cached: 63728 kB
SwapCached: 0 kB
Active: 26056 kB
Inactive: 73692 kB
HighTotal: 131056 kB
HighFree: 36720 kB
LowTotal: 898952 kB
LowFree: 876032 kB
SwapTotal: 1060208 kB
SwapFree: 1060208 kB
And afterwards:
total: used: free: shared: buffers: cached:
Mem: 1054728192 120537088 934191104 0 10612736 65273856
Swap: 1085652992 0 1085652992
MemTotal: 1030008 kB
MemFree: 912296 kB
MemShared: 0 kB
Buffers: 10364 kB
Cached: 63744 kB
SwapCached: 0 kB
Active: 26140 kB
Inactive: 73812 kB
HighTotal: 131056 kB
HighFree: 36608 kB
LowTotal: 898952 kB
LowFree: 875688 kB
SwapTotal: 1060208 kB
SwapFree: 1060208 kB
Can this be highmem-related?
Regards,
Stephan
-
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/