Re: building x11-wm/plasma5-kwin w/ poudriere results in out of swap space

[Martin Wilke]

On 2019-06-11 14:59, Matthias Apitz wrote:

Hello,

I'm build the latest port svn checkout (June 10) on r342378 with
poudriere and (after isolating it) have the problem that building
x11-wm/plasma5-kwin runs reproducible out of swap during 'configure'
phase:

[00:00:49] Cleaning the build queue
[00:00:49] Sanity checking build queue
[00:00:49] Processing PRIORITY_BOOST
[00:00:50] Balancing pool
[00:00:50] Recording filesystem state for prepkg... done
[00:00:52] Building 1 packages using 1 builders
[00:00:52] Starting/Cloning builders
[00:00:54] Hit CTRL+t at any time to see build progress and stats
[00:00:54] [01] [00:00:00] Building x11-wm/plasma5-kwin | 
plasma5-kwin-5.15.5

load: 0.95  cmd: sh 19376 [piperd] 67.68r 0.00u 0.00s 0% 3932k
[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s]
[parallel_build:] Queued: 1  Built: 0  Failed: 0  Skipped: 0  Ignored:
0  Tobuild: 1   Time: 00:01:40
[01]: x11-wm/plasma5-kwin   | plasma5-kwin-5.15.5
build-depends   (00:01:06 / 00:01:08)
[00:02:02] Logs:
/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s
load: 0.52  cmd: wc 26535 [piperd] 0.10r 0.00u 0.00s 0% 2656k
[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s]
[parallel_build:] Queued: 1  Built: 0  Failed: 0  Skipped: 0  Ignored:
0  Tobuild: 1   Time: 00:03:27
[01]: x11-wm/plasma5-kwin   | plasma5-kwin-5.15.5   configure
  (00:01:17 / 00:02:55)
[00:03:49] Logs:
/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s
^C[00:04:13] Error: Signal SIGINT caught, cleaning up and exiting

Is this a known issue? Or should I investigate deeper which process it
is?


This problem is not only for plasma5 its random happened since import of 
clang8. I have not found any real solution for it.




matthias


--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ 
+49-176-38902045

Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!



- End forwarded message -

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: build is broken

[Martin Wilke]

Thanks.

On Wed, Oct 24, 2018 at 8:11 AM Warner Losh  wrote:

> Konstantin fixed it a few minutes ago.
>
> Warner
>
> On Tue, Oct 23, 2018, 6:09 PM Martin Wilke  wrote:
>
>> as of rev: 339671
>>
>> build fails
>>
>> https://dpaste.de/NCeV/raw
>>
>> - Miwi
>> --
>> +-oOO--(_)--OOo-+
>> With best Regards,
>> Martin Wilke (miwi_(at)_FreeBSD.org)
>>
>> Mess with the Best, Die like the Rest
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
>> "
>>
>

-- 
+-oOO--(_)--OOo-+
With best Regards,
Martin Wilke (miwi_(at)_FreeBSD.org)

Mess with the Best, Die like the Rest
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

build is broken

[Martin Wilke]

as of rev: 339671

build fails

https://dpaste.de/NCeV/raw

- Miwi
-- 
+-oOO--(_)--OOo-+
With best Regards,
Martin Wilke (miwi_(at)_FreeBSD.org)

Mess with the Best, Die like the Rest
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make distribution fails, A failure has been detected in another branch of the parallel make

[Martin Wilke]

r336743 CONFSGRP should be CONFSGROUP ?

> On 28 Jul 2018, at 1:30 AM, Charlie Li  wrote:
> 
> On 27/07/2018 13:21, Martin Wilke wrote:
>> I just upgraded a jail in poudriere with latest head, 
>> https://dpaste.de/bfTT/raw <https://dpaste.de/bfTT/raw>.
>> 
> I was about to inquire about this myself. Can additionally confirm this
> has been happening since at least r336735.
> 
> -- 
> Charlie Li
> Can't think of a witty .sigline today…
> 
> (This email address is for mailing list use only; replace local-part
> with vishwin for off-list communication)
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

make distribution fails, A failure has been detected in another branch of the parallel make

[Martin Wilke]

Hi,

I just upgraded a jail in poudriere with latest head, 
https://dpaste.de/bfTT/raw .

- Martin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: errors building 9-STABLE on recent HEAD

[Martin Wilke]

Yea thank you guys, I got it to work now.

