ia64 r255472 buildkernel gives this error:
cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs
-fdiagnostics-show-option -no
FreeBSD mech-as221.men.bris.ac.uk 10.0-ALPHA2 FreeBSD 10.0-ALPHA2 #8 r255811:
Tue Sep 24 09:04:17 BST 2013
r...@mech-as221.men.bris.ac.uk:/usr/obj/usr/src/sys/UZI ia64
panic: deadlkres: possible deadlock detected for 0xe00012d07b00, blocked
for 902743 ticks
cpuid = 1
KDB: stack backtr
>From davide.itali...@gmail.com Wed Sep 25 16:12:47 2013
>
>Can you please paste the output of 'show locks', 'show alllocks',
>'show lockedvnods' at least?
>Ideally you should provide all the informations listed here.
>http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.ht
This panic was triggered by "svn up", while
portmaster updates were going on:
FreeBSD mech-as221.men.bris.ac.uk 10.0-ALPHA2 FreeBSD 10.0-ALPHA2 #8 r255811:
Tue Sep 24 09:04:17 BST 2013
r...@mech-as221.men.bris.ac.uk:/usr/obj/usr/src/sys/UZI ia64
- - - - - - - - - - Prior Console Output -
>From davide.itali...@gmail.com Wed Sep 25 19:00:09 2013
>
>On Wed, Sep 25, 2013 at 5:30 PM, Anton Shterenlikht wrote:
>> >From davide.itali...@gmail.com Wed Sep 25 16:12:47 2013
>>>
>>>Can you please paste the output of 'show locks', 'show al
I asked in ports@ and was told this is a current@ issue.
Please help.
Anton
>Date: Tue, 1 Oct 2013 16:37:26 -0500
>From: Bryan Drewery
>To: Anton Shterenlikht
>Subject: Re: poudriere jail building error: make[4]:
> "/pdr/jails/ia64/usr/src/etc/periodic/daily/Makefile
>From davide.itali...@gmail.com Thu Sep 26 13:12:30 2013
>On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht wrote:
>>
>> Regarding textdump(4), I'm not clear where the following
>> "scripts" should be located and used:
>>
>
>[snip]
>
&
>From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013
>
>If you're not able to get a full dump, a textdump would be enough.
>In your DDB scripts just remove the 'call doadump' step and you should
>be done, unless I'm missing something.
>Please adjust the script as well to include all the informa
BTW, I see in dmesg:
Starting ddb.
ddb: sysctl: debug.ddb.scripting.scripts: Invalid argument
/etc/rc: WARNING: failed to start ddb
What is that about?
panic: uma_zfree: Freeing to non free bucket index.
cpuid = 0
KDB: stack backtrace:
db_trace_self(0x9ffc00158380) at db_trace_self+0x40
db
>From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013
>
>If you're not able to get a full dump, a textdump would be enough.
>In your DDB scripts just remove the 'call doadump' step and you should
>be done, unless I'm missing something.
>Please adjust the script as well to include all the informa
>From davide.itali...@gmail.com Mon Oct 14 12:50:44 2013
>
>This is fair enough -- If you're still at the ddb prompt, please print
>the whole panic message (or at least the address of the lock reported
>as deadlocked by DEADLKRES), so that we can at least have a candidate.
>
Here's another one, fo
>From davide.itali...@gmail.com Tue Oct 15 11:30:07 2013
>
>On Tue, Oct 15, 2013 at 10:43 AM, Anton Shterenlikht wrote:
>
>> Anyway, savecore eventually deadlocks:
>>
>> panic: deadlkres: possible deadlock detected for 0xe000127b7b00, blocked
>> for 90140
I'm trying to set up textdump(4).
On boot I see:
WITNESS: unable to allocate a new witness object
also
Expensive timeout(9) function: 0x9ffc00e222e0(0xa09ed320)
0.002434387 s
kickstart.
Does the first indicate I haven't set up
WITNESS correctly?
What does the second tell me?
Th
panic:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/182999
deadlock:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
>From kostik...@gmail.com Wed Oct 16 13:02:51 2013
>
>On Wed, Oct 16, 2013 at 02:55:26PM +0300, Konstantin Belousov wrote:
>> On Wed, Oct 16, 2013 at 09:02:19AM +0100, Anton Shterenlikht wrote:
>> > panic:
>> > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dker
Issuing reboot:
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
1: buf:0xa0009e10e200, vnode:0, flags:0, blkno:0, lblkno:0, buflock:lock
type bufwait: EXCL by thread 0xe00012741680 (pid 104
After updating to r256624, the system is very unresponsive,
and really unusable - any command (ps, df, top, ls, etc.)
might take up to 1 min to return. However, I could not get
it to panic.
So I reverted back to r255488.
This time I managed to obtain a textdump:
http://www.freebsd.org/cgi/query-p
This time alllocks has lots of info.
I updated the PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
Thanks
Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
>From adrian.ch...@gmail.com Wed Oct 23 14:22:00 2013
>On 23 October 2013 02:18, Anton Shterenlikht wrote:
>
>> After updating to r256624, the system is very unresponsive,
>> and really unusable - any command (ps, df, top, ls, etc.)
>> might take up to 1 min to retur
>From j...@freebsd.org Wed Oct 23 16:54:12 2013
>
>On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote:
>> This time alllocks has lots of info.
>>
>> I updated the PR:
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
>
>Hmm, unfortuna
>From j...@freebsd.org Wed Oct 23 21:10:30 2013
>> >>
>> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
>> >
>> >Hmm, unfortunately it seems like all the stack traces did not work. There
>are
>> >lots of threads blocked on VM-related locks, and CPU 0 is running
>vm_daemon.
>> >Proba
On r255488 ia64 I get spontaneous reboots,
which are more or less reproducible.
These are triggered by nginx serving poudriere built
packages.
The is no panic, and no traces in the logs.
The system just reboots.
A similar issue was seen in about 2011, when
we tried to build is64 packages on portsc
Hello
I updated to r257910 amd64.
I now get lots of:
ata0: FAILURE - zero length DMA transfer attempted
ata0: setting up DMA failed
Please advise
Below are dmesg.boot and pciconf -lv
Many thanks
Anton
***
Rebooting...
cpu_reset: Stopping other CPUs
C
>From s...@freebsd.org Sun Dec 29 09:11:31 2013
>
>Am 28.12.2013 22:01, schrieb Anton Shterenlikht:
>> Hello
>>
>> I updated to r257910 amd64.
>> I now get lots of:
>>
>> ata0: FAILURE - zero length DMA transfer attempted
>> ata0: setting up D
Something wrong with the svn0.eu.freebsd.org mirror:
svn: E60: Unable to connect to a repository at URL
'https://svn0.eu.freebsd.org/base/head'
svn: E60: Error running context: Operation timed out
I hope it's temprorary problem, but
please advise if the mirror address has
changed.
Thank
>From g...@freebsd.org Thu Feb 6 15:34:12 2014
>
>On Thu, Feb 06, 2014 at 01:07:50AM -0800, Anton Shterenlikht wrote:
>> Something wrong with the svn0.eu.freebsd.org mirror:
>>=20
>> svn: E60: Unable to connect to a repository at URL 'https://svn0.eu.f=
>re
/usr/src/UPDATING:
20130905:
The PROCDESC kernel option is now part of the GENERIC kernel
configuration and is required for the rwhod(8) to work.
If you are using custom kernel configuration, you should include
'options PROCDESC'.
There is no later entry advising n
Not sure if this is sparc64 or a kernel issue:
http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curr
ia64 r260914 GENERIC kernel contains:
device kbdmux # keyboard multiplexer
device vt # Virtual terminals
device vt_vga # VGA terminal device
Trying to build it, I get:
linking kernel.debug
vt_core.o: In function `vt_window_switch':
/usr/s
>From j...@freebsd.org Fri Feb 28 20:57:59 2014
>
>On Friday, February 28, 2014 9:23:28 am Anton Shterenlikht wrote:
>> ia64 r260914 GENERIC kernel contains:
>>
>> device kbdmux # keyboard multiplexer
>> device vt
Please close this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/158542
I can no longer reproduce the problem.
Thanks
Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, sen
In my initial PR (sparc64 r261798),
http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
I said that rsync was triggering this panic.
While true, I now see that there's more to it.
I disabled the rsync, and the cron jobs.
Still I get exactly the same panic every
night at 03:02:
# grep Dumptime /va
>From: Mark Felder
>
>On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote:
>> In my initial PR (sparc64 r261798),
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
>>
>> I said that rsync was triggering this panic.
>> While true, I now s
>From g...@freebsd.org Thu Mar 6 15:58:51 2014
>
>On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote:
>> >Can you go into /etc/periodic/daily and execute those scripts one by
>> >one? You should be able to narrow down which one is the culprit.
>
>From b...@0x20.net Thu Mar 6 22:02:56 2014
>
>On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote:
>> In my initial PR (sparc64 r261798),
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
>>
>> I said that rsync was triggering th
>From b...@0x20.net Thu Mar 6 22:02:56 2014
>
>On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote:
>> In my initial PR (sparc64 r261798),
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
>>
>> I said that rsync was triggering th
FreeBSD 11.0-CURRENT #1 r263096
Is casperd started by default?
I haven't enabled it in /etc/rc.conf
I think I get this error when trying
to use ping, e.g.:
# ping localhost
Broken pipe
# ping freebsd.org
Broken pipe
#
Mar 13 12:08:48 casperd[1313]: [ERROR] (casperd) Unable to receive message fr
I've spent a lot of time on this.
At some point I started suspecting
disk failures, based on dd errors and smartmontools
reports. So I replaced the disks,
and then replaced the whole box for
another nominally identical SunBlade 1500.
The panics persisted.
I now think that multiple cold reboots
migh
Got the same trap twice in a row.
Both times triggered by building
one of these moc related ports
in poudriere:
02 www/webkit-qt4 configure
03 www/webkit-gtk2 build
04 sysutils/qzeitgeist build
01 www/webkit-qt4 configure
02 www/webkit-gtk2 configure
03 multime
I'm not sure it's the same issue.
I use neither vmimage nor pf.
Also, as I mentioned in
http://lists.freebsd.org/pipermail/freebsd-current/2014-March/048939.html
r258000, from 11 Nov 2013, works fine.
I haven't received any hint as
to what might have caused this
panic between 258000 and 260689.
So,
I've a storage array accessed with an isp(4) device
from ia64/FreeBSD box. I'm looking for a better supported
alternative to ia64, e.g. amd64 or sparc64 to house
this isp(4) device:
isp0@pci0:192:1:0: class=0x0c0400 card=0x12d6103c chip=0x24221077 rev=0x02
hdr=0x00
vendor = 'QLogic C
Kimmo Paasiala writes:
> > =buildworld===
> >
> >
/usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/usersmtp.c:1864:8:
> > error: incompatible pointer types passing 'void ()' to parameter
of type
> > 'void (*)(c
A migration *guide*, yes. Tools to convert one syntax to another: no.
ok, so what is the brief migraiton advice?
The Handbook mentions PF and IPFW.
I gather from your mails that PF is the recommended choice.
Is that so?
If I choose PF, can I just follow the
Handbook PF section, and once i
# svn up /usr/src/
Updating '/usr/src':
svn: E175002: Unable to connect to a repository at URL
'https://svn.freebsd.org/base/head'
svn: E175002: OPTIONS of 'https://svn.freebsd.org/base/head': could not connect
to server (https://svn.freebsd.org)
#
# svn info /usr/src/
Path: /usr/src
Working Co
From g...@freebsd.org Mon Apr 22 22:57:51 2013
On Mon, Apr 22, 2013 at 05:28:15PM -0400, Glen Barber wrote:
> > # svn up /usr/src/
> > Updating '/usr/src':
> > svn: E175002: Unable to connect to a repository at URL
'https://svn.fre=
ebsd.org/base/he
# uname -a
FreeBSD mech-aslap239.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r2463
70M: Tue Feb 19 09:04:48 GMT 2013 r...@mech-aslap239.men.bris.ac.uk:/usr/obj
/usr/src/sys/BUZI amd64
make buildworld:
c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
amd64 r250633 buildworld fine,
but on "make -j4 buildkernel" got this error:
===> Ports module net/bwn-firmware-kmod (all)
*skip*
Extracting v4/b0g0initvals5.fw
/usr/bin/touch /usr/obj/usr/src/sys/BUZI/usr/ports/net/bwn-firmware-kmod/work/bg
/v4/ucode.fw
make: illegal option -- J
usage: make [-
In addition to what I wrote already for sparc64,
I now get this failure on amd64 r249781:
(EE) Jun 14 18:17:27 NVIDIA(0): Failed to initialize default colormap
(EE) NVIDIA(0): *** Aborting ***
Maybe my "portmaster -r perl" didn't go well?
Or do I need to rebuild some other ports?
Thanks
Anton
From: Walter Hurry
Subject: Re: Cannot startx on FreeBSD10 Current
Date: Fri, 14 Jun 2013 20:50:59 + (UTC)
On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote:
> On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry
> wrote:
>
>
From: Walter Hurry
Subject: Re: Cannot startx on FreeBSD10 Current
Date: Sun, 16 Jun 2013 17:53:53 + (UTC)
On Sun, 16 Jun 2013 11:27:36 +0100, Anton Shterenlikht wrote:
> From: Walter Hurry
> Subject: Re: Cannot startx on Fre
svn --version
svn, version 1.8.0 (r1490375)
compiled Jun 20 2013, 09:21:02 on amd64-portbld-freebsd10.0
# svn up
Updating '.':
svn: E17: Unrecognized URL scheme for
'https://svn0.us-east.freebsd.org/base/head'
Anton
___
freebsd-current@freebsd.
On 06/20/13 10:32, Anton Shterenlikht wrote:
> svn --version
> svn, version 1.8.0 (r1490375)
> compiled Jun 20 2013, 09:21:02 on amd64-portbld-freebsd10.0
>
> # svn up
> Updating '.':
> svn: E1700
This happened when exiting from cssh session:
panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ /usr/src/
sys/ia64/ia64/trap.c:562
cpuid = 1
KDB: enter: panic
[ thread pid 52881 tid 100409 ]
Stopped at kdb_enter+0x92: [I2]addl r14=0xffe29320,gp ;;
db> show ms
>Delivered-To: freebsd-current@freebsd.org
>Date: Sat, 3 Aug 2013 15:17:02 -0700
>From: Steve Kargl
>To: Glen Barber
>Subject: Re: svn error during 'make buildkernel'?
>svn repository. The change to use svnlite in newvers.sh should
>have an entry in UPDATING to alert users that have a too old
>Subject: Re: GCC withdraw
>From: Warner Losh
>Date: Thu, 29 Aug 2013 10:00:19 -0600
> Gcc is still an absolute requirement on all non-x86 platforms (including arm)
> due to the issues with clang. Some of these issues are bugs in specific
> things (arm) that keep coming up (and keep getting fix
errors
/usr/src/sbin/hastctl/../hastd/pjdlog.c: In function
'pjdlog_printf_render_sockaddr':
/usr/src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required
alignment of target type
*** Error code 1
Please advise
Thanks
Anton
--
Anton Shterenlikht
Room 2.6, Queen's Bu
On Tue, Mar 08, 2011 at 10:14:54AM +, Anton Shterenlikht wrote:
> Updating sparc64 from r202445 to r219379:
>
>
> cc -O2 -pipe -I/usr/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT
> -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers
>
c8104000-0xa000c810bfff
flags: 0x4 pflags: 0
state: RUNNING (CPU 0)
priority: 120
container lock: sched lock 0 (0x9ffc00a304c0)
db>
Any use?
Thanks
Anton
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)1
options=3
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
nd6 options=21
ZEEV>
Many thanks
Anton
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
Universit
On Thu, Jun 30, 2011 at 05:11:24AM -0700, Matthew Jacob wrote:
> On 6/30/2011 3:25 AM, Anton Shterenlikht wrote:
> >I see in my logs:
> >
> >isp0: Polled Mailbox Command (0x54) Timeout (50us) (started @
> >isp_plogx:2122)
> >isp0: Mailbox Command 'EXEC
On Tue, Jul 05, 2011 at 08:13:02AM -0700, Marcel Moolenaar wrote:
>
> On Jul 5, 2011, at 1:39 AM, Anton Shterenlikht wrote:
>
> > On Thu, Jun 30, 2011 at 05:11:24AM -0700, Matthew Jacob wrote:
> >> On 6/30/2011 3:25 AM, Anton Shterenlikht wrote:
> >>> I see i
On Tue, Jul 05, 2011 at 07:34:44AM -0700, Matthew Jacob wrote:
> On 7/5/2011 1:39 AM, Anton Shterenlikht wrote:
> > ...
> >dmesg:
> >
> >http://seis.bris.ac.uk/~mexas/freebsd/ia64/rx2620/ZEEV/dmesg.boot
> >
> >Many thanks
> >Anton
> >
>
>
0xa000c815b4e8, 0x9ffc003dc9c0, 0x50e) at writ
e+0xd0
syscallenter(0xe00011d62450, 0xa000c815b3a0, 0xa000c815b3a8) at sysc
allenter+0x4e0
syscall(0xa000c815b4c8, 0xe00011d62450, 0x6, 0x9ffc007dd880, 0x8, 0x
0) at syscall+0x60
epc_syscall_return() at epc_syscall_return
db>
-
On Fri, Aug 12, 2011 at 03:19:04PM +0100, Anton Shterenlikht wrote:
> On ia64 r221488
>
> # cd /usr/ports/lang/perl5.14/
> # make test
>
> isitmychild: rmatrix mismatch between pipe mutex (index 5) and select mtxpool
> (i
> ndex 447): w_rmatrix[5][447] == 1 but w_rm
On Fri, Aug 12, 2011 at 05:45:55PM -0700, Marcel Moolenaar wrote:
>
> On Aug 12, 2011, at 7:19 AM, Anton Shterenlikht wrote:
>
> > On ia64 r221488
>
> Please update to at least r223700, as that was a major stability fix.
UZI> uname -a
FreeBSD mech-as221.men.bris.ac.
On Mon, Aug 15, 2011 at 06:34:51PM +0100, Anton Shterenlikht wrote:
> On Fri, Aug 12, 2011 at 05:45:55PM -0700, Marcel Moolenaar wrote:
> >
> > On Aug 12, 2011, at 7:19 AM, Anton Shterenlikht wrote:
> >
> > > On ia64 r221488
> >
> > Please updat
On Tue, Aug 16, 2011 at 04:49:44PM -0700, Marcel Moolenaar wrote:
>
> On Aug 16, 2011, at 1:12 AM, Anton Shterenlikht wrote:
>
> > On Mon, Aug 15, 2011 at 06:34:51PM +0100, Anton Shterenlikht wrote:
> >> On Fri, Aug 12, 2011 at 05:45:55PM -0700, Marcel Moolenaar wrote
I'm looking for help to make graphics work on Dell Precision 3520.
This did work in r332432:
http://freebsd.1045724.x6.nabble.com/Dell-Precision-3520-laptop-help-with-dual-graphics-card-td6249818.html
I now updated to:
# uname -a
FreeBSD z.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r333982: Thu
Please help get touchpad mouse on
Dell Precision 3520.
The usb mouse works fine.
z> pciconf -lv
hostb0@pci0:0:0:0: class=0x06 card=0x07a91028 chip=0x19108086 rev=0x07
hdr=0x00
vendor = 'Intel Corporation'
device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host
B
On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote:
>
>
> On 06/07/2018 13:21, Anton Shterenlikht wrote:
> > Please help get touchpad mouse on
> > Dell Precision 3520.
> > The usb mouse works fine.
>
>
> pciconf isn't really applica
201 - 270 of 270 matches
Mail list logo
