Hi Tom
On Sun, Sep 8, 2013 at 11:38 AM, Tom Gundersen wrote:
> On Sun, Sep 8, 2013 at 2:13 AM, David Herrmann wrote:
>> Hi
>>
>> On Sun, Sep 8, 2013 at 1:22 AM, Tom Gundersen wrote:
>>> Hi David,
>>>
>>> On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen wrote:
On Sat, Sep 7, 2013 at 4:30
Hi Tom
On Sun, Sep 8, 2013 at 11:38 AM, Tom Gundersen t...@jklm.no wrote:
On Sun, Sep 8, 2013 at 2:13 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Sun, Sep 8, 2013 at 1:22 AM, Tom Gundersen t...@jklm.no wrote:
Hi David,
On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen t...@jklm.no
On Sun, Sep 8, 2013 at 2:13 AM, David Herrmann wrote:
> Hi
>
> On Sun, Sep 8, 2013 at 1:22 AM, Tom Gundersen wrote:
>> Hi David,
>>
>> On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen wrote:
>>> On Sat, Sep 7, 2013 at 4:30 PM, David Herrmann
>>> wrote:
Attached are two patches. The first
On Sun, Sep 8, 2013 at 2:13 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Sun, Sep 8, 2013 at 1:22 AM, Tom Gundersen t...@jklm.no wrote:
Hi David,
On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen t...@jklm.no wrote:
On Sat, Sep 7, 2013 at 4:30 PM, David Herrmann dh.herrm...@gmail.com
Hi
On Sun, Sep 8, 2013 at 1:22 AM, Tom Gundersen wrote:
> Hi David,
>
> On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen wrote:
>> On Sat, Sep 7, 2013 at 4:30 PM, David Herrmann wrote:
>>> Attached are two patches. The first one should fix this issue, the
>>> second one is the rebased
Hi David,
On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen wrote:
> On Sat, Sep 7, 2013 at 4:30 PM, David Herrmann wrote:
>> Attached are two patches. The first one should fix this issue, the
>> second one is the rebased ioremap_wc() patch from the other thread.
>>
>> Does this fix the issue (and
Hi Tom
On Sat, Sep 7, 2013 at 3:52 PM, David Herrmann wrote:
> Hi
>
> On Sat, Sep 7, 2013 at 3:45 PM, Tom Gundersen wrote:
>> On Sat, Sep 7, 2013 at 2:40 PM, David Herrmann wrote:
>>>
>>> It seems to be unrelated to the x86-sysfb changes. The WARN_ON
>>> triggered here obviously means that
Hi
On Sat, Sep 7, 2013 at 3:45 PM, Tom Gundersen wrote:
> On Sat, Sep 7, 2013 at 2:40 PM, David Herrmann wrote:
>> On Fri, Sep 6, 2013 at 2:10 PM, Tom Gundersen wrote:
>>> Hi guys,
>>>
>>> With current git (v3.11-5058-g57d7309) I get the following oops:
>>>
>>> [5.434312] [ cut
On Sat, Sep 7, 2013 at 2:40 PM, David Herrmann wrote:
> On Fri, Sep 6, 2013 at 2:10 PM, Tom Gundersen wrote:
>> Hi guys,
>>
>> With current git (v3.11-5058-g57d7309) I get the following oops:
>>
>> [5.434312] [ cut here ]
>> [5.434318] WARNING: CPU: 2 PID: 199 at
Hi
On Fri, Sep 6, 2013 at 2:10 PM, Tom Gundersen wrote:
> Hi guys,
>
> With current git (v3.11-5058-g57d7309) I get the following oops:
>
> [5.434312] [ cut here ]
> [5.434318] WARNING: CPU: 2 PID: 199 at arch/x86/mm/ioremap.c:171
> __ioremap_caller+0x2e3/0x390()
Hi
On Fri, Sep 6, 2013 at 2:10 PM, Tom Gundersen t...@jklm.no wrote:
Hi guys,
With current git (v3.11-5058-g57d7309) I get the following oops:
[5.434312] [ cut here ]
[5.434318] WARNING: CPU: 2 PID: 199 at arch/x86/mm/ioremap.c:171
On Sat, Sep 7, 2013 at 2:40 PM, David Herrmann dh.herrm...@gmail.com wrote:
On Fri, Sep 6, 2013 at 2:10 PM, Tom Gundersen t...@jklm.no wrote:
Hi guys,
With current git (v3.11-5058-g57d7309) I get the following oops:
[5.434312] [ cut here ]
[5.434318] WARNING:
Hi
On Sat, Sep 7, 2013 at 3:45 PM, Tom Gundersen t...@jklm.no wrote:
On Sat, Sep 7, 2013 at 2:40 PM, David Herrmann dh.herrm...@gmail.com wrote:
On Fri, Sep 6, 2013 at 2:10 PM, Tom Gundersen t...@jklm.no wrote:
Hi guys,
With current git (v3.11-5058-g57d7309) I get the following oops:
[
Hi Tom
On Sat, Sep 7, 2013 at 3:52 PM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Sat, Sep 7, 2013 at 3:45 PM, Tom Gundersen t...@jklm.no wrote:
On Sat, Sep 7, 2013 at 2:40 PM, David Herrmann dh.herrm...@gmail.com wrote:
It seems to be unrelated to the x86-sysfb changes. The WARN_ON
Hi David,
On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen t...@jklm.no wrote:
On Sat, Sep 7, 2013 at 4:30 PM, David Herrmann dh.herrm...@gmail.com wrote:
Attached are two patches. The first one should fix this issue, the
second one is the rebased ioremap_wc() patch from the other thread.
Does
Hi
On Sun, Sep 8, 2013 at 1:22 AM, Tom Gundersen t...@jklm.no wrote:
Hi David,
On Sat, Sep 7, 2013 at 11:57 PM, Tom Gundersen t...@jklm.no wrote:
On Sat, Sep 7, 2013 at 4:30 PM, David Herrmann dh.herrm...@gmail.com wrote:
Attached are two patches. The first one should fix this issue, the
Hi guys,
With current git (v3.11-5058-g57d7309) I get the following oops:
[5.434312] [ cut here ]
[5.434318] WARNING: CPU: 2 PID: 199 at arch/x86/mm/ioremap.c:171
__ioremap_caller+0x2e3/0x390()
[5.434321] Info: mapping multiple BARs. Your kernel is fine.
[
Hi guys,
With current git (v3.11-5058-g57d7309) I get the following oops:
[5.434312] [ cut here ]
[5.434318] WARNING: CPU: 2 PID: 199 at arch/x86/mm/ioremap.c:171
__ioremap_caller+0x2e3/0x390()
[5.434321] Info: mapping multiple BARs. Your kernel is fine.
[
18 matches
Mail list logo
