So apparently the value of 'rebooting' is 0 at the time of the hang...
db> x rebooting
rebooting: 0
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stab
On Sun, Jun 16, 2013 at 08:06:21PM +0200, Michiel Boland wrote:
> On 06/16/2013 19:46, Konstantin Belousov wrote:
> > On Sun, Jun 16, 2013 at 07:12:33PM +0200, Michiel Boland wrote:
> >> On 06/16/2013 17:37, Konstantin Belousov wrote:
> >> [...]
> >>> I do not see anything related to i915 in the co
On Sun, 2013-06-16 at 09:07 -0700, Jeremy Chadwick wrote:
> On Sun, Jun 16, 2013 at 06:01:49PM +0200, Michiel Boland wrote:
> > On 06/16/2013 17:55, Jeremy Chadwick wrote:
> > [...]
> >
> > >Are you running moused(8)? Actually, I can see quite clearly that you
> > >are in your core.txt:
> > >
> >
On 06/16/2013 20:06, Michiel Boland wrote:
FWIW - the saved core from the ddb-induced panic has
(kgdb) print rebooting
$1 = 1
I realised instantly after I sent my message that this is meaningless - so
please ignore that.
___
freebsd-stable@freebs
On 06/16/2013 19:46, Konstantin Belousov wrote:
On Sun, Jun 16, 2013 at 07:12:33PM +0200, Michiel Boland wrote:
On 06/16/2013 17:37, Konstantin Belousov wrote:
[...]
I do not see anything related to i915 in the core.txt you provided.
Next time the machine hangs, start with the output of ps com
On Sun, Jun 16, 2013 at 07:12:33PM +0200, Michiel Boland wrote:
> On 06/16/2013 17:37, Konstantin Belousov wrote:
> [...]
> > I do not see anything related to i915 in the core.txt you provided.
> >
> > Next time the machine hangs, start with the output of ps command from
> > ddb and 'show allpcpu',
On 06/16/2013 17:37, Konstantin Belousov wrote:
[...]
I do not see anything related to i915 in the core.txt you provided.
Next time the machine hangs, start with the output of ps command from
ddb and 'show allpcpu', together with 'alltrace'.
Ok, I captured 'ps', 'show allpcpu' and 'alltrace'
On 16/06/13 20:30, Jeremy Chadwick wrote:
> * Output from: strings /boot/kernel/kernel | egrep ^option Thanks.
I stumbled across this one about a week ago:
strings /boot/kernel/kernel | head -1
and was wondering about the history of where it came from / what it means.
I can see it was added t
- Original Message -
From: "Michiel Boland"
To: "FreeBSD Stable"
Sent: Sunday, June 16, 2013 4:11 PM
Subject: system sporadically hangs on shutdown after switching to WITH_NEW_XORG
Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X server
with Intel driver has
On Sun, Jun 16, 2013 at 06:01:49PM +0200, Michiel Boland wrote:
> On 06/16/2013 17:55, Jeremy Chadwick wrote:
> [...]
>
> >Are you running moused(8)? Actually, I can see quite clearly that you
> >are in your core.txt:
> >
> >Starting ums0 moused.
> >
> >Try turning that off. Don't ask me how, be
On 06/16/2013 17:55, Jeremy Chadwick wrote:
[...]
Are you running moused(8)? Actually, I can see quite clearly that you
are in your core.txt:
Starting ums0 moused.
Try turning that off. Don't ask me how, because devd(8) / devd.conf(5)
might be involved.
The moused is started by devd - I d
On Sun, Jun 16, 2013 at 05:48:52PM +0200, Michiel Boland wrote:
> On 06/16/2013 17:37, Konstantin Belousov wrote:
> >On Sun, Jun 16, 2013 at 05:11:15PM +0200, Michiel Boland wrote:
> >>Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X
> >>server
> >>with Intel driver has some
On 06/16/2013 17:37, Konstantin Belousov wrote:
On Sun, Jun 16, 2013 at 05:11:15PM +0200, Michiel Boland wrote:
Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X server
with Intel driver has some issues that make it unusable for me.
The new X server and Intel driver works
On Sun, Jun 16, 2013 at 05:11:15PM +0200, Michiel Boland wrote:
> Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X
> server
> with Intel driver has some issues that make it unusable for me.
>
> The new X server and Intel driver works extremely well, so kudos to whoever
>
Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X server
with Intel driver has some issues that make it unusable for me.
The new X server and Intel driver works extremely well, so kudos to whoever made
this possible.
Unfortunately, I am now experiencing random hangs on s
On Sun, Jun 16, 2013 at 11:55:38AM +0200, Andre Albsmeier wrote:
> On Sun, 16-Jun-2013 at 10:49:37 +0200, Jeremy Chadwick wrote:
> > On Sun, Jun 16, 2013 at 10:02:39AM +0200, Andre Albsmeier wrote:
> > > On Sun, 16-Jun-2013 at 08:54:41 +0200, Jeremy Chadwick wrote:
> > > > On Fri, May 31, 2013 at 0
On Sun, 16-Jun-2013 at 10:49:37 +0200, Jeremy Chadwick wrote:
> On Sun, Jun 16, 2013 at 10:02:39AM +0200, Andre Albsmeier wrote:
> > On Sun, 16-Jun-2013 at 08:54:41 +0200, Jeremy Chadwick wrote:
> > > On Fri, May 31, 2013 at 07:25:23PM +0200, Andre Albsmeier wrote:
> > > > On Fri, 31-May-2013 at 16
On Sun, Jun 16, 2013 at 10:02:39AM +0200, Andre Albsmeier wrote:
> On Sun, 16-Jun-2013 at 08:54:41 +0200, Jeremy Chadwick wrote:
> > On Fri, May 31, 2013 at 07:25:23PM +0200, Andre Albsmeier wrote:
> > > On Fri, 31-May-2013 at 16:51:03 +0200, John Baldwin wrote:
> > > > On Friday, May 31, 2013 8:26
On Sun, 16-Jun-2013 at 08:54:41 +0200, Jeremy Chadwick wrote:
> On Fri, May 31, 2013 at 07:25:23PM +0200, Andre Albsmeier wrote:
> > On Fri, 31-May-2013 at 16:51:03 +0200, John Baldwin wrote:
> > > On Friday, May 31, 2013 8:26:11 am Andre Albsmeier wrote:
> > > > Each day at 5:15 we are generating
On Fri, May 31, 2013 at 07:25:23PM +0200, Andre Albsmeier wrote:
> On Fri, 31-May-2013 at 16:51:03 +0200, John Baldwin wrote:
> > On Friday, May 31, 2013 8:26:11 am Andre Albsmeier wrote:
> > > Each day at 5:15 we are generating snapshots on various machines.
> > > This used to work perfectly under
20 matches
Mail list logo
