Re: pkgsrc reports
Rumko, the patch that was proposed by OBATA Akio / oba...@netbsd.org works correctly and is a good solution. I've also submitted it upstream[1]. The remaining build issue is something that needs investigation and affects a number of packages. It might well not be mono related, so there is absolutely no reason to hold off this patch. The other issue happens due to the linker script forcing the __progname symbol to be local by using local: *. Similar things happen to xchat and asterisk, at least. This issue might well be in other toolsuites, since NetBSD doesn't seem to be affected. Cheers, Alex [1]: http://bugzilla.xamarin.com/show_bug.cgi?id=123 On 22 May 2011 17:21, Rumko rum...@gmail.com wrote: On Sunday 15. of May 2011 08:45:25 Francois Tigeot wrote: On Sat, May 14, 2011 at 07:43:45PM +0200, Rumko wrote: Francois Tigeot wrote: On Wed, May 11, 2011 at 07:56:29AM +0100, Alex Hornung wrote: It seems that to get mono building again we just need a simple patch (upstream and pkgsrc ideally :)) to mono/utils/mono-sigcontext.h, as well as undefining the defined(UCONTEXT_GREGS) (config? Makefile?) option. I've opened a PR with patch a month ago: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=44846 It has been assigned to dfly-pkg-people@ and never been committed afaik. AFAIR I was told that the patch in the PR did not in fact fix the build, it just made it move along further. Please finish the patches or if they in fact do fix the build, nudge me again and I'll look into it. The next error is unrelated and is possibly caused by a problem in our toolchain. Please look into the error in order to make the package actually build. Now if you want to sit on patches so be it; I won't waste anymore time trying to fix mono. Have you upstreamed these patches? P.S.: IIRC I saw some mono related commits lately in pkgsrc, maybe the patches now fix all build-time errors? -- Regards, Rumko
Re: intr 11 livelock limit messages
Sepherosa Ziehau wrote: On Sun, Jul 31, 2011 at 12:49 AM, Mark Doe mark.doe.p...@gmail.com wrote: Edward M. wrote: On 07/30/11 06:05, Pang Yan Han wrote: Hi guys, I've just installed DragonFlyBSD 2.10.1 and kept seeing the below messages at some point of booting: intr 11 at 40001/4 hz, livelocked limit engaged! intr 11 at x/2 hz, livelock removed It alternates between the above 2 messages and occurs without stop, even after I've logged in. May I know what is causing this and how can I solve it? Thanks. I was also getting getting the same messages, but they stop, when i switched from 32bit to 64 bit DragonFlyBSD.install. Regards, Edward I am still getting this messages on a 64Bit box (2.11-DEVEL). They start when i plugin a network card (doesnt matter which one, tested with 4 different brands) AND running on IDE mode instead of AHCI. Please post the boot_verbose dmesg, vmstat -iv, acpidump -t and acpidump -v Best Regards, sephe please review vmstat -iv, acpidump -t and acpidump -v http://paste.kde.org/104041/ and the dmesg.boot -v http://paste.kde.org/104059/
Re: intr 11 livelock limit messages
Sepherosa Ziehau wrote: On Sun, Jul 31, 2011 at 12:49 AM, Mark Doe mark.doe.p...@gmail.com wrote: Edward M. wrote: On 07/30/11 06:05, Pang Yan Han wrote: Hi guys, I've just installed DragonFlyBSD 2.10.1 and kept seeing the below messages at some point of booting: intr 11 at 40001/4 hz, livelocked limit engaged! intr 11 at x/2 hz, livelock removed It alternates between the above 2 messages and occurs without stop, even after I've logged in. May I know what is causing this and how can I solve it? Thanks. I was also getting getting the same messages, but they stop, when i switched from 32bit to 64 bit DragonFlyBSD.install. Regards, Edward I am still getting this messages on a 64Bit box (2.11-DEVEL). They start when i plugin a network card (doesnt matter which one, tested with 4 different brands) AND running on IDE mode instead of AHCI. Please post the boot_verbose dmesg, vmstat -iv, acpidump -t and acpidump -v Best Regards, sephe the normal dmesg reveals that livelock starts immediately after getting networkcard em0 (doesnt matter which brand here) active! dmesg | tail -150 snip ar0: 1907739MB FreeBSD PseudoRAID RAID0+1 (stripe 128 KB) status: READY ar0: 3907049984 sectors [46594C/255H/63S] subdisks defined as: ar0: disk0 READY (master) using ad8 at ata4-master ar0: disk1 READY (master) using ad10 at ata5-master ar0: disk2 READY (mirror) using ad12 at ata6-master ar0: disk3 READY (mirror) using ad14 at ata7-master ** ATA PseudoRAID ar1 Metadata ** = format Intel MatrixRAID typeRAID1 flags 0x01 1READY magic_0 0x4e318ed5 magic_1 0x generation 1 total_sectors 976773165 offset_sectors 0 heads 255 sectors 63 cylinders 60801 width 1 interleave 8 total_disks 2 disk 0: flags = 0x0b bONLINE,ASSIGNED,PRESENT ad16: sectors 976773165 disk 1: flags = 0x0b bONLINE,ASSIGNED,PRESENT ad18: sectors 976773165 = No policy for ar1 specified, or policy not found disk scheduler: set policy of ar1 to noop ar1: 476940MB Intel MatrixRAID RAID1 status: READY ar1: 976773165 sectors [60801C/255H/63S] subdisks defined as: ar1: disk0 READY (master) using ad16 at ata8-master ar1: disk1 READY (mirror) using ad18 at ata9-master ar0: Found GPT in slice #1 Mounting root from hammer:serno/WD-WCAV9L391158.s1d tryroot serno/WD-WCAV9L391158.s1d HAMMER(ROOT) recovery check seqno=01341e57 HAMMER(ROOT) recovery range 3000136c4a30-3000136c4a30 HAMMER(ROOT) recovery nexto 3000136c4a30 endseqno=01341e58 HAMMER(ROOT) mounted clean, no recovery needed Mounting devfs start_init: trying /sbin/init em0: Link is up 1000 Mbps Full Duplex intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 6/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 3/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 3/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 404/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 404/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at
Re: intr 11 livelock limit messages
Hi Sepherosa, Turns out it's me using a UP kernel when I'm supposed to be using a SMP one. Sorry for the noise. On Sun, Jul 31, 2011 at 7:07 PM, Mark Doe mark.doe.p...@gmail.com wrote: Sepherosa Ziehau wrote: On Sun, Jul 31, 2011 at 12:49 AM, Mark Doe mark.doe.p...@gmail.com wrote: Edward M. wrote: On 07/30/11 06:05, Pang Yan Han wrote: Hi guys, I've just installed DragonFlyBSD 2.10.1 and kept seeing the below messages at some point of booting: intr 11 at 40001/4 hz, livelocked limit engaged! intr 11 at x/2 hz, livelock removed It alternates between the above 2 messages and occurs without stop, even after I've logged in. May I know what is causing this and how can I solve it? Thanks. I was also getting getting the same messages, but they stop, when i switched from 32bit to 64 bit DragonFlyBSD.install. Regards, Edward I am still getting this messages on a 64Bit box (2.11-DEVEL). They start when i plugin a network card (doesnt matter which one, tested with 4 different brands) AND running on IDE mode instead of AHCI. Please post the boot_verbose dmesg, vmstat -iv, acpidump -t and acpidump -v Best Regards, sephe the normal dmesg reveals that livelock starts immediately after getting networkcard em0 (doesnt matter which brand here) active! dmesg | tail -150 snip ar0: 1907739MB FreeBSD PseudoRAID RAID0+1 (stripe 128 KB) status: READY ar0: 3907049984 sectors [46594C/255H/63S] subdisks defined as: ar0: disk0 READY (master) using ad8 at ata4-master ar0: disk1 READY (master) using ad10 at ata5-master ar0: disk2 READY (mirror) using ad12 at ata6-master ar0: disk3 READY (mirror) using ad14 at ata7-master ** ATA PseudoRAID ar1 Metadata ** = format Intel MatrixRAID typeRAID1 flags 0x01 1READY magic_0 0x4e318ed5 magic_1 0x generation 1 total_sectors 976773165 offset_sectors 0 heads 255 sectors 63 cylinders 60801 width 1 interleave 8 total_disks 2 disk 0: flags = 0x0b bONLINE,ASSIGNED,PRESENT ad16: sectors 976773165 disk 1: flags = 0x0b bONLINE,ASSIGNED,PRESENT ad18: sectors 976773165 = No policy for ar1 specified, or policy not found disk scheduler: set policy of ar1 to noop ar1: 476940MB Intel MatrixRAID RAID1 status: READY ar1: 976773165 sectors [60801C/255H/63S] subdisks defined as: ar1: disk0 READY (master) using ad16 at ata8-master ar1: disk1 READY (mirror) using ad18 at ata9-master ar0: Found GPT in slice #1 Mounting root from hammer:serno/WD-WCAV9L391158.s1d tryroot serno/WD-WCAV9L391158.s1d HAMMER(ROOT) recovery check seqno=01341e57 HAMMER(ROOT) recovery range 3000136c4a30-3000136c4a30 HAMMER(ROOT) recovery nexto 3000136c4a30 endseqno=01341e58 HAMMER(ROOT) mounted clean, no recovery needed Mounting devfs start_init: trying /sbin/init em0: Link is up 1000 Mbps Full Duplex intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 6/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 3/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 4/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 5/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 0/2 hz, livelock removed intr 19 at 40001/4 hz, livelocked limit engaged! intr 19 at 3/2 hz, livelock
