Bug#667552: kfreebsd-image-9.0-1-686: fails to initialize 3ware 7810 RAID controller
Robert Millan writes: > El 4 d’abril de 2012 22:50, Christoph Egger ha escrit: >> This box has a Disk array connected to a 3ware Inc. 7810 RAID >> controller card and is supposed to boot from it This is working all >> fine with the Debian 8.2 and 8.3 kernels as well as the 9.0-RELEASE >> one from kfreebsd-downloader. > > Does it happen with kfreebsd-10? kfreebsd-10 boots fine Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vclebjvv@hepworth.siccegge.de
Bug#667552: marked as done (kfreebsd-image-9.0-1-686: fails to initialize 3ware 7810 RAID controller)
Your message dated Thu, 05 Apr 2012 11:54:15 +0200 with message-id <87398ibj20@hepworth.siccegge.de> and subject line Re: Bug#667552: kfreebsd-image-9.0-1-686: fails to initialize 3ware 7810 RAID controller has caused the Debian Bug report #667552, regarding kfreebsd-image-9.0-1-686: fails to initialize 3ware 7810 RAID controller to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kfreebsd-image-9.0-1-686 Version: 9.0-1 Severity: important Hi! This box has a Disk array connected to a 3ware Inc. 7810 RAID controller card and is supposed to boot from it This is working all fine with the Debian 8.2 and 8.3 kernels as well as the 9.0-RELEASE one from kfreebsd-downloader. However when using the 9.0 debian kernel the box is instantly resetting when it gets to initialize the Controller. I'll try to decode some of the last console output but it's quite hard as it basically instantly reboots when reaching this point. % sudo sysctl dev.twe dev.twe.0.%desc: 3ware Storage Controller. Driver version 1.50.01.002 dev.twe.0.%driver: twe dev.twe.0.%location: slot=3 function=0 dev.twe.0.%pnpinfo: vendor=0x13c1 device=0x1001 subvendor=0x13c1 subdevice=0x1001 class=0x010400 dev.twe.0.%parent: pci1 % dmesg twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xb800-0xb80f mem 0xfe8ffc00-0xfe8ffc0f,0xfe00-0xfe7f irq 20 at device 3.0 on pci1 twe0: [GIANT-LOCKED] twe0: [ITHREAD] twe0: AEN: twe0: 8 ports, Firmware FE7X 1.05.00.068, BIOS BE7X 1.08.00.048 Failing boot: twe0: FATAL STATUS BIT(S) 20 twe0: status Feel free to try and read more on http://people.debian.org/~christoph/3ware-raid-kfreebsd.jpg Regards Christoph -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-i386 (i386) Kernel: kFreeBSD 8.3-0-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.0-1-686 depends on: ii devd 8.2+ds3-2 ii freebsd-utils 8.2+ds3-2 ii kbdcontrol 9.0+ds1-1 ii kldutils 9.0+ds1-1 Versions of packages kfreebsd-image-9.0-1-686 recommends: ii libc0.1-i686 2.13-27 kfreebsd-image-9.0-1-686 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 9.0-2 Christoph Egger writes: > Robert Millan writes: >> El 4 d’abril de 2012 22:50, Christoph Egger ha escrit: >>> This box has a Disk array connected to a 3ware Inc. 7810 RAID >>> controller card and is supposed to boot from it This is working all >>> fine with the Debian 8.2 and 8.3 kernels as well as the 9.0-RELEASE >>> one from kfreebsd-downloader. >> >> Does it happen with kfreebsd-10? > > kfreebsd-10 boots fine For a reason not clear to me from the changelog the kfreebsd-9 kernel from unstable (and not from testing) works here as well and the server boots. Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer --- End Message ---
Re: Bug#654783: python2.7: FTBFS(kfreebsd): testsuite hang
Hi,
With eglibc patched with Robert's timer.diff I still see a hang at
test_signal, when building python2.7-2.7.3~rc2 on kfreebsd-i386
(8.3~svn230343-1 686 kernel).
Skipping that test, I then experience a hang at test_socket. More test
failures are in the attached file (probably less serious, known issues).
test_io was disabled, but so far it has been working. I'll try running
it a few more times with randomised test order (-r option).
I also tried the disabled test_bsddb3 which still fails.
And just to confirm I that I'm really using the patched eglibc:
> $ ldd /home/steven/python2.7-2.7.3~rc2/build-debug/python
> libpthread.so.0 => /lib/i386-kfreebsd-gnu/i686/cmov/libpthread.so.0
> (0x2102b000)
> libdl.so.2 => /lib/i386-kfreebsd-gnu/i686/cmov/libdl.so.2 (0x21041000)
> libutil.so.1 => /lib/i386-kfreebsd-gnu/i686/cmov/libutil.so.1
> (0x21045000)
> libssl.so.1.0.0 => /usr/lib/i386-kfreebsd-gnu/libssl.so.1.0.0
> (0x21049000)
> libcrypto.so.1.0.0 => /usr/lib/i386-kfreebsd-gnu/libcrypto.so.1.0.0
> (0x210a8000)
> libz.so.1 => /usr/lib/i386-kfreebsd-gnu/libz.so.1 (0x21282000)
> libm.so.1 => /lib/i386-kfreebsd-gnu/i686/cmov/libm.so.1 (0x2129a000)
> libc.so.0.1 => /lib/i386-kfreebsd-gnu/i686/cmov/libc.so.0.1
> (0x212c)
> /lib/ld.so.1 (0x01001000)
> $ objdump -d /lib/i386-kfreebsd-gnu/i686/cmov/libc.so.0.1 | grep 'ktimer_.*:$'
> 000fbff0 <__syscall_ktimer_create>:
> 000fc020 <__syscall_ktimer_gettime>:
> 000fc050 <__syscall_ktimer_settime>:
> 000fc080 <__syscall_ktimer_getoverrun>:
> 000fc0b0 <__syscall_ktimer_delete>:
> $ grep ktimer /lib/i386-kfreebsd-gnu/ -R
> Binary file /lib/i386-kfreebsd-gnu/libc-2.13.so matches
> Binary file /lib/i386-kfreebsd-gnu/librt-2.13.so matches
> Binary file /lib/i386-kfreebsd-gnu/libc.so.0.1 matches
> Binary file /lib/i386-kfreebsd-gnu/librt.so.1 matches
> Binary file /lib/i386-kfreebsd-gnu/i686/cmov/libc-2.13.so matches
> Binary file /lib/i386-kfreebsd-gnu/i686/cmov/librt-2.13.so matches
> Binary file /lib/i386-kfreebsd-gnu/i686/cmov/libc.so.0.1 matches
> Binary file /lib/i386-kfreebsd-gnu/i686/cmov/librt.so.1 matches
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
==
FAIL: test_parse_makefile_base
(distutils.tests.test_sysconfig.SysconfigTestCase)
--
Traceback (most recent call last):
File
"/home/steven/python2.7-2.7.3~rc2/Lib/distutils/tests/test_sysconfig.py", line
60, in test_parse_makefile_base
'OTHER': 'foo'})
AssertionError: {'VAR': '$OTHER', 'CONFIG_ARGS': "'--arg1=optarg1' 'ENV=LIB'",
'OTHER': 'foo'} != {'CONFIG_ARGS': "'--arg1=optarg1' 'ENV=LIB'", 'OTHER': 'foo'}
- {'CONFIG_ARGS': "'--arg1=optarg1' 'ENV=LIB'", 'OTHER': 'foo', 'VAR': '$OTHER'}
? -
+ {'CONFIG_ARGS': "'--arg1=optarg1' 'ENV=LIB'", 'OTHER': 'foo'}
==
FAIL: test_parse_makefile_literal_dollar
(distutils.tests.test_sysconfig.SysconfigTestCase)
--
Traceback (most recent call last):
File
"/home/steven/python2.7-2.7.3~rc2/Lib/distutils/tests/test_sysconfig.py", line
72, in test_parse_makefile_literal_dollar
'OTHER': 'foo'})
AssertionError: {'VAR': '$OTHER', 'CONFIG_ARGS': "'--arg1=optarg1'
'ENV=\\$LIB'", 'OTHER': 'foo' [truncated]... != {'CONFIG_ARGS':
"'--arg1=optarg1' 'ENV=\\$LIB'", 'OTHER': 'foo'}
- {'CONFIG_ARGS': "'--arg1=optarg1' 'ENV=\\$LIB'",
+ {'CONFIG_ARGS': "'--arg1=optarg1' 'ENV=\\$LIB'", 'OTHER': 'foo'}
?
- 'OTHER': 'foo',
- 'VAR': '$OTHER'}
--
Ran 181 tests in 42.963s
FAILED (failures=2, skipped=13)
Warning -- os.environ was modified by test_distutils
test test_distutils failed -- multiple errors occurred
Re-running test 'test_posix' in verbose mode
testNoArgFunctions (test.test_posix.PosixTester) ... ok
test_access (test.test_posix.PosixTester) ... ok
test_chdir (test.test_posix.PosixTester) ... ok
test_chflags (test.test_posix.PosixTester) ... ERROR
test_chown (test.test_posix.PosixTester) ... ok
test_confstr (test.test_posix.PosixTester) ... ok
test_dup (test.test_posix.PosixTester) ... ok
test_dup2 (test.test_posix.PosixTester) ... ok
test_fchown (test.test_posix.PosixTester) ... ok
test_fdopen (test.test_posix.PosixTester) ... ok
test_fstat (test.test_posix.PosixTester) ... ok
test_fstatvfs (test.test_posix.PosixTester) ... ok
test_ftruncate (test.test_posix.PosixTester) ... ok
test_getcwd_long_pathnames (test.test_posix.PosixTester) ... FAIL
test_getgroups (test.test_posix.PosixTester) ... ok
test_getresgid (test.test_posix.PosixTester) ... ok
test_getresuid (test.test_posix.PosixTester) ... ok
test_ini
Re: libsoup2.4: FTBFS on kfreebsd-*: test-suite FAIL: context-test
El 20 de març de 2012 21:38, Steven Chamberlain ha escrit: > I've narrowed down the context-test failures to g_cond_wait_until [1] > returning false without actually waiting until the requested time. This suggests pthread_cond_timedwait buggyness. I'll investigate this. > Under gdb we hit a familiar-looking issue that I'm sure we've seen > before on kfreebsd: > >> Starting program: >> /tmp/tmp.iqfzT2Ty1x/libsoup2.4-2.37.92/tests/.libs/lt-context-test -d >> >> Program received signal ?, Unknown signal. Actually GDB knows the signal number, it just fails to convert it to "SIGXXX", which probably means it's one of the signals below SIGRTMIN that don't have a SIG* macro (i.e. pthread sigrestart, sigcancel, etc). -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOfDtXPuPAqDwWbA9e51C8weHK4=t9uvrdob6tyrhjgwjyy...@mail.gmail.com
Updating w.d.o/{intro/organization#distribution,ports/}
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [ Huge cross-post, sorry. Please, only respond to your port list and debian-www@l.d.o, or at least keep me CC if you drop debian-www ] Hi ports and ports-like team, The ports and ports-like part of our organization page [1] might be pretty outdated on the members side. Could you please confirm that the members list of your team is still accurate, or provide an updated list. Without any answer within a week, I'll drop the members name from this page, but will keep the name of the port and a link to the mailing list as main contact point. If you answer after a week, I'll also be happy to update the page afterwards. 1: http://www.debian.org/intro/organization#distribution If you have any update to propose about your port page [2], I'd also be happy to update the respective page on your behalf, and would be even happier if you do it yourself (please, ask for write access [3] if you're not already a member of webwml). 2: http://www.debian.org/ports/ 3: http://www.debian.org/devel/website/using_cvs#write-access We also have one open bug report [4] about the www.d.o/ports/ part, specific to amd64, any help to solve it would be welcome (closing it in case it doesn't make sense could also be appropriate). 4: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611830 Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPfgAgAAoJELgqIXr9/gnyzpUP/2fIZ8QyGu/Zk04wk2FFNQIw /TX13YDWpcZFLdObqwsiyGITIav0Q77bdfhc71dW/m3ZpHbV5l86W1LvazGwn8Wt sseeBp3a/dKPmeKVzPq8Q7zWNXDioDodkKLHmJefB8ziuaOgw/bROanCCGhOflnp yneSaga5qdTGB0tLxxHgPzpRl+CIR05x+gOmW76DXLykdSFs/G9DMPj+eoR5lZXT 0cnu1mA7u1kpPdw6QBW15DEWisQorkDhyqvHsJ2w9owPTcIzx8E02PuesRqe/Ngi jG/paUn1CpDq+mRfx5iTP3Wf1DDWpMriUzyBxpnsXsNQuOPznrP1xhQ8leHbSX+k e1X369isjQ0WiyOApna653KpQmNBW/dewyKr7ATwf4rXYL0F1vj7NZGYRN/+fXio xEypEWEYHuOVVzylty4I87tFo8FAxrcb7dyaEeD/ADdjxWKk5uH3UdJzvgH36U/S dsmEafdI9aQIKyCcaCsqbYSICSy3xgEk4JdLNiI7qvyrqLhbsK1cPIod6FJOiq29 QJ7UpIk76AiyYgPYOl7i8v4kx8cEM3XZMjbJlI4cyk/3Xa4GyitWuWT5pB3KiOSm Ejwi/atgCxzJgzAt8P5s3m9KM3+68TL2qO/HjGk/ei31MNXGSz2wiEjU/a8qdhZd bQpLlaqtB//svizu91tW =Nh8A -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f7e0020.8060...@debian.org
Re: FTBFS on kfreebsd-*: test-suite FAIL: context-test
clone 663056 -1 -2 retitle -1 confusing g_cond_wait_until() API (and docs) invites to unintentional abuse severity -1 normal reassign -1 libglib2.0-dev forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=673607 retitle -2 optional pthread_condattr_setclock() facility is not implemented severity -2 wishlist reassign -2 libc0.1 thanks The way g_cond_wait_until() is currently defined, libsoup usage of this function is incorrect. If you need a short term solution, the test could be disabled, or it could be rewritten using clock_gettime() and pthread_cond_timedwait(). Otherwise you can wait until the API is redefined, or until pthread_condattr_setclock() is implemented in Glibc. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caofdtxn7r2wedncoiis7sbrhjhh_o9clafse8fcbuhwbrqi...@mail.gmail.com
Ruby also affected
Btw Ruby does something similar. I'll have a look tomorrow. El 5 d’abril de 2012 23:11, Robert Millan ha escrit: > clone 663056 -1 -2 > retitle -1 confusing g_cond_wait_until() API (and docs) invites to > unintentional abuse > severity -1 normal > reassign -1 libglib2.0-dev > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=673607 > retitle -2 optional pthread_condattr_setclock() facility is not implemented > severity -2 wishlist > reassign -2 libc0.1 > thanks > > The way g_cond_wait_until() is currently defined, libsoup usage of > this function is incorrect. If you need a short term solution, the > test could be disabled, or it could be rewritten using clock_gettime() > and pthread_cond_timedwait(). > > Otherwise you can wait until the API is redefined, or until > pthread_condattr_setclock() is implemented in Glibc. > > -- > Robert Millan -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caofdtxokcyfjszhbjxr+hvoo6x0d0nbqc070dppmaqtuxz4...@mail.gmail.com
Re: libsoup2.4: FTBFS on kfreebsd-*: test-suite FAIL: context-test
Hi, Just made an observation to be wary of: connection-test doesn't always fail. It actually seems to be about 50-50 for me, on kfreebsd-i386 8.3~svn230343-1 with 4-way SMP. Example of success: > steven@kfreebsd-i386:~/libsoup2.4-2.38.0$ tests/connection-test -d > > Invalid Content-Length framing tests > Content-Length larger than message body length > Server claims 'Connection: close' but doesn't > > Unexpected timing out of persistent connections > Async session > First message > Second message > Sync session > First message > Second message > > Exceeding max-conns > Async session > Sync session > > Non-persistent connections are closed immediately > Async session > Sync session > > Non-idempotent methods are always sent on new connections > Async session > Sync session > > connection-test: OK Failure on next attempt: > steven@kfreebsd-i386:~/libsoup2.4-2.38.0$ tests/connection-test -d > > Invalid Content-Length framing tests > Content-Length larger than message body length > Server claims 'Connection: close' but doesn't > > Unexpected timing out of persistent connections > Async session > First message > Second message > Sync session > First message > Second message > > Exceeding max-conns > Async session > Sync session > > Non-persistent connections are closed immediately > Async session > Sync session > leaked SoupSession! > > Non-idempotent methods are always sent on new connections > Async session > > (connection-test:9504): libsoup-CRITICAL **: soup_message_queue_destroy: > assertion `queue->head == NULL' failed > Sync session > > connection-test: 2 error(s). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f7e241d.3010...@pyro.eu.org
Re: FTBFS on kfreebsd-*: test-suite FAIL: context-test
On 05/04/12 22:11, Robert Millan wrote: > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=673607 glib2.0 2.32.0-3 with the patch you posted there has fixed libsoup2.4's context-test for me. Is that what you expected? That just leaves the intermittent failures of connection-test. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f7e4ca7.3090...@pyro.eu.org
Re: Bug#654783: python2.7: FTBFS(kfreebsd): testsuite hang
reopen 654783 debian-bsd@lists.debian.org notfixed 654783 python2.7/2.7.3~rc2-2 found 654783 python2.7/2.7.3~rc2-2 thanks Log of the latest kfreebsd build failure is: https://buildd.debian.org/status/fetch.php?pkg=python2.7&arch=kfreebsd-amd64&ver=2.7.3~rc2-2&stamp=1333657799 I mentioned today that test_socket hangs, but only moments before this was uploaded to unstable. In the past few hours I've managed to reproduce a hang of test_io on kfreebsd-i386, so that is apparently still an issue (but not always). Also I've run into hangs of test_threading and test_gdb for the first time. The picture is beginning to look quite similar across hurd-i386, kfreebsd-amd64, kfreebsd-i386, sparc (and previously also hppa), with mostly the same set of tests failing, even if some of them fail more or less often. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f7e4ef6.2060...@pyro.eu.org