- Martin
On Jul 16, 2013, at 11:42 AM, hiren panchasara hiren.panchas...@gmail.com 
wrote:

 On Mon, Jul 15, 2013 at 8:27 PM, wen heping wenhep...@gmail.com wrote:
 I build 9-STABLE on head today, while failed many times last month.
 
 There were some intermittent issues but *recent* stable/9 should build
 fine on *recent* head. If not, please report the errors and have sjg@
 look at them.
 
 Thanks,
 Hiren
 
 wen
 
 
 2013/7/16 Brooks Davis bro...@freebsd.org
 
 After not working for quite some time, I was able to build 9-STABLE last
 week.  I'm not sure if something changed in the branch or if the new
 current I'd updated to fixed it.
 
 -- Brooks
 
 On Sat, Jul 13, 2013 at 11:07:04PM +0800, Martin Wilke wrote:
 Hi,
 
 I see exactly the same error on pointyhat too, did you find any work
 around for that?
 
 On Jun 25, 2013, at 4:11 AM, Brooks Davis bro...@freebsd.org wrote:
 
 I recently upgraded my main buildbox from an ancient 9.0-STABLE
 snapshot
 to head and I've run into an issue building 9-STABLE on it.  Initally
 this was broken by the switch to bmake, but Simon committed a work
 around that and using the fmake port also works around it.  Now I'm
 seeing a strange error in yacc generated code.  I say strange because
 yacc is correctly being bootstrapped so we're using the expected
 version
 and not the one in HEAD.
 
 Does anyone have any insight into this issue?
 
 cc -O2 -pipe  -DBFD_DEFAULT_TARGET_SIZE=64 -I.
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../libbfd
 -I/home/bed22/obj/home/bed22/src-9/gnu/usr.bin/binutils/ld/../libbfd
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include
 -DTARGET=\x86_64-unknown-freebsd\ -DDEFAULT_EMULATION=\elf_x86_64_fbsd\
 -DSCRIPTDIR=\/usr/libdata\ -DBFD_VERSION_STRING=\2.17.50 [FreeBSD]
 2007-07-03\ -DBINDIR=\/usr/bin\ -DTARGET_SYSTEM_ROOT=\\
 -DTOOLBINDIR=\//usr/bin/libexec\ -D_GNU_SOURCE
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/bfd
 -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k
 -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
 -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c ldlex.c
 cc1: warnings being treated as errors
 stdout: In function 'yy_get_next_buffer':
 stdout:3229: warning: passing argument 2 of 'yy_input' from
 incompatible pointer type
 *** [ldlex.o] Error code 1
 
 Stop in /home/bed22/src-9/gnu/usr.bin/binutils/ld.
 *** [all] Error code 1
 
 Thanks,
 Brooks
 
 +-oOO--(_)--OOo-+
 With best Regards,
   Martin Wilke (miwi_(at)_FreeBSD.org)
 
 Mess with the Best, Die like the Rest
 
 
 
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
 


+-oOO--(_)--OOo-+
With best Regards,
   Martin Wilke (miwi_(at)_FreeBSD.org)

Mess with the Best, Die like the Rest

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: errors building 9-STABLE on recent HEAD

[Martin Wilke]

Hi,

I see exactly the same error on pointyhat too, did you find any work around for 
that?

On Jun 25, 2013, at 4:11 AM, Brooks Davis bro...@freebsd.org wrote:

 I recently upgraded my main buildbox from an ancient 9.0-STABLE snapshot
 to head and I've run into an issue building 9-STABLE on it.  Initally
 this was broken by the switch to bmake, but Simon committed a work
 around that and using the fmake port also works around it.  Now I'm
 seeing a strange error in yacc generated code.  I say strange because
 yacc is correctly being bootstrapped so we're using the expected version
 and not the one in HEAD.
 
 Does anyone have any insight into this issue?
 
 cc -O2 -pipe  -DBFD_DEFAULT_TARGET_SIZE=64 -I.  
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld 
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../libbfd 
 -I/home/bed22/obj/home/bed22/src-9/gnu/usr.bin/binutils/ld/../libbfd 
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include
  -DTARGET=\x86_64-unknown-freebsd\ -DDEFAULT_EMULATION=\elf_x86_64_fbsd\ 
 -DSCRIPTDIR=\/usr/libdata\ -DBFD_VERSION_STRING=\2.17.50 [FreeBSD] 
 2007-07-03\ -DBINDIR=\/usr/bin\ -DTARGET_SYSTEM_ROOT=\\ 
 -DTOOLBINDIR=\//usr/bin/libexec\ -D_GNU_SOURCE 
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld 
 -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/bfd 
 -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k 
 -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
 -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c ldlex.c
 cc1: warnings being treated as errors
 stdout: In function 'yy_get_next_buffer':
 stdout:3229: warning: passing argument 2 of 'yy_input' from
 incompatible pointer type
 *** [ldlex.o] Error code 1
 
 Stop in /home/bed22/src-9/gnu/usr.bin/binutils/ld.
 *** [all] Error code 1
 
 Thanks,
 Brooks

