On Thu, Dec 20, 2001 at 09:25:07AM -0500, [EMAIL PROTECTED] wrote: > Ok, I changed my code to use vmalloc instead of kmalloc, which allowed > the code to proceed. My memory alloc sequence looks like this: > > alloc 0x100000 bytes > alloc 0x000140 bytes > alloc 0x000030 bytes > > The last alloc, for 0x000030 bytes, happens 39 times. Somewhere along > the line, I get the following message: (see below) > > Anybody have any clues as to what could be happening? Note that the code > in question (except for the allocs) has compiled and run succesfully on > two other operating systems. That doesn't mean that there isn't a > pointer error - but if there is, it hasn't been caught yet.
Use ksymoops to figure out where your code is oopsing. See Documentation/oops-tracing.txt for more info on doing this. But again, I don't see why you have to allocate these large amounts of memory. If you already have the data in memory, just copy it in small chunks, like the usb-serial drivers do. Or just post your code for others to take a look at. thanks, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
