ACPI: working ACPI vs broken ACPI
Hi all, I see these differences here in acpidump: Working board: PM2_GPE0_BLK=0xe428-0xe42f Broken board: PM2_GPE0_BLK=0x428-0x42f PM2_GPE1_BLK=0x528-0x52f, GPE1_BASE=32 And the broken board shows errors like this: The errors like: Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block1 defined as GPE32 to GPE63 ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT Wild guess: Seem to result from this. If I'm looking at NetBSD's http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/acpi/acpi_ec.c they have a lot done since they took acpi from us. I'm sure it works for netbsd. Is anybody working on this ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
linux binary and pwrite() problem...
Hi, I have two fbsd systems, both running 4.7 and linux_base-7.1_2. I am trying to run a gameserver linux binary (sof2 v1.02) on one of these machines but it just hangs if i start it. The strange thing is that exactly the same binary works on the other fbsd box with the same linux_base port. The only thing that differs is the build date of the two boxes, which is '4.7-RELEASE-p4 #0: Sun Feb 9 00:34:14 CET 2003' for the one that doesn't work and '4.7-RELEASE-p2 #13: Sat Dec 7 12:58:57 CET 2002' for the working machine. I have traced the processes on both machines with 'ktrace' and everying looks fine until the following strange thing: On the 'not-working' machine: # kdump ...snip... 94449 sof2ded RET ftruncate 1001/0x3e9 94449 sof2ded CALL lseek 94449 sof2ded RET lseek 1001/0x3e9 94449 sof2ded CALL #208(0x,0x3e9,0x) 94449 sof2ded RET #208 0 94449 sof2ded CALL pwrite(0x4,0xbfbfe618,0xbfbfe588,0x8) 94449 sof2ded RET pwrite 0 94449 sof2ded PSIG SIGILL caught handler=0x8126678 mask=0x0 code=0x0 94449 sof2ded PSIG SIGINT SIG_DFL While on the working box i got the following: # kdump ...snip... 3874 sof2ded RET ftruncate 1001/0x3e9 3874 sof2ded CALL lseek 3874 sof2ded RET lseek 1001/0x3e9 3874 sof2ded CALL #208(0x,0x3e9,0x) 3874 sof2ded RET #208 0 3874 sof2ded CALL write(0x2,0xbfbfd75c,0x24) 3874 sof2ded GIO fd 2 wrote 36 bytes SOF2MP V1.02 linux-i386 Sep 23 2002 I cannot explain why on one box 'pwrite()' is called and on the other one 'write()', is this the first box has a newer build date? Or are there any other components that might have an effect on running linux binaries. Anything else i could do to track down this problem? Cheers, Tom PS: please cc: me for im not subscribed to hackers... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: linux binary and pwrite() problem...
In the last episode (Feb 15), Thomas Spreng said: Hi, I have two fbsd systems, both running 4.7 and linux_base-7.1_2. I am trying to run a gameserver linux binary (sof2 v1.02) on one of these machines but it just hangs if i start it. The strange thing is that exactly the same binary works on the other fbsd box with the same linux_base port. The only thing that differs is the build date of the two boxes, which is '4.7-RELEASE-p4 #0: Sun Feb 9 00:34:14 CET 2003' for the one that doesn't work and '4.7-RELEASE-p2 #13: Sat Dec 7 12:58:57 CET 2002' for the working machine. I have traced the processes on both machines with 'ktrace' and everying looks fine until the following strange thing: On the 'not-working' machine: # kdump ...snip... 94449 sof2ded RET ftruncate 1001/0x3e9 94449 sof2ded CALL lseek 94449 sof2ded RET lseek 1001/0x3e9 94449 sof2ded CALL #208(0x,0x3e9,0x) 94449 sof2ded RET #208 0 94449 sof2ded CALL pwrite(0x4,0xbfbfe618,0xbfbfe588,0x8) 94449 sof2ded RET pwrite 0 94449 sof2ded PSIG SIGILL caught handler=0x8126678 mask=0x0 code=0x0 94449 sof2ded PSIG SIGINT SIG_DFL While on the working box i got the following: # kdump ...snip... 3874 sof2ded RET ftruncate 1001/0x3e9 3874 sof2ded CALL lseek 3874 sof2ded RET lseek 1001/0x3e9 3874 sof2ded CALL #208(0x,0x3e9,0x) 3874 sof2ded RET #208 0 3874 sof2ded CALL write(0x2,0xbfbfd75c,0x24) 3874 sof2ded GIO fd 2 wrote 36 bytes SOF2MP V1.02 linux-i386 Sep 23 2002 I cannot explain why on one box 'pwrite()' is called and on the other one 'write()', is this the first box has a newer build date? Or are there any other components that might have an effect on running linux binaries. You need to install the devel/linux_kdump port and run that instead of kdump on Linux traces. Some syscall numbers map to different functions (#208 for example is unused in FreeBSD but is setresuid() in Linux). -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
FreeSBIE-0.9.0 (beta) released
Fire up your download managers guys, I'm proud to announce that freesbie 0.9.0 livecd is out and ready for download at http://www.freesbie.org/?section=ISO-en This brand new ISO has a beta support for the new init engine of 5.x FreeBSD branch, and many improvements in floppy backup and restore, hard disk autodetection. As this is a beta test, and we need more auditing and test and patches and many other things ;), if you encounter problems please contact us and tell us the description of your problem, with you dmesg and as much debug information as you can. We really need your help. Thanks for attention :) Bye, Dario -- Dario Freni ([EMAIL PROTECTED]) - SaturNero on IRCNet, Azzurra Gruppo Utenti FreeBSD Italia (http://www.gufi.org) GPG Public key at http://www.saturnero.net/saturnero.asc signature.asc Description: Questa parte del messaggio `e firmata
Re: FreeSBIE-0.9.0 (beta) released
On Sat, Feb 15, 2003 at 10:13:41PM +0100, Dario Freni wrote: Fire up your download managers guys, I'm proud to announce that freesbie 0.9.0 livecd is out and ready for download at It might generate more enthusiasm for testing if you could briefly mention what FreeSBIE does. Kris msg39959/pgp0.pgp Description: PGP signature
Re: FreeSBIE-0.9.0 (beta) released
Il Sat, 2003-02-15 alle 23:04, Kris Kennaway ha scritto: It might generate more enthusiasm for testing if you could briefly mention what FreeSBIE does. You're right :) Sorry for that. From www.freesbie.org site: ---8 What is FreeSBIE? Simply: a live system on CD, or an operating system that is able to load directly from a bootable CD, without any installation process, without any hard disk. It's based on the FreeBSD operating system. FreeSBIE project goals are mainly two: - To develop a suite of programs to be used to create your own CD, with all the personalizations you like - To make various ISO images available, maybe each one with its different goals and possible uses. ---8 If you would try the toolkit scripts I suggest you to download them from cvs. More instruction on the site. Cheers, Dario -- Dario Freni ([EMAIL PROTECTED]) - SaturNero on IRCNet, Azzurra Gruppo Utenti FreeBSD Italia (http://www.gufi.org) GPG Public key at http://www.saturnero.net/saturnero.asc signature.asc Description: Questa parte del messaggio `e firmata
Re: FreeSBIE-0.9.0 (beta) released
Kris Kennaway wrote: On Sat, Feb 15, 2003 at 10:13:41PM +0100, Dario Freni wrote: Fire up your download managers guys, I'm proud to announce that freesbie 0.9.0 livecd is out and ready for download at It might generate more enthusiasm for testing if you could briefly mention what FreeSBIE does. Kris -- Part 1.2Type: application/pgp-signature I agree, please, please, please, if something is available for testing, or if there is some interesting link or something it really helps if it is described and if one knows what one is getting into when one goes and does something. Have Fun, Sends Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
where's my pr gone?
what's up with kern/47512: bash in gdb triggers kernel panic it appears empty to me by the way: anyone able to reproduce? quick test, anyone with current, just try gdb bash, do an 'ls', and tell me about the consequences Friedemann To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: where's my pr gone? - supplemental
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/47512 this happens only with the above link, i.e. from the pr summary. searching for the bugid 47512 works (= not empty) someone want to look at this? On Sun, 16 Feb 2003, Friedemann Becker wrote: what's up with kern/47512: bash in gdb triggers kernel panic it appears empty to me by the way: anyone able to reproduce? quick test, anyone with current, just try gdb bash, do an 'ls', and tell me about the consequences Friedemann To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-bugs in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ACPI: working ACPI vs broken ACPI
On Sat, 15 Feb 2003, Martin Blapp wrote: Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block1 defined as GPE32 to GPE63 I see similar errors on my Presario 2100US... Wild guess: Seem to result from this. If I'm looking at NetBSD's http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/acpi/acpi_ec.c they have a lot done since they took acpi from us. I'm sure it works for netbsd. Is anybody working on this ? Martin I've been trying to load that URL since yesterday, but it's not working from here. Can you elaborate on what it does? Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Binary security updates
On december 25th, I released a first draft of a binary security update tool aimed at allowing people to track the security branches without keeping a source tree or recompiling; the response was generally positive, but as I pointed out in my announcement, there were several problems which needed to be fixed. I'm just about finished fixing up all those details, and I intend to release a new version soon and start publishing the necessary updates for i386 4.8-RELEASE when it comes out (not that I expect 4.8-RELEASE to include any security holes, of course ;). These would, of course, be freely available (although I might ask for donations to cover bandwidth costs if I get lots of traffic). Would any FreeBSD developer(s) be willing to help me with this? I'd very much like to have at least one person look over my code and give it some sort of stamp of approval; both for my own peace of mind and to make people feel more happy about using it. Colin Percival To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
ACPI throttle doesn't cool CPU
Greetings, After setting hw.acpi.cpu.performance_speed to 1, a dmesg of acpi_cpu0: set speed to 6.2% and a dog slow system, I am still finding my CPU pumping out heat. It's an AMD 1333 with an A7V board. Is this typical behaviour? If so, I'll just underclock the CPU in the bios. I was hoping to be able to run it at full speed during builds. All this ACPI stuff seems interesting, is it well documented anywhere? The man page wasn't of much use. thanks, sh To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
rfc, optimizing select/poll.
please include me on cc' as I'm not subscribed to this list. I'm thinking about doing some more work on select/poll for freebsd. The gist of my changes would be two modifications. 1) when select has to allocate space via malloc, cache it in the proc struct to avoid dipping into malloc on future calls. 2) get rid of select collisions. now that we have the tracking of the selinfo structs, we can actually allocate then ahead of time and hang them off of the selinfo in the objects, this would have some memory overhead, but get rid of the collision problem. So, what I'm asking is... Can anyone state ahead of time why they would object to this? (please reply publically) Who will test it? (privately plz) Thanks! -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