+-oOO--(_)--OOo-+
With best Regards,
   Martin Wilke (miwi_(at)_FreeBSD.org)

Mess with the Best, Die like the Rest

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: panic: solaris assert: sa.sa_magic == 0x2F505A (0x4d5ea364 == 0x2f505a), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c, line: 625

[Martin Wilke]

 = 0xfe00691a51f0, list_prev = 0xfe0042628ab0}, 
 {list_next = 0x0, list_prev = 0x0}, {list_next = 0x0, list_prev = 0x0}, 
 {list_next = 0x0, list_prev = 0x0}}, dn_mtx = {lock_object = {
  lo_name = 0x811da0bf dn-dn_mtx, lo_flags = 4096, lo_data 
 = 0, lo_witness = 0x0}, sx_lock = 1}, dn_dirty_records = {{list_size = 208, 
 list_offset = 0, list_head = {
list_next = 0xfe004261c470, list_prev = 0xfe004261c470}}, 
 {list_size = 208, list_offset = 0, list_head = {list_next = 
 0xfe004261c490, list_prev = 0xfe004261c490}}, {list_size = 208, 
  list_offset = 0, list_head = {list_next = 0xfe004261c4b0, list_prev 
 = 0xfe004261c4b0}}, {list_size = 208, list_offset = 0, list_head = 
 {list_next = 0xfe004261c4d0, 
list_prev = 0xfe004261c4d0}}}, dn_ranges = {{avl_root = 0x0, 
 avl_compar = 0x81106ec0 free_range_compar, avl_offset = 0, 
 avl_numnodes = 0, avl_size = 40}, {avl_root = 0x0, 
  avl_compar = 0x81106ec0 free_range_compar, avl_offset = 0, 
 avl_numnodes = 0, avl_size = 40}, {avl_root = 0x0, avl_compar = 
 0x81106ec0 free_range_compar, avl_offset = 0, 
  avl_numnodes = 0, avl_size = 40}, {avl_root = 0x0, avl_compar = 
 0x81106ec0 free_range_compar, avl_offset = 0, avl_numnodes = 0, 
 avl_size = 40}}, dn_allocated_txg = 3292, dn_free_txg = 0, 
  dn_assigned_txg = 0, dn_notxholds = {cv_description = 0x811da0dd 
 dn-dn_notxholds, cv_waiters = 0}, dn_dirtyctx = DN_UNDIRTIED, 
 dn_dirtyctx_firstset = 0x0, dn_tx_holds = {rc_count = 0}, 
  dn_holds = {rc_count = 3}, dn_dbufs_mtx = {lock_object = {lo_name = 
 0x811da0cb dn-dn_dbufs_mtx, lo_flags = 4096, lo_data = 0, 
 lo_witness = 0x0}, sx_lock = 1}, dn_dbufs = {list_size = 224, 
list_offset = 176, list_head = {list_next = 0xfe004261c5f8, list_prev 
 = 0xfe004261c5f8}}, dn_bonus = 0x0, dn_have_spill = 0, dn_zio = 
 0xfe00695af000, dn_oldused = 2560, dn_oldflags = 3, 
  dn_olduid = 1001, dn_oldgid = 1001, dn_newuid = 0, dn_newgid = 0, 
 dn_id_flags = 5, dn_zfetch = {zf_rwlock = {lock_object = {lo_name = 
 0x811dd156 zf-zf_rwlock, lo_flags = 4096, lo_data = 0, 
lo_witness = 0x0}, sx_lock = 1}, zf_stream = {list_size = 112, 
 list_offset = 88, list_head = {list_next = 0xfe004261c688, list_prev = 
 0xfe004261c688}}, zf_dnode = 0xfe004261c358, 
zf_stream_cnt = 0, zf_alloc_fail = 0}}
 
 The incremental was created with:
 zfs send -i @2013-03-28_14:21 tank/home/fk@2013-04-01_12:31
 piped through mbuffer and received with:
 zfs receive -v -u -F rockbox/backup/r500/tank/home/fk
 
 Reading the incremental directly from a file triggers the
 panic as as well, but sometimes it takes more than one attempt.
 
 The offending sa_magic in the panic message is always the same.
 
 The receiving pool appears to be okay:
 
 fk@r500 ~ $zpool status rockbox
  pool: rockbox
 state: ONLINE
 status: Some supported features are not enabled on the pool. The pool can
   still be used, but some features are unavailable.
 action: Enable all features using 'zpool upgrade'. Once this is done,
   the pool may no longer be accessible by software that does not support
   the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 0h3m with 0 errors on Mon Apr  1 13:57:35 2013
 config:
 
   NAME STATE READ WRITE CKSUM
   rockbox  ONLINE   0 0 0
 label/rockbox.eli  ONLINE   0 0 0
 
 errors: No known data errors
 
 The feature that isn't yet enabled is lz4 but after upgrading
 a copy of the pool the panic was still reproducible. On the
 receiving side gzip compression is enabled.
 
 Fabian

