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:	Thu, 6 Oct 2011 10:12:57 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Keith Packard <keithp@...thp.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Dave Airlie <airlied@...ux.ie>, dri-devel@...ts.freedesktop.org
Subject: Re: [PULL] drm-intel-fixes (drm/i915 driver)

On Thu, Sep 29, 2011 at 6:18 PM, Keith Packard <keithp@...thp.com> wrote:
>
> Here are three tiny patches, two new bug fixes and one regression fix
> that disables FBC on Ironlake and older chips.

So I got this error notice at bootup with the current -git tree.
Everything seems to work despite it, but I thought I'd mention it.

  [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH

This is a Lenovo X1.

                      Linus

---
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09) (prog-if
00 [VGA controller])
	Subsystem: Lenovo Device 21e8
	Flags: bus master, fast devsel, latency 0, IRQ 40
	Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 5000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
00: 86 80 26 01 07 04 90 00 09 00 00 03 00 00 00 00
10: 04 00 00 f0 00 00 00 00 0c 00 00 e0 00 00 00 00
20: 01 50 00 00 00 00 00 00 00 00 00 00 aa 17 e8 21
30: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