Re: perl 5.16 on current
AN wrote on 09.10.2012 22:16: Has anyone upgraded to Perl 5.16.0? Are there any outstanding issues or problems? Any packages that don't build? Thanks in advance for any feedback. Using it since August, had no problems with it. But I don't use it for programming, only for usual system/desktop stuff. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: system hangs on shutdown while on wireless (ath) (Was: drm2 and the kernel messages on shutdown)
Ruslan Mahmatkhanov wrote on 18.06.2012 13:10: Ivan Klymenko wrote on 18.06.2012 13:02: В Mon, 18 Jun 2012 12:35:33 +0400 Ruslan Mahmatkhanov пишет: Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. PS. I'm now subscribed to current@. So do not need to approve my previous message, that's waiting for moderator approval. Dear Ruslan. Your problems hang your laptop is not associated with the transition to drm2. And you can see this - when the downgrade to the SVN revision r236313 Your problems are now committing to this http://svnweb.freebsd.org/base?view=revision&revision=236317 You can check it and make sure my right. Good luck Thanks Ivan, I'll check it out. But the request in subject line is still valid for me, because the current state make me feels like.. uhmm.. a blind kitten :) Hi, I still didn't tried to revert this change to check if it the reason. But I realized that I only got this issue when I'm on wireless. And I can 100% reproduce this. When using ethernet (re) - system shuts down just fine. When using wireless (ath) - it hanging forever. So it seems like ath deadlock or something (cc:ing Adrian). Would you please provide me with instructions on how to debug this, or what info should I provide to you to realize this. Thanks. ath0@pci0:37:0:0: class=0x028000 card=0x1461103c chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9285 Wireless Network Adapter (PCI-Express)' class = network My -current is from Sat Jul 14 12:15:20 2012 (svn #238449). -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
drm2 and the kernel messages on shutdown
Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: drm2 and the kernel messages on shutdown
Eric Masson wrote on 18.06.2012 13:08: Ruslan Mahmatkhanov writes: Hi, I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. As stated in the wiki page, syscons is not integrated with kms atm, so you need a serial console to get system messages. http://wiki.freebsd.org/Intel_GPU Éric Masson Ok, but in the earlier revision of this page or in some heads-up message in mailing list there was a note about that, that kernel messages are disabled just for development convenience, so this is main reason why I ever asked that. So, since there is some technical restriction about that, I would to shut up and wait. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: drm2 and the kernel messages on shutdown
Ivan Klymenko wrote on 18.06.2012 13:02: В Mon, 18 Jun 2012 12:35:33 +0400 Ruslan Mahmatkhanov пишет: Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. PS. I'm now subscribed to current@. So do not need to approve my previous message, that's waiting for moderator approval. Dear Ruslan. Your problems hang your laptop is not associated with the transition to drm2. And you can see this - when the downgrade to the SVN revision r236313 Your problems are now committing to this http://svnweb.freebsd.org/base?view=revision&revision=236317 You can check it and make sure my right. Good luck Thanks Ivan, I'll check it out. But the request in subject line is still valid for me, because the current state make me feels like.. uhmm.. a blind kitten :) -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
drm2 and the kernel messages on shutdown
Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. PS. I'm now subscribed to current@. So do not need to approve my previous message, that's waiting for moderator approval. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: lock order reversal in sys/kern/vfs_mount.c
John Baldwin wrote on 08.06.2012 18:45: On Friday, June 08, 2012 4:21:34 am Ruslan Mahmatkhanov wrote: Ruslan Mahmatkhanov wrote on 08.06.2012 12:10: Good day, After updating to yesterdays -current, I got this on boot: lock order reversal: 1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254 2nd 0xfe0007ed9478 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2158 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2c witness_checkorder() at witness_checkorder+0x853 __lockmgr_args() at __lockmgr_args+0x113a vop_stdlock() at vop_stdlock+0x39 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xbf _vn_lock() at _vn_lock+0x47 vget() at vget+0x7b devfs_allocv() at devfs_allocv+0x13f devfs_root() at devfs_root+0x4d dounmount() at dounmount+0x45c vfs_unmountall() at vfs_unmountall+0x4c kern_reboot() at kern_reboot+0x84b sys_reboot() at sys_reboot+0x68 amd64_syscall() at amd64_syscall+0x2e0 Xfast_syscall() at Xfast_syscall+0xf7 --- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x40ebbc, rsp = 0x7fffd6c8, rbp = 0x65 --- Reverting to old kernel (that was built about a week ago) helped to avoid this. Any thoughts? And this one comes up with the recent update too: driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) cpu0: on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu1: on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu2: on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu3: on acpi0 What the additional info should I supply to understand what's wrong? Here is my full dmesg; http://people.freebsd.org/~rm/dmesg.txt Is this a verbose boot? Also, can you try this to get more details in the log message: Sorry for delay. This particular panic had triggered by intel video driver (x11-drivers/xf86-video-intel v 2.19.0). After I rebuild it with new kernel, all is going fine. The panic appeared after GDM login, and I was able to catch some driver-related errors in xorg log. Thanks John. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: lock order reversal in sys/kern/vfs_mount.c
Ruslan Mahmatkhanov wrote on 08.06.2012 12:10: Good day, After updating to yesterdays -current, I got this on boot: lock order reversal: 1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254 2nd 0xfe0007ed9478 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2158 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2c witness_checkorder() at witness_checkorder+0x853 __lockmgr_args() at __lockmgr_args+0x113a vop_stdlock() at vop_stdlock+0x39 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xbf _vn_lock() at _vn_lock+0x47 vget() at vget+0x7b devfs_allocv() at devfs_allocv+0x13f devfs_root() at devfs_root+0x4d dounmount() at dounmount+0x45c vfs_unmountall() at vfs_unmountall+0x4c kern_reboot() at kern_reboot+0x84b sys_reboot() at sys_reboot+0x68 amd64_syscall() at amd64_syscall+0x2e0 Xfast_syscall() at Xfast_syscall+0xf7 --- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x40ebbc, rsp = 0x7fffd6c8, rbp = 0x65 --- Reverting to old kernel (that was built about a week ago) helped to avoid this. Any thoughts? And this one comes up with the recent update too: driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) cpu0: on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu1: on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu2: on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu3: on acpi0 What the additional info should I supply to understand what's wrong? Here is my full dmesg; http://people.freebsd.org/~rm/dmesg.txt -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
lock order reversal in sys/kern/vfs_mount.c
Good day, After updating to yesterdays -current, I got this on boot: lock order reversal: 1st 0xfe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254 2nd 0xfe0007ed9478 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2158 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2c witness_checkorder() at witness_checkorder+0x853 __lockmgr_args() at __lockmgr_args+0x113a vop_stdlock() at vop_stdlock+0x39 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xbf _vn_lock() at _vn_lock+0x47 vget() at vget+0x7b devfs_allocv() at devfs_allocv+0x13f devfs_root() at devfs_root+0x4d dounmount() at dounmount+0x45c vfs_unmountall() at vfs_unmountall+0x4c kern_reboot() at kern_reboot+0x84b sys_reboot() at sys_reboot+0x68 amd64_syscall() at amd64_syscall+0x2e0 Xfast_syscall() at Xfast_syscall+0xf7 --- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x40ebbc, rsp = 0x7fffd6c8, rbp = 0x65 --- Reverting to old kernel (that was built about a week ago) helped to avoid this. Any thoughts? -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
Problem with kernel memory dump after panic
Hi! I'm getting if_bwn panics with high traffic on -CURRENT: http://lists.freebsd.org/pipermail/freebsd-mobile/2011-November/012481.html And now i realize that it probably may be also reproduced on earlier FreeBSD versions, because i didn't do such high-trafficking before, so i got an illusion that this is -CURRENT-specific problem - it's an assumption nevertheless. I'm tried to investigate the causes (well, actually Adrian (adrian) tried :)), and i got some problem when i try to show backtrace to him: smeshariki3# kgdb -q -c /var/crash/vmcore.1 /boot/kernel/kernel (no debugging symbols found)...#0 0xc06f6aad in doadump () (kgdb) bt #0 0xc06f6aad in doadump () #1 0xc0af42e0 in show_busybufs () #2 0xefd25620 in ?? () #3 0xc06f7012 in kern_reboot () Previous frame inner to this frame (corrupt stack?) (kgdb) I have all the debugging disabled in my kernel, but Adrian claims that it still should carry some valuable data in backtrace, that is missed now, and he suggested me to ask freebsd-current@ about this. So I'm here. "Where is my backtrace, dude?" (C) PS. I have system sources, my kernel is in sync with world and third-party modules. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: [UPDATE] Re: Update on ports on 10.0
Erwin Lansing wrote on 27.10.2011 14:21: On Fri, Oct 21, 2011 at 12:44:34PM +0300, Ion-Mihai Tetcu wrote: What, on the other hand, makes sense is to have the fix that should include: a) a KNOB (WITH_FBSD10_FIX or similar), b) that only is run from bsd.port.mk when OSVERSION>100 c) runs the latest version of the above patch. The KNOB's existence allow us to turn on the fix only for broken ports, and easily know what these broken ports are -- so we can poke maintainers from time to time about upstream fixes, ... Erwin is currently running a build on i386-10 with this and the following patches: - bsd.port.mk patch from beat (based on ed@, jilles@ and stas@ patches) - python patch from beat - python patch from linimon - WITH_FBSD10_FIX in: - textproc/expat2 - devel/pcre - devel/libtool - audio/libogg Results by Monday. These patches have now been committed to the tree, notably with lang/python27 missing in the above list but was included as well. There have been some proposals already and we can now incrementally improve the workaround and, more importantly, start fixing individual ports. Please note that the patch tries to balance between being a general enough fix to make it easy to get a working system running while not just swiping the whole issue under the rug and forget about it until the next release cycle. Make sure to send any fixes upstream to the hack can be removed from the ports again. Thanks for all your patience and thanks for all those involved, especially beat who sent many patches and improvements. Erwin About devel/libtool fix. Why to not update it to 2.4.2 where this was fixed upstream? I mean http://bugs.freebsd.org/162012 -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
locate broken on CURRENT
Good day, after recent code syncing and updating to FreeBSD 10.0-CURRENT i've got this problem: [rm@smeshariki3 ~]> locate some-word locate: integer out of +-MAXPATHLEN (1024): 1037 Dunno if this is known problem. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: siba_bwn in GENERIC
Adrian Chadd wrote on 11.09.2011 04:56: Please submit a PR so I/others don't forget. Then just follow through with an email to me w/ the PR number. Thanks, Adrian Done. http://bugs.freebsd.org/160652 -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: siba_bwn in GENERIC
Adrian Chadd wrote on 26.08.2011 15:15: On 26 August 2011 15:14, Ruslan Mahmatkhanov wrote: Good day! Right now we have this line in GENERIC: #device bwn # Broadcom BCM43xx wireless NICs From user POV all he need to do to make his broadcom wifi work, is to uncomment this line and recompile his kernel. But this actually not sufficient - he also need to add device siba_bwn, and then install net/bwn-firmware-kmod. But he will know that after recompiling his kernel when his wireless adapter will not work as expected :). So may be we need to also add siba_bwn (commented out by default) in GENERIC and some reference about net/bwn-firmware-kmod? I think it's a good idea, along with any other documentation related changes that need to occur. Thanks, Adrian Adrian, is there any hope this change will go to 9.0-R? Should i submit pr for that? -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
siba_bwn in GENERIC
Good day! Right now we have this line in GENERIC: #device bwn # Broadcom BCM43xx wireless NICs From user POV all he need to do to make his broadcom wifi work, is to uncomment this line and recompile his kernel. But this actually not sufficient - he also need to add device siba_bwn, and then install net/bwn-firmware-kmod. But he will know that after recompiling his kernel when his wireless adapter will not work as expected :). So may be we need to also add siba_bwn (commented out by default) in GENERIC and some reference about net/bwn-firmware-kmod? -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: [Testing wanted] USB patch for HAL
24.06.2011 17:31, Hans Petter Selasky пишет: Hi, It appears there are some bugs in the USB2 HAL implementation. For example the parent USB device is not always correctly set and there are problems with dynamic attach/detach of USB devices in hald. For users of 9-current and 8-stable: Copy the attached file to /usr/ports/sysutils/hal/files/ Then rebuild HAL. Does it fix any USB/HAL related problems? For example related to multimedia/webcamd, lshal, mouse, keyboard etc. --HPS Thanks a lot! My mouse, usb-sticks and usb-hdd now appeared again after reattach with this patch how it was before. It's on 9-current. PS. Maybe there is the same magic that will make my battery indicator state changes when i replug AC power? :) I understand that this not related with USB2, but it worked before on 8-stable. Does anybody expecting the same trouble? -- Regards, Ruslan ___ 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"
