This regression still exists as of r302073:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204852
Run /usr/sbin/gstat, press 'q'
Prior to 11-CURRENT gstat would exit.
"Currently" gstat regressively also requires .
...keith
___
freebsd-curr
On Tue, 21 Jun 2016, Ian Lepore wrote:
On Tue, 2016-06-21 at 08:11 -0300, Otacílio wrote:
Em 21/06/2016 07:33, Keith White escreveu:
In an earlier message Ian said that he thought he knew what the
problem was...
Here the problem occurs when using wifi. I do not have tested wired
because I
On Tue, 21 Jun 2016, Mark Millard wrote:
Otacílio otacilio.neto at bsd.com.br wrote on Tue Jun 21 00:06:39 UTC 2016 :
> The kernel panic is totally reproducible. I need only do a ssh in the
> beaglebone using ptty on windows or ssh on freebsd and the kernel
> panic is raised.
. . .
FreeBSD11
On Mon, 20 Jun 2016, Luiz Otavio O Souza wrote:
On Sun, Jun 19, 2016 at 1:11 AM, Maxim Sobolev wrote:
Jim, some update from here. Running r283287 of the driver, I still see the
same "watchdog timeout" messages, but they do not lead to the interface
lockout. The traffic resumes momentarily. Whic
On Fri, 17 Jun 2016, Adrian Chadd wrote:
Just disable 11n for now. ifconfig wlan0 -ht (and reassociate.)
See if it's that.
-adrian
...
Apparently not. I have the same panic even with 11n disabled.
...keith
___
freebsd-current@freebsd.org mailin
On Fri, 17 Jun 2016, Ian Lepore wrote:
On Fri, 2016-06-17 at 07:52 -0700, Adrian Chadd wrote:
Just disable 11n for now. ifconfig wlan0 -ht (and reassociate.)
See if it's that.
-adrian
You can see from the crash info that it's an alignment fault:
r6 =c21a4876
ldmib r6,{r1-r2}
An ldm
On Thu, 16 Jun 2016, Keith White wrote:
On Wed, 15 Jun 2016, Mark Millard wrote:
https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061904.html
reports an RPI-B alignment fault for -r301815 (the snapshot) "when
connecting via WiFi".
-r301872 (
https://lists.f
On Wed, 15 Jun 2016, Mark Millard wrote:
https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061904.html reports an
RPI-B alignment fault for -r301815 (the snapshot) "when connecting via WiFi".
-r301872 (
https://lists.freebsd.org/pipermail/svn-src-head/2016-June/088339.html ) has a
On Thu, 16 Jun 2016, Svatopluk Kraus wrote:
There was a fix committed in r301872 which should help.
Svatopluk Kraus
...
Thanks!
I'd tried r301932 with the same panic. I'll try again with r301872
and a pristine /usr/obj
...keith
___
freebsd-curren
I get the following panic when connecting via WiFi to an RPI-B
running the r301815 snapshot:
Fatal kernel mode data abort: 'Alignment Fault' on read
trapframe: 0xc18f28c0
FSR=0001, FAR=c21a287a, spsr=6013
r0 =c07a6548, r1 =0004, r2 =c060513d, r3 =07b6
r4 =c18f2a28, r5 =c18f2b40, r
ect reduced performance.
UMA startup boot_pages: 1024
...
And can start all 120 processors.
Thanks!
...keith
--
Keith White, genie.uottawa.ca engineering.uottawa.ca
kwh...@uottawa.ca [+1 613 562 5800 x6681]
___
freebsd-current@freebsd.org mailing
of days. Any suggestions?
...keith
--
Keith White, genie.uottawa.ca engineering.uottawa.ca
kwh...@uottawa.ca [+1 613 562 5800 x6681]
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, sen
On Wed, 23 Oct 2013, Mateusz Guzik wrote:
On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
I get a "gnop lock" panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock "gnop lock" 0xf80002566640 already initialized
# kgdb
I get a "gnop lock" panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock "gnop lock" 0xf80002566640 already initialized
# kgdb /boot/kernel.r256923/kernel /var/crash/vmcore.last
...
Unread portion of the kernel message buffer:
panic: lock "gnop lock" 0xff
On Mon, 14 Oct 2013, Andriy Gapon wrote:
on 14/10/2013 03:34 Keith White said the following:
I get the following assert failure with a recent current:
panic: solaris assert: dn->dn_datablkshift != 0, file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_t
I get the following assert failure with a recent current:
panic: solaris assert: dn->dn_datablkshift != 0, file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_tx.c,
line: 638
# uname -a
FreeBSD freebsd10 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r256304: Thu Oct 10
On Thu, 3 Oct 2013, Andriy Gapon wrote:
on 02/10/2013 20:59 Keith White said the following:
On Wed, 2 Oct 2013, Andriy Gapon wrote:
on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following:
Sorry, debugging this is *way* beyond me. Any hints, patches to try?
Please share the stack
On Wed, 2 Oct 2013, Andriy Gapon wrote:
on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following:
Sorry, debugging this is *way* beyond me. Any hints, patches to try?
Please share the stack trace.
--
Andriy Gapon
There's now a pr for this panic: kern/182570
Here's the stack trace:
On Tue, 10 Apr 2012, Daichi GOTO wrote:
Thanks kwhite,
I found an another lock issue. Please try a patch included.
...
Success.
Your latest patch fixes the problem. Thanks!
...keith
___
freebsd-current@freebsd.org mailing list
http://lists.freebs
19 matches
Mail list logo
