>
> This occured only once and after the reboot, I found a corrupted file on my
> nullfs-mount. It wasn't mutilated, but showed content of another valid file
> in the same directory (like 'cat fil1 >> vfile2')
>
> Any ideas if this has been recently addressed since 09/09?
>
Maybe we have the
Hello,
got this panic today booting a test machine with kernel from 09/09/2019,
r352054:
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0x80541088
stack pointer = 0x28:0xfe578420
frame pointer
Hi Konstantin,
BINGO! 110 out of 100 possible points :-)
Yes, that fixed the problem:
root@blnn719x - ~
2048 # uname -a
FreeBSD blnn719x.ad001.siemens.net 11.3-PRERELEASE FreeBSD
11.3-PRERELEASE #2 r349719M: Thu Jul 11 09:12:21 CEST 2019
r...@blnn719x.ad001.siemens.net:/usr/obj/usr/src/sys
On Wed, Jul 10, 2019 at 03:02:40PM +0200, Schuendehuette, Matthias (LDA IT PLM)
wrote:
> Sorry, wrong link... :-(
>
> See the verbose boot messages here...
>
> https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
>
> ...in file "Boot_verbose.jpg"
Can you try the following
and
the kernel which fails to boot.
With best regards and have a nice weekend
Matthias Schuendehuette
-Ursprüngliche Nachricht-
Von: Konstantin Belousov Gesendet: Mittwoch, 3.
Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT
PLM)
Cc: 'freebsd-stable@freebsd.org';
freebsd-stable@freebsd.org'; Osipov, Michael (LDA IT
PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at 08:42:21AM +, Schuendehuette, Matthias wrote:
Hello Konstantin,
I did some research regarding the kernel crash with the following results>
1) Last working
your machine, and
the kernel which fails to boot.
>
>
>
> With best regards and have a nice weekend
>
> Matthias Schuendehuette
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Konstantin Belousov
> Gesendet: Mittwoch, 3. Juli 2019 15:55
> An: Schuen
e
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org' ; Osipov, Michael
(LDA IT PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at
il: +49 170 8162912
mailto:matthias.schuendehue...@siemens.com
www.siemens.com/ingenuityforlife
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org' ; Osipov, M
nd
> Tel.: +49 30 386-29957
> Mobil: +49 170 8162912
> mailto:matthias.schuendehue...@siemens.com
>
> www.siemens.com/ingenuityforlife
>
> -Ursprüngliche Nachricht-
> Von: Konstantin Belousov
> Gesendet: Donnerstag, 27. Juni 2019 21:00
> An: Schuendehuette,
fe
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Donnerstag, 27. Juni 2019 21:00
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org'
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Mat
Nachricht-
Von: Konstantin Belousov
Gesendet: Donnerstag, 27. Juni 2019 21:00
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org'
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Matthias wrote:
> Hi,
On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Matthias wrote:
> Hi,
>
> the missing attachments can be found here now:
>
> https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
>
So your AP (Application Processor) seems to get fault, most likely in the
trap handle
Hi,
the missing attachments can be found here now:
https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
with best regards
Matthias Schündehütte
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
This list doesn't allow attachments.
Diese Mailingliste erlaubt keine Anhänge.
On 26.06.19 10:13, Schuendehuette, Matthias wrote:
Hello,
for some days now the GENERIC kernel of 11.3-PRERELEASE (i386) crashes on my
ProLiant DL380 G5 server.
Main error message is "kernel tr
Hello,
for some days now the GENERIC kernel of 11.3-PRERELEASE (i386) crashes on my
ProLiant DL380 G5 server.
Main error message is "kernel trap 12 with interrupts disabled".
Since there is no crash dump I attach some screen shots of the boot messages.
I hope this does not violate t
I've just updated to r347946 from r344695. Upon booting the loader, I get:
panic: free: guard2 fail @ 0xcd8de040 + 2061 from unknown:0
I'm using gptzfsboot, and the boot blocks are current. The previous
loader works fine - boot loader_lua and loader_4th are ok. But the
current loaders, both ul
2018-06-18 8:02 GMT+02:00 Ed Schouten :
> I've just committed the patch (r335314) and
> will MFC it to 11-STABLE before the end of the week.
Done, in r335492. Thanks again for reporting this issue!
--
Ed Schouten
Nuxi, 's-Hertogenbosch, the Netherlands
__
Hi Michael,
2018-06-17 22:04 GMT+02:00 Michael Grimm :
> Thanks, your patch fixed it!
That's awesome. Thanks for confirming!
> I am not that much experienced, but that's what I did:
>
> #) svn update -r 335059
> #) applied your patch
> #) recompiled world and kernel
> #) reinstalled world and ke
Hi Ed --
> On 17. Jun 2018, at 19:27, Ed Schouten wrote:
>
> Hi Michael,
>
> 2018-06-17 17:52 GMT+02:00 Michael Grimm :
>> I do believe that this commit might be the cause:
>> https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revision=335059&view=markup&sortby=file
>
> Thanks
Hi Michael,
2018-06-17 17:52 GMT+02:00 Michael Grimm :
> I do believe that this commit might be the cause:
> https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revision=335059&view=markup&sortby=file
Thanks for reporting this issue. I just did some debugging on my
system and I th
On 17. Jun 2018, at 18:06, Yasuhiro KIMURA wrote:
> There was a large MFC about syslogd at r335059:
> So how about take following steps?
>
> 1. svn update -r 335058 /usr/src
> 2. Rebuild and reinstall /usr/sbin/syslogd and /usr/bin/wall on both
> host and jail.
> 3. Restart syslogd on both ho
From: Michael Grimm
Subject: syslogd became silent between 11.2-PRERELEASE r334874 and r335282
Date: Sun, 17 Jun 2018 16:27:33 +0200
> I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE
> r335282, upgraded from r334874 today.
There was a large MFC about sysl
On 17. Jun 2018, at 16:27, Michael Grimm wrote:
> Hi,
>
> I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE
> r335282, upgraded from r334874 today.
>
> All syslog messages at each jail become forwarded to syslogd running at the
> host. This s
On 17. Jun 2018, at 16:50, Gary Palmer wrote:
> On Sun, Jun 17, 2018 at 04:27:33PM +0200, Michael Grimm wrote:
>> Host's syslogd can be reached from inside every jail, e.g.:
>>
>> jtest> nc -4vuw 1 10.x.y.z 514
>> Connection to 10.x.y.z 514 port [udp/syslog] succeeded!
>
> UDP is con
On Sun, Jun 17, 2018 at 04:27:33PM +0200, Michael Grimm wrote:
> Hi,
>
> I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE
> r335282, upgraded from r334874 today.
>
> All syslog messages at each jail become forwarded to syslogd running at the
Hi,
I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE
r335282, upgraded from r334874 today.
All syslog messages at each jail become forwarded to syslogd running at the
host. This setup worked for years. Today not a single syslog message becomes
forwarded to the
On Sat, Jun 02, 2018 at 08:14:37AM -0700, Kevin Oberman wrote:
> After teh announcement of RC1 I updated my 11-STABLE box, expecting wither
> that I would see RC1 or STABLE, depending on whether the 11.2 BRANCH had
> been created, but instead I am "back" at 11.2-PRERELEA
On 06/02/18 11:14, Kevin Oberman wrote:
> After teh announcement of RC1 I updated my 11-STABLE box, expecting wither
> that I would see RC1 or STABLE, depending on whether the 11.2 BRANCH had
> been created, but instead I am "back" at 11.2-PRERELEASE #1.
>
> Is this in
After teh announcement of RC1 I updated my 11-STABLE box, expecting wither
that I would see RC1 or STABLE, depending on whether the 11.2 BRANCH had
been created, but instead I am "back" at 11.2-PRERELEASE #1.
Is this intentional? At least it is confusing.
--
Kevin Oberman, Part time
Just been through the azure python code - my intiial impressin was wrong, its
not the chnage to the periphlist output which is the issue. Instead
its the fact that a simple 'devlist' now puts the pass devices first in
the list, and the azure waagent uses the first listed device when it initially
lo
Thank you, It is stil building, but it looks like it is past libpcap.
Thanks again for your work.
Op 31/05/2017 om 10:21 schreef Xin Li:
> Should be fixed by r319297.
>
> Cheers,
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/
Should be fixed by r319297.
Cheers,
signature.asc
Description: OpenPGP digital signature
On 5/31/17 00:25, Johan Hendriks wrote:
> I am on the following revision.
>
> root@desk:/usr/src # uname -a
> FreeBSD desk.server.mylab.nl 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #89
> r319098: Mon May 29 10:55:56 CEST 2017
> r...@desk.server.mylab.nl:/usr/obj/usr/s
I am on the following revision.
root@desk:/usr/src # uname -a
FreeBSD desk.server.mylab.nl 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #89
r319098: Mon May 29 10:55:56 CEST 2017
r...@desk.server.mylab.nl:/usr/obj/usr/src/sys/KRNL amd64
I have updated to the following revision
At revision
A bit more investigation on this and I think I found what the differece is
at least. waagent is using camcontrol periphlist 3:1:0 to find devices,
and this has chnaged from placing the discs before the pass
devices to afterwards. So on an earlier version I get this:
root@joanna-may:/home/w
> The agent has just been updated in the ports tree a few days ago, can you
> try the new version?
Just checked and the version in ports is 2.2.8, and I am running 2.2.11
-pete.
..
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/m
ime I tried it
clashed and didnt work at all actually). )
-pete.
On 05/26/17 13:30, Baptiste Daroussin wrote:
On Fri, May 26, 2017 at 01:26:46PM +0100, Pete French wrote:
Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
now find the below backtrace from waagent when it
On Fri, May 26, 2017 at 01:26:46PM +0100, Pete French wrote:
> Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
> now find the below backtrace from waagent when it tries to attach
> the resource disc. It looks as if it is finding 'pass1' as the device,
Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
now find the below backtrace from waagent when it tries to attach
the resource disc. It looks as if it is finding 'pass1' as the device,
when it should be finding 'da1'. As the waagents hasnt changed I am
On Mon, May 22, 2017 at 10:15:03PM +0200, Kurt Jaeger wrote:
> Hi!
>
> > After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> > coming up. They were fine in 11.0-RELEASE.
>
> Please submit a PR via bugs.freebsd.org and send the PR number.
>
&g
On Mon, May 22, 2017 at 10:15:03PM +0200, Kurt Jaeger wrote:
> Hi!
>
> > After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> > coming up. They were fine in 11.0-RELEASE.
>
> Please submit a PR via bugs.freebsd.org and send the PR number.
>
&g
On 23.05.2017 23:12, Zaphod Beeblebrox wrote:
> I just added a setkey for the reverse, and connections still do not happen.
Look at the `netstat -sp tcp | grep sign' output.
Also there are some debug messages can be generated by TCP syncache
code, you can see them in the syslog's logs under LOG_DE
10:29 AM, Mike Tancsa <mailto:m...@sentex.net>> wrote:
>
> On 5/22/2017 3:24 PM, Zaphod Beeblebrox wrote:
> > After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> > coming up. They were fine in 11.0-RELEASE.
>
> Make sure the
I just added a setkey for the reverse, and connections still do not happen.
On Tue, May 23, 2017 at 10:29 AM, Mike Tancsa wrote:
> On 5/22/2017 3:24 PM, Zaphod Beeblebrox wrote:
> > After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> > coming up. They we
On 5/22/2017 3:24 PM, Zaphod Beeblebrox wrote:
> After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> coming up. They were fine in 11.0-RELEASE.
Make sure the SA entries have both directions. See this thread for more
details.
https://lists.freebsd.org/pipermail/f
Hi!
> After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> coming up. They were fine in 11.0-RELEASE.
Please submit a PR via bugs.freebsd.org and send the PR number.
We should bring this to the attention of re@.
--
p...@opsec.eu+49 171 3
After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
coming up. They were fine in 11.0-RELEASE.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On Fri, 27 Jan 2017 00:33:10 +0200
Ivan Klymenko wrote:
> On Wed, 28 Dec 2016 09:57:29 -0800
> hiren panchasara wrote:
>
> > On 12/28/16 at 07:53P, Ivan Klymenko wrote:
> > > On Wed, 28 Dec 2016 09:41:42 -0800
> > > hiren panchasara wrote:
> > >
> > > > Can you open a bug report at http
On Fri, 27 Jan 2017 19:16:04 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 17:41, Ivan Klymenko wrote:
> >> I didn't done the merge of the patch into stable/11 and
> >> releng/11.0, because Adrian said it is not good enough and he will
> >> rework it better :)
> >>
> >
> >
> > Jan 27 16:17:0
On 27.01.2017 17:41, Ivan Klymenko wrote:
I didn't done the merge of the patch into stable/11 and releng/11.0,
because Adrian said it is not good enough and he will rework it
better :)
Jan 27 16:17:07 ns kernel: Fatal trap 12: page fault while in kernel mode
Jan 27 16:17:07 ns kernel: cpuid =
On Fri, 27 Jan 2017 15:01:18 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 14:58, Ivan Klymenko wrote:
> > On Fri, 27 Jan 2017 13:46:30 +0300
> > "Andrey V. Elsukov" wrote:
> >
> >> On 27.01.2017 01:33, Ivan Klymenko wrote:
> >>> The reason most panics served as tuning Netisr:
> >>> net.i
On Fri, 27 Jan 2017 15:01:18 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 14:58, Ivan Klymenko wrote:
> > On Fri, 27 Jan 2017 13:46:30 +0300
> > "Andrey V. Elsukov" wrote:
> >
> >> On 27.01.2017 01:33, Ivan Klymenko wrote:
> >>> The reason most panics served as tuning Netisr:
> >>> net.i
On 27.01.2017 14:58, Ivan Klymenko wrote:
On Fri, 27 Jan 2017 13:46:30 +0300
"Andrey V. Elsukov" wrote:
On 27.01.2017 01:33, Ivan Klymenko wrote:
The reason most panics served as tuning Netisr:
net.isr.numthreads=4
net.isr.maxthreads=4
net.isr.bindthreads=1
Apparently, this subsystem at some
On Fri, 27 Jan 2017 13:46:30 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 01:33, Ivan Klymenko wrote:
> > The reason most panics served as tuning Netisr:
> > net.isr.numthreads=4
> > net.isr.maxthreads=4
> > net.isr.bindthreads=1
> >
> > Apparently, this subsystem at some moment had been bro
On 27.01.2017 01:33, Ivan Klymenko wrote:
The reason most panics served as tuning Netisr:
net.isr.numthreads=4
net.isr.maxthreads=4
net.isr.bindthreads=1
Apparently, this subsystem at some moment had been broken.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836
--
WBR, Andrey V. Elsu
On Wed, 28 Dec 2016 09:57:29 -0800
hiren panchasara wrote:
> On 12/28/16 at 07:53P, Ivan Klymenko wrote:
> > On Wed, 28 Dec 2016 09:41:42 -0800
> > hiren panchasara wrote:
> >
> > > Can you open a bug report at https://bugs.freebsd.org/bugzilla/
> > > with necessary details? Looks like virtua
Next panic
uname -a
FreeBSD ns 11.0-STABLE FreeBSD 11.0-STABLE #1 r310470: Fri Dec 23 12:00:49 EET
2016 root@ns:/usr/obj/usr/src/sys/bzk11 amd64
Dec 28 09:43:21 ns kernel: Fatal trap 12: page fault while in kernel mode
Dec 28 09:43:21 ns kernel: cpuid = 3; apic id = 03
Dec 28 09:43:21 ns ker
On Mon, 21 Nov 2016 18:35:24 +0100
Oliver Pinter wrote:
> On Mon, Nov 21, 2016 at 5:34 PM, Ivan Klymenko wrote:
> > Next
>
> Are you able to reproduce these without loaded VirtualBox kernel
> modules?
>
This is hard to do - server is used on a daily works.
Panic often occur when one of the ow
On Mon, Nov 21, 2016 at 5:34 PM, Ivan Klymenko wrote:
> Next
> uname -a
> FreeBSD nonamehost 11.0-STABLE FreeBSD 11.0-STABLE #10 r308523: Fri Nov 11
> 13:52:01 EET 2016 root@nonamehost:/usr/obj/usr/src/sys/bzk11 amd64
>
> Nov 21 17:33:40 ns kernel: Fatal trap 12: page fault while in kernel
Next
uname -a
FreeBSD nonamehost 11.0-STABLE FreeBSD 11.0-STABLE #10 r308523: Fri Nov 11
13:52:01 EET 2016 root@nonamehost:/usr/obj/usr/src/sys/bzk11 amd64
Nov 21 17:33:40 ns kernel: Fatal trap 12: page fault while in kernel mode
Nov 21 17:33:40 ns kernel: cpuid = 0; apic id = 00
Nov 21 17:
Next panic
Oct 28 09:06:50 ns kernel: panic: sbsndptr: sockbuf 0xf8008f186878 and mbuf
0xf8008f29d200 clashing
Oct 28 09:06:50 ns kernel: cpuid = 7
Oct 28 09:06:50 ns kernel: KDB: stack backtrace:
Oct 28 09:06:50 ns kernel: #0 0x80b5f0e7 at kdb_backtrace+0x67
Oct 28 09:06:50 ns ke
Next
Oct 21 22:06:26 ns syslogd: kernel boot file is /boot/kernel/kernel
Oct 21 22:06:26 ns kernel: panic: sbsndptr: sockbuf 0xf80201038518 and mbuf
0xf802820a1200 clashing
Oct 21 22:06:26 ns kernel: cpuid = 3
Oct 21 22:06:26 ns kernel: KDB: stack backtrace:
Oct 21 22:06:26 ns kernel: #0
Hi, friendly community.
I present to you my collection.
I have :
//===//
System Information
Manufacturer: Supermicro
Product Name: X10SLH-F/X10SLM+-F
//===//
pciconf -lv
hostb0
On Sat, 3 Sep 2016 15:56:51 +0100, Steven Hartland wrote:
> That file is not accessible
>
> On 03/09/2016 10:51, Volodymyr Kostyrko wrote:
> > Hi all.
> >
> > Got one host without keyboard so can't dump it.
> >
> > Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
> >
That file is not accessible
On 03/09/2016 10:51, Volodymyr Kostyrko wrote:
Hi all.
Got one host without keyboard so can't dump it.
Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
This is MINIMAL kernel with minor additions.
___
Hi,
I've the same issue here with my ZFS server. I've updated from 10.3-STABLE
to 11-PRERELEASE. Then after some time my server just crash.
Then i tried to update again using another svn server. After many tries
(because my server has been crashed all the time) i got RC2. But same i
Hi all.
Got one host without keyboard so can't dump it.
Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
This is MINIMAL kernel with minor additions.
--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing lis
On Sun, Mar 20, 2016 at 07:47:58AM +0800, Erich Dollansky wrote:
> Hi,
>
> On Sat, 19 Mar 2016 08:23:09 -0600
> Ian Lepore wrote:
>
> > On Sat, 2016-03-19 at 13:48 +0800, Erich Dollansky wrote:
> > >
> > > nothing else was changed on the machine except the update. I could
> > > use
> > >
> > >
Hi,
On Sat, 19 Mar 2016 08:23:09 -0600
Ian Lepore wrote:
> On Sat, 2016-03-19 at 13:48 +0800, Erich Dollansky wrote:
> >
> > nothing else was changed on the machine except the update. I could
> > use
> >
> > ssh 192.168.12.12
> >
> > to connect to a jail running under that IP address before t
On Sat, 2016-03-19 at 13:48 +0800, Erich Dollansky wrote:
> Hi,
>
> nothing else was changed on the machine except the update. I could
> use
>
> ssh 192.168.12.12
>
> to connect to a jail running under that IP address before the update
> without problems.
>
> It works now only with
>
> ssh -Y
Hi,
nothing else was changed on the machine except the update. I could use
ssh 192.168.12.12
to connect to a jail running under that IP address before the update
without problems.
It works now only with
ssh -Y 192.168.12.12
The /etc/ssh/ssh_config file says:
Host *
ForwardX11 yes
So, it sho
- John's Original Message -
> Hi Folks,
>
>I'm seeing a panic with the 9.2-PRERELEASE code. The system
> will stay up for anywhere from a couple of seconds to a few hours
> and then panic.
I have continued to look at this problem and believe I have mad
On Thursday, September 12, 2013 1:29:40 am Marko Cupać wrote:
> On Wed, 11 Sep 2013 11:11:24 -0400
> John Baldwin wrote:
>
> > Is this reproducible?
>
> It happened a few times before (maybe 3-4 times this year), but I can't
> reproduce it intentionally.
Hmm, I'm tempted to chalk this up to a h
On Wed, 11 Sep 2013 11:11:24 -0400
John Baldwin wrote:
> Is this reproducible?
It happened a few times before (maybe 3-4 times this year), but I can't
reproduce it intentionally.
--
Marko Cupać
___
freebsd-stable@freebsd.org mailing list
http://lists
On Tuesday, September 10, 2013 10:50:55 am Marko Cupać wrote:
> My 9.2-PRERELEASE #0 r254557 amd64 just dumped core on shutdown. I
> updated src to Last Changed Rev: 255395 two days ago but did not get
> to rebuild world&kernel. Also I did not rebuild any ports since.
> Virtualbox
ning the following version of FreeBSD
uname -a
FreeBSD beasty.testdomain.local 9.2-PRERELEASE FreeBSD
9.2-PRERELEASE #0
r254646: Thu Aug 22 09:46:05 CEST 2013
root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL
amd64
I have updated the source using the following comm
>
> > > > > > is the info after a forced panic.
> > > > > >
> > > > > Looks like the same hang to me. Several threads are sleeping on
> > > > > "pgrbwt"
> > > > > and lots are waiting for an NFS
lowing version of FreeBSD
uname -a
FreeBSD beasty.testdomain.local 9.2-PRERELEASE FreeBSD
9.2-PRERELEASE #0
r254646: Thu Aug 22 09:46:05 CEST 2013
root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL
amd64
I have updated the source using the following command.
svn co http://s
r a forced panic.
> > > > >
> > > > Looks like the same hang to me. Several threads are sleeping on
> > > > "pgrbwt"
> > > > and lots are waiting for an NFS vnode lock.
> > > >
> > > > It should be fixed in RC3 (or rever
t; > > >=20
> > > > > Looks like the same hang to me. Several threads are sleeping on
> > > > > "pgrbwt"
> > > > > and lots are waiting for an NFS vnode lock.
> > > > >=20
> > > > > It should be fixed in
before 'make buildworld'
need:
cd /usr/src/usr.bin/yacc && make obj && make depend && make && make install
2013/8/27 Johan Hendriks
> Hello all
>
> I am running the following version of FreeBSD
>
> uname -a
> FreeBSD beasty.testdom
t; > > > is the info after a forced panic.
> > > > >
> > > > Looks like the same hang to me. Several threads are sleeping on
> > > > "pgrbwt"
> > > > and lots are waiting for an NFS vnode lock.
> > > >
> >
everal threads are sleeping on
> > > "pgrbwt"
> > > and lots are waiting for an NFS vnode lock.
> > >
> > > It should be fixed in RC3 (or revert r250907). If it still hangs
> > > with
> > > RC3 (or r250907 reverted), email
Hello all
I am running the following version of FreeBSD
uname -a
FreeBSD beasty.testdomain.local 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0
r254646: Thu Aug 22 09:46:05 CEST 2013
root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL
amd64
I have updated the source using the following command
ots are waiting for an NFS vnode lock.
> >
> > It should be fixed in RC3 (or revert r250907). If it still hangs
> > with
> > RC3 (or r250907 reverted), email again.
> >
> im following stable, hence it's till calling itself 9.2-PRERELEASE,
> but
> I did a syn
ngs with
> RC3 (or r250907 reverted), email again.
>
im following stable, hence it's till calling itself 9.2-PRERELEASE, but
I did a sync this morning - local time, after rc3 was anounced.
but after 3.45 minutes is hung, data in
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/core.txt/
Daniel Braniss wrote:
> I upgraded our web server, and only after 3 hours it hung :-(
> (as a side note, I have 2 other web servers, also running 9.2 doing
> great :-)
> go figure.
>
> anyways, in
> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/core.txt/0
>
> is the info after a forced panic.
I upgraded our web server, and only after 3 hours it hung :-(
(as a side note, I have 2 other web servers, also running 9.2 doing great :-)
go figure.
anyways, in
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/core.txt/0
is the info after a forced panic.
my guts say its running out of resou
t; > > > Hi!
>> > > > >
>> > > > > I'm not sure what could've caused this! Not much has changed in
>> the
>> > > > > wireless stack and ath driver between 9.1 and 9.2. Would you be
>> able to
>> > > > > work through different svn versions
On Tue, 20 Aug 2013, J David wrote:
On Sun, Aug 18, 2013 at 3:43 PM, Warren Block wrote:
On Sun, 18 Aug 2013, David Demelier wrote:
http://files.malikania.fr/DSC_0223.jpg
What's that? Is this a joke?
Yes, sort of.
This is fantastic. Kudos and thanks for the laugh to whoever snuck it in
On Sun, Aug 18, 2013 at 3:43 PM, Warren Block wrote:
> On Sun, 18 Aug 2013, David Demelier wrote:
>> http://files.malikania.fr/DSC_0223.jpg
>>
>> What's that? Is this a joke?
>
> Yes, sort of.
This is fantastic. Kudos and thanks for the laugh to whoever snuck it in there.
> After you're tired o
ou be
> able to
> > > > > work through different svn versions of stable/9 between 9.1 and
> 9.2 to
> > > > > narrow down when things broke?
> > > > >
> > > > > It may be something other than the wifi driver/stack.
>
A lot of the ath PRs filed by me can be closed. They're reminders that
things needed fixing, which I've done.
A lot of them are for older cards on older machines with odd behaviour due
to PCI/cardbus issues, power save bugs, ACPI hilarity, etc. I've tried to
port over some fixes to address these b
Are you running the AR9285 on -HEAD? If not, upgrade. It should behave
much, much better.
-adrian
On 19 August 2013 00:59, Marko Cupać wrote:
> I am struggling with my AR9285 for more than a year now. Sometimes it
> is better, sometimes worse, but never without disconnections.
>
> I have al
Ok it's gotten worse now. I can no longer restart netif, it just hangs
there in "uninterruptible wait" forever (trying to "delete" the wlan0
interface using ifconfig)
On Mon, Aug 19, 2013 at 09:59:19AM +0200, Marko Cupać wrote:
> I am struggling with my AR9285 for more than a year now. Sometimes it
gt; narrow down when things broke?
> > > >
> > > > It may be something other than the wifi driver/stack.
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > -adrian
> > > >
> > > >
> > > >
&g
On Mon, Aug 19, 2013 at 11:40:44AM +0200, Marko Cupać wrote:
> I am total layman, and am just sharing my experimentations. I
> am not sure if they will get us any improvements. What else can I do when
> there are 175 PRs currently open:
> http://lists.freebsd.org/pipermail/freebsd-wireless/2013-Aug
On Mon, 19 Aug 2013 14:46:01 +0530
Tj Hariharan wrote:
> Hmm, let me know how that goes, I'll probably try it too. How did you
> find the number '51200', and what does that value do?
I searched error message I was getting and found this thread:
http://lists.freebsd.org/pipermail/freebsd-net/2009
On Mon, Aug 19, 2013 at 09:59:19AM +0200, Marko Cupać wrote:
> I am struggling with my AR9285 for more than a year now. Sometimes it
> is better, sometimes worse, but never without disconnections.
>
> I have also noticed it dies more frequently on heavy usage. I read
> somewhere that raising value
1 - 100 of 1313 matches
Mail list logo
