Christian Kratzer wrote:
> Hi Rick,
>
> On Sun, 18 Oct 2015, Rick Macklem wrote:
>
> > Christian Kratzer wrote:
> >> Hi Rick,
> >>
> >> looks like your latest patch nailed the issue. The box has been up for 3
> >> days:
> >>
> >> ck@noc3:~ % uptime
> >> 12:22PM up 3 days, 4:11, 1 user
Hi Rick,
On Sun, 18 Oct 2015, Rick Macklem wrote:
Christian Kratzer wrote:
Hi Rick,
looks like your latest patch nailed the issue. The box has been up for 3
days:
ck@noc3:~ % uptime
12:22PM up 3 days, 4:11, 1 user, load averages: 0.07, 0.10, 0.08
ck@noc3:~ %
If it does not
Christian Kratzer wrote:
> Hi Rick,
>
> looks like your latest patch nailed the issue. The box has been up for 3
> days:
>
> ck@noc3:~ % uptime
> 12:22PM up 3 days, 4:11, 1 user, load averages: 0.07, 0.10, 0.08
> ck@noc3:~ %
>
> If it does not crash over the weekend this seems t
Christian Kratzer wrote:
> Hi Rick,
>
> looks like your latest patch nailed the issue. The box has been up for 3
> days:
>
> ck@noc3:~ % uptime
> 12:22PM up 3 days, 4:11, 1 user, load averages: 0.07, 0.10, 0.08
> ck@noc3:~ %
>
> If it does not crash over the weekend this seems t
Hi Rick,
looks like your latest patch nailed the issue. The box has been up for 3 days:
ck@noc3:~ % uptime
12:22PM up 3 days, 4:11, 1 user, load averages: 0.07, 0.10, 0.08
ck@noc3:~ %
If it does not crash over the weekend this seems to be it:
ck@noc3:/usr/src % svn diff sys/nets
Hi Rick,
On Mon, 12 Oct 2015, Rick Macklem wrote:
Well, you can try the attached one instead of the previous ones (ie. against
stable).
It just delays destroying the mutexes until the iod thread is exiting.
I can't quite see why the previous patches wouldn't fix it, but this one leaves
smb_io
Christian Kratzer wrote:
> Hi Rick,
>
> On Mon, 12 Oct 2015, Rick Macklem wrote:
>
> > Christian Kratzer wrote:
> >> Hi Rick,
> >>
> >> there was also a second more recent crash in /var/crash
> >>
> >> Mon Oct 12 03:01:16 CEST 2015
> >>
> >> FreeBSD noc3.cksoft.de 10.2-STABLE FreeBSD 10
Hi Rick,
On Mon, 12 Oct 2015, Rick Macklem wrote:
Christian Kratzer wrote:
Hi Rick,
there was also a second more recent crash in /var/crash
Mon Oct 12 03:01:16 CEST 2015
FreeBSD noc3.cksoft.de 10.2-STABLE FreeBSD 10.2-STABLE #2 r288980M: Sun
Oct 11 08:37:40 CEST 2015
c..
Christian Kratzer wrote:
> Hi Rick,
>
> there was also a second more recent crash in /var/crash
>
> Mon Oct 12 03:01:16 CEST 2015
>
> FreeBSD noc3.cksoft.de 10.2-STABLE FreeBSD 10.2-STABLE #2 r288980M: Sun
> Oct 11 08:37:40 CEST 2015
> c...@noc3.cksoft.de:/usr/obj/usr/src/sys
Hi Rick,
there was also a second more recent crash in /var/crash
Mon Oct 12 03:01:16 CEST 2015
FreeBSD noc3.cksoft.de 10.2-STABLE FreeBSD 10.2-STABLE #2 r288980M: Sun Oct
11 08:37:40 CEST 2015 c...@noc3.cksoft.de:/usr/obj/usr/src/sys/NOC amd64
panic: Assertion mtx_unowned(m)
Hi Rick,
On Sat, 10 Oct 2015, Rick Macklem wrote:
Hi again,
Attached is a semantically equivalent patch to the one I posted a few
minutes ago, but I think this one is more readable.
Please let me know if you get it tested, rick
the box crashed again tonight with your patch applied. Here's t
Hi Rick,
On Sat, 10 Oct 2015, Rick Macklem wrote:
Hi again,
Attached is a semantically equivalent patch to the one I posted a few
minutes ago, but I think this one is more readable.
Please let me know if you get it tested, rick
I have patched the 10-stable kernel on the box. Judging from t
Hi again,
Attached is a semantically equivalent patch to the one I posted a few
minutes ago, but I think this one is more readable.
Please let me know if you get it tested, rick
- Original Message -
> Hi John,
>
> the box crashed again running a 10-stable kernel with following patch of
Hi,
Maybe you could try the attached patch instead of the one below?
(Completely untested. I haven't even tried to compile it.)
rick
- Original Message -
> Hi John,
>
> the box crashed again running a 10-stable kernel with following patch of
> yours:
>
> On Wed, 7 Oct 2015, John Baldwi
Christian Kratzer wrote:
> Hi John,
>
> the box crashed again running a 10-stable kernel with following patch of
> yours:
>
> On Wed, 7 Oct 2015, John Baldwin wrote:
> > Index: smb_iod.c
> > ===
> > --- smb_iod.c (revision 288952)
Hi John,
the box crashed again running a 10-stable kernel with following patch of yours:
On Wed, 7 Oct 2015, John Baldwin wrote:
Index: smb_iod.c
===
--- smb_iod.c (revision 288952)
+++ smb_iod.c (working copy)
@@ -624,6 +624,1
Hi John,
On Wed, 7 Oct 2015, John Baldwin wrote:
mtx_lock = 1444181401}
Ok, so that is a destroyed mutex. This means it is probably not Giant, and
it might be some mutex in smb_iod_main() that shows up in smb_iod_thread() due
to inlining.
Actually, we know this from your earlier mail:
On Wednesday, October 07, 2015 08:52:30 AM Christian Kratzer wrote:
> Hi,
>
> On Tue, 6 Oct 2015, John Baldwin wrote:
>
> >> This crash is occurring when doing an mtx_unlock(&Giant). Unfortunately,
> >> I'm not
> >> conversant w.r.t. this code. I've cc'd jhb@ in case he has some insight.
> >> If
Hi,
On Tue, 6 Oct 2015, John Baldwin wrote:
This crash is occurring when doing an mtx_unlock(&Giant). Unfortunately, I'm not
conversant w.r.t. this code. I've cc'd jhb@ in case he has some insight.
If you don't get any responses, I'd suggest reposting to freebsd-current@ with
"crashes in mtx_un
On Monday, October 05, 2015 06:16:54 PM Rick Macklem wrote:
> Christian Kratzer wrote:
> > Hi,
> >
> > I run a regular rsync job that runs from cron and copies stuff that gets
> > created on a Windows smbfs share.
> >
> > Starting about 10.1-RELEASE the VM has become unstable and started panicing
Hi,
On Mon, 5 Oct 2015, dweimer wrote:
root@noc2:/var/crash # freebsd-version -u
10.2-RELEASE-p5
root@noc2:/var/crash # freebsd-version -k
10.2-RELEASE
Shouldn't the kernel version also be 10.2-RELEASE-p5? Perhaps the user land
being different than the kernel is causing a
On Mon, Oct 5, 2015 at 5:00 PM, dweimer wrote:
> On 2015-10-05 5:16 pm, Rick Macklem wrote:
>
>> Christian Kratzer wrote:
>>
>>> Hi,
>>>
>>> I run a regular rsync job that runs from cron and copies stuff that gets
>>> created on a Windows smbfs share.
>>>
>>> Starting about 10.1-RELEASE the VM ha
On 2015-10-05 5:16 pm, Rick Macklem wrote:
Christian Kratzer wrote:
Hi,
I run a regular rsync job that runs from cron and copies stuff that
gets
created on a Windows smbfs share.
Starting about 10.1-RELEASE the VM has become unstable and started
panicing.
I have narrowed the issue down to
Christian Kratzer wrote:
> Hi,
>
> I run a regular rsync job that runs from cron and copies stuff that gets
> created on a Windows smbfs share.
>
> Starting about 10.1-RELEASE the VM has become unstable and started panicing.
>
> I have narrowed the issue down to the aforementioned rsync job.
>
Hi,
I run a regular rsync job that runs from cron and copies stuff that gets
created on a Windows smbfs share.
Starting about 10.1-RELEASE the VM has become unstable and started panicing.
I have narrowed the issue down to the aforementioned rsync job.
When I move the job to a different VM the
25 matches
Mail list logo
