[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <q2y74fd948d1004100621zfb0d7a15laa64ff4afd289fc1@mail.gmail.com>
Date: Sat, 10 Apr 2010 14:21:19 +0100
From: Pedro Ribeiro <pedrib@...il.com>
To: Daniel Mack <daniel@...aq.de>
Cc: Alan Stern <stern@...land.harvard.edu>,
Robert Hancock <hancockrwd@...il.com>,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
Greg KH <gregkh@...e.de>, alsa-devel@...a-project.org,
linux-usb@...r.kernel.org
Subject: Re: USB transfer_buffer allocations on 64bit systems
On 10 April 2010 13:49, Daniel Mack <daniel@...aq.de> wrote:
> On Fri, Apr 09, 2010 at 07:19:22PM +0100, Pedro Ribeiro wrote:
>> On 9 April 2010 19:09, Daniel Mack <daniel@...aq.de> wrote:
>> > On Fri, Apr 09, 2010 at 12:01:27PM -0400, Alan Stern wrote:
>> >> I don't see anything suspicious. The transfer_buffer addresses repeat
>> >> every 32 URBs, and the DMA addresses cycle almost entirely uniformly
>> >> from 0x20000000 to 0x23ffffff in units of 0x2000 (there are a few gaps
>> >> where the interval is a little bigger).
>> >
>> > The DMA pointers do indeed look sane. I wanted to take a deeper look at
>> > this and set up a 64bit system today. However, I fail to see the problem
>> > here. Pedro, how much RAM does your machine have installed?
>> >
>> > Daniel
>> >
>> >
>>
>> It has 4 GB.
>
> Upgraded my machine now to 4GB, but I still can't reproduce this bug.
> Pedro, can you send your config, please?
>
> Daniel
>
Here it is. It is configured for realtime and TuxOnIce patches.
However, the bug still occurs without these kernel patches.
Pedro
Download attachment ".config_2.6.33-rt-ToI" of type "application/octet-stream" (90819 bytes)
Powered by blists - more mailing lists