[head tinderbox] failure on sparc64/sparc64
TB --- 2013-12-09 07:29:38 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-09 07:29:38 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-12-09 07:29:38 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2013-12-09 07:29:38 - cleaning the object tree TB --- 2013-12-09 07:29:38 - /usr/local/bin/svn stat /src TB --- 2013-12-09 07:29:41 - At svn revision 259112 TB --- 2013-12-09 07:29:42 - building world TB --- 2013-12-09 07:29:42 - CROSS_BUILD_TESTING=YES TB --- 2013-12-09 07:29:42 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-09 07:29:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-09 07:29:42 - SRCCONF=/dev/null TB --- 2013-12-09 07:29:42 - TARGET=sparc64 TB --- 2013-12-09 07:29:42 - TARGET_ARCH=sparc64 TB --- 2013-12-09 07:29:42 - TZ=UTC TB --- 2013-12-09 07:29:42 - __MAKE_CONF=/dev/null TB --- 2013-12-09 07:29:42 - cd /src TB --- 2013-12-09 07:29:42 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Dec 9 07:29:50 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Dec 9 08:34:57 UTC 2013 TB --- 2013-12-09 08:34:57 - generating LINT kernel config TB --- 2013-12-09 08:34:57 - cd /src/sys/sparc64/conf TB --- 2013-12-09 08:34:57 - /usr/bin/make -B LINT TB --- 2013-12-09 08:34:58 - cd /src/sys/sparc64/conf TB --- 2013-12-09 08:34:58 - /usr/sbin/config -m LINT TB --- 2013-12-09 08:34:58 - building LINT kernel TB --- 2013-12-09 08:34:58 - CROSS_BUILD_TESTING=YES TB --- 2013-12-09 08:34:58 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-09 08:34:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-09 08:34:58 - SRCCONF=/dev/null TB --- 2013-12-09 08:34:58 - TARGET=sparc64 TB --- 2013-12-09 08:34:58 - TARGET_ARCH=sparc64 TB --- 2013-12-09 08:34:58 - TZ=UTC TB --- 2013-12-09 08:34:58 - __MAKE_CONF=/dev/null TB --- 2013-12-09 08:34:58 - cd /src TB --- 2013-12-09 08:34:58 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Dec 9 08:34:58 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/sparc64.sparc64/src/sys/LINT -std=iso9899:1999 /src/sys/modules/cd9660_iconv/../../fs/cd9660/cd9660_iconv.c ===> crypto (depend) @ -> /src/sys awk -f @/tools/makeobjops.awk @/opencrypto/cryptodev_if.m -c bmake[3]: don't know how to make deflate.c. Stop bmake[3]: stopped in /src/sys/modules/crypto *** Error code 2 Stop. bmake[2]: stopped in /src/sys/modules *** Error code 1 Stop. bmake[1]: stopped in /obj/sparc64.sparc64/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-12-09 08:36:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-12-09 08:36:50 - ERROR: failed to build LINT kernel TB --- 2013-12-09 08:36:50 - 3113.12 user 581.30 system 4031.94 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-sparc64-sparc64.full ___ 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"
[head tinderbox] failure on powerpc/powerpc
TB --- 2013-12-09 06:00:55 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-09 06:00:55 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-12-09 06:00:55 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2013-12-09 06:00:55 - cleaning the object tree TB --- 2013-12-09 06:00:55 - /usr/local/bin/svn stat /src TB --- 2013-12-09 06:01:08 - At svn revision 259112 TB --- 2013-12-09 06:01:09 - building world TB --- 2013-12-09 06:01:09 - CROSS_BUILD_TESTING=YES TB --- 2013-12-09 06:01:09 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-09 06:01:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-09 06:01:09 - SRCCONF=/dev/null TB --- 2013-12-09 06:01:09 - TARGET=powerpc TB --- 2013-12-09 06:01:09 - TARGET_ARCH=powerpc TB --- 2013-12-09 06:01:09 - TZ=UTC TB --- 2013-12-09 06:01:09 - __MAKE_CONF=/dev/null TB --- 2013-12-09 06:01:09 - cd /src TB --- 2013-12-09 06:01:09 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Dec 9 06:01:18 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Dec 9 08:38:01 UTC 2013 TB --- 2013-12-09 08:38:01 - generating LINT kernel config TB --- 2013-12-09 08:38:01 - cd /src/sys/powerpc/conf TB --- 2013-12-09 08:38:01 - /usr/bin/make -B LINT TB --- 2013-12-09 08:38:01 - cd /src/sys/powerpc/conf TB --- 2013-12-09 08:38:01 - /usr/sbin/config -m LINT TB --- 2013-12-09 08:38:01 - building LINT kernel TB --- 2013-12-09 08:38:01 - CROSS_BUILD_TESTING=YES TB --- 2013-12-09 08:38:01 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-09 08:38:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-09 08:38:01 - SRCCONF=/dev/null TB --- 2013-12-09 08:38:01 - TARGET=powerpc TB --- 2013-12-09 08:38:01 - TARGET_ARCH=powerpc TB --- 2013-12-09 08:38:01 - TZ=UTC TB --- 2013-12-09 08:38:01 - __MAKE_CONF=/dev/null TB --- 2013-12-09 08:38:01 - cd /src TB --- 2013-12-09 08:38:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Dec 9 08:38:02 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/powerpc.powerpc/src/sys/LINT -std=iso9899:1999 /src/sys/modules/cpufreq/../../dev/cpufreq/ichss.c /src/sys/modules/cpufreq/../../powerpc/cpufreq/dfs.c ===> crypto (depend) @ -> /src/sys awk -f @/tools/makeobjops.awk @/opencrypto/cryptodev_if.m -c bmake[3]: don't know how to make deflate.c. Stop bmake[3]: stopped in /src/sys/modules/crypto *** Error code 2 Stop. bmake[2]: stopped in /src/sys/modules *** Error code 1 Stop. bmake[1]: stopped in /obj/powerpc.powerpc/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-12-09 08:39:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-12-09 08:39:25 - ERROR: failed to build LINT kernel TB --- 2013-12-09 08:39:25 - 8073.29 user 997.61 system 9509.89 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc-powerpc.full ___ 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"
[head tinderbox] failure on powerpc64/powerpc
TB --- 2013-12-09 06:41:24 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-09 06:41:24 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-12-09 06:41:24 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2013-12-09 06:41:24 - cleaning the object tree TB --- 2013-12-09 06:41:24 - /usr/local/bin/svn stat /src TB --- 2013-12-09 06:41:28 - At svn revision 259112 TB --- 2013-12-09 06:41:29 - building world TB --- 2013-12-09 06:41:29 - CROSS_BUILD_TESTING=YES TB --- 2013-12-09 06:41:29 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-09 06:41:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-09 06:41:29 - SRCCONF=/dev/null TB --- 2013-12-09 06:41:29 - TARGET=powerpc TB --- 2013-12-09 06:41:29 - TARGET_ARCH=powerpc64 TB --- 2013-12-09 06:41:29 - TZ=UTC TB --- 2013-12-09 06:41:29 - __MAKE_CONF=/dev/null TB --- 2013-12-09 06:41:29 - cd /src TB --- 2013-12-09 06:41:29 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Dec 9 06:41:35 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Dec 9 09:45:53 UTC 2013 TB --- 2013-12-09 09:45:53 - generating LINT kernel config TB --- 2013-12-09 09:45:53 - cd /src/sys/powerpc/conf TB --- 2013-12-09 09:45:53 - /usr/bin/make -B LINT TB --- 2013-12-09 09:45:53 - cd /src/sys/powerpc/conf TB --- 2013-12-09 09:45:53 - /usr/sbin/config -m LINT TB --- 2013-12-09 09:45:53 - skipping LINT kernel TB --- 2013-12-09 09:45:53 - cd /src/sys/powerpc/conf TB --- 2013-12-09 09:45:53 - /usr/sbin/config -m GENERIC TB --- 2013-12-09 09:45:53 - skipping GENERIC kernel TB --- 2013-12-09 09:45:53 - cd /src/sys/powerpc/conf TB --- 2013-12-09 09:45:53 - /usr/sbin/config -m GENERIC64 TB --- 2013-12-09 09:45:53 - building GENERIC64 kernel TB --- 2013-12-09 09:45:53 - CROSS_BUILD_TESTING=YES TB --- 2013-12-09 09:45:53 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-09 09:45:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-09 09:45:53 - SRCCONF=/dev/null TB --- 2013-12-09 09:45:53 - TARGET=powerpc TB --- 2013-12-09 09:45:53 - TARGET_ARCH=powerpc64 TB --- 2013-12-09 09:45:53 - TZ=UTC TB --- 2013-12-09 09:45:53 - __MAKE_CONF=/dev/null TB --- 2013-12-09 09:45:53 - cd /src TB --- 2013-12-09 09:45:53 - /usr/bin/make -B buildkernel KERNCONF=GENERIC64 >>> Kernel build for GENERIC64 started on Mon Dec 9 09:45:53 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/powerpc.powerpc64/src/sys/GENERIC64 -std=iso9899:1999 /src/sys/modules/cpufreq/../../dev/cpufreq/ichss.c /src/sys/modules/cpufreq/../../powerpc/cpufreq/dfs.c ===> crypto (depend) @ -> /src/sys awk -f @/tools/makeobjops.awk @/opencrypto/cryptodev_if.m -c bmake[3]: don't know how to make deflate.c. Stop bmake[3]: stopped in /src/sys/modules/crypto *** Error code 2 Stop. bmake[2]: stopped in /src/sys/modules *** Error code 1 Stop. bmake[1]: stopped in /obj/powerpc.powerpc64/src/sys/GENERIC64 *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-12-09 09:46:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-12-09 09:46:35 - ERROR: failed to build GENERIC64 kernel TB --- 2013-12-09 09:46:35 - 9647.10 user 1219.50 system 1.55 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc64-powerpc.full ___ 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: nanobsd / dd problem?
Stefan Hegnauer wrote: On Monday, December 09, 2013 at 5:43 AM Konstantin Belousov wrote: On Sun, Dec 08, 2013 at 06:31:36PM +0100, Stefan Hegnauer wrote: Hi, I am using freebsd-current (FreeBSD BUILDMASTER 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r259095: Sun Dec 8 10:20:40 CET 2013 root@BUILDMASTER:/usr/obj/usr/src/sys/ASUS i386) in a VirtualBox as a build machine for nanobsd images to be used on pc-engines.ch alix boards. The only difference to GENERIC is the inclusion of 'march=geode' and disabling of most debugging switches (malloc, Witness etc). Worked like a charm in the past. Since late summer - sorry, no exact date / svn revision - nanobsd.sh fails at the last stage when building the disk image, e.g. with ... 00:00:25 ### log: /usr/obj/nanobsd.alixpf//_.di # Looking a bit closer it seems that dd(1) returns with an I/O error whenever the input is a file created with mdconfig(8): # dd if=/dev/zero of=somebackingfile bs=1k count=5k # mdconfig -f somebackingfile -u md0 # newfs -U /dev/md0 # dd if=/dev/md0 of=/dev/null dd: /dev/md0: Input/output error 10241+0 records in 10241+0 records out 5243392 bytes transferred in 3.240345 secs (1618159 bytes/sec) The outputfile in nanobsd.sh seems to be error-free. It should be one block larger than the right size. \ Anyone else seen similar behaviour? How to proceed/fix it? The following patch should clear the error. The issue is that kern_physio() incorrectly detects EOF due to incorrect calculation of bio bio_resid after the bio_length was clipped by the 'excess' code in g_io_check(). Both bio_length and bio_resid appear to be 0 in the pre-last dd transfer, which starts exactly and the mediasize, and kern_physio() thinks that it transferred one more block than was transferred. I _suspect_ that it was caused by 'excess' code moving in r256880, but I am really not in the right condition to analyze it. If somebody could try the same dd experiment to confirm or deny my suspicion, it would be useful. The patch below should be a right thing to do anyway. diff --git a/sys/kern/vfs_bio.c b/sys/kern/vfs_bio.c index c23a74b..b7c4d60 100644 --- a/sys/kern/vfs_bio.c +++ b/sys/kern/vfs_bio.c @@ -3679,7 +3679,6 @@ bufdonebio(struct bio *bip) bp = bip->bio_caller2; bp->b_resid = bp->b_bcount - bip->bio_completed; - bp->b_resid = bip->bio_resid; /* XXX: remove */ bp->b_ioflags = bip->bio_flags; bp->b_error = bip->bio_error; if (bp->b_error) Works for me - please commit! Thanks a lot! -Stefan ___ 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" I have a similar problem with nanobsd.sh on FreeBSD 10.x. I am able to build the image but sometimes (could not figured out the reason why) the image is build incorrectly. For example on an incorrectly built image when I boot i got: Trying to mount root from ufs:/dev/ada0s1a [ro]... mount: /dev/ada0s3: Invalid argument mount -o ro /dev/ada0s3 /conf/default/etc failed: dropping into /bin/sh It seems the partition that hold config files cannot be accessed. Hope your fix will fix this problem too (asumming you will also commit on 10.x). Theres also an issue with package management, the nanobsd script still uses pkg_add instead of pkg. ovi ___ 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: nanobsd / dd problem?
On Mon, Dec 09, 2013 at 06:42:39AM +0200, Konstantin Belousov wrote: > On Sun, Dec 08, 2013 at 06:31:36PM +0100, Stefan Hegnauer wrote: > > Hi, > > > > > > > > I am using freebsd-current (FreeBSD BUILDMASTER 11.0-CURRENT FreeBSD > > 11.0-CURRENT #0 r259095: Sun Dec 8 10:20:40 CET 2013 > > root@BUILDMASTER:/usr/obj/usr/src/sys/ASUS i386) in a VirtualBox as a build > > machine for nanobsd images to be used on pc-engines.ch alix boards. The only > > difference to GENERIC is the inclusion of 'march=geode' and disabling of > > most debugging switches (malloc, Witness etc). Worked like a charm in the > > past. > > > > > > > > Since late summer - sorry, no exact date / svn revision - nanobsd.sh fails > > at the last stage when building the disk image, e.g. with > > > > ... > > > > 00:00:25 ### log: /usr/obj/nanobsd.alixpf//_.di > > > > # > > > > > > > > Looking a bit closer it seems that dd(1) returns with an I/O error whenever > > the input is a file created with mdconfig(8): > > > > # dd if=/dev/zero of=somebackingfile bs=1k count=5k > > > > # mdconfig -f somebackingfile -u md0 > > > > # newfs -U /dev/md0 > > > > # dd if=/dev/md0 of=/dev/null > > > > dd: /dev/md0: Input/output error > > > > 10241+0 records in > > > > 10241+0 records out > > > > 5243392 bytes transferred in 3.240345 secs (1618159 bytes/sec) > > > > > > > > The outputfile in nanobsd.sh seems to be error-free. > It should be one block larger than the right size. > \ > > > > Anyone else seen similar behaviour? How to proceed/fix it? > > > > The following patch should clear the error. > > The issue is that kern_physio() incorrectly detects EOF due to incorrect > calculation of bio bio_resid after the bio_length was clipped by the > 'excess' code in g_io_check(). Both bio_length and bio_resid appear > to be 0 in the pre-last dd transfer, which starts exactly and the > mediasize, and kern_physio() thinks that it transferred one more block > than was transferred. > > I _suspect_ that it was caused by 'excess' code moving in r256880, > but I am really not in the right condition to analyze it. If somebody > could try the same dd experiment to confirm or deny my suspicion, it > would be useful. > > The patch below should be a right thing to do anyway. > > diff --git a/sys/kern/vfs_bio.c b/sys/kern/vfs_bio.c > index c23a74b..b7c4d60 100644 > --- a/sys/kern/vfs_bio.c > +++ b/sys/kern/vfs_bio.c > @@ -3679,7 +3679,6 @@ bufdonebio(struct bio *bip) > > bp = bip->bio_caller2; > bp->b_resid = bp->b_bcount - bip->bio_completed; > - bp->b_resid = bip->bio_resid; /* XXX: remove */ > bp->b_ioflags = bip->bio_flags; > bp->b_error = bip->bio_error; > if (bp->b_error) I have tested this patch with a buildworld + selected other tests. No problems seen (and problem fixed, of cause). - Peter ___ 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: nanobsd / dd problem?
On Mon, Dec 9, 2013 at 5:42 AM, Konstantin Belousov wrote: > > > > The patch below should be a right thing to do anyway. > > diff --git a/sys/kern/vfs_bio.c b/sys/kern/vfs_bio.c > index c23a74b..b7c4d60 100644 > --- a/sys/kern/vfs_bio.c > +++ b/sys/kern/vfs_bio.c > @@ -3679,7 +3679,6 @@ bufdonebio(struct bio *bip) > > bp = bip->bio_caller2; > bp->b_resid = bp->b_bcount - bip->bio_completed; > - bp->b_resid = bip->bio_resid; /* XXX: remove */ > bp->b_ioflags = bip->bio_flags; > bp->b_error = bip->bio_error; > if (bp->b_error) > Problem fixed with your patch for me too: Thanks. Olivier ___ 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: [R259114/Newcons] Compile failure
On Sun, 8 Dec 2013 21:05:47 -0600 Larry Rosenman wrote: > cc -c -O2 -pipe -fno-strict-aliasing -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 > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone > -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables > -ffreestanding -fno-strict-overflow -fstack-protector -Werror > /usr/src/sys/dev/vt/vt_core.c > /usr/src/sys/dev/vt/vt_core.c:1313:9: error: implicit declaration of function > 'IOCPARM_IVAL' is invalid in C99 [-Werror,-Wimplicit-function-declaration] > ival = IOCPARM_IVAL(data); >^ > 1 error generated. > *** Error code 1 > > Stop. > make[2]: stopped in /usr/obj/usr/src/sys/BORG-DTRACE > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > ^C > [1] Done(1) nohup make -DNO_CLEAN buildworld buildkernel > >>make.noc.out 2>&1 > # svn up > Updating '.': > At revision 259114. > # svn info > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/head > Relative URL: ^/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 259114 > Node Kind: directory > Schedule: normal > Last Changed Author: alfred > Last Changed Rev: 259114 > Last Changed Date: 2013-12-08 20:06:52 -0600 (Sun, 08 Dec 2013) > > # > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: l...@lerctr.org > US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 > ___ > 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" Hello Larry! It is now fixed (r259130). Thanks a lot! WBW -- Aleksandr Rybalko --- Begin Message --- cc -c -O2 -pipe -fno-strict-aliasing -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 -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fno-strict-overflow -fstack-protector -Werror /usr/src/sys/dev/vt/vt_core.c /usr/src/sys/dev/vt/vt_core.c:1313:9: error: implicit declaration of function 'IOCPARM_IVAL' is invalid in C99 [-Werror,-Wimplicit-function-declaration] ival = IOCPARM_IVAL(data); ^ 1 error generated. *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/sys/BORG-DTRACE *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src ^C [1] Done(1) nohup make -DNO_CLEAN buildworld buildkernel >>make.noc.out 2>&1 # svn up Updating '.': At revision 259114. # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 259114 Node Kind: directory Schedule: normal Last Changed Author: alfred Last Changed Rev: 259114 Last Changed Date: 2013-12-08 20:06:52 -0600 (Sun, 08 Dec 2013) # -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ 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" --- End Message --- ___ 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: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
On Mon, 9 Dec 2013 10:59:14 +0200 Markiyan Kushnir wrote: > Hello, > > I'm on rev. 259102 and hitting drm not being able to attach to fbd > device at X startup (X freezing). > > Attaching /var/log/messages, pciconf output and kern.conftxt. Please > let me know if there is something I'm missing here. Posting in this > thread since I thought it might be relevant to this commit? > > Thanks, > Markiyan > > > 2013/12/8 Marc UBM : > > Hiho! :-) > > > > Thanks a lot for working on this! > > > > As soon as X is started, things work fine. Before that (as soon as vt > > is initialized after the boot menu), output on all ttys is flickering, > > resolution is at 640x480 (guessing here) and changing anything via > > vidcontrol fails with "inappropriate ioctl for device". Also, screen > > output starts overlapping, but a "clear" command fixes that > > temporarily. The "Alt-Gr" key does nothing, manually entering ascii > > keycodes via alt+number (e.g. alt-124 for |) works. > > > > Relevant pciconf output: > > > > vgapci0@pci0:0:2:0: class=0x03 card=0x40011297 chip=0x2e328086 > > rev=0x03 hdr=0x00 vendor = 'Intel Corporation' > > device = '4 Series Chipset Integrated Graphics Controller' > > class = display > > subclass = VGA > > > > vgapci1@pci0:0:2:1: class=0x038000 card=0x40011297 chip=0x2e338086 > > rev=0x03 hdr=0x00 vendor = 'Intel Corporation' > > device = '4 Series Chipset Integrated Graphics Controller' > > class = display > > > > Best regards, > > Marc > > > > [[CUT]] > > > > > > -- > > Marc "UBM" Bocklet > > ___ > > 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" Hi Markiyan! According to attached kernel config you run system with syscons (device sc). If you want to test it with vt (newcons), follow instructions on the wiki page. https://wiki.freebsd.org/Newcons Thanks. WBW -- Aleksandr Rybalko ___ 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: [Newcons] EDID message every second or 2?
On Sat, 07 Dec 2013 18:12:03 -0600 Larry Rosenman wrote: > On 2013-12-07 18:07, Aleksandr Rybalko wrote: > > > > > Hi Larry, > > > > Looks like you have display with broken info block (a.k.a. EDID). > > That message come from drm2 code, so you can to try to remove DRM > > debug flag from kernel config (if it there). > > > > Otherwise we have to find way to preload correct EDID. XOrg able to do > > that, but we still no, IIRC. > > > > Thanks! > > WBW > > -- > > Aleksandr Rybalko > I don't see a DRM debug flag in GENERIC or my config. > > Ideas? > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org > US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 Hi again Larry! :) Looks like your problem fixed in r259104 by Jean (dumbbell) today. So you can try to update and rebuild. WBW -- Aleksandr Rybalko ___ 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: [Newcons] EDID message every second or 2?
On 08.12.2013 00:14, Larry Rosenman wrote: > info: [drm] Loading R100 Microcode > error: [drm:pid0:r100_cp_init_microcode] *ERROR* radeon_cp: Failed to load > firmware "radeonkmsfw_R100_cp" > error: [drm:pid0:r100_cp_init] *ERROR* Failed to load firmware! Hi! I don't know if this could explain your EDID problem, but several users had this failure to load firmware and I couldn't reproduce it. Do you have a file called radeonkmsfw_R100_cp.ko in your kernel directory (eg. /boot/kernel/radeonkmsfw_R100_cp.ko)? -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
Re: r259072 is not a happy camper...
On Saturday, December 07, 2013 2:32:56 pm Poul-Henning Kamp wrote: > > I updated my "canary" machine to -current today and it's not a happy > camper. Trying to run a buildworld on it I get the follwing reproducible > panic: > > FreeBSD/amd64 (ni.freebsd.dk) (cuau0) > > login: lock order reversal: > 1st 0xf8011641a9a0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_lookup.c:518 > 2nd 0xfe00e7858790 bufwait (bufwait) @ > /freebsd/head/sys/ufs/ffs/ffs_vnops > .c:262 > 3rd 0xf800b40ad5f0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_subr.c:2101 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0111361da0 > kdb_backtrace() at kdb_backtrace+0x39/frampanic: bad stray interrupt > cpuid = 2 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe011120e9e0 > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe011120ea90 > vpanic() at vpanic+0x126/frame 0xfe011120ead0 > kassert_panic() at kassert_panic+0x136/frame 0xfe011120eb40 > intr_event_handle() at intr_event_handle+0x11d/frame 0xfe011120eb90 > intr_execute_handlers() at intr_execute_handlers+0x48/frame 0xfe011120ebc0 > lapic_handle_intr() at lapic_handle_intr+0x73/frame 0xfe011120ebf0 > Xapic_isr1() at Xapic_isr1+0xa4/frame 0xfe011120ebf0 > --- interrupt, rip = 0x11f7b11, rsp = 0x7fff8b50, rbp = 0x7fff8b80 --- > KDB: enter: panic > [ thread pid 72149 tid 100102 ] > Stopped at kdb_enter+0x3e: movq$0,kdb_why > db> Hmmm. Maybe do 'show lapic' and 'show apic' in ddb and paste that here? -- 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"
Re: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
2013/12/9 Aleksandr Rybalko : > On Mon, 9 Dec 2013 10:59:14 +0200 > Markiyan Kushnir wrote: > >> Hello, >> >> I'm on rev. 259102 and hitting drm not being able to attach to fbd >> device at X startup (X freezing). >> >> Attaching /var/log/messages, pciconf output and kern.conftxt. Please >> let me know if there is something I'm missing here. Posting in this >> thread since I thought it might be relevant to this commit? >> >> Thanks, >> Markiyan >> >> >> 2013/12/8 Marc UBM : >> > Hiho! :-) >> > >> > Thanks a lot for working on this! >> > >> > As soon as X is started, things work fine. Before that (as soon as vt >> > is initialized after the boot menu), output on all ttys is flickering, >> > resolution is at 640x480 (guessing here) and changing anything via >> > vidcontrol fails with "inappropriate ioctl for device". Also, screen >> > output starts overlapping, but a "clear" command fixes that >> > temporarily. The "Alt-Gr" key does nothing, manually entering ascii >> > keycodes via alt+number (e.g. alt-124 for |) works. >> > >> > Relevant pciconf output: >> > >> > vgapci0@pci0:0:2:0: class=0x03 card=0x40011297 chip=0x2e328086 >> > rev=0x03 hdr=0x00 vendor = 'Intel Corporation' >> > device = '4 Series Chipset Integrated Graphics Controller' >> > class = display >> > subclass = VGA >> > >> > vgapci1@pci0:0:2:1: class=0x038000 card=0x40011297 chip=0x2e338086 >> > rev=0x03 hdr=0x00 vendor = 'Intel Corporation' >> > device = '4 Series Chipset Integrated Graphics Controller' >> > class = display >> > >> > Best regards, >> > Marc >> > >> > > [[CUT]] >> > >> > >> > -- >> > Marc "UBM" Bocklet >> > ___ >> > 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" > > Hi Markiyan! > > According to attached kernel config you run system with syscons (device > sc). > > If you want to test it with vt (newcons), follow instructions on the > wiki page. > https://wiki.freebsd.org/Newcons > Ah, thanks! I'll give it a try. I simply was curious of testing X running on a Radeon card on CURRENT. Testing vt is a bit different thing, and I will try it separately as well. Yet how about this error with drm_fb_helper_single_fb_probe? Does it mean I cannot use the old sc and vga devices now? > Thanks. > > WBW > -- > Aleksandr Rybalko ___ 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: nanobsd / dd problem?
Hi, On Mon, 9 Dec 2013, freebsdonline wrote: ... Theres also an issue with package management, the nanobsd script still uses pkg_add instead of pkg. for -current I've added cust_pkgng() to nanobsd.sh It needs to get called manually instead of cust_pkg() though. ( customize_cmd cust_pkgng ) Greetings --- Michael Reifenberger ___ 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: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
On 09.12.2013 09:59, Markiyan Kushnir wrote: > I'm on rev. 259102 and hitting drm not being able to attach to fbd > device at X startup (X freezing). I believe those issues are unrelated: I have the "Failed to attach fbd device" because I'm using syscons, however, X.Org works perfectly well. From your /var/log/messages, the driver properly initialized the card and logged no error. Can you post your Xorg.0.log please? How do you determine that X is frozen? -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
FreeBSD 10.0-RC1 now available
The first RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. * Please see the change list for an important note regarding the bsdinstall(8) ZFS on GELI option. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/ (or any of the FreeBSD mirror sites). If you notice problems you can report them through the normal GNATS PR system or here on the -current mailing list. If you would like to use SVN to do a source based update of an existing system, use the "releng/10.0" branch. Important note to freebsd-update(8) users: Please be sure to follow the instructions in the following FreeBSD Errata Notices before upgrading the system to 10.0-RC1: - EN-13:04.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:04.freebsd-update.asc - EN-13:05.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:05.freebsd-update.asc Pre-installed virtual machine images for 10.0-RC1 are also available for amd64 and i386 architectures. The images are located under the 'snapshots' directory on FTP, here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-RC1/ The disk images are available in both QCOW2, VHD, and VMDK format. The image download size is approximately 135 MB, which decompress to a 20GB sparse image. The partition layout is: - 512k - freebsd-boot GPT partition type (bootfs GPT label) - 1GB - freebsd-swap GPT partition type (swapfs GPT label) - ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) Changes between -BETA4 and -RC1 include: - Fix to a regression in bsdinstall(8) that prevents ZFS on GELI installation from working correctly.[*] *Please note: a last-minute problem was found in 10.0-RC1 testing with this installation option that is still being investigated. Please do *not* select the GELI encryption option from the installer. Although the installation successfully completes, the GELI passphrase will *not* decrypt the GELI provider. - Build Hyper-V kernel modules by default for i386. - Update oce(4) driver to support 40Gbps devices. - Improve robustness of the Xen balloon driver. - Fix accounting for hw.realmem on the i386 and amd64 platforms. - Fix poweroff(8) on XenServer. - Fix powerd/states on AMD cpus. - Add support for BCM57764, BCM57767, BCM57782, BCM57786 and BCM57787. - Fix PKG_ABI detection in bsdconfig(8) after pkg-1.2. - Fix emulated jail_v0 byte order. - Fix hang on reboot with active iSCSI connections. - Fix a potential system crash if a jail(8) is created and destroyed on systems with VIMAGE. == ISO CHECKSUMS == - 10.0-RC1 amd64: SHA256 (FreeBSD-10.0-RC1-amd64-bootonly.iso) = c640ac78fee2cbc411b701ecc028286c7514fe324ce5ba57176edc42fa143d85 SHA256 (FreeBSD-10.0-RC1-amd64-disc1.iso) = f41c8d4b78cfb6ec0cca4ad21f937fe1e6a65e7b61167467860110c3290d650e SHA256 (FreeBSD-10.0-RC1-amd64-memstick.img) = 9015c7cb025bc9d62eb989b22a172a756a6fb53646bad9fa83ee6e53358737f8 MD5 (FreeBSD-10.0-RC1-amd64-bootonly.iso) = f183fe88ed81d2cebef7fed42084d62b MD5 (FreeBSD-10.0-RC1-amd64-disc1.iso) = dd2b48fbe752a78d6e002abbd1a04bc6 MD5 (FreeBSD-10.0-RC1-amd64-memstick.img) = 54d1c86aa05bfbf5e5c11450c74e3e5a - 10.0-RC1 i386: SHA256 (FreeBSD-10.0-RC1-i386-bootonly.iso) = a77c69c1483447a47aa7efb74a77d0db297427671384f6743330a3c5b508c3ee SHA256 (FreeBSD-10.0-RC1-i386-disc1.iso) = beb48fcd2dfcde9ace0a44ff689085baf3bc80575503af4e3bc445ec894d2255 SHA256 (FreeBSD-10.0-RC1-i386-memstick.img) = 01fbf1c70af180a7d01fc0d279552d24ad6da302ec0fac0727ff00bd146cc04f MD5 (FreeBSD-10.0-RC1-i386-bootonly.iso) = 03a30dc2485ec596dfc068c0e173510c MD5 (FreeBSD-10.0-RC1-i386-disc1.iso) = c11cd8955b183a39163f4eb66f4a312a MD5 (FreeBSD-10.0-RC1-i386-memstick.img) = 9c544ef2186c25b8ed76690f806dbc67 - 10.0-RC1 ia64: SHA256 (FreeBSD-10.0-RC1-ia64-bootonly.iso) = fe13352fad5835b85d19897ac222c73a13be29be848a80c1a025871bd60735ae SHA256 (FreeBSD-10.0-RC1-ia64-disc1.iso) = c031581ebdcb457233b3a51ef6598053130ac4a9414fef885d2e1cbabe7c41a4 SHA256 (FreeBSD-10.0-RC1-ia64-memstick.img) = bd9b058d639a6649a7394dc1bc588e80f75c41bc1521a50b66d9d8a623fee9fd MD5 (FreeBSD-10.0-RC1-ia64-bootonly.iso) = c6df39a7a561dee8ffddb412f5313f50 MD5 (FreeBSD-10.0-RC1-ia64-disc1.iso) = 19dea92e71cfb9fe0c66f57be4588805 MD5 (FreeBSD-10.0-RC1-ia64-memstick.img) = a783748b0f101629a7c2a2ad87d8d813 - 10.0-RC1 powerpc: SHA256 (FreeBSD-10.0-RC1-powerpc-bootonly.iso) = 2feb3f9a7b1e3c5662fc8be154cc758e32afcb5c4b97ecaf9c3d24cc4cee9599
Re: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
On Sun, 8 Dec 2013 16:36:10 +0100 Marc UBM wrote: > Hiho! :-) > > Thanks a lot for working on this! > > As soon as X is started, things work fine. Before that (as soon as vt > is initialized after the boot menu), output on all ttys is flickering, > resolution is at 640x480 (guessing here) and changing anything via > vidcontrol fails with "inappropriate ioctl for device". Also, screen > output starts overlapping, but a "clear" command fixes that > temporarily. The "Alt-Gr" key does nothing, manually entering ascii > keycodes via alt+number (e.g. alt-124 for |) works. > > Relevant pciconf output: > > vgapci0@pci0:0:2:0: class=0x03 card=0x40011297 chip=0x2e328086 > rev=0x03 hdr=0x00 vendor = 'Intel Corporation' > device = '4 Series Chipset Integrated Graphics Controller' > class = display > subclass = VGA > > vgapci1@pci0:0:2:1: class=0x038000 card=0x40011297 chip=0x2e338086 > rev=0x03 hdr=0x00 vendor = 'Intel Corporation' > device = '4 Series Chipset Integrated Graphics Controller' > class = display > > Best regards, > Marc > > > > > -- > Marc "UBM" Bocklet > ___ > 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" Hi Marc, yeah I seen same at the test board vgapci0@pci0:0:2:0: class=0x03 card=0x00368086 chip=0x00428086 First thought was about firmware(BIOS) bug related to VGA graphic mode. Are your board made by Intel too (mine is INTEL DH55HC)? WBW -- Aleksandr Rybalko ___ 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: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
On Mon, 9 Dec 2013 22:49:33 +0200 Aleksandr Rybalko wrote: > > Hi Marc, > > yeah I seen same at the test board > > vgapci0@pci0:0:2:0: class=0x03 card=0x00368086 chip=0x00428086 > > First thought was about firmware(BIOS) bug related to VGA graphic mode. > Are your board made by Intel too (mine is INTEL DH55HC)? > > WBW > -- > Aleksandr Rybalko Yeah, this is a Shuttle barebone with an Intel Board inside it: http://www.shuttle.eu/index.php?id=836&L=0 dmesg is attached. Bye Marc dmesg.newcons Description: Binary data ___ 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 with -CURRENT @Boot [r259130]
On Mon, 9 Dec 2013 10:36:34 -0600 Larry Rosenman wrote: > > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/head > Relative URL: ^/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 259130 > Node Kind: directory > Schedule: normal > Last Changed Author: ray > Last Changed Rev: 259130 > Last Changed Date: 2013-12-09 09:28:34 -0600 (Mon, 09 Dec 2013) > [[cut]] Can you please share core and kernel with modules. I'm not sure, but looks like it is related to vt (newcons). So I have to investigate. Thanks! WBW -- Aleksandr Rybalko ___ 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"
[SOLVED]Re: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
ok, now I'm at r259128 (both world and kernel), and ports at r335849 all rebuilt from scratch, the issue's gone away. Right before rebuild, it was the window manager (I would guess) that must be freeezing (no mouse, no feedback to keyboard, however clean shutdown of X from within external ssh sesssion). I think I must have messed something up with my base and ports. My typical desktop setup is X + compiz-fusion + lxsession (session mananger only, not even full lxde) + cairo-dock. PS. In my then broken setup, plain Xorg server + twm were not freezing. With kernel rebuild I've replaced sc with vt and things now are running plain ATM. Yes it appears the issue was not repated to vt. Thank you Jean-Sébastien and Aleksandr for taking care. -- Markiyan 2013/12/9 Jean-Sébastien Pédron : > On 09.12.2013 09:59, Markiyan Kushnir wrote: >> I'm on rev. 259102 and hitting drm not being able to attach to fbd >> device at X startup (X freezing). > > I believe those issues are unrelated: I have the "Failed to attach fbd > device" because I'm using syscons, however, X.Org works perfectly well. > > From your /var/log/messages, the driver properly initialized the card > and logged no error. > > Can you post your Xorg.0.log please? > > How do you determine that X is frozen? > > -- > Jean-Sébastien Pédron > ___ 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: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken
On Mon, 9 Dec 2013 19:48:44 +0200 Markiyan Kushnir wrote: > 2013/12/9 Aleksandr Rybalko : > > On Mon, 9 Dec 2013 10:59:14 +0200 > > Markiyan Kushnir wrote: > > > >> Hello, > >> > >> I'm on rev. 259102 and hitting drm not being able to attach to fbd > >> device at X startup (X freezing). > >> > >> Attaching /var/log/messages, pciconf output and kern.conftxt. > >> Please let me know if there is something I'm missing here. Posting > >> in this thread since I thought it might be relevant to this commit? > >> > >> Thanks, > >> Markiyan > >> > >> > >> 2013/12/8 Marc UBM : > >> > Hiho! :-) > >> > > >> > Thanks a lot for working on this! > >> > > >> > As soon as X is started, things work fine. Before that (as soon > >> > as vt is initialized after the boot menu), output on all ttys is > >> > flickering, resolution is at 640x480 (guessing here) and > >> > changing anything via vidcontrol fails with "inappropriate ioctl > >> > for device". Also, screen output starts overlapping, but a > >> > "clear" command fixes that temporarily. The "Alt-Gr" key does > >> > nothing, manually entering ascii keycodes via alt+number (e.g. > >> > alt-124 for |) works. > >> > > >> > Relevant pciconf output: > >> > > >> > vgapci0@pci0:0:2:0: class=0x03 card=0x40011297 > >> > chip=0x2e328086 rev=0x03 hdr=0x00 vendor = 'Intel > >> > Corporation' device = '4 Series Chipset Integrated Graphics > >> > Controller' class = display > >> > subclass = VGA > >> > > >> > vgapci1@pci0:0:2:1: class=0x038000 card=0x40011297 > >> > chip=0x2e338086 rev=0x03 hdr=0x00 vendor = 'Intel > >> > Corporation' device = '4 Series Chipset Integrated Graphics > >> > Controller' class = display > >> > > >> > Best regards, > >> > Marc > >> > > >> > > > [[CUT]] > >> > > >> > > >> > -- > >> > Marc "UBM" Bocklet > >> > ___ > >> > 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" > > > > Hi Markiyan! > > > > According to attached kernel config you run system with syscons > > (device sc). > > > > If you want to test it with vt (newcons), follow instructions on the > > wiki page. > > https://wiki.freebsd.org/Newcons > > > > Ah, thanks! I'll give it a try. I simply was curious of testing X > running on a Radeon card on CURRENT. Testing vt is a bit different > thing, and I will try it separately as well. Yet how about this error > with drm_fb_helper_single_fb_probe? Does it mean I cannot use the old > sc and vga devices now? It is not fatal in syscons case. We decide to mark this message as error, to get more attention when run with newcons. For newcons it indicate that vt will not be able to draw into framebuffer(memory region which contain image you see on display). But it have no impact on sc (syscons). > > > > > Thanks. > > > > WBW > > -- > > Aleksandr Rybalko Thanks! -- Aleksandr Rybalko ___ 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: svn commit: r255715 - head/usr.bin/calendar
[ reviving an old thread ] On Fri, Oct 25, 2013 at 7:25 PM, Matthew D. Fuller wrote: > Firstly, my ~/.calendar/calendar (which I'd long since forgotten even > existed; hadn't been touched since last millennium) had lines like > > #include > > which had worked fine previously, but now force-added the path to the > beginning, leading to a long list of > > 38152 calendar NAMI > "/usr/share/calendar//usr/share/calendar/calendar.birthday" > > in the ktrace output. It could reasonably be argued that it's > coloring outside the lines a bit, but the manpage still speaks as > though it should DTRT. I just fix only this. > But the major upshot was that it didn't find any actual files, and so > calendar output nothing and exited without any errors or error code. > That part, doesn't seem so much right; it should at least say > SOMETHING, neh? This is still a problem > But with that tracked down and changed, it now started outputting > stuff. Too much stuff. Way too much stuff, in character sets my > xterm didn't know what to do with. It turns out THAT was a result of > lines in the file like > > /* #include */ > > which cpp properly did nothing with, but the built-in parsing still > sees and processes. That's definitely buggy... As is this. -- Eitan Adler ___ 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 with -CURRENT @Boot [r259130]
On 2013-12-09 16:04, Aleksandr Rybalko wrote: On Mon, 9 Dec 2013 10:36:34 -0600 Larry Rosenman wrote: Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 259130 Node Kind: directory Schedule: normal Last Changed Author: ray Last Changed Rev: 259130 Last Changed Date: 2013-12-09 09:28:34 -0600 (Mon, 09 Dec 2013) [[cut]] Can you please share core and kernel with modules. I'm not sure, but looks like it is related to vt (newcons). So I have to investigate. Thanks! WBW I've passed ray@ credentials to get at the core/kernel/etc on the system that generated it. Thanks all. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ 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"
