Re: ACPI broke going from 8 to 9
On Sat, Dec 31, 2011 at 3:31 PM, Jeremy Chadwick wrote: > On Sat, Dec 31, 2011 at 04:17:16PM -0700, Dan Allen wrote: >> On 31 Dec 2011, at 12:34 PM, Garrett Cooper wrote: >> >> > Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and >> > try booting the new kernel. See if this works. >> >> It worked! No hang, power button works. Nice. I hope this experimental >> option stays in. >> >> Thank you everyone for your help. Happy New Years! > > This option isn't documented **anywhere** in the entire src tree. It's > purely #ifdef all over. > > The code in question was committed 7 months ago. It was MFC'd to > RELENG_8 6 months ago. Here's the HEAD commit message: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pci/pci.c#rev1.420 > > The RELENG_8 MFC is revision 1.386.2.15. > > The committer is jhb@, with mav@ being the individual who tested it, so > I imagine either of these folks will have some excellent insights as to > what's causing Dan's problem. I'm CC'ing them both directly on this > thread. > > In the meantime: Dan, when you say in your original mail, "I just > upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9", can you > please provide uname -a output from the system when it was running > RELENG_8? I'm looking specifically for the exact time when the kernel > was built, because there may have been fixes (that broke things for you) > between the above commit and present-day RELENG_8 (I have not examined > all commits). It's going to be the feature that's going to cause headaches post-9.0-RELEASE based on my observations of several mailing list posts and the fact that 9.0 isn't actually RELEASEd yet (people have run into issues with acpi, atkbdc, mfi, and usb so far, but that's probably not everything). If it could be made into a runtime tunable, that would be awesome, but that would require changes to driver structures and methods. With a little pointer aliasing and tunable guard sprinkling it wouldn't be hard to solve -- but it's still work. In the meantime, could someone please commit PR # 163748 to note what NEW_PCIB is and MFC it to RELENG_9 and could we consider disabling NEW_PCIB on i386 and pc98 until all the issues are ironed out? Thanks, -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: ACPI broke going from 8 to 9
On 31 Dec 2011, at 4:31 PM, Jeremy Chadwick wrote: > In the meantime: Dan, when you say in your original mail, "I just > upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9", can you > please provide uname -a output from the system when it was running > RELENG_8? I'm looking specifically for the exact time when the kernel > was built Almost every day I csup from RELENG_x and build. The traces of RELENG_8 are gone, so no, unfortunately I cannot give you a uname -a from those days. However, I have a build log file, and I see that I moved from RELENG_8 to RELENG_9 on Friday, Dec 23, 2011. I csup'd at 12:24:26 MST and discovered the failure at 15:41 MST. This "nooptions NEW_PCIB" fix does seem rather tenuous if it is not documented. Wouldn't a better route be something like if (ACPI < 2.0) oldCode(); else newCodeForNewACPI(); so that it will always work for everyone without having to build a special kernel? After all, I went from a working system to a hung system which is not the best upgrade path... ;-) Dan ___ 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 broke going from 8 to 9
On Sat, Dec 31, 2011 at 04:17:16PM -0700, Dan Allen wrote: > On 31 Dec 2011, at 12:34 PM, Garrett Cooper wrote: > > > Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and > > try booting the new kernel. See if this works. > > It worked! No hang, power button works. Nice. I hope this experimental > option stays in. > > Thank you everyone for your help. Happy New Years! This option isn't documented **anywhere** in the entire src tree. It's purely #ifdef all over. The code in question was committed 7 months ago. It was MFC'd to RELENG_8 6 months ago. Here's the HEAD commit message: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pci/pci.c#rev1.420 The RELENG_8 MFC is revision 1.386.2.15. The committer is jhb@, with mav@ being the individual who tested it, so I imagine either of these folks will have some excellent insights as to what's causing Dan's problem. I'm CC'ing them both directly on this thread. In the meantime: Dan, when you say in your original mail, "I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9", can you please provide uname -a output from the system when it was running RELENG_8? I'm looking specifically for the exact time when the kernel was built, because there may have been fixes (that broke things for you) between the above commit and present-day RELENG_8 (I have not examined all commits). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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 broke going from 8 to 9
On 31 Dec 2011, at 12:34 PM, Garrett Cooper wrote: > Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and > try booting the new kernel. See if this works. It worked! No hang, power button works. Nice. I hope this experimental option stays in. Thank you everyone for your help. Happy New Years! Dan ___ 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 broke going from 8 to 9
On 31 December 2011 16:08, Dan Allen wrote: > Almost every day I csup from RELENG_x and build. The traces of RELENG_8 are > gone, so no, unfortunately I cannot give you a uname -a from those days. Would you consider having a small partition to do the same for HEAD? :P > However, I have a build log file, and I see that I moved from RELENG_8 to > RELENG_9 on Friday, Dec 23, 2011. I csup'd at 12:24:26 MST and discovered > the failure at 15:41 MST. > > This "nooptions NEW_PCIB" fix does seem rather tenuous if it is not > documented. Wouldn't a better route be something like > > if (ACPI < 2.0) > oldCode(); > else > newCodeForNewACPI(); > > so that it will always work for everyone without having to build a special > kernel? After all, I went from a working system to a hung system which is > not the best upgrade path... ;-) Well it's hard to test stuff out without the hardware. :) And it's quite possible a lot of silly looking issues are actually working around real bugs in the hardware. I'm glad this issue was solved so quickly for you. Let's hope we can get you onto testing out HEAD (in a separate partition!) so we can ensure we don't break the basic stuff. :) Adrian ___ 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 broke going from 8 to 9
On Sat, Dec 31, 2011 at 11:25 AM, Dan Allen wrote: > > On 31 Dec 2011, at 12:16 PM, Garrett Cooper wrote: > >> Ok. The GX270 is pretty old, so this is probably a stretch but is >> there an ACPI toggle / 'conformance' option in the BIOS? My guess is >> that the machine is 1.0/1.1 spec, not 2.0 spec. >> -Garrett > > No, there is no such option. I have been through all of the settings in the > new BIOS and tried a variety of things, but nothing seems to work. > > Thanks for your help. It sounds like I am out of luck. Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and try booting the new kernel. See if this works. Thanks! -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: ACPI broke going from 8 to 9
On 31 Dec 2011, at 12:16 PM, Garrett Cooper wrote: > Ok. The GX270 is pretty old, so this is probably a stretch but is > there an ACPI toggle / 'conformance' option in the BIOS? My guess is > that the machine is 1.0/1.1 spec, not 2.0 spec. > -Garrett No, there is no such option. I have been through all of the settings in the new BIOS and tried a variety of things, but nothing seems to work. Thanks for your help. It sounds like I am out of luck. Dan ___ 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: segfault from php/freebsd/dtrace
On Thu, Dec 29, 2011 at 12:37 PM, Oleg Ginzburg wrote: > Hi maillist, > > I try to use dtrace + php/dtrace on the freebsd. In certain cases ive get > Segmentation fault and don't understand what of subsystem has a problem. Yes, Userland DTrace is unfortunately still very experimental at this point. I've got a list of at least 10 outstanding bugs that I hope to start addressing early in the new year. In your case, dtrace(1) and/or libproc does not clean up after itself properly in the case of an error. I'm not entirely sure what is causing the segfault in php, though. Which version are you running? The output of uname -a would be helpful. ___ 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 broke going from 8 to 9
On 31 Dec 2011, at 11:40 AM, Garrett Cooper wrote: > Is your Optiplex running the latest BIOS firmware? My Dell OptiPlex GX270 was running BIOS A06, but I found that there was an A07. So I installed A07 hoping that would do the trick, but it still prints: pci0: on pcib0 and then hangs. Dan ___ 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 broke going from 8 to 9
On Sat, Dec 31, 2011 at 10:56 AM, Dan Allen wrote: > > On 31 Dec 2011, at 11:40 AM, Garrett Cooper wrote: > >> Is your Optiplex running the latest BIOS firmware? > > My Dell OptiPlex GX270 was running BIOS A06, but I found that there was an > A07. So I installed A07 hoping that would do the trick, but it still prints: > > pci0: on pcib0 > > and then hangs. Ok. The GX270 is pretty old, so this is probably a stretch but is there an ACPI toggle / 'conformance' option in the BIOS? My guess is that the machine is 1.0/1.1 spec, not 2.0 spec. -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: ACPI broke going from 8 to 9
On Sat, Dec 31, 2011 at 9:03 AM, Dan Allen wrote: > I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9. The > machine no longer boots. However, if I put > > hint.acpi.0.disabled=1 > > in /boot/loader.conf then the machine runs fine. With RELENG_8 the machine > had no loader.conf, and the power button worked on my desktop machine. Now > with ACPI disabled my power button does not work. I have found that the > machine hangs at boot during a scan of the PCI bus, but if I disable that > (hw.acpi.disable=pci) then the machine cannot find a boot drive. > > So I have lost functionality that worked fine in BSD 8. > > Thoughts? Suggestions? Is your Optiplex running the latest BIOS firmware? Thanks! -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"
ACPI broke going from 8 to 9
I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9. The machine no longer boots. However, if I put hint.acpi.0.disabled=1 in /boot/loader.conf then the machine runs fine. With RELENG_8 the machine had no loader.conf, and the power button worked on my desktop machine. Now with ACPI disabled my power button does not work. I have found that the machine hangs at boot during a scan of the PCI bus, but if I disable that (hw.acpi.disable=pci) then the machine cannot find a boot drive. So I have lost functionality that worked fine in BSD 8. Thoughts? Suggestions? Thanks, Dan Allen ___ 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: dump cannot do incremental backups when device name is too long
Am Sun, 11 Sep 2011 10:54:17 +0200 schrieb Martin Sugioarto : > Synopsis: [patch] dump(8) cannot do incremental backups when device > name is too long > > State-Changed-From-To: open->patched > State-Changed-By: mckusick > State-Changed-When: Fri Oct 21 22:49:35 UTC 2011 > State-Changed-Why: > A patch has been applied to head. > It will be MFC'ed after appropriate burnin time. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=160678 Hi all, can someone add this patch (not my version, but the one Mr McKusick posted) to the future release branch? I tested it for a long time now and didn't have any problems. Thank you. -- Martin signature.asc Description: PGP signature
[cft] Small patch for calendar(1)
Hi,
for a while now, calendar(1) seems to have forgotten how to handle what
the man page describes as: 'A month without a day matches the first of
that month.'
A notable result of this is, that the output of 'calendar -f
/usr/share/calendar/calendar.all' is always headed by 'Unprocessed'
error messages.
The attached patch tries to help calendar(1) remember how to do this as
is described in the man page.
Since I'm not an avid calendar(1) user, I'd very much like others to
review and try out the patch, before I go pester commiters by opening a PR.
MfG CoCo
--- src/usr.bin/calendar/parsedata.c.orig 2011-12-31 11:36:40.0
+0100
+++ src/usr.bin/calendar/parsedata.c2011-12-31 11:57:55.0 +0100
@@ -174,11 +174,22 @@
}
if (isonlydigits(date, 1)) {
/* Assume month number only */
- *flags |= F_MONTH;
+ *flags |= (F_MONTH | F_DAYOFMONTH);
+ *idayofmonth = 1;
*imonth = (int)strtol(date, (char **)NULL, 10);
strcpy(month, getmonthname(*imonth));
return(1);
}
+ if ((checkmonth(date, &len, &offset, &pmonth) != 0)) {
+ /* Assume month name only */
+ *flags |= (F_MONTH | F_DAYOFMONTH);
+ *idayofmonth = 1;
+ *imonth = offset;
+ strcpy(month, getmonthname(*imonth));
+ return(1);
+ }
+
+
return (0);
}
}
___
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: atkbdc broken on current ?
I've installed 9.0-RC3 on an Acer Aspir One net book and with acpi enabled atkbdc (and atkbd) are not loaded at all. I can use a usb keyboard with no problems, but once I've selected my boot options the integrated keyboard stops responding. The fix mentioned in this thread does not address my problem. Any suggestions as to what steps I should try next? ___ 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"
