On Thu, Apr 26, 2018 at 06:25:13PM +0300, Ville Syrjälä wrote:
> On Thu, Apr 26, 2018 at 06:16:41PM +0300, Ville Syrjälä wrote:
> > On Thu, Apr 26, 2018 at 05:56:14PM +0300, Ville Syrjälä wrote:
> > > On Thu, Apr 26, 2018 at 10:27:19AM -0400, Dave Jones wrote:
>
On Thu, Apr 26, 2018 at 04:10:45PM +0300, Ville Syrjälä wrote:
> On Mon, Apr 23, 2018 at 11:27:13AM -0400, Dave Jones wrote:
> > This warning just started appearing during boot on a machine I upgraded
> > to 4.17-rc2. The warning seems to have been there since 2015, but it
This warning just started appearing during boot on a machine I upgraded
to 4.17-rc2. The warning seems to have been there since 2015, but it
has never triggered before today.
Dave
[1.158500] fb: switching to inteldrmfb from EFI VGA
[1.159073] Console: switching to colour dummy de
On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
> On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
> > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
> > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
> > > their recent patches.
>
On Mon, Sep 07, 2015 at 02:45:59PM -0400, Dave Jones wrote:
> On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
> >
> > Hi Linus,
> >
> > This is the main pull request for the drm for 4.3. Nouveau is probably
> the biggest
> > amount
On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
>
> Hi Linus,
>
> This is the main pull request for the drm for 4.3. Nouveau is probably the
> biggest
> amount of changes in here, since it missed 4.2. Highlights below, along with
> the usual
> bunch of fixes. There are a fe
I finally got around to playing with kasan. It didn't end well.
I added some debugging to validate_cmds_sorted to print out the table
sizes right before the stack traces.
Dave
validate_cmds_sorted: table:a1fb4220 cmd_table_count:3
validate_cmds_sorted: table:a1fb4220 tabl
On Wed, Mar 25, 2015 at 09:56:28AM +0100, Daniel Vetter wrote:
> > I've started seeing this one too as of rc5.
> > Along with..
>
> Yeah we're freeing memory too early with these bugs. To get up to the
> current debug state can you please cherry-pick
>
> commit f55548b5af87ebfc586ca757489
On Mon, Mar 23, 2015 at 11:33:42AM -0400, Josh Boyer wrote:
> I have a machine that no longer boots in a headless manner with -rc5.
> It's an Celeron based NUC device. I blacklisted the i915 driver and
> it boots fine, then I ran insmod manually and got the backtrace below.
> This machine on
Just hit this while fuzz-testing, (curiously, no graphics
related stuff was happening, X isn't even loaded on that box).
dmar: DRHD: handling fault status reg 2
dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7ff000
DMAR:[fault reason 05] PTE Write access is not set
00:02:0 is..
On Thu, Jan 30, 2014 at 05:58:38PM +0100, Daniel Vetter wrote:
> This regression has been introduced in
>
> commit b3f2333de8e81b089262b26d52272911523e605f
> Author: Daniel Vetter
> Date: Wed Dec 11 11:34:31 2013 +0100
>
> drm: restrict the device list for shadow attached drivers
>
I left this on overnight, and this morning this was in the log.
Dave
WARNING: CPU: 1 PID: 131 at drivers/gpu/drm/i915/intel_display.c:6309
hsw_enable_pc8_work+0x6a9/0x6d0()
Power well on
Modules linked in: tun hidp bnep rfcomm can_raw can_bcm caif_socket caif phonet
af_rxrpc bluetooth c
On Wed, May 22, 2013 at 01:10:36AM +0200, Daniel Vetter wrote:
> On Wed, May 22, 2013 at 1:01 AM, Dave Jones wrote:
> > This is new to me as of 3.10-rc2.
>
> If this is an ironlake with a DP output it's a know issue which seems
> to pop up every once in a while.
This is new to me as of 3.10-rc2.
WARNING: at drivers/gpu/drm/i915/intel_display.c:997
intel_wait_for_pipe_off+0x194/0x1a0 [i915]()
pipe_off wait timed out
Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_LOG
xt_limit ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filt
On Sun, Mar 17, 2013 at 08:50:03PM +0100, Daniel Vetter wrote:
> Doesn't that mean that we need these checks everywhere? Or at least a
> fixup in drm core proper?
>
> And I think we need to add trinity to our test setup eventually ;-)
Note that trinity's ioctl fuzzing is still very new (adde
15 matches
Mail list logo
