Well, there still isn't much anyone apart from Apple can do to fix it
:-).
On Sat, Nov 12, 2011 at 05:01:39PM -0500, Tim Gray wrote:
> I know this was an older thread but figured I'd post a follow up. I'm
> now on OS X 10.7.2 and just tried tmux for the first time in months.
> Sure enough, af
I know this was an older thread but figured I'd post a follow up. I'm
now on OS X 10.7.2 and just tried tmux for the first time in months.
Sure enough, after running for a couple of hours, I got a kernel panic
when I sent a kill-server command to tmux.
So whatever is going on, Apple hasn't fi
very very unlikely to be hardware
should never end up in spec_close with a zero ref count so the panic is
probably correct, the bug is elsewhere
On Tue, Jul 26, 2011 at 01:55:37PM +, Jeff Billimek wrote:
> Nicholas Marriott gmail.com> writes:
>
> >
> > Ah yes, I found an older version bef
You shouldn't get in there if it is 0, because then how would you call
close() on a device node with no references. So it's a bug to be in
spec_close with a 0 reference count.
On Tue, Jul 26, 2011 at 01:55:37PM +, Jeff Billimek wrote:
> Nicholas Marriott gmail.com> writes:
>
> >
> > Ah y
Nicholas Marriott gmail.com> writes:
>
> Ah yes, I found an older version before.
>
> It is much more likely to be a bug in the tty layer given this.
Hi Nicholas,
So given that these panics may be related to the tty layer, I've observed the
following behaviors as a user not running tmux (at
Ah yes, I found an older version before.
It is much more likely to be a bug in the tty layer given this.
On Tue, Jul 26, 2011 at 01:19:19PM +, Jeff Billimek wrote:
> Jeff Billimek billimek.com> writes:
>
> > Hi there,
> >
> > I just got the new macbook air (running OS X 10.7) and get the
Jeff Billimek billimek.com> writes:
> Hi there,
>
> I just got the new macbook air (running OS X 10.7) and get the same
> kernel panic whenever I try to shut down the system:
> panic(cpu 2 caller 0xff8000328b22):
> "Negative open count?"@/SourceCache/xnu/xnu-
> 1699.23.2/bsd/miscfs/specfs/
Just a suggestion, but could you try running strace (or MacOSX's
equivalent) on tmux, and redirect the output to another computer,
something like this:
otherhost:
ncat -l -p 5678 2>&1 | tee tmux_log
localhost:
strace -f tmux 2>&1 | ncat otherhost 5678
Then you'd be able to see/tell us, roughly w
My thought is that the panic is in VFS so it could be a FS bug and you
might be able to avoid it by putting the tmux socket on a different FS.
Probably won't help though.
On Sun, Jul 24, 2011 at 06:45:56AM -0400, Chas. Owens wrote:
> On Sat, Jul 23, 2011 at 22:23, Tim Gray wrote:
> > On Jul 24,
On Sat, Jul 23, 2011 at 22:23, Tim Gray wrote:
> On Jul 24, 2011 at 03:18 AM +0100, Nicholas Marriott wrote:
>>maybe try putting it on a memory FS
>>
>>do you have anything tmux uses on something other than HFS+?
>
> Not that I know of. I've not done anything at all to the standard OS X
> Macbook
might support tmpfs, dunno. panic was in vfs so could help
although this is not really a problem anyone but apple can fix, userland
programs should not be able to panic the kernel
On Sat, Jul 23, 2011 at 10:23:03PM -0400, Tim Gray wrote:
> On Jul 24, 2011 at 03:18 AM +0100, Nicholas Marriott wro
On Jul 24, 2011 at 03:18 AM +0100, Nicholas Marriott wrote:
>maybe try putting it on a memory FS
>
>do you have anything tmux uses on something other than HFS+?
Not that I know of. I've not done anything at all to the standard OS X
Macbook install. One main partition that everything is on.
I'm
maybe try putting it on a memory FS
do you have anything tmux uses on something other than HFS+?
On Sat, Jul 23, 2011 at 10:11:49PM -0400, Tim Gray wrote:
> On Jul 24, 2011 at 02:35 AM +0100, Nicholas Marriott wrote:
> >What filesystem are you using for /tmp (or whereever the tmux sockets
> >are
On Jul 24, 2011 at 02:35 AM +0100, Nicholas Marriott wrote:
>What filesystem are you using for /tmp (or whereever the tmux sockets
>are)?
HFS+, the OS X default.
--
Magic Quadrant for Content-Aware Data Loss Prevention
Re
What filesystem are you using for /tmp (or whereever the tmux sockets
are)?
On Sat, Jul 23, 2011 at 10:05:25AM -0400, Tim Gray wrote:
> On Jul 22, 2011 at 07:50 PM -0400, Tim Gray wrote:
> >While I was just able to cause 1 or 2 panics *with* the wrapper enabled
> >(but not consistently), I was no
On Jul 22, 2011 at 07:50 PM -0400, Tim Gray wrote:
>While I was just able to cause 1 or 2 panics *with* the wrapper enabled
>(but not consistently), I was not able to cause any with it disabled.
>I'll try running like this for a bit and see what I come up with.
Brief followup. At the end of the n
Tim Gray protozoic.com> writes:
>
> I just upgraded my Mac to OS X 10.7. So far I've had two kernel panics,
> both times when messing around in tmux. I *think* tmux is the one
> causing them, but what do I know :) It could be something else.
Hi there,
I just got the new macbook air (runni
On Jul 22, 2011 at 04:42 PM -0500, Chris Johnsen wrote:
>This message comes from the use of the "reattach-to-user-namespace"
>program from
>
>https://github.com/ChrisJohnsen/tmux-MacOSX-pasteboard
>
>You probably have tmux configured to run the reattach program for each
>new window (e.g. via
On 2011 Jul 21, at 21:35, Tim Gray wrote:
> I just upgraded my Mac to OS X 10.7. So far I've had two kernel
> panics,
> both times when messing around in tmux. I *think* tmux is the one
> causing them, but what do I know :) It could be something else.
>
> When I start the tmux session, I do se
Well I'd like to help but there is nothing much I can do other than
suggest you try to reproduce it on FreeBSD (or, worse, Darwin) and then
maybe we can do something about it :-).
There was a report of tmux triggering a kernel panic on FreeBSD a year
or so ago, maybe Apple synced up that bug, migh
On Jul 22, 2011 at 04:10 AM +0100, Nicholas Marriott wrote:
>If tmux causes a kernel panic it is entirely certain it isn't a tmux
>problem, it is a kernel bug.
I see what you are saying.
>The message you show only really shows it is something to do with the
>VFS but not much else. specfs is basic
If tmux causes a kernel panic it is entirely certain it isn't a tmux
problem, it is a kernel bug.
The message you show only really shows it is something to do with the
VFS but not much else. specfs is basically a set of utility routines
used by a whole bunch of other stuff.
Are you certain you ca
22 matches
Mail list logo
