[head tinderbox] failure on i386/pc98
TB --- 2012-05-13 06:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-05-13 06:10:00 - 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 --- 2012-05-13 06:10:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2012-05-13 06:10:00 - cleaning the object tree TB --- 2012-05-13 06:14:23 - cvsupping the source tree TB --- 2012-05-13 06:14:23 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2012-05-13 06:15:16 - building world TB --- 2012-05-13 06:15:16 - CROSS_BUILD_TESTING=YES TB --- 2012-05-13 06:15:16 - MAKEOBJDIRPREFIX=/obj TB --- 2012-05-13 06:15:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-05-13 06:15:16 - SRCCONF=/dev/null TB --- 2012-05-13 06:15:16 - TARGET=pc98 TB --- 2012-05-13 06:15:16 - TARGET_ARCH=i386 TB --- 2012-05-13 06:15:16 - TZ=UTC TB --- 2012-05-13 06:15:16 - __MAKE_CONF=/dev/null TB --- 2012-05-13 06:15:16 - cd /src TB --- 2012-05-13 06:15:16 - /usr/bin/make -B buildworld World build started on Sun May 13 06:15:17 UTC 2012 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 [...] cc -O2 -pipe -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/pc98/loader/../../ficl -I/src/sys/boot/pc98/loader/../../ficl/i386 -DLOADER_GZIP_SUPPORT -I/src/sys/boot/pc98/loader/../../common -I/src/sys/boot/pc98/loader/../../i386 -I. -Wall -I/src/sys/boot/pc98/loader/.. -I/src/sys/boot/pc98/loader/../btx/lib -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -Os -DPC98 -std=gnu99 -c /src/sys/boot/pc98/loader/../../common/isapnp.c cc -O2 -pipe -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/pc98/loader/../../ficl -I/src/sys/boot/pc98/loader/../../ficl/i386 -DLOADER_GZIP_SUPPORT -I/src/sys/boot/pc98/loader/../../common -I/src/sys/boot/pc98/loader/../../i386 -I. -Wall -I/src/sys/boot/pc98/loader/.. -I/src/sys/boot/pc98/loader/../btx/lib -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -Os -DPC98 -std=gnu99 -c /src/sys/boot/pc98/loader/../../common/pnp.c cc -O2 -pipe -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/pc98/loader/../../ficl -I/src/sys/boot/pc98/loader/../../ficl/i386 -DLOADER_GZIP_SUPPORT -I/src/sys/boot/pc98/loader/../../common -I/src/sys/boot/pc98/loader/../../i386 -I. -Wall -I/src/sys/boot/pc98/loader/.. -I/src/sys/boot/pc98/loader/../btx/lib -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -Os -DPC98 -std=gnu99 -c /src/sys/boot/pc98/loader/../../common/interp_forth.c cc -O2 -pipe -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/pc98/loader/../../ficl -I/src/sys/boot/pc98/loader/../../ficl/i386 -DLOADER_GZIP_SUPPORT -I/src/sys/boot/pc98/loader/../../common -I/src/sys/boot/pc98/loader/../../i386 -I. -Wall -I/src/sys/boot/pc98/loader/.. -I/src/sys/boot/pc98/loader/../btx/lib -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -Os -DPC98 -std=gnu99 -static -Ttext 0x0 -nostdlib -o loader.sym /obj/pc98.i386/src/sys/boot/pc98/loader/../btx/lib/crt0.o main.o conf.o vers.o boot.o commands.o console.o devopen.o disk.o interp.o interp_backslash.o interp_parse.o ls.o misc.o module.o panic.o load_elf32.o load_elf32_obj.o reloc_elf32.o bcache.o isapnp.o pnp.o interp_forth.o /obj/pc98.i386/src/sys/boot/pc98/loader/../../ficl/libficl.a /obj/pc98.i386/src/sys/boot/pc98/loader/../libpc98/libpc98.a /obj/pc98.i386/src/tmp/usr/lib/libstand.a /obj/pc98.i386/src/sys/boot/pc98/loader/../libpc98/libpc98.a(devicename.o): In function `i386_parsedev': devicename.c:(.text+0x19b): undefined reference to `zfs_parsedev' /obj/pc98.i386/src/sys/boot/pc98/loader/../libpc98/libpc98.a(devicename.o): In function `i386_fmtdev': devicename.c:(.text+0x301): undefined reference to `zfs_fmtdev' *** Error code 1 Stop in /src/sys/boot/pc98/loader. *** Error code 1 Stop in /src/sys/boot/pc98. *** Error code 1 Stop in /src/sys/boot. *** Error code 1 Stop in /src/sys. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-05-13 08:30:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-05-13 08:30:11 - ERROR: failed to build world TB --- 2012-05-13 08:30:11 - 6029.41 user 827.75 system 8411.09 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full ___ freebsd-current@freebsd.org mailing list
ACPI 'driver bug: Unable to set devclass'
I've just updated to -current and noticed the following errors in dmesg: acpi0: NEC on motherboard acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bbf0 (3) failed driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) cpu0: ACPI CPU on acpi0 ACPI Warning: Incorrect checksum in table [OEMB] - 0x45, should be 0x44 (20120420/tbutils-293) driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu2: ACPI CPU on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu1: ACPI CPU on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) -- Bruce Cran ___ 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
Default directory used for 'zpool import' broken (/dev/dsk)?
When running 'zpool import' without -d I get the error: cannot open '/dev/dsk': must be an absolute path zpool(8) suggests the default should have been updated for FreeBSD: If the -d option is not specified, this command searches for devices in /dev Was this broken recently? -- Bruce Cran ___ 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: [CFT] SMP/i386 suspend/resume
Al 11/05/2012 04:10, En/na Mitsuru IWASAKI ha escrit: Hi I've been working on suspend/resume for SMP/i386 for a week and created patches against CURRENT, RELENG_9 and RELENG_8 available at: http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_9-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_8-20120511.diff A lot of portion of the patches was ported from amd64. Testing on Thinkpad X60 (Core Duo T2300), so far so good :) I'll commit them against CURRENT hopefully next week. Reporting from an Acer Centrino Duo, running CURRENT r235266. The machine has an nvidia card (Ge7300go). The acpi_video and nvidia modules are there. I did test it a few times with X running (plain twm) and worked just fine. Setting hw.acpi.lid_switch_state=S3 allowed me to use the close-the-lid-to-sleep functionality. The problem comes when I suspend the machine in the console. The machine resumes fine (I can ping and ssh it) but the screen remains black. I set hw.acpi.reset_video to 0 or 1 but no go. If I'm in a console but X is running, after the resume I can CTRL+ALT+F9 and get my video back; then I can return to the console. If I don't have X running, I don't know how to get my console back. Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] SMP/i386 suspend/resume
Hi, Thanks for your report. From: Peter Jeremy pe...@rulingia.com Subject: Re: [CFT] SMP/i386 suspend/resume Date: Fri, 11 May 2012 21:20:05 +1000 Message-ID: 2012052005.ga87...@server.rulingia.com On 2012-May-11 11:10:19 +0900, Mitsuru IWASAKI iwas...@jp.freebsd.org wrote: I've been working on suspend/resume for SMP/i386 for a week and created patches against CURRENT, RELENG_9 and RELENG_8 available at: Thank you for that. Since I was in the process of upgrading my netbook (Acer Aspire One AOA-110 - Atom N270), I rolled your RELENG_8 patch on top of r235229. Unfortunately, the result hasn't been a complete success. I can suspend to S3 with no problems (though that worked before). The resume is less successful. If X is running, I get a garbage screen. If I suspend at a VTY, the screen comes back correctly but there is no response from keyboard, touchpad or wired network (though it has the correct lights). Let me know if you have any suggestions for debugging. I think graphic driver (or pic?) has some problems on resume and they are out of scope of my patches. HEAD and RELENG_9 have better support on interrupt re-enabling than RELENG_8 I think. Could you try them? And for ps/2 mouse, kernel option PSM_HOOKRESUME and PSM_RESETAFTERSUSPEND would be useful. Thanks -- Peter Jeremy ___ 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: [CFT] SMP/i386 suspend/resume
Hi, Thanks for you report. From: David Wolfskill d...@freebsd.org Subject: Re: [CFT] SMP/i386 suspend/resume Date: Fri, 11 May 2012 13:22:57 + Message-ID: 20120511132257.ga96...@freefall.freebsd.org On Fri, May 11, 2012 at 11:10:19AM +0900, Mitsuru IWASAKI wrote: Hi I've been working on suspend/resume for SMP/i386 for a week and created patches against CURRENT, RELENG_9 and RELENG_8 available at: http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_9-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_8-20120511.diff ... I'm sorry to report that while head stable/9 did work for me (see previous notes in this thread), stable/8 did not. Well, suspend seemed to, but on resume, the screen stayed dark and the machine was (as far as I could tell without trying to ping it from another machine) unresponsive. OK, we need some more investigation on RELENG_8 SMP. I think Core 2 Duo can run amd64, would like to confirm this problem can be reproduced only on i386 or not. Could you try same thing on amd64? Thanks This was on the same Dell Precision M4400 as before (Core(TM)2 Duo CPU T9600), running: FreeBSD localhost 8.3-STABLE FreeBSD 8.3-STABLE #382 235262M: Fri May 11 04:45:52 EDT 2012 root@localhost:/common/S1/obj/usr/src/sys/CANARY i386 Peace, david -- David H. Wolfskilld...@freebsd.org There is a use for spam: it helps identify spammers. I have no use for spammers. ___ 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: [CFT] SMP/i386 suspend/resume
On Sun, May 13, 2012 at 10:59:17PM +0900, Mitsuru IWASAKI wrote: OK, we need some more investigation on RELENG_8 SMP. I think Core 2 Duo can run amd64, would like to confirm this problem can be reproduced only on i386 or not. Could you try same thing on amd64? Well, that will require a bit more work -- I'm pretty sure the hardware can run amd64, but I only have i386 inistalled presently. And I'm getting ready to head to the airport to fly back home now. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgphBxFgtbr6Y.pgp Description: PGP signature
Re: panic, seems related to r234386
On Sun, May 13, 2012 at 12:49:38AM +0200, Mateusz Guzik wrote:
On Thu, May 10, 2012 at 12:39:00PM +0200, Peter Holm wrote:
On Thu, May 10, 2012 at 12:21:18PM +0200, Mateusz Guzik wrote:
On Tue, May 08, 2012 at 09:45:14PM +0200, Peter Holm wrote:
On Mon, May 07, 2012 at 10:11:53PM +0200, Mateusz Guzik wrote:
On Mon, May 07, 2012 at 12:28:41PM -0700, Doug Barton wrote:
On 05/06/2012 15:19, Sergey Kandaurov wrote:
On 7 May 2012 01:54, Doug Barton do...@freebsd.org wrote:
I got this with today's current, previous (working) kernel is
r232719.
panic: _mtx_lock_sleep: recursed on non-recursive mutex struct
mount mtx
@ /frontier/svn/head/sys/kern/vfs_subr.c:4595
...
Please try this patch.
Index: fs/ext2fs/ext2_vfsops.c
===
--- fs/ext2fs/ext2_vfsops.c (revision 235108)
+++ fs/ext2fs/ext2_vfsops.c (working copy)
@@ -830,7 +830,6 @@
/*
* Write back each (modified) inode.
*/
- MNT_ILOCK(mp);
loop:
MNT_VNODE_FOREACH_ALL(vp, mp, mvp) {
if (vp-v_type == VNON) {
Didn't help, sorry. I put 234385 through some pretty heavy load
yesterday, and everything was fine. As soon as I move up to 234386,
the
panic triggered again. So I cleaned everything up, applied your
patch,
built a kernel from scratch, and rebooted. It was Ok for a few
seconds
after boot, then panic'ed again, I think in a different place, but
I'm
not sure because subsequent attempts to fsck the file systems
caused new
panics which overwrote the old ones before they could be saved.
Another MNT_ILOCK was hiding few lines below, try this patch:
http://student.agh.edu.pl/~mjguzik/patches/ext2fs-ilock.patch
I've tested this a bit and I believe this fixes your problem.
Gave this a spin and found what looks like a deadlock:
http://people.freebsd.org/~pho/stress/log/ext2fs.txt
Not a new problem, it would seem. Same issue with 8.3-PRERELEASE
r232656M.
pid 2680 (fts) holds lock for vnode cb4be414 and tries to lock cc0ac15c
pid 2581 (openat) holds lock for vnode cc0ac15c and tries to lock cb4be414
openat calls rmdir foo/bar and ext2_rmdir unlocks and tries to lock
again foo's vnode.
This is fairly easly reproducible with concurrently running mkdir and fts
testcase programs that are provided by stress2.
I'll try to come up with a patch by the end of the week.
Easier way to reproduce: mkdir from stress2 and while true; do find /mnt
/dev/null; done on another terminal.
Assuming foo/bar directory tree, deadlock happens during removal of bar
with simultaneous lookup of .. in bar.
Proposed trivial patch:
http://student.agh.edu.pl/~mjguzik/patches/ext2fs_rmdir-deadlock.patch
If the lock cannot be acquired immediately unlocks 'bar' vnode and then
locks both vnodes in order.
After patching this I ran into another issue - wrong vnode type panics
from cache_enter_time after calls by ext2_lookup. (It takes some time to
reproduce this, testcase as before.)
It looks like ext2_lookup is actually adapted version of ufs_lookup and
lacks some bugfixes present in current ufs_lookup. I believe those
bugfixes address this bug.
Here is my attempt to fix the problem (based on ufs_lookup changes):
http://student.agh.edu.pl/~mjguzik/patches/ext2fs_lookup-relookup.patch
I have tested these two patches for a few hours and they do indeed
seem to fix the problem I had seen before.
Regards,
- 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: [CFT] SMP/i386 suspend/resume
Hi, Thanks for your report. From: Gustau Pérez i Querol gpe...@entel.upc.edu Subject: Re: [CFT] SMP/i386 suspend/resume Date: Sun, 13 May 2012 09:57:33 +0200 Message-ID: 4faf696d.3060...@entel.upc.edu Al 11/05/2012 04:10, En/na Mitsuru IWASAKI ha escrit: Hi I've been working on suspend/resume for SMP/i386 for a week and created patches against CURRENT, RELENG_9 and RELENG_8 available at: http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_9-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_8-20120511.diff A lot of portion of the patches was ported from amd64. Testing on Thinkpad X60 (Core Duo T2300), so far so good :) I'll commit them against CURRENT hopefully next week. Reporting from an Acer Centrino Duo, running CURRENT r235266. The machine has an nvidia card (Ge7300go). The acpi_video and nvidia modules are there. I did test it a few times with X running (plain twm) and worked just fine. Setting hw.acpi.lid_switch_state=S3 allowed me to use the close-the-lid-to-sleep functionality. The problem comes when I suspend the machine in the console. The machine resumes fine (I can ping and ssh it) but the screen remains black. I set hw.acpi.reset_video to 0 or 1 but no go. If I'm in a console but X is running, after the resume I can CTRL+ALT+F9 and get my video back; then I can return to the console. If I don't have X running, I don't know how to get my console back. I think this is graphic driver problem. nvidia's driver seems to have correct suspend/resume method. http://www.nvidia.com/object/freebsd_archive.html Have you try it? Thanks Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] SMP/i386 suspend/resume
Hi, From: David Wolfskill da...@catwhisker.org Subject: Re: [CFT] SMP/i386 suspend/resume Date: Sun, 13 May 2012 07:03:02 -0700 Message-ID: 20120513140302.gi13...@albert.catwhisker.org On Sun, May 13, 2012 at 10:59:17PM +0900, Mitsuru IWASAKI wrote: OK, we need some more investigation on RELENG_8 SMP. I think Core 2 Duo can run amd64, would like to confirm this problem can be reproduced only on i386 or not. Could you try same thing on amd64? Well, that will require a bit more work -- I'm pretty sure the hardware can run amd64, but I only have i386 inistalled presently. And I'm getting ready to head to the airport to fly back home now. Understood. I don't need to hurry on this. BTW, amd64 Live CD might be useful for this purpose. Thanks! Peace, david -- David H. Wolfskillda...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. ___ 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: [CFT] SMP/i386 suspend/resume
Enviat des del meu iTotxo El 13/05/2012, a les 16:40, Mitsuru IWASAKI iwas...@jp.freebsd.org va escriure: Hi, Thanks for your report. From: Gustau Pérez i Querol gpe...@entel.upc.edu Subject: Re: [CFT] SMP/i386 suspend/resume Date: Sun, 13 May 2012 09:57:33 +0200 Message-ID: 4faf696d.3060...@entel.upc.edu Al 11/05/2012 04:10, En/na Mitsuru IWASAKI ha escrit: Hi I've been working on suspend/resume for SMP/i386 for a week and created patches against CURRENT, RELENG_9 and RELENG_8 available at: http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-CURRENT-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_9-20120511.diff http://people.freebsd.org/~iwasaki/acpi/i386-SMP-suspend-RELENG_8-20120511.diff A lot of portion of the patches was ported from amd64. Testing on Thinkpad X60 (Core Duo T2300), so far so good :) I'll commit them against CURRENT hopefully next week. Reporting from an Acer Centrino Duo, running CURRENT r235266. The machine has an nvidia card (Ge7300go). The acpi_video and nvidia modules are there. I did test it a few times with X running (plain twm) and worked just fine. Setting hw.acpi.lid_switch_state=S3 allowed me to use the close-the-lid-to-sleep functionality. The problem comes when I suspend the machine in the console. The machine resumes fine (I can ping and ssh it) but the screen remains black. I set hw.acpi.reset_video to 0 or 1 but no go. If I'm in a console but X is running, after the resume I can CTRL+ALT+F9 and get my video back; then I can return to the console. If I don't have X running, I don't know how to get my console back. I think this is graphic driver problem. nvidia's driver seems to have correct suspend/resume method. http://www.nvidia.com/object/freebsd_archive.html Have you try it? Yes, it is running the propietary driver. Everything was done with it loaded. Do you want me to try without the nvidia binary driver? OTOH, IIRC the console only test (without X) without acpi_video lead to freeze. No crash dump. The machine has no serial or fwire ports :( Thanks Gus Thanks Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACPI 'driver bug: Unable to set devclass'
on 13/05/2012 11:39 Bruce Cran said the following: I've just updated to -current and noticed the following errors in dmesg: acpi0: NEC on motherboard acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bbf0 (3) failed driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) cpu0: ACPI CPU on acpi0 ACPI Warning: Incorrect checksum in table [OEMB] - 0x45, should be 0x44 (20120420/tbutils-293) driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu2: ACPI CPU on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu1: ACPI CPU on acpi0 driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) Can you produce an equivalent snippet with verbose logging enabled? I have a suspicion that these messages are a byproduct from r231161. -- Andriy Gapon ___ 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
SUJ file system corruption.
FYI: Saw a crash due to filesystem corruption when running SUJ. This is on a ARM AM335x system (BeagleBone) that is still pretty experimental, so I certainly cannot rule out other problems, but in case it means something to someone, here's the scenario: Reset the board to reboot (which is routine for these small embedded boards) and when it came back up it went through SUJ recovery, and then a little later the kernel panicked with this stack trace: rm: /var/run/dmesg.boot: Bad file descriptor panic: ffs_write: type 0xc1e86660 0 (0,1024) KDB: enter: panic [ thread pid 492 tid 100044 ] Stopped at $d: ldrbr15, [r15, r15, ror r15]! db bt Tracing pid 492 tid 100044 td 0xc1dbc5c0 kdb_enter() at kdb_enter+0xc scp=0xc0321c08 rlv=0xc02f0024 (panic+0xe8) rsp=0xcb3e3ba8 rfp=0xcb3e3bbc r4=0x0100 panic() at panic+0x10 scp=0xc02eff4c rlv=0xc043b2f4 (ffs_write+0x114) rsp=0xcb3e3bd0 rfp=0xcb3e3c48 ffs_write() at ffs_write+0xc scp=0xc043b1ec rlv=0xc049d55c (VOP_WRITE_APV+0x128) rsp=0xcb3e3c4c rfp=0xcb3e3cf0 r10=0x00020001 r9=0x r8=0x r7=0x r6=0x r5=0xcb3e3cfc r4=0xc055a78c VOP_WRITE_APV() at VOP_WRITE_APV+0xc scp=0xc049d440 rlv=0xc0390ca4 (vn_write+0x28c) rsp=0xcb3e3cf4 rfp=0xcb3e3d3c r7=0xcb3e3db4 r6=0xc1dc09a0 r5=0xc1e86660 r4=0x vn_write() at vn_write+0xc scp=0xc0390a24 rlv=0xc0339c88 (dofilewrite+0x98) rsp=0xcb3e3d40 rfp=0xcb3e3d70 r10=0x r9=0x0400 r8=0xc1dc09a0 r7=0xc1dbc5c0 r6=0x0001 r5=0xcb3e3db4 r4=0x dofilewrite() at dofilewrite+0xc scp=0xc0339bfc rlv=0xc033b508 (kern_writev+0x60) rsp=0xcb3e3d74 rfp=0xcb3e3da8 r10=0x r9=0xbfffecec r8=0xc1dbc5c0 r7=0xcb3e3db4 r6=0x0001 r5=0x r4=0x kern_writev() at kern_writev+0xc scp=0xc033b4b4 rlv=0xc033b620 (sys_write+0x58) rsp=0xcb3e3dac rfp=0xcb3e3de0 r8=0x r7=0xc1d9a000 r6=0xc1dbc5c0 r5=0xcb3e3eac r4=0x2047c400 sys_write() at sys_write+0xc scp=0xc033b5d4 rlv=0xc048934c (swi_handler+0x2d0) rsp=0xcb3e3de4 rfp=0xcb3e3ea8 swi_handler() at swi_handler+0xc scp=0xc0489088 rlv=0xc047c440 (swi_entry+0x28) rsp=0xcb3e3eac rfp=0xbfffea5c r10=0x2017be50 r8=0x2041c000 r7=0x002d r6=0x0400 r5=0x2017cc18 r4=0x2047c400 Rebooted and ran fsck -y without using the journal and noticed: ** Phase 2 - Check Pathnames UNALLOCATED I=244 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 00:00 1970 NAME=/var/run/dmesg.boot UNEXPECTED SOFT UPDATE INCONSISTENCY If I can find a way to reproduce this, I'll let you know. Cheers, Tim ___ 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: ACPI 'driver bug: Unable to set devclass'
On 13/05/2012 21:06, Andriy Gapon wrote: Can you produce an equivalent snippet with verbose logging enabled? I have a suspicion that these messages are a byproduct from r231161. acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bbf0 (3) failed acpi_sysresource: acpi_sysresource0 already exists; skipping it driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) acpi_timer: acpi_timer0 already exists; skipping it driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) cpu0: ACPI CPU on acpi0 ACPI Warning: Incorrect checksum in table [OEMB] - 0x45, should be 0x44 (20120420/tbutils-293) ACPI: SSDT 0xbb7900f0 01340 (v01 DpgPmm P001Ist 0011 INTL 20051117) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0 01340 (v01 DpgPmm P001Ist 0011 INTL 20051117) ACPI: SSDT 0xbb791430 004F4 (v01 PmRef P001Cst 3001 INTL 20051117) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0 004F4 (v01 PmRef P001Cst 3001 INTL 20051117) acpi_sysresource: acpi_sysresource2 already exists; skipping it driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu2: ACPI CPU on acpi0 acpi_sysresource: acpi_sysresource1 already exists; skipping it driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) cpu1: ACPI CPU on acpi0 acpi_sysresource: acpi_sysresource3 already exists; skipping it driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) -- Bruce Cran ___ 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: [review request] usr.sbin/service - make showing files configurable
On 5/12/2012 8:23 PM, Bryan Drewery wrote: Hi, I found service(8) to be inconsistent that it listed files with `service -e`, but plain services with `service -l` That behavior is by design. Thanks for your interest, Doug -- This .signature sanitized for your protection ___ 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: r235275 - projects user
When you proposed these changes not only did I not see a consensus for you to move forward, I saw a non-zero number of people push back. Why did you proceed? Doug On 5/11/2012 9:08 AM, Ulrich Spoerlein wrote: Author: uqs Date: Fri May 11 16:08:51 2012 New Revision: 235275 URL: http://svn.freebsd.org/changeset/base/235275 Log: Update guidelines on user/ and projects/ The goal is to make it clearer where future branches should be created. A consistent layout under projects/ would also help with conversions to other VCSes that do not follow the everything-is-a-subdir dogma. TL;DR - If it's a branch of head that you want to merge back - projects/ - If it's something else - user/your-login/ (e.g. portmaster, stress2, etc.) Discussed on: developers Silence by: peter Modified: user/GUIDELINES.txt Changes in other areas also in this revision: Modified: projects/GUIDELINES.txt Modified: user/GUIDELINES.txt == --- user/GUIDELINES.txt Fri May 11 16:04:55 2012(r235274) +++ user/GUIDELINES.txt Fri May 11 16:08:51 2012(r235275) @@ -1,16 +1,9 @@ $FreeBSD$ -Golden rules: -Rule #1: TAKE IT EASY! DON'T RUSH AND MAKE A MESS! ASK IF NEEDED! -Rule #2: See rule #1, repeat as needed +Guidelines for what can go in /user +--- -Peril sensitive sunglasses advisory: -This is in flux. Expect refinement. Expect typos. - -Guidelines for what can go in /user and /projects -- - -First of all, eveyrbody needs to keep in mind that this repository is +First of all, everybody needs to keep in mind that this repository is replicated as a unit. Anything that goes into the repository uses project and volunteer resources. Once something goes in, it essentially never comes out. Therefore, these are not dumping grounds to put random junk in the @@ -19,82 +12,39 @@ tree that we have to mirror forever. General guidelines: * Should be relevant to FreeBSD. -* Should be at least concievably of interest to somebody else. -* Should be in a format that is suitable to merge into the base tree. +* Should be at least conceivably of interest to somebody else. * Should be something that is worth people's time to read commit mail for. * Write decent commit messages! +The difference between /projects and /user wasn't very clear in the past. +Going forward /projects is reserved for branches of FreeBSD itself for possible +re-integration into /head. Branches shall not be nested into e.g. +/projects/foo/stable8, instead /projects/foo_stable8 shall be used. -The difference between /projects and /user is mostly one of intentions. - -If some WIP is intended to be committed to the main src tree, then it -should go in /projects/$name/*. We encourage people to subscribe to projects -commit messages. The reason is that WIP in projects can be expected to hit -the base tree at some point. - -If some WIP is more of an experiment or speculative, that might not ever be -merged, then it goes in /user/$username/$name/*. We don't encourage -people to subscribe to user commit messages. - -If it is something unrelated to the src tree, it should probably go elsewhere. -There will be a separate repostory made available for such things, whether it -be a special version of mysql or xorg or gcc or whatever. - +/user can be used for tools and software tightly related to FreeBSD, but which +is not a copy/branch of FreeBSD itself. Layout: -Since this is for WIP that can concievably be merged, there is an argument -that can be made that teaching the pre-commit scripts to sanity check WIP -as it goes, rather than having a mammoth fixup being needed prior to merging. - -For that to work, the layout has to be predictable. eg: a branch of -head/sys/* for a project called ia65 should be /projects/ia65/sys/*. -An experimental X11-aware verison of bin/ls/* in a user directory for jdoe -would be /user/jdoe/x11-ls/bin/ls/*. - -Creation and merging: - -Merging is in flux. The procedure as understood right now: - -Assume projects/ia65/sys. $BASE=svn+ssh://svn.freebsd.org/base +Since this is for auxiliary/experimental projects that might not be branched +from head, an argument can be made that we teach the pre-commit scripts to +sanity check WIP as it goes in. Initial creation: - $ svn cp --parents $BASE/head/sys $BASE/projects/ia65/sys + Assume user/pho/stress2. BASE=svn+ssh://svn.freebsd.org/base -Then check it out: - $ svn co $BASE/projects/ia65 + $ svn mkdir $BASE/user/pho/stress2 -To integrate changes from head into your branch: - $ cd ia65/sys ; svn update; svn status | read output! Should preferably be clean. - (you may prefer to do merges in a second, clean checkout. It will be easier!) - $
FYI FreeBSD clang build fails on new import of sort
trying to rerun a clang build of FreeBSD CURRENT fails on new import of sort, cat /etc/src.conf WITH_CLANG_IS_CC=1 make world -SNIP--- clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/coll.c clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/file.c /usr/src/usr.bin/sort/file.c:601:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(7)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n)catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:942:11: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(8)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n)catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1279:10: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(9)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n)catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1295:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] errx(2, getstr(10)); ^~ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n)catgets(catalog, 1, n, nlsstr[n]) ^ 4 errors generated. *** [file.o] Error code 1 Stop in /usr/src/usr.bin/sort. ___ 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: FYI FreeBSD clang build fails on new import of sort
On Sun, May 13, 2012 at 5:02 PM, Outback Dingo outbackdi...@gmail.com wrote: trying to rerun a clang build of FreeBSD CURRENT fails on new import of sort, cat /etc/src.conf WITH_CLANG_IS_CC=1 make world -SNIP--- clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/coll.c clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/file.c /usr/src/usr.bin/sort/file.c:601:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(7)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:942:11: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(8)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1279:10: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(9)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1295:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] errx(2, getstr(10)); ^~ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ 4 errors generated. *** [file.o] Error code 1 Stop in /usr/src/usr.bin/sort. Yeah... errx(2, getstr(9)) should be errx(2, %s, getstr(9))... -Garrett ___ 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: FYI FreeBSD clang build fails on new import of sort
Thank you for the error report, we are going to fix it ASAP. Oleg -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- curr...@freebsd.org] On Behalf Of Garrett Cooper Sent: Sunday, May 13, 2012 5:49 PM To: Outback Dingo Cc: freebsd-current Subject: Re: FYI FreeBSD clang build fails on new import of sort On Sun, May 13, 2012 at 5:02 PM, Outback Dingo outbackdi...@gmail.com wrote: trying to rerun a clang build of FreeBSD CURRENT fails on new import of sort, cat /etc/src.conf WITH_CLANG_IS_CC=1 make world -SNIP--- clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/coll.c clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/file.c /usr/src/usr.bin/sort/file.c:601:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(7)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:942:11: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(8)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1279:10: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(9)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1295:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] errx(2, getstr(10)); ^~ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ 4 errors generated. *** [file.o] Error code 1 Stop in /usr/src/usr.bin/sort. Yeah... errx(2, getstr(9)) should be errx(2, %s, getstr(9))... -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current- unsubscr...@freebsd.org ___ freebsd-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: FYI FreeBSD clang build fails on new import of sort
Obviously, the option -Wall implies -Wformat-security in clang. The compiler that we used for the development does not turns on -Wformat-security with -Wall. It is an easy fix, we will submit it soon. Thanks Oleg -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- curr...@freebsd.org] On Behalf Of Garrett Cooper Sent: Sunday, May 13, 2012 5:49 PM To: Outback Dingo Cc: freebsd-current Subject: Re: FYI FreeBSD clang build fails on new import of sort On Sun, May 13, 2012 at 5:02 PM, Outback Dingo outbackdi...@gmail.com wrote: trying to rerun a clang build of FreeBSD CURRENT fails on new import of sort, cat /etc/src.conf WITH_CLANG_IS_CC=1 make world -SNIP--- clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/coll.c clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/sort/file.c /usr/src/usr.bin/sort/file.c:601:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(7)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:942:11: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(8)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1279:10: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] err(2, getstr(9)); ^ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ /usr/src/usr.bin/sort/file.c:1295:12: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security] errx(2, getstr(10)); ^~ /usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr' #define getstr(n) catgets(catalog, 1, n, nlsstr[n]) ^ 4 errors generated. *** [file.o] Error code 1 Stop in /usr/src/usr.bin/sort. Yeah... errx(2, getstr(9)) should be errx(2, %s, getstr(9))... -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current- unsubscr...@freebsd.org ___ freebsd-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: [CFT] SMP/i386 suspend/resume
Hi, Reporting from an Acer Centrino Duo, running CURRENT r235266. The machine has an nvidia card (Ge7300go). The acpi_video and nvidia modules are there. I did test it a few times with X running (plain twm) and worked just fine. Setting hw.acpi.lid_switch_state=S3 allowed me to use the close-the-lid-to-sleep functionality. The problem comes when I suspend the machine in the console. The machine resumes fine (I can ping and ssh it) but the screen remains black. I set hw.acpi.reset_video to 0 or 1 but no go. If I'm in a console but X is running, after the resume I can CTRL+ALT+F9 and get my video back; then I can return to the console. If I don't have X running, I don't know how to get my console back. I think this is graphic driver problem. nvidia's driver seems to have correct suspend/resume method. http://www.nvidia.com/object/freebsd_archive.html Have you try it? Yes, it is running the propietary driver. Everything was done with it loaded. Do you want me to try without the nvidia binary driver? Yes, if it doesn't bother you. Hmmm, it doesn't seem related with my SMP/i386 sleep patches. Could you try also Uni-processer kernel (w/o SMP and apic from config file) without my patches? OTOH, IIRC the console only test (without X) without acpi_video lead to freeze. No crash dump. The machine has no serial or fwire ports :( We can improve video initialization on another opportunity. Linux have many video hacks while we have only hw.acpi.reset_video ;) http://www.kernel.org/doc/Documentation/power/video.txt I believe there are some solutions for you in this document, then we can implement them in our source if found. Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
