I have two outputs: LVDS1 and HDMI1. When the computer starts the
LVDS1 and HDMI1 output is mirrored. I see the same output on both
screens. However, once I start X and switch back to the console the
HDMI output is disabled when looking at the console. This means that
any audio I may have playi
On 10 February 2014 16:07, Alexey Dokuchaev wrote:
>
> 1. Before going X, switching consoles took considerable time (about or more
> than one second). Every time my monitor briefly displayed mode information
> pane like it does when new mode is being switched. It does not happen after
> X was lo
Referencing at https://forums.freebsd.org/viewtopic.php?f=39&t=44691#p249459
I'm wondering if the problem is in my system or not.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
stack trace from kgdb could be a good middle ground between ddb stack trace and
a full vmcore file...
on 10/02/2014 22:56 Jeremie Le Hen said the following:
> Hi,
>
> I run 11.0-CURRENT r260696 on amd64.
>
> I've got the following panic:
>
> panic: LK_RETRY set with incompatible flags (0x20040
[snip]
My experiences with newcons/drm2:
* suspend/resume occasionally throws up a panic in the softclock code,
with some vaguely invalid looking newcons timer entry. THis happens
after it comes out of suspend, after af ew seconds. It sucks and makes
things rather unusable.
* Occasionally a resum
On Sun, Nov 03, 2013 at 11:16:53PM -0800, Kevin Oberman wrote:
> Are you booting directly to X or using startx from the console? In either
> case, I think that i915kms should auto-load at the start of X, so you
> should not need to pre-load it.
Just switched to newcons on fresh -CURRENT, seem to w
Hi,
I run 11.0-CURRENT r260696 on amd64.
I've got the following panic:
panic: LK_RETRY set with incompatible flags (0x200400) or an error occured (11)
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe00e5e53980
kdb_backtrace() at kdb_backtrace+0
On Mon, Feb 10, 2014 at 01:25:06PM +0100, Hans Petter Selasky wrote:
> On 02/10/14 13:21, Alexey Dokuchaev wrote:
> >To augment this a bit: I also came across one of these dongles (vendor
> >0x0bda product 0x8176) that gave me this "timeout waiting for checksum
> >report" message. Retrying didn't
On 02/10/14 13:21, Alexey Dokuchaev wrote:
On Tue, Oct 15, 2013 at 11:13:56PM -0700, Rui Paulo wrote:
On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
I too am seeing
urtwn0: timeout waiting for checksum report
Sorry, this is a know problem that I haven't been able to figure out...
I
On Tue, Oct 15, 2013 at 11:13:56PM -0700, Rui Paulo wrote:
> On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
> > I too am seeing
> > urtwn0: timeout waiting for checksum report
>
> Sorry, this is a know problem that I haven't been able to figure out...
> It probably exists in the OpenBSD dri
10 matches
Mail list logo