+-oOO--(_)--OOo-+
With best Regards,
   Martin Wilke (miwi_(at)_FreeBSD.org)

Mess with the Best, Die like the Rest

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

[CFT] Xorg 7.7 ready for testing!

[Martin Wilke]

Hi Fans,

The FreeBSD Xorg Team is pleased to announce Xorg 7.7 Release. We are
very happy to be able to Call for testing shortly after the Xorg team
annouced 7.7 release. This CFT is also open for discussion on how we
should move forward with xorg release as we are facing some issues and
we would like to ask for your opinion. Right now we have 2 existing
xorg versions in our Ports Tree. The situation is quite bad due to our
poor graphic card support. That means we do not have much choice but to
take it as how it is now. But with regards to mesa support, we have to
face some new challanges.

With the new mesa 8.0 release, accelerated support for a number of
older graphic cards was dropped. At the moment we are not sure how to
deal with that.We are thinking of just replacing mesa 7.11 with 8.0 or
making a new flag like WITH_MESA= 7.11.2 / 8.0 in combination with
WITH_NEW_XORG, and let the mesa 7.6.1 set as default together with the
old xorg version. Obviosly the latter option make the already complex
situation more complex. The problem is, users, especially  the new ones
can easily get confused with it. Another issue is, the packages.We
can't deliver a package set with the new Xorg releases. This means
users with new hardware will have to compile everything by themselves.
Though I'm totally fine with compiling, not everyone has the CPU power
to compile everything. What I'm trying to say is, I would love to see
the newer xorg released as the default version, but i know this will
break a lot of old hardware. The thing is, when we want to try to
become a Modern Operating System, I dont see any other way to make the
new xorg as default but to give Users the chance to compile the old
xorg with a flag like WITH_OLD_XORG.

Some notes regarding KMS support:
KMS Support has been completely migrated to FreeBSD 10. The MFC to 9
will come soon, that means so long its not MFC'd to 9-Stable, users
need to get the latest patch from our x11 mailing list.

This testing includes
* libdrm 2.4.34 (including KMS support)
* mesa 8.0.3
* full Xorg 7.7 release Change log
  http://www.x.org/releases/X11R7.7/changelog.html

Checkout Xorg Development Repo:
You will need to install devel/subversion in order to checkout the xorg
repo. Next, you will need to add WITH_NEW_XORG=yes in
your /etc/make.conf if you want to try out the new Xorg and mesa. Note
that if you are not qualified for the KMS patch, you shouldn’t use
WITH_NEW_XORG=yes because the old intel driver doesn’t build with the
new X server. If you are qualified, you should also set WITH_KMS=yes
in /etc/make.conf. Nvidia and ATI users should set WITH_NEW_XORG=yes.

svn co https://trillian.chruetertee.ch/svn/ports/trunk

A small merge script to merge the svn checkout into the real portstree
can be found here:

http://people.freebsd.org/~miwi/xorg/xorgmerge

The script is a modified version of the old kdemerge script. Please set
the KDEDIR variable to the path of your X.org ports. After merging, run
one of the following command, depending on which tool you use to manage
your installed packages.

portupgrade -af \*
portmaster -a


After installing these, you will have to rebuild all xf86-* ports. We
will bump all releated ports during the commit to the ports tree.

