linux-kernel - Re: [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 22 Jan 2011 11:18:53 +0000
From:	Chris Clayton <chris2553@...glemail.com>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/i915: Increase the amount of defense before computing vblank timestamps

On Saturday 22 January 2011, Chris Wilson wrote:
> Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
> ---
>
> Chris, does this help?
>

Sorry Chris, X still doesn't start with this patch applied. The symptoms are 
slightly different in that the monitor doesn't go into power saving mode, but 
the screen is still black and I have to recycle the power to get the machine 
back.
The messages in the log file has changed though.We now have:

Jan 22 11:03:47 upstairs kernel: r8169 0000:02:00.0: eth0: link up
Jan 22 11:03:57 upstairs kernel: [drm] Initialized drm 1.1.0 20060810
Jan 22 11:03:58 upstairs kernel: pci 0000:00:02.0: PCI INT A -> GSI 16 (level, 
low) -> IRQ 16
Jan 22 11:03:58 upstairs kernel: pci 0000:00:02.0: setting latency timer to 64
Jan 22 11:03:58 upstairs kernel: ioremap error for 0xbdce0000-0xbdce3000, 
requested 0x10, got 0x0
Jan 22 11:03:58 upstairs kernel: [drm] Supports vblank timestamp caching Rev 1 
(10.10.2010).
Jan 22 11:03:58 upstairs kernel: [drm] Driver supports precise vblank timestamp 
query.
Jan 22 11:03:58 upstairs kernel: [drm] Initialized i915 1.6.0 20080730 for 
0000:00:02.0 on minor 0
Jan 22 11:04:18 upstairs kernel: [drm:i915_get_vblank_timestamp] *ERROR* Invalid 
crtc 0
Jan 22 11:04:18 upstairs last message repeated 8 times
Jan 22 11:04:18 upstairs kernel: [drm:i915_do_wait_request] *ERROR* something 
(likely vbetool) disabled interrupts, re-enabling
Jan 22 11:04:21 upstairs kernel: [drm:i915_get_vblank_timestamp] *ERROR* Invalid 
crtc 0
Jan 22 11:04:29 upstairs last message repeated 35 times
Jan 22 11:04:29 upstairs kernel: [drm:i915_do_wait_request] *ERROR* something 
(likely vbetool) disabled interrupts, re-enabling
Jan 22 11:04:32 upstairs kernel: [drm:i915_get_vblank_timestamp] *ERROR* Invalid 
crtc 0
Jan 22 11:05:00 upstairs last message repeated 98 times
Jan 22 11:05:00 upstairs kernel: [drm:i915_do_wait_request] *ERROR* something 
(likely vbetool) disabled interrupts, re-enabling
Jan 22 11:05:03 upstairs kernel: [drm:i915_get_vblank_timestamp] *ERROR* Invalid 
crtc 0
Jan 22 11:05:06 upstairs last message repeated 17 times
Jan 22 11:05:06 upstairs kernel: [drm:i915_do_wait_request] *ERROR* something 
(likely vbetool) disabled interrupts, re-enabling

> If you can convert the address to a line number that would pinpoint the

Not done that before and nothing jumped out of my search on google, so how do I 
go about getting the line number for you, please?

> NULL pointer exactly. Though judging by the address and position of the
> dereference a NULL crtc looks most likely.

<snip>

-- 
The more I see, the more I know. The more I know, the less I understand. 
Changing Man - Paul Weller
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/