Roadmap:
Our current plan is to let the CFT running for a while, and see what
the outcome of the discussion above is. We hope to get a lot of
feedback to solve as many problems as possible. Also we are working on
the libglut to freeglut migration, this will definitely complete before
we import Xorg 7.7. So we still have enough time.  We are looking
forward for your feedback.

- miwi on behalf of the FreeBSD X11 Team

PS: Please reply only to x11@ thanks.

-- 
+--oOO--(_)--OOo+

Facebook:   miwi1
Twitter:miwi_

With best Regards,
Martin Wilke (miwi_(at)_FreeBSD.org)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

[CFT] Xorg Upgrade 7.5.2

[Martin Wilke]

Knock knock...

The X11 Team is pleased to announce the next round of Xorg updates.
Note that this is experimental so you really have to know what you are
doing, read UPDATING in the repository, and follow our exact
instructions. We are specifically looking for feedback from Intel, ATI
and NVIDIA users.

Summary of changes:

xf86-video-nouveau has been removed along with the WITHOUT_NOUVEAU
knob. We suggest switching to the nvidia blob. 

KMS Support [1]:
Unfortunately, the intel KMS driver will only work for the latest
FreeBSD 9-STABLE or 10-CURRENT users. The patch for HEAD current is
named all.13.1.patch. The higher the version the newer the patch is.
Other needed patches are already available in the Xorg update.

HEAD Users:
Get the latest patchset from Kib here: 
http://people.freebsd.org/~kib/drm/

9-STABLE Users: 
'meowthink' is currently maintaining the backport to 9 STABLE.
Make sure you have the latest FreeBSD 9-STABLE source.
Get the patch from here:
https://docs.google.com/leaf?id=0BxbPi2OX4_B-NWY3NWU3MzEtNDBjYy00NTljLThlZGItMWFlYjIyYjI4Yjk3hl=en_US

Rebuild your Kernel and reboot.

Known issuse:
There will be a patch reject in the sys/dev/drm/i915_suspend.c file.
The solution is to manually undo the expansion of the $FreeBSD: $
tag, so it only saysis $FreeBSD$.

Checkout Xorg Development Repo:
You will need to install devel/subversion in order to checkout the xorg
repo. Next, you will need to add WITH_NEW_XORG=yes in
your /etc/make.conf if you want to try out the new Xorg and mesa.

Intel users: note that if you are not qualified for the KMS patch, you
shouldn't use WITH_NEW_XORG=yes because the old intel driver doesn't
build with the new X server. If you are qualified, you should also set
WITH_KMS=yes in /etc/make.conf. 

svn co https://trillian.chruetertee.ch/svn/ports/tags/xorg_7_5_2

A small merge script to merge the svn checkout into the real portstree
can be found here:

http://people.freebsd.org/~miwi/xorg/xorgmerge

The script is a modified version of the old kdemerge script. Please set
the KDEDIR variable to the path of your X.org ports.

After merging, run one of the following command, depending on which
tool you use to manage your installed packages.

portupgrade -af \*
portmaster -a

After installing these, you will have to rebuild all xf86-* ports. We
will bump all related ports during the commit to the ports tree.

Roadmap:

Our current plan is to let the CFT running until the last weekend of
February. We hope to get a lot feedback to solve as many problems as
possible. So please help us to get the best xorg update ever in!


Links:
http://wiki.freebsd.org/Intel_GPU [1]
http://wiki.freebsd.org/Xorg
http://miwi.bsdcrew.de/2012/02/working-on-xorg-stuff/

Your FreeBSD Xorg Team

PS: Please reply to the x11@ mailing list. Cross posted due to the
potentially disruptive nature of the change and need to get a wide
variety of testers.

-- 
+--oOO--(_)--OOo+
With best Regards,
Martin Wilke (miwi_(at)_FreeBSD.org)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: firefox stuck in libthr

[Martin Wilke]

Hi Steve,

at least it would be helpful to know what FBSD Version u are using.

- Martin

On Nov 25, 2011, at 3:10 AM, Steve Kargl wrote:

 Firefox seems to have got stuck inside libthr.
 
 (gdb) 
 #0  0x49d307d3 in ?? () from /lib/libthr.so.3
 #1  0x49d2a582 in ?? () from /lib/libthr.so.3
 #2  0x49d2fed2 in ?? () from /lib/libthr.so.3
 #3  0x49d32eb5 in ?? () from /lib/libthr.so.3
 #4  0x49ceab82 in pthread_cond_timedwait () from /lib/libc.so.7
 #5  0x49972865 in ?? () from /usr/local/lib/libplds4.so.1
 #6  0x4b7f8784 in ?? ()
 #7  0x4b7f27e0 in ?? ()
 #8  0xbe8ededc in ?? ()
 #9  0x49ce9914 in pthread_getspecific () from /lib/libc.so.7
 #10 0x499736ea in PR_WaitCondVar () from /usr/local/lib/libplds4.so.1
 #11 0x483f91bf in ?? () from /usr/local/lib/firefox/libxul.so
 #12 0x4b7f8780 in ?? ()
 #13 0x000493e0 in ?? ()
 #14 0xbe8edf34 in ?? ()
 #15 0x in ?? ()
 
 I'll see if I can get more information once I rebuild
 libthr with debugging symbols and firefox as well.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

gmirror failed with error 19.

[Martin Wilke]

Hi,

I face the same error since upgrade from 8.2 to 9.0RC1, is there any way to fix 
that?

thx Martin___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

9.0 B1 Panic

[Martin Wilke]

9.0 Beta1 Panic

Hi guys,

I just downloaded and install  9.0 BETA1 but it panics on ACPI. Please view 
attached screenshot for the error. If you need more information, do let us know.

Thanks.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 9.0 B1 Panic

[Martin Wilke]

On Aug 2, 2011, at 6:58 PM, Lystopad Olexandr wrote:

 Hello, Martin Wilke!
 
 On Tue, Aug 02, 2011 at 12:41:29PM +0800
 m...@freebsd.org wrote about 9.0 B1 Panic:
 9.0 Beta1 Panic
 
 Hi guys,
 
 I just downloaded and install  9.0 BETA1 but it panics on ACPI. Please view 
 attached screenshot for the error. If you need more information, do let us 
 know.
 
 There no attachments in your mail.


Erms Sorry forgot about that.

http://people.freebsd.org/~miwi/90b1.png

 
 -- 
 Lystopad Olexandr 

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 9.0 B1 Panic

[Martin Wilke]

On Aug 3, 2011, at 12:56 AM, John Baldwin wrote:

 On Tuesday, August 02, 2011 8:58:10 am Martin Wilke wrote:
 
 On Aug 2, 2011, at 6:58 PM, Lystopad Olexandr wrote:
 
 Hello, Martin Wilke!
 
 On Tue, Aug 02, 2011 at 12:41:29PM +0800
 m...@freebsd.org wrote about 9.0 B1 Panic:
 9.0 Beta1 Panic
 
 Hi guys,
 
 I just downloaded and install  9.0 BETA1 but it panics on ACPI. Please 
 view attached screenshot for the error. If you need more information, do let 
 us know.
 
 There no attachments in your mail.
 
 
 Erms Sorry forgot about that.
 
 http://people.freebsd.org/~miwi/90b1.png
 
 Can you get a stack trace?

Hi,
unfortunately no, because the system freeze few sec after the panic.

- Martin

 
 -- 
 John Baldwin

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

FreeBSD 8.1 re0 shows half duplex

[Martin Wilke]

Howdy Guys,

I have a strange problem, I'm on FreeBSD 8.1 and ifconfig re0 shows
half-duplex (see output) and the download speed
is damn slow, maximum 20 kbps. I'm not sure how to debug this so it would be
nice if someone can
help me to fix it.

When i change it manually via command line, the media line appeared to have
2 entries -- full-duplex and half-duplex

re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC
ether 6c:62:6d:90:6e:63
inet XX netmask 0xffc0 broadcast XX
media: Ethernet 100baseTX full-duplex (100baseTX half-duplex)
status: active


main# uname -a
FreeBSD  8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #0: Fri Jan 14 04:15:56
UTC 2011 root@freebsd:/usr/obj/usr/src/sys/GENERIC amd64
main#

# dmesg
re0: RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet port
0xe800-0xe8ff mem 0xfbeff000-0xfbef,0xf6ff-0xf6ff irq 16 at
device 0.0 on pci6
re0: Using 1 MSI messages
re0: Chip rev. 0x3c00
re0: MAC rev. 0x0040
miibus0: MII bus on re0
re0: Ethernet address: 6c:62:6d:90:6e:63
re0: [FILTER]
re0: link state changed to UP
main#

# pciconf -lv
re0@pci0:6:0:0: class=0x02 card=0x75221462 chip=0x816810ec rev=0x02
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
class = network
subclass = ethernet


# dmideco
http://nopaste.unixfreunde.de/46256
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org