cam_periph_mapmem: attempt to map 2779097930 bytes, which is greater than 65536
I've just upgraded to 11-CURRENT and noticed a couple of new cam_periph_mapmem warnings in the dmesg output: Trying to mount root from zfs:zroot []... WARNING: attempt to domain_add(netgraph) after domainfinalize() cam_periph_mapmem: attempt to map 2779097930 bytes, which is greater than 65536 cam_periph_mapmem: attempt to map 2779097930 bytes, which is greater than 65536 If it's relevant, the disks I have installed are: ses0 at ahciem0 bus 0 scbus6 target 0 lun 0 ses0: AHCI SGPIO Enclosure 1.00 0001 SEMB S-E-S 2.00 device ses0: SEMB SES Device ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ST750LX003-1AC154 SM12 ATA-8 SATA 3.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ST31000340NS MA0D ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: ST31000340NS MA08 ATA-8 SATA 2.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad8 ada3 at ahcich4 bus 0 scbus4 target 0 lun 0 ada3: ST31000340NS MA0D ATA-8 SATA 2.x device ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada3: Previously was known as ad12 -- 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: rcs
On 10/9/2013 3:17 PM, Alfred Perlstein wrote: Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That is broken now? At some point it was decided that the installer should be as simple as possible and package installation was a post-install task, for once the system was up and running. I think that might be changing with bsdinstall getting pkgng support, but it did seem like a fairly major regression at the time. -- 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: Any objections/comments on axing out old ATA stack?
On 04/04/2013 09:00, Matthias Andree wrote: Any good concurrent write exercise tools for Unix that I could run on the Linux ext4 partition that you would propose? benchmarks/fio is good for that. -- 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: [HEADSUP] current switched by default to pkgng
On 10/10/2012 17:31, Baptiste Daroussin wrote: Yes there is http://pkg.FreeBSD.org (no website in there no need to try to there) which will point you to pkgbeta.freebsd.org where some packages resides. On my systems pkg.freebsd.org doesn't seem to exist: ping pkg.freebsd.org ping: cannot resolve pkg.freebsd.org: No address associated with name -- 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: FreeBSD 10-CURRENT and 9-STABLE snapshots
On 05/10/2012 15:29, Miroslav Lachman wrote: Unofficial snapshots can be downloaded from https://pub.allbsd.org/FreeBSD-snapshots/ for a long time (bootonly.iso too) I'm baffled as to why those aren't just made official. -- 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: PCIe hotplug
On 21/07/2012 03:04, Julian Elischer wrote: Is anyone looking at PCIe hotplug support? There's a (mostly empty) wiki page at http://wiki.freebsd.org/PCIHotplug . -- 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: [IMPORT] bsdconfig(8)
On 14/07/2012 03:48, Devin Teske wrote: I'm [re-]announcing that (after much delay from the first announcement) that I am finally importing bsdconfig(8) into HEAD. I've noticed a couple of issues: The welcome page mentions setting the root password and the time zone, but bsdinstall will have already done that. ...look at the 'Packages' item in this menu. and on the main page - Most importantly, you can use the Packages utility... - I don't see a Packages entry in the menu. -- 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: [IMPORT] bsdconfig(8)
On 14/07/2012 20:49, Devin Teske wrote: The goal is to have bsdinstall drop those functionalities and instead link to bsdconfig. Won't that mean it'll be possible to end up with an installation without a root password set? -- 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: [IMPORT] bsdconfig(8)
On 14/07/2012 21:17, Devin Teske wrote: The implication is that bsdconfig and bsdinstall will forever live side-by-side once linked together. That includes having bsdconfig live on the installation media so that bsdinstall can utilize it during the installation to (among other things) set the root password. Doesn't that mean that bsdconfig would be invoked as bsdconfig password which would bypass the welcome screen and so by the time the user does see it the root password (and timezone) will have been set? -- 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: [IMPORT] bsdconfig(8)
On 14/07/2012 22:07, Devin Teske wrote: bsdinstall asks to set the root password (by either executing bsdconfig password -- in which a transition is only noticeable because the --backtitle changes from FreeBSD Installer to bsdconfig -- or bsdinstall could instead include /usr/libexec/bsdconfig/040.password/include/password.subr and call the f_dialog_input_password() function where it can control --backtitle to make the usage even more seemless; making bsdconfig's functionality look like bsdinstall's). After asking to set the root password, bsdinstall can now (like sysinstall) ask the user if they'd like to visit the configuration menu one last time to make any additional changes (and bsdconfig -- no arguments -- would provide that menu). You forgot to explain the 'express' mode that bypasses the bsdconfig password step. -- 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: [IMPORT] bsdconfig(8)
On 14/07/2012 22:58, Devin Teske wrote: Did I? When one starts discussing 'Express Install', we're clearly in the realm of bsdinstall, not bsdconfig. Like you stated, in that case bsdinstall would not use bsdconfig. I'm getting really confused here. Either bsdconfig password gets run before the post-install configuration menu is shown and therefore the text saying to set the root password in the welcome screen is unnecessary, or it doesn't get run and it's possible to quit bsdconfig without setting the root password. -- 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: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
On 28/06/2012 00:11, Devin Teske wrote: I'd like to announce that I intend to import bsdconfig(8) today. I haven't seen this get committed yet - was there a problem? -- 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] sysutils/bsdconfig: Replacement for sysinstall(8) post-install configuration abilities
On 27/06/2012 02:11, Devin Teske wrote:
Fixed.
Thanks!
The mouse daemon flags text still seems to have an upper-case 'S'
('Please Specify').
--
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] sysutils/bsdconfig: Replacement for sysinstall(8) post-install configuration abilities
On 27/06/2012 02:11, Devin Teske wrote: Like tzsetup -h and many others that are this way. I just can't win (inconsistencies everywhere in the system w/respect to this). Not at all: bsdconfig claims to support -h whereas tzsetup doesn't: SYNOPSIS tzsetup [-nrs] [-C chroot_directory] [zoneinfo_file | zoneinfo_name] SYNOPSIS bsdconfig [-h] bsdconfig command [-h] bsdconfig [OPTIONS] [command [OPTIONS]] -- 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] sysutils/bsdconfig: Replacement for sysinstall(8) post-install configuration abilities
On 21/06/2012 00:40, Devin Teske wrote: If you have the time and/or energy, please test and report any issues that you experience. I've noticed a few typos and other minor issues: In bsdconfig(8): Contains a link to itself under SEE ALSO. bsdconfig takes a commands as an argument - should be command. bsdconfig mouse: Typo se Configuration menu. Please Specify the mouse daemon flags - don't need upper-case S. bsdconfig hostname: The example should probably be in the example.com domain. bsdconfig netdev: Select a TCP/IP network interface to configure doesn't need TCP/IP. bsdconfig nameservers: Please enter the new TCP/IP address of the DNS nameserver should just be IP address. TCP/IP is being used where just IP was needed in other places too. 'bsdconfig command -h' doesn't always work: bsdconfig hostname -h Illegal option -h -- 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
random device not loaded; using insecure entropy during boot
While booting -current I noticed a new warning introduced in r230230** http://svnweb.freebsd.org/base?view=revisionrevision=230230 (though it's not in 'dmesg' once booted): FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 5 random device not loaded; using insecure entropy I guess something's wanting random data before its been initialized? Once booted kern.random shows that it is loaded and working. -- 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
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: 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: ECC memory driver in FreeBSD 10?
On 6 Apr 2012, at 12:48, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I'm looking for a way to force FreeBSD 10 to maintain/watch ECC errors reported by UEFI (or BIOS). Since ECC is said to be essential for server systems both in buisness and science and I do not question this, I was wondering if I can not report ECC errors via a watchdog or UEFI (ACPI?) report to syslog facility on FreeBSD. FreeBSD is supposed to be a server operating system, as far as I know, so I believe there must be something which didn't have revealed itself to me, yet. FreeBSD logs ECC errors it finds (I don't know how but I doubt it's via the BIOS) by default: I had some RAM go bad a few months ago and messages appeared in dmesg. Is there something in addition you need? -- 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: ABI/architecture identification for packages
On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
i386-32 and amd64-64 is weird and confusing.
IMO, you should go either with x86-{32,64} names, or with i386/amd64,
not with a mix.
Would we ever want to support something like x32 from Linux (which might be
amd64-32)?
http://www.linuxplumbersconf.org/2011/ocw/sessions/531
--
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: sysinstall as a post-install tool
On 04/01/2012 03:39, Craig Rodrigues wrote: Where is the code for this? Would committing your sade additions now to a project branch in Subversion be appropriate? That way folks could check it out from SVN, and provide comments and patches, and help push things along faster. When your code is complete, it could be merged to HEAD. I didn't do the work, it was Andrey Elsukov (ae@) - the code's at http://svnweb.freebsd.org/base/user/ae/usr.sbin/sade/ . While I understand some of the concerns about removing sysinstall in HEAD, I think that sysinstall is so far behind the curve in usefulness, that I think that putting a bullet in its head now and forcing a mini-crisis to implement something better is not a bad idea, even though it may violate POLA. I can see that people prefer bsdinstall so I'll stop trying to keep sysinstall going. -- 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: sysinstall as a post-install tool
On 04/01/2012 00:27, Marcel Moolenaar wrote: ATM it doesn't understand GEOM stuff (like mirror, stripe, raid, ...), but patches to change this and to clean it up internally are more than welcome. There's a rewrite almost ready to go that supports ZFS etc. at http://butcher.heavennet.ru/sade/ - I'm hoping to find some time to finish it off and import it. -- 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: Apropos Removal of sysinstall
On 29/12/2011 18:39, Renato Botelho wrote: IIRC, PCBSD installer can install a regular FreeBSD on ZFS. It can do, but you're left with a /very/ basic installation - the hostname, network interfaces etc. aren't configured, which could be a problem for some people. If I thought there would be any support for it, I'd try and find time to plug in the sade(4) rewrite into sysinstall - it has a rather nice UI and supports ZFS. -- 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: Removal of sysinstall from HEAD and lack of a post-install configuration tool
On 29/12/2011 16:37, Nathan Whitehorn wrote: I'd appreciate any specific comments you might have, and especially specific suggestions for improvements. Except from people who are old hands at sysinstall, I've received almost universally positive comments on the user experience. Patches would be even more appreciated, since real life has intervened to steal most of my FreeBSD time. There was talk in the past that any future installer should be based around the pc-sysinstall backend - has there been any progress towards moving bsdinstall to it? -- 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: Removal of sysinstall from HEAD and lack of a post-install configuration tool
On 29/12/2011 21:30, Chris Rees wrote: Nah, pkg_add -r works and grabs anything you need. Try it with something monstrous (like gcc...) But then you have to know the exact name of the package, which isn't always obvious. -- 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: Removal of sysinstall from HEAD and lack of a post-install configuration tool
I think such a tool should /not/ be a port, since I expect it would include a package browser in it. I think it's something that could really help new users get used to FreeBSD without having to trawl through man pages right at the start. -- Bruce Cran Sent from my iPad On 27 Dec 2011, at 05:05, Doug Barton do...@freebsd.org wrote: On 12/26/2011 20:29, Xin LI wrote: On Mon, Dec 26, 2011 at 3:36 PM, Doug Barton do...@freebsd.org wrote: The story so far ... sysinstall was removed from HEAD in October. I (and others) objected on the basis that at this time there is no replacement for the post-install configuration role that sysinstall played. More sysinstall components were then removed. Then the old version of libdialog (which sysinstall used) was removed. Thus at this point it's not possible to easily restore sysinstall. So my question is, how much do you care? Is lack of that functionality in HEAD something that we care about? Perhaps make it a port instead? I personally don't use sysinstall for post-install tasks at all, but it won't hurt to have such functionality. You're not the first person to suggest that, but I don't see how it's actually responsive to the problem. This issue only affects HEAD, so a port would not be generally useful. It would also be an enormous amount of work to make it into a port. It would be much easier to revert the necessary changes to bring back the old libdialog and sysinstall itself. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: SCHED_ULE should not be the default
On 18/12/2011 10:34, Adrian Chadd wrote: I applaud reppie for trying to make it as easy as possible for people to use KTR to provide scheduler traces for him to go digging with, so please, if you have these issues and you can absolutely reproduce them, please follow his instructions and work with him to get him what he needs. Who's 'reppie'? -- 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: SCHED_ULE should not be the default
On 13/12/2011 09:00, Andrey Chernov wrote: I observe ULE interactivity slowness even on single core machine (Pentium 4) in very visible places, like 'ps ax' output stucks in the middle by ~1 second. When I switch back to SHED_4BSD, all slowness is gone. I'm also seeing problems with ULE on a dual-socket quad-core Xeon machine with 16 logical CPUs. If I run tar xf somefile.tar and make -j16 buildworld then logging into another console can take several seconds. Sometimes even the Password: prompt can take a couple of seconds to appear after typing my username. -- 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: SCHED_ULE should not be the default
On 12/12/2011 15:51, Steve Kargl wrote: This comes up every 9 months or so, and must be approaching FAQ status. In a HPC environment, I recommend 4BSD. Depending on the workload, ULE can cause a severe increase in turn around time when doing already long computations. If you have an MPI application, simply launching greater than ncpu+1 jobs can show the problem. PS: search the list archives for kargl and ULE. This isn't something that can be fixed by tuning ULE? For example for desktop applications kern.sched.preempt_thresh should be set to 224 from its default. I'm wondering if the installer should ask people what the typical use will be, and tune the scheduler appropriately. -- 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: SCHED_ULE should not be the default
On 12/12/2011 23:48, O. Hartmann wrote: Is the tuning of kern.sched.preempt_thresh and a proper method of estimating its correct value for the intended to use workload documented in the manpages, maybe tuning()? I find it hard to crawl a lot of pros and cons of mailing lists for evaluating a correct value of this, seemingly, important tunable. Note that I said for example :) I was suggesting that there may be sysctl's that can be tweaked to improve performance. -- 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: Dog Food tm
On 08/12/2011 15:55, Sean Bruno wrote: BSDInstaller and its predecessor Sysinstall don't have any code to create or destroy zfs(4) or geom(4) volumes. So, the amount of exposure to real users is approaching 0 in comparison to the number of people who really do use FreeBSD. I have my hands full with other projects at the moment, but I'm more than happy to grant access to a two disk SATA server if someone wants to enhance BSDInstall with zfs(4) or geom(4) volume management features. I don't know if it supports RAID, but the geom-aware rewrite of sade(4) supports zfs: http://butcher.heavennet.ru/sade/ Unfortunately it was never completed because of the difficulties of using ncurses/dialog. -- 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: CVS removal from the base
On 04/12/2011 09:08, sth...@nethelp.no wrote: It's not unthinkable. However, IMHO we're then gradually edging closer to various Linux distros that need lots of packages installed to do anything useful. And that, of course, brings up the question - why not just use Linux in the first place? For me, having FreeBSD as a self contained system with lots of useful functionality in the base system is one of the main reasons why I use FreeBSD. +1 -- Bruce ___ 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: possible array out of bounds access in sys/netinet/sctp_output.c
On 27/11/2011 16:52, Michael Tüxen wrote: the reason why we don't use addr_type[] is that the same code is used on different plattforms and (at least at one point of time), using addr_type[] didn't work there. Unfortunately I don't think even the Windows 8 Driver Kit will support much more than stdint.h out of C99. -- 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: 9.0-RC2 - bsdinstall - ifconfig
On 23/11/2011 14:06, Stefan Bethke wrote: http://www.freebsd.org/cgi/query-pr.cgi?pr=162787 That's a much better PR than the one I submitted about the problem last year: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/151229 :) -- 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
9.0-RC1 fails to boot (run_interrupt_driven_hooks: still waiting...)
with 3 vectors em1: Ethernet address: xx:xx:xx:xx:xx:xx uhci3: Intel 82801JI (ICH10) USB controller USB-A port 0xb880-0xb89f irq 23 at device 29.0 on pci0 uhci3: LegSup = 0x2f00 usbus4: Intel 82801JI (ICH10) USB controller USB-A on uhci3 uhci4: Intel 82801JI (ICH10) USB controller USB-B port 0xbc00-0xbc1f irq 19 at device 29.1 on pci0 uhci4: LegSup = 0x2f00 usbus5: Intel 82801JI (ICH10) USB controller USB-B on uhci4 uhci5: Intel 82801JI (ICH10) USB controller USB-C port 0xc000-0xc01f irq 18 at device 29.2 on pci0 uhci5: LegSup = 0x2f00 usbus6: Intel 82801JI (ICH10) USB controller USB-C on uhci5 ehci1: Intel 82801JI (ICH10) USB 2.0 controller USB-A mem 0xfbbf6000-0xfbbf63ff irq 18 at device 29.7 on pci0 usbus7: EHCI version 1.0 usbus7: Intel 82801JI (ICH10) USB 2.0 controller USB-A on ehci1 pcib9: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pbib9 vgapci0: VGA-compatible display port 0xdc00-0xdc7f mem 0xfb00-0xfb7f,0xfafe-0xfaff irq 16 at device 0.0 on pci1 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 ahci0: Intel ICH10 AHCI SATA controller port 0xc080-0xc087,0xc880-0xc883,0xc800-xc807,0xc480-0xc483,0xc400-0xc41f mem 0xfbbf8000-0xfbbf87ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier not supported ahcich0: ACPI channel at channel 0 on ahci0 ahcich1: ACPI channel at channel 1 on ahci0 ahcich2: ACPI channel at channel 2 on ahci0 ahcich3: ACPI channel at channel 3 on ahci0 ahcich4: ACPI channel at channel 4 on ahci0 ahcich5: ACPI channel at channel 5 on ahci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) pcib10: ACPI Host-PCI bridge on acpi0 pci128: ACPI PCI bus on pcib10 pcib11: PCI-PCI bridge at device 0.0 on pci128 pci132: PCI bus on pcib11 pcib12: ACPI PCI-PCI bridge at device 1.0 on pci128 pci131: ACPI PCI bus on pcib12 -- 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: 9.0-RC1 fails to boot (run_interrupt_driven_hooks: still waiting...)
On 13/11/2011 01:07, Bruce Cran wrote: FreeBSD 9.0-RC1 doesn't boot on my Tyan S7025 system: it gets stuck at xpt_config: run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config I had a Firewire card in the machine - removing it caused the problem to go away. -- 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: replacement of ataidle for freebsd 9
Why do you not want to use ataidle? -- Bruce Cran (ataidle maintainer) On 22 Oct 2011, at 11:36, Eugene Dzhurinsky jdeve...@gmail.com wrote: Hello, can somebody please advice how to disable APM power management for HDD on laptops? camcontrol cmd ada0 -a EF 05 00 00 00 00 00 00 00 00 00 00 -v camcontrol: error sending command (pass0:ahcich0:0:0:0): SETFEATURES. ACB: ef 05 00 00 00 00 00 00 00 00 00 00 (pass0:ahcich0:0:0:0): CAM status: ATA Status Error (pass0:ahcich0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass0:ahcich0:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00 What else should I try? uname -a FreeBSD devbox 9.0-RC1 FreeBSD 9.0-RC1 #0: Thu Oct 20 08:48:57 EEST 2011 root@devbox:/usr/obj/usr/src/sys/GENERIC amd64 Thanks! -- Eugene N Dzhurinsky ___ 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: replacement of ataidle for freebsd 9
On 22/10/2011 16:21, Eugene Dzhurinsky wrote: ataidle -P 0 /dev/ada0 ataidle: error opening /dev/ada0 Thanks for reporting the breakage, I'll see if I can get it fixed in time for 9.0. -- 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: FreeBSD 9.0-BETA3 Available...
On 29/09/2011 02:42, Ken Smith wrote: MD5 (FreeBSD-9.0-BETA3-amd64-bootonly.iso) = 2ce7b93d28fd7ff37965893f1af3f7fc MD5 (FreeBSD-9.0-BETA3-amd64-dvd1.iso) = 4affc701f2052edc548274f090e49235 MD5 (FreeBSD-9.0-BETA3-amd64-memstick.img) = e260f2f2122326cb9a93ac83eb006c1c The -dvd1.iso files seem to be less than a CD, at 610MB. Are they expected to contain more data over time, or could 'dvd' be removed? -- 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: 9.0 beta2 the new bsdinstaller
On 18/09/2011 10:55, Thomas Mueller mueller6727@bellsouth.net wrote: Also, I can't see the function of the 64 KB boot partition with no file system, which does not boot for me, though I can boot the main partition using grub2 from the System Rescue CD (http://sysresccd.org/). I seem to remember (perhaps incorrectly) there was a discussion about bumping the default to 128 kB or more for the freebsd-boot partition. Will 64 kB be enough for 9.x? -- 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: ataidle + notebook hdd + 9.0-BETA2
On 14/09/2011 04:59, Nenhum_de_Nos wrote: rush# ataidle -P 243 /dev/ada0 (pass0:ata2:0:0:0): SETFEATURES. ACB: ef 05 00 00 00 40 00 00 00 00 f3 00 (pass0:ata2:0:0:0): CAM status: CCB request completed with an error Failed to configure APM: No error: 0 Can you post the output of ataidle /dev/ada0 to see what features the disk supports? -- 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: FreeBSD 9.0-BETA2 Available...
On 07/09/2011 15:51, Ken Smith wrote: As before one of the many new features of 9.0 we would like tested is the new installer, so fresh installs on test systems are encouraged. The shift in the directory layout described above is in part due to the new installer. FTP-based installs of BETA1 would have failed, as-is the new installer expects this for where to find the FTP install trees: There's still a typo in the installer: Resovler Configuration. Also, it seems the OK button doesn't work if the installer fails to fetch a file - to exit from the Fetch Error screen I had to press Ctrl-C. -- 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: Unusually high LA without any load at FreeBSD9-BETA2
On 06/09/2011 18:05, Garrett Cooper wrote: What is LA? Load Average? -- 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: http://www.freebsd.org/marketing/os-comparison.html
On 29/08/2011 20:58, Volodymyr Kostyrko wrote: = SMP = * (?something about comparing other shedulers with SCHED_ULE), (?some rt stuff), (?some comparison with other interesting shedulers, like DragonflyBSD and QNX). From a recent post to -questions: Alas, during a recent kernel build, I used the -j2 command line option in make and watched as the scheduler repeatedly assigned two instances of cc (the most CPU-intensive program) to the same core. I'm not sure this is something we're really better at, unfortunately: I know I've watched Windows really grok multi-socket, multi-core HyperThreaded systems and prefer real cores on the same NUMA node when running a multi-threaded application, whereas it seems FreeBSD struggles sometimes. -- 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: http://www.freebsd.org/marketing/os-comparison.html
On 30/08/2011 15:30, Mihamina Rakotomandimby wrote: For a _comparison_, I think it's up to somewhere else: To really compare, it's mandatory to really now the multiple compared items. Who cares about the latest MS Windows internals (deep networking capability, filesystem tricks, kernel scheduler specs,...) in here? I migh be wrong, but IMHO core devs and power users wont spend time to deeply investigate on the other systems. You're wrong :) I write Windows drivers for a living, so I care about that stuff. -- 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: http://www.freebsd.org/marketing/os-comparison.html
On 30/08/2011 17:43, Chris Brennan wrote: I do have any idea ... but I don't want to be the one spearheading such a project, I lack the technical skills or the professional expertise to lead this project, but I will certainly contribute if and where possible... I could probably contribute too, since I know quite a bit about Windows and FreeBSD, and I'd be keen to learn about Linux (it would give me a reason to read the copy of Essential Linux Device Drivers I bought!). However I don't have a lot of time at the moment so I certainly couldn't lead the project. -- 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: libdialog strangeness after source upgrade to head/9.0BETA1
On 08/08/2011 11:05, Jakub Lach wrote: Any ideas what I have screwed up (starting from scratch not counting) ? (Unfortunately) it's working as designed: space toggles options and pressing return/enter now presses the active button. You can use tab to move between fields and buttons when there are more than 2 fields. -- 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: USB keyboard problems at mountroot
On 08/08/2011 06:01, Daniel O'Connor wrote: I installed current on a PC with a USB keyboard and found that the keyboard doesn't come up until after mountroot which is a bit of a problem when I bugger up the fstab :) I note there is a PR on this http://www.freebsd.org/cgi/query-pr.cgi?pr=133989 but it hasn't seen much action.. I also recall a thread recently but my google-fu fails me for the moment.. Does anyone have a work around for it? I think setting kern.cam.scsi_delay has worked for me in the past. -- 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: bsdtar(1) can't extract new ISO images
On 06/08/2011 18:02, Martin Matuska wrote: The error is in FreeBSD ISO images. They are created using makefs and that doesn't create ISO files that strictly comple to the ECMA-119 (ISO9660 standard). I have already filed a PR at NetBSD (bin/45217): http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45217 The volume_set_id doesn't have to be filled with 0x20 characters, too. I am also preparing a patch for libarchive (different things), but that won't fix that one bug - makefs needs to be fixed. Thanks for the information - I suspect this is also the problem I saw a few weeks ago on OS X Lion when trying to extract an ISO of Windows Server 2003 R2: neutrino:tmp brucec$ tar -xvf en_win_srv_2003_r2_standard_with_sp2_cd2_X13-68583.iso neutrino:tmp brucec$ echo $? 0 It would be nice if bsdtar exited with a non-zero code in this case. -- 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
9.0-BETA1 installer issues
I've been trying out 9.0-BETA1: it's a lot easier to install than previous releases with bsdinstall, but I spotted a few issues: Typo - Resovler Configuration. If I leave the resolver window for a while it gets corrupted with: Aug 2 10:31:23 dhclient[973]: Bogus domain search list 15: lan, . In the documentation installation screen, it should say At a minimum... - the 'a' is missing. Also, there should perhaps be a semi-colon between English version and this is the original. The menu also doesn't appear to do anything once you select OK. The shell menu should perhaps have a newline after making, to avoid configuration wrapping. Also, the partitioning screen should maybe have Continue instead of Exit. The known issue with the installation not creating /home is still present in BETA1. -- 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: 9.0-BETA1 installer issues
On 02/08/2011 14:36, Nathan Whitehorn wrote: The spelling fixes are easy to fix. The documentation issue is more confusing. It should begin running pkg_add, after you press OK, assuming you selected something. Do you have the installer log handy? It will be in /tmp. I selected both English and French documentation sets but pressing OK just returns back to the final menu. I can't see any log files in /tmp, /root or /var/tmp. -- 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: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 25/07/2011 06:01, Freddie Cash wrote: Thank goodness. The worst thing about sysinstall was that it tried to be a Swiss Army knife doing everything, yet not doing any one thing well. It made a royal mess of rc.conf if you tried to use it to configure a system. Usually the first time someone mentions they use it for post-install configuration, the recommendation is to stop doing that! An os installer should do just that: install the os and nothing else. I tend to disagree with this. For people unfamiliar with FreeBSD using it as a systems administration tool can be really useful, at least until they understand where all the various configuration files are and how they work. Having recently switched to opensuse from Ubuntu I know I find the YaST tool incredibly useful, and probably wouldn't have continued using SuSE if it hadn't been there. Its installer mode is one of the better installers I've come across, and lets you fine-tune the configuration. -- 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
8th July snapshot: bsdinstall not creating homedir
I've installed FreeBSD snapshots a couple of times this week. With Virtualbox 4.1 on both Windows and OS X with a 20GB disk I've found the installer forgets to create the homedir - /home doesn't exist, so when you get placed at / when logging in. Unfortunately pub.allbsd.org seems to be queued up so I've not been able to try any more recent snapshots (should the snapshot ISOs be labelled with -release.iso)? -- 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: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 25/07/2011 00:03, Ron McDowell wrote: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Another potential problem is that the new version of libdialog that the new installer uses changes the way navigation is done: on Linux and in the previous version on FreeBSD it's possible to press Tab to change focus to the buttons and different UI elements. That doesn't work any more. -- 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: Trying to install current from a memory stick and then a DVD and got a new and strange installer.
On 25/07/2011 02:08, Nathan Whitehorn wrote: On 07/24/11 20:03, Bruce Cran wrote: On 25/07/2011 00:03, Ron McDowell wrote: 1) no back button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no minimal install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no post-install uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Another potential problem is that the new version of libdialog that the new installer uses changes the way navigation is done: on Linux and in the previous version on FreeBSD it's possible to press Tab to change focus to the buttons and different UI elements. That doesn't work any more. It's a change from before, but a normalization with respect to most Linux distributions, since we are now using the same dialog as, e.g., Debian and Ubuntu. The Debian 6.0.2.1 installer appears to use the old navigation method, and SuSE 11.4 seems to too. -- 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: Switch from legacy ata(4) to CAM-based ATA
On Thu, 21 Apr 2011 07:51:56 + Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net wrote: a) we MUST HAVE a transition scheme if we cam-base ATA by default. Something that converts things automatically to whatever? That's not been done in more than one year. It's not acceptable to update, reboot and not find the root file system no matter what. We all agreed on that back then. I do not really care how it's done. I have been testing cam based ata for a while now on the machines I can cope with as a developer and even then I screwed the transition partly two times in the last months. How's a normal user to do that flawlessly? In particular it's fairly common that the mapping isn't adX - adaX. I've come across cases where ata(4) created ad10, ad12, ad16, etc. which got mapped to ada0, ada1, ada2 etc. When combined with a USB keyboard that often doesn't work at the root mount prompt, recovery can be a bit tricky. -- 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: Switch from legacy ata(4) to CAM-based ATA
On Wed, 20 Apr 2011 12:57:47 +0300 Alexander Motin m...@freebsd.org wrote: If somebody has any problems with new ATA stack, please repeat your tests with latest HEAD code and contact me if problem is still there. Next three weeks before BSDCan I am going to dedicate to fixing possibly remaining issues. I've not checked recently with -current, but at least on the latest 8-stable there's a problem with using ATA_CAM on Xen: during boot there's a pause for a minute after which run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config is displayed. -- 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: Switch from legacy ata(4) to CAM-based ATA
On Wed, 20 Apr 2011 15:21:48 +0300 Alexander Motin m...@freebsd.org wrote: Verbose dmesg from the fresh system would be appreciated. I've put a verbose dmesg at http://www.cran.org.uk/~brucec/freebsd/dmesg.verbose_20110420.txt -- 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: Switch from legacy ata(4) to CAM-based ATA
On Wed, 20 Apr 2011 21:54:52 +0300 Alexander Motin m...@freebsd.org wrote: Could you show me verbose dmesg with legacy ATA to make sure? Same time I'll try to think what can we do about it. You're right - with the verbose dmesg with ata(4) there are lines: unknown: FAILURE - ATA_IDENTIFY timed out LBA=0 The full dmesg is at http://www.cran.org.uk/~brucec/freebsd/dmesg.verbose_ata_20110420.txt . -- 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: Switch from legacy ata(4) to CAM-based ATA
On Thu, 21 Apr 2011 00:17:44 +0300 Alexander Motin m...@freebsd.org wrote: 2 Bruce: Looking on XEN sources, it seems that the only place how it differs missing and present disk is the device signature. ata(4) at this moment doesn't checks signature if it is not ATAPI and READY bit is set. Attached patch should solve the problem by using more strict check, and I only hope it won't break anything else. Try it please. That seems to have fixed it. Thanks! -- 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
Finding typos using codespell
There's a new tool that can be used to find spelling mistakes in code: codespell from http://www.politreco.com has already been used to find mistakes in both Linux and LLVM. I ran it on sys/ and it found lots of potential typos - the full diff (which I know does contain some incorrect changes) can be found at http://www.cran.org.uk/~brucec/freebsd/codespell_sys.diff . -- 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: Getting /usr/src/ from SVN directly?
On Fri, 25 Mar 2011 16:25:18 -0700 Nerius Landys nlan...@gmail.com wrote: So for example: cd /usr/ rm -rf src/ svn checkout svn://some.repos.freebsd.org/src-all/path/to/ ./src The hostname is svn.freebsd.org, and the branches are under 'base' - i.e. base/head, base/stable/8 etc. svn checkout svn://svn.freebsd.org/base/head -- 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: how to build kernel with CTF data for DTrace?
On Wed, 23 Mar 2011 10:23:50 + (UTC) Anton Yuzhaninov cit...@citrin.ru wrote: options DDB_CTF options KDTRACE_HOOKS makeoptions DEBUG=-g makeoptions WITH_CTF=1 I have rebuild kernel with this options, but: $ ctfdump -l /boot/kernel/kernel /boot/kernel/kernel does not contain .SUNW_ctf data Is instruction in wiki outdated? I think you need to specify WITH_CTF=1 on the commandline, e.g. make WITH_CTF=1 buildkernel -- 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: /etc/rc.d/powerd vs. lack of OID dev.cpu.0.freq
On Thu, 17 Mar 2011 14:41:35 +0200 Andriy Gapon a...@freebsd.org wrote: The OID in question should be provided by cpufreq driver. You should be looking at dmesg and other kernel-related things to find out what changed on that level. The OID does exist - sysctl -d dev.cpu.0.freq works - it's just that querying the value always fails unless EST is enabled. -- 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: /etc/rc.d/powerd vs. lack of OID dev.cpu.0.freq
On Thu, 17 Mar 2011 13:46:01 + Bruce Cran br...@cran.org.uk wrote: On Thu, 17 Mar 2011 14:41:35 +0200 Andriy Gapon a...@freebsd.org wrote: The OID in question should be provided by cpufreq driver. You should be looking at dmesg and other kernel-related things to find out what changed on that level. The OID does exist - sysctl -d dev.cpu.0.freq works - it's just that querying the value always fails unless EST is enabled. So it's been pointed out to me that EST is the only backend on core i7 so by disabling EST there's no way to query/change frequencies - hence the sysctl doesn't work. -- 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: Request for review/testing: switching the default installer
On Mon, 28 Feb 2011 08:49:07 -0600 Nathan Whitehorn nwhiteh...@freebsd.org wrote: - There is only one CD image produced, which is always also a live CD It would be really useful if a netinstall ISO could be made too - people still have slow Internet connections where having a bootonly disc is nice. For example Debian's 35 MB business-card CD is great when you can only download at 50 kB/s. -- 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: Next ZFSv28 patchset ready for testing.
On Wed, 2011-02-23 at 23:28 +0100, Olivier Smedts wrote: I'm successfuly using the following on latest 9-CURRENT : http://people.freebsd.org/~mm/patches/zfs/v28/head-zfsv28-20110219-nopython.patch.xz sys/cddl/compat/opensolaris/sys/sysmacros.h will fail to patch on the latest -CURRENT but that's because the changes have already been added. -- 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: Next ZFSv28 patchset ready for testing.
On Fri, Feb 25, 2011 at 10:59:04AM +0100, Olivier Smedts wrote: Added ? The patch fails because the svn tag is not expanded, but what the patch does is remove the file. You can do so after patching if it failed. It looks like there are two patches to sysmacros.h - the first adds SIGNOF and highbit and the second then removes the file. -- 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: Next ZFSv28 patchset ready for testing.
On Fri, 2011-02-25 at 13:08 +0100, Olivier Smedts wrote: Not the same sysmacros.h, the one patched is sys/cddl/contrib/opensolaris/uts/common/sys/sysmacros.h, the other one you referenced (sys/cddl/compat/opensolaris/sys/sysmacros.h) is removed by the patch. So it is - apologies for the noise. -- 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: Cosmetic path to bsdinstall
On Thu, 24 Feb 2011 09:00:44 -0600 Nathan Whitehorn nwhiteh...@freebsd.org wrote: Having CAM devices be part of newbus would simplify this a very great deal... It's required if we're ever going to have suspend/resume working properly because currently CAM doesn't get a suspend notification, so doesn't know to spin-down disks etc. -- 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: Cosmetic path to bsdinstall
On Thu, 24 Feb 2011 15:38:15 -0500 Jung-uk Kim j...@freebsd.org wrote: FYI, I've been using the following hack for a while now: http://people.freebsd.org/~jkim/ada_suspend.diff Thanks, I'd given up trying to fix this because I was under the impression it needed newbus. I'll see if I can get something similar committed so at least another part of suspend/resume works. I think someone mentioned there was documentation somewhere that was going to be put on the Wiki about what needs done in order to get suspend/resume working properly. Does anyone know where that might be? -- 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: FreeBSD Installer Roadmap
On Wed, 2011-02-23 at 11:33 -0500, John Baldwin wrote: That is mostly true. There are some SCSI BIOSes that would examine the MBR and infer what C/H/S geometry the OS was expecting from the MBR. The original dedicated disk dummy MBR triggered a divide by zero in one of these BIOS ROMs. I guess RAID BIOS's read through the MBR too: my Gigabyte board has an Intel AHCI BIOS (1.20E seems to be the problematic revision) with fakeraid that hangs (requiring a CMOS reset) if you install FreeBSD physically after Windows 7 x64 for example - and some IBM laptops have a bug related to repair partitions and FreeBSD too (http://wiki.pcbsd.org/index.php/Laptops), so they must read the MBR too. -- 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: FreeBSD Installer Roadmap
On Tue, 2011-02-22 at 01:03 -0600, Josh Paetzel wrote: I suppose my last question is along the lines of, If adding geom_mirror support to sysinstall was easy, why has it been 6+ years since gmirror made it's appearance in FreeBSD and you still can't create or install to a gmirror with sysinstall? It's not been added because everyone thinks sysinstall code is horrible and won't touch it. -- 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: FreeBSD Installer Roadmap
On Mon, 2011-02-21 at 16:12 -0600, Josh Paetzel wrote: pc-sysinstall has been used as the PC-BSD installer for quite a while now, and has done a lot of installs on a lot of different hardware platforms. I'll wager that the compatibility of the shell command gpart is a better bet than the stick your thumbs in you ears and yell nananana while you scribble 1's and 0's to a disk and voila, there's a disklabel approach that sysinstall uses. I wish that was true: unfortunately I tried and failed to create a ZFS installation with pc-sysinstall, and I get a few worrying error messages even with UFS while it repartitions the disk - people have been reporting it creating unbootable systems. gpart might be more compatible, but I don't think parsing the output of tools like as fdisk, diskinfo and dmesg is. The concerns about GPT, ZFS, gmirror etc. in sysinstall could all be resolved in a couple of days by ripping out the existing partitioning code and replacing it with ae@'s new version of sade from /user/ae/usr.sbin/sade . However since the future is pc-sysinstall I've now shifted my work to improving the Qt front-end. -- 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: FreeBSD Installer Roadmap
On Mon, 2011-02-21 at 16:12 -0600, Josh Paetzel wrote: pc-sysinstall has been used as the PC-BSD installer for quite a while now, and has done a lot of installs on a lot of different hardware platforms. I'll wager that the compatibility of the shell command gpart is a better bet than the stick your thumbs in you ears and yell nananana while you scribble 1's and 0's to a disk and voila, there's a disklabel approach that sysinstall uses. I wish that was true: unfortunately I tried and failed to create a ZFS installation with pc-sysinstall, and I get a few worrying error messages even with UFS while it repartitions the disk - people have been reporting it creating unbootable systems. gpart might be more compatible, but I don't think parsing the output of tools like as fdisk, diskinfo and dmesg is. The concerns about GPT, ZFS, gmirror etc. in sysinstall could all be resolved in a couple of days by ripping out the existing partitioning code and replacing it with ae@'s new version of sade from /user/ae/usr.sbin/sade . However since the future is pc-sysinstall I've now shifted my work to improving the Qt front-end. -- 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: FreeBSD Installer Roadmap
On Saturday 19 February 2011 03:04:39 Devin Teske wrote: There are many reasons for this, and none of them are selfish (although it remains possible to drum-up some selfish reason, all of the reasons behind our motivation are in-fact unselfish). Truth-be-told, I welcome the replacement of sysinstall but am very wary that ANY replacement will be able to exactly replicate the hardware compatibility that sysinstall currently enjoys. I do indeed envision a great celebration as FreeBSD-9 bucks sysinstall but also at the same time have nightmares of receiving waves of calls from people having trouble (for example) installing FreeBSD-9 on their AMD K6 based system, circa long-long-ago in a universe far-far-away. (yes, we do have data centers running that very equipment with uptime in the 1,000's of days). I think bsdinstall as it currently is is simple enough that there shouldn't be any compatibility issues: it uses gpart for partitioning, runs tools like tzsetup to configure settings etc. so there's far less to go wrong than sysinstall's custom code which for example could crash on the probing devices screen. -- 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: Non-SCSI cam layer based device noise (was Re: Intermittent pauses copying from one usb drive to another)
On Saturday 05 February 2011 19:32:59 Garrett Cooper wrote: On a more relevant topic it would also be nice if the following noise (note the Medium not present errors) didn't end up in the syslog every time I turned on my monitor (the monitor has built in card readers and I rarely populate them with real flash devices), but I don't know if that's doable because it might break some helpful output in syslog when failures do occur with real SCSI enabled devices: There was a discussion about this a few months ago - see http://lists.freebsd.org/pipermail/freebsd-scsi/2010-November/004650.html . -- 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: Loading uart module fails
On Tue, 18 Jan 2011 11:25:38 -0500 John Baldwin j...@freebsd.org wrote: Oh, the uart[01] devices already exist. I suspect if you removed the hints from /boot/device.hints and then kldloaded uart you would be ok. I think this is an old bug that might also be in 8.x. I'm running -CURRENT from a couple of weeks ago so it if it's an old bug it apparently hasn't been fixed yet. -- 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: Loading uart module fails
On Mon, 10 Jan 2011 14:46:06 -0500 John Baldwin j...@freebsd.org wrote: Can you get devinfo -rv output before you try to kldload uart? I've attached the devinfo output. -- Bruce Crannexus0 cryptosoft0 padlock0 npx0 ram0 I/O memory addresses: 0x0-0x9fbff 0x9fc00-0x9 0x10-0x77e acpi0 Interrupt request lines: 3 I/O ports: 0x10-0x1f 0x22-0x3f 0x44-0x5f 0x62-0x63 0x65-0x6f 0x74-0x7f 0x91-0x93 0xa2-0xbf 0xe0-0xef 0x4d0-0x4d1 I/O memory addresses: 0xd6000-0xd7fff 0xf-0xf7fff 0xf8000-0xfbfff 0xfc000-0xf 0x77f-0x77f 0xfee0-0xfee00fff 0x-0x cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU0 acpi_throttle0 acpi_button0 pnpinfo _HID=PNP0C0C _UID=0 at handle=\_SB_.PWRB acpi_sysresource0 pnpinfo _HID=PNP0C01 _UID=0 at handle=\_SB_.MEM_ pcib0 pnpinfo _HID=PNP0A03 _UID=0 at handle=\_SB_.PCI0 I/O ports: 0xcf8-0xcff 0x4000-0x407f 0x4080-0x40ff 0x5000-0x500f 0x6000-0x607f pci0 hostb0 pnpinfo vendor=0x1106 device=0x0601 subvendor=0x1106 subdevice=0x6010 class=0x06 at slot=0 function=0 I/O memory addresses: 0xd000-0xdfff agp0 pcib1 pnpinfo vendor=0x1106 device=0x8601 subvendor=0x subdevice=0x class=0x060400 at slot=1 function=0 pci1 vgapci0 pnpinfo vendor=0x1023 device=0x8500 subvendor=0x1023 subdevice=0x8500 class=0x03 at slot=0 function=0 I/O memory addresses: 0xe100-0xe17f 0xe180-0xe1ff 0xe200-0xe201 vgapm0 scpm0 drm0 isab0 pnpinfo vendor=0x1106 device=0x8231 subvendor=0x1106 subdevice=0x6010 class=0x060100 at slot=17 function=0 handle=\_SB_.PCI0.VT86 isa0 pmtimer0 sc0 vga0 I/O ports: 0x3c0-0x3df I/O memory addresses: 0xa-0xb orm0 pnpinfo pnpid=ORM I/O memory addresses: 0xc-0xcbfff 0xcc000-0xd5fff atkbdc0 I/O ports: 0x60 0x64 atkbd0 Interrupt request lines: 1 fdc0 ppc0 uart0 uart1 atapci0 pnpinfo vendor=0x1106 device=0x0571 subvendor=0x1106 subdevice=0x6010 class=0x01018a at slot=17 function=1 handle=\_SB_.PCI0.IDE0 I/O ports: 0x170-0x177 0x1f0-0x1f7 0x376 0x3f6 0xe800-0xe80f ata0 at channel=0 Interrupt request lines: 14 ata1 at channel=1 Interrupt request lines: 15 uhci0 pnpinfo vendor=0x1106 device=0x3038 subvendor=0x0925 subdevice=0x1234 class=0x0c0300 at slot=17 function=2 handle=\_SB_.PCI0.USB0 Interrupt request lines: 10 I/O ports: 0xd000-0xd01f usbus0 uhub0 uhci1 pnpinfo vendor=0x1106 device=0x3038 subvendor=0x0925 subdevice=0x1234 class=0x0c0300 at slot=17 function=3 handle=\_SB_.PCI0.USB1 Interrupt request lines: 10 I/O ports: 0xd400-0xd41f usbus1 uhub1 unknown pnpinfo vendor=0x1106 device=0x8235 subvendor=0x1106 subdevice=0x6010 class=0x068000 at slot=17 function=4 handle=\_SB_.PCI0.VTAC unknown pnpinfo vendor=0x1106 device=0x3058 subvendor=0x1106 subdevice=0x6010 class=0x040100 at slot=17 function=5 I/O ports: 0xd800-0xd8ff 0xdc00-0xdc03 0xe000-0xe003 vr0 pnpinfo vendor=0x1106 device=0x3065 subvendor=0x1106 subdevice=0x0102 class=0x02 at slot=18 function=0 handle=\_SB_.PCI0.LAN0 Interrupt request lines: 11 I/O ports: 0xe400-0xe4ff I/O memory addresses: 0xe500-0xe5ff miibus0 ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at phyno=1 pcib2 pnpinfo vendor=0x1011 device=0x0024 subvendor=0x subdevice=0x class=0x060400 at slot=20 function=0 pci2 dc0 pnpinfo vendor=0x1011 device=0x0019 subvendor=0x1186 subdevice=0x1112 class=0x02 at slot=4 function=0 Interrupt request lines: 5 I/O ports: 0xc000-0xc07f I/O memory addresses:
Re: why panic(9) ?
On Wed, 12 Jan 2011 13:43:10 +0100 Nils Holland n...@tisys.org wrote: Having a job in which I have to support people working on Windows, I can say for sure that there's no such thing in Windows that prevents third-party system level stuff to bring down the system. ;-) In Windows there's a tool that runs when you build a driver called Microsoft Auto Code Review that checks for things like buffer overflows etc. One thing it flags is if your driver calls KeBugCheckEx and warns that it's normally better to log the error and stop processing data instead of bringing the system down. I always get that warning because my driver was ported from FreeBSD, including a panic() function. -- 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
Loading uart module fails
Hi, I removed uart from my kernel configuration - when I tried to load it later as a module I got the following error: acpi_timer0: couldn't allocate resource (port 0x4008) driver bug: Unable to set devclass (devname: (null)) -- 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: Request for testing/comments -- import of new dialog/libdialog
On Thu, 6 Jan 2011 12:09:27 +0100 Erik Trulsson ertr1...@student.uu.se wrote: Why not keep the old version as libdialog and instead use a new name for the new library (libndialog or whatever) ? (I am not saying you should do this - it is a real question.) Because then we can never upgrade to a newer version of libdialog. -- 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: a few OptionalObsoleteFiles.inc improvements
On Tue, 14 Dec 2010 04:47:39 + b. f. bf1...@googlemail.com wrote: The last part of your patch reverts a change that Warner Losh made in r212525 as part of his tbemd project merge. It's possible that this change may have been an unintended, but it followed a discussion in which Warner rejected a related patch proposed by Garrett Cooper, partly because sysinstall is included in build-tools in Makefile.inc1, even though some thought that it should not be. In any event, you should probably look into that before committing the last part of your patch. I'm wondering if people might be surprised to find sade gone if they set WITHOUT_SYSINSTALL - one's an installer, the other a partitioning program. -- 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: two issues with cdfs
On Fri, 26 Nov 2010 15:28:00 +0200 Andriy Gapon a...@freebsd.org wrote: What's cdfs? :-/ Apparently it's another name for ISO 9660 - http://en.wikipedia.org/wiki/ISO_9660 - which we call cd9660. -- 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: sound config problem
On Wed, 24 Nov 2010 12:27:49 +0200 Daniel Nebdal dneb...@gmail.com wrote: Just as a starter, does it work at all? That is, do you have a /dev/dsp? Do simple OSS programs work? (mpg123 is a nice minimal test; mplayer is fine.) There's always a chance of the problem being on the gnome side of things, so it just seems sensible to start with the really simple things. Apologies if you've done this already. :) The simplest test is: cat /dev/random /dev/dsp -- 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: panic with devclass_get_name (dc=0xdeadc0dedeadc0de)
On Mon, 22 Nov 2010 12:00:57 -0500 Roger Hammerstein cheek...@live.com wrote: I can routinely panic a machine with dd if=/dev/zero of=/dev/ad8 bs=64k count=100 this part doesn't look good: devclass_get_name (dc=0xdeadc0dedeadc0de) Fatal trap 9: general protection fault while in kernel mode I wonder if this is related to http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133286 ? -- 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
src/bin and src/sbin now building with clang without NO_WERROR
I've just committed some fixes to src/bin and src/sbin so those directories now build using clang without needing to use WERROR and NO_WERROR. I'm planning to start going through usr.bin and usr.sbin next. -- 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: tmpfs out of space (ZFS related?)
On Mon, 22 Nov 2010 00:43:03 +0300 Eir Nym eir...@gmail.com wrote: Which type of MFS do you use? I think you shold use swap-backed for your /tmp, not malloc-based. Last type is only for in-kernel file system. It's tmpfs(5), not md(4). -- 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
zfs/vm panic: vm_object_page_collect_flush failed
Hi, I've been building KDE on a new -CURRENT system with ZFS and hit a panic - vm_object_page_collect_flush failed (more info is at http://www.cran.org.uk/~brucec/freebsd/zfs_vm_panic.txt). #9 0x802a6190 in panic (fmt=Variable fmt is not available. ) at /usr/src/head/sys/kern/kern_shutdown.c:574 #10 0x8043744e in vm_object_page_clean (object=Variable object is not available. ) at /usr/src/head/sys/vm/vm_object.c:823 #11 0x804376f6 in vm_object_terminate (object=0xff011a96d5e8) at /usr/src/head/sys/vm/vm_object.c:691 #12 0x804446d8 in vnode_destroy_vobject (vp=0xff00bd2acb40) at /usr/src/head/sys/vm/vnode_pager.c:167 #13 0x80a56252 in zfs_freebsd_reclaim (ap=Variable ap is not available. ) at /usr/src/head/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4836 #14 0x803396e5 in vgonel (vp=0xff00bd2acb40) at vnode_if.h:830 #15 0x80339a4c in vrecycle (vp=0xff00bd2acb40, td=Variable td is not available. ) at /usr/src/head/sys/kern/vfs_subr.c:2517 #16 0x80a3149a in zfs_zinactive (zp=0xff0096d06dc0) at /usr/src/head/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_znode.c:1066 #17 0x80a55c96 in zfs_inactive (vp=0xff00bd2acb40, cr=Variable cr is not available. ) at /usr/src/head/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4059 #18 0x80a55e3a in zfs_freebsd_inactive (ap=Variable ap is not available. ) at /usr/src/head/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4792 #19 0x80338e92 in vinactive (vp=0xff00bd2acb40, td=0xff019871b450) at vnode_if.h:807 #20 0x8033c961 in vputx (vp=0xff00bd2acb40, func=1) at /usr/src/head/sys/kern/vfs_subr.c:2238 #21 0x80438dd7 in vm_object_deallocate (object=0xff011a96d5e8) at /usr/src/head/sys/vm/vm_object.c:447 #22 0x8042f68c in vm_map_entry_deallocate (entry=0xff00bd6054b0, system_map=0) at /usr/src/head/sys/vm/vm_map.c:2622 #23 0x8042f6c2 in vm_map_process_deferred () at /usr/src/head/sys/vm/vm_map.c:466 #24 0x80430d2f in vm_map_remove (map=0xff0093adac40, start=Variable start is not available. ) at /usr/src/head/sys/vm/vm_map.c:2793 #25 0x80434057 in vmspace_exit (td=0xff019871b450) at /usr/src/head/sys/vm/vm_map.c:333 #26 0x8027bea6 in exit1 (td=0xff019871b450, rv=0) at /usr/src/head/sys/kern/kern_exit.c:299 #27 0x8027c9ee in sys_exit (td=Variable td is not available. ) at /usr/src/head/sys/kern/kern_exit.c:109 #28 0x802e699a in syscallenter (td=0xff019871b450, sa=0xff81b832eba0) at /usr/src/head/sys/kern/subr_trap.c:318 #29 0x8046323c in syscall (frame=0xff81b832ec40) at /usr/src/head/sys/amd64/amd64/trap.c:938 #30 0x8044dd42 in Xfast_syscall () at /usr/src/head/sys/amd64/amd64/exception.S:381 #31 0x0008006e567c in ?? () -- 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: TTY task group scheduling
On Fri, 19 Nov 2010 00:17:10 + Alexander Best arun...@freebsd.org wrote: 17:51 @ Genesys : Luigi Rizzo had a plugabble scheduler back in 4.* or \ thereabouts 17:51 @ Genesys : you could kldload new ones and switch to them on the fly 17:52 @ arundel : wow. that sounds cool. too bad it didn't make it into src \ tree. by now it's probably outdated and needs to be reworked quite a bit. does anybody know something about this? Google suggests that the work was a GSoC project in 2005 on a pluggable disk scheduler. -- 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
siftr LOR: PFil hook read/write mutex vs. tcp
1st 0x80990308 PFil read/write mutex (PFil hook read/write mutex @ /usr/src/head/sys/net/pfil.c:77 2nd 0x80991528 tcp (tcp) @ /usr/src/head/sys/modules/siftr/../../netinet/siftr.c:702 KDB: stack backtrace: db_trace_self_wrapper() kdb_backtrace() _witness_debugger() witness_checkorder() _rw_rlock() siftr_chkpkt() pfil_run_hooks() ip_input() netisr_dispatch_src() ether_demux() ether_input() msk_handle_events() msk_intr() intr_event_execute_handlers() ithread_loop() fork_exit() fork_trampoline() --- trap 0, rip = 0, rsp = 0xff8123559cf0, rbp = 0 --- -- 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
Ctrl-alt-delete in syscons pause/scrollback mode breaks system
Today I came back to my computer and realised I'd left ttyv0 in history/scrollback mode, with scroll-lock enabled. To see what would happen I pressed Ctrl-Alt-Delete to reboot and was surprised to see that it seemed to get partway through the process but it never rebooted: the other ttys were killed and I could still break into the debugger but otherwise the system was unresponsive. Trying to repeat it after rebooting I ended up with a system that won't even break into the debugger. Is this expected? -- 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
Corruption of UFS filesystems after using md(4)
I've noticed in recent months that I appear to be getting silent corruption of my UFS filesystems - and I think it may be linked to using md(4) or creating sparse files. I created a 20GB md device using truncate -s 20G mdfile mdconfig -a -f mdfile and then ran some gpart commands before using mdconfig -d -u 0 and rm'ing the file. Some time later I noticed the following had been logged to dmesg: free inode /usr/3367984 had 128 blocks free inode /usr/3367984 had 32 blocks Now, whenever I run vim it creates a sparse 20GB .viminfo file - on another server those files were reported as being 8TB. I've disabled background fsck so the filesystems should have been clean when the system booted, and I'm not using SU+J. -- 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: Corruption of UFS filesystems after using md(4)
On Tuesday 02 November 2010 19:12:14 Bruce Cran wrote: I've noticed in recent months that I appear to be getting silent corruption of my UFS filesystems - and I think it may be linked to using md(4) or creating sparse files. I've confirmed this is a UFS bug related to sparse files: truncate -s20G f1 rm f1 is enough to trigger the error and start generating .viminfo files that appear to be 20GB. When running fsck I get an Invalid block count error if I just reboot without removing the .viminfo file; if I do remove it, I get a Partially allocated inode error. -- 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: Corruption of UFS filesystems after using md(4)
On Tuesday 02 November 2010 19:57:32 Kostik Belousov wrote: What is .viminfo ? How is it related to the command you have shown ? What are exact mount options you are using ? .viminfo is a file created by vim containing various bits of session information. I don't know why it gets corrupted, but I guess it's the way it's created. I've seen other dot files get corrupted in the past too though. /usr is mounted as: /dev/ada0s1f on /usr (ufs, local, soft-updates) Its entry in /etc/fstab is: /dev/ada0s1f/usrufs rw 2 2 It's a totally standard installation from a HEAD snapshot which is now running r214509. I've now seen the problem on a xen VPS, a desktop and a laptop. -- 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
panic after entering blank line at mountroot prompt
I recently ran my FreeBSD installation in a virtual machine, and when I booted on real hardware I'd forgotten to update /etc/fstab. I saw the rootmount prompt and tried to clear away the USB probe messages by pressing enter. It appears there's a problem with the mountroot code though because instead of another line, I got a panic: failed to (re-)mount root. Should the mountroot parser be failing if it doesn't find a valid root to mount on the first line? -- 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: calcru: runtime went backwards
On Saturday 30 October 2010 20:19:04 David Rhodus wrote: I haven't seen much of this since 5.x days. Anyone else see calcru messages lately ? -DR NFS# uname -a FreeBSD NFS.Lesmilde.com 9.0-CURRENT FreeBSD 9.0-CURRENT #2: Fri Oct 29 01:07:40 CDT 2010 r...@nfs.lesmilde.com:/usr/obj/usr/src/sys/GENERIC amd64 NFS# tail -25 /var/log/messages Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 91464 usec to 40935 usec for pid 2709 (csh) It seems to occur if certain CPU power features are enabled in the BIOS - EIST or C1E? I also saw it today when I connected to the virtual VGA console on my Xen VPS. -- 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: Small /etc/src.conf
On Sat, 23 Oct 2010 13:40:01 -0700 Sean Bruno sean...@yahoo-inc.com wrote: Anyone have a src.conf + make.conf that I can steal to build a small installation of BSD? I've been trying to shrink the installation so I can cram an ISO of BSD across the network into a remote installation thing in an HP box. The following might be useful on a small system to speed up build times and reduce the ISO size on a UFS only system where IPFW is used for firewalling: In /etc/src.conf: MODULES_OVERRIDE=md ipfw libalias WITHOUT_GPIB=yes WITHOUT_INFO=yes WITHOUT_ATM=yes WITHOUT_BLUETOOTH=yes WITHOUT_GAMES=yes WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_NCP=yes WITHOUT_NDIS=yes WITHOUT_PF=yes WITHOUT_PPP=yes WITHOUT_PROFILE=yes WITHOUT_WIRELESS=yes # No wireless cards WITHOUT_WPA_SUPPLICANT_EAPOL=yes WITHOUT_ZFS=yes # UFS only system In make.conf you might want to set WITH_X11/WITHOUT_X11 so that for example editors/vim doesn't pull in X11. I also set DISTDIR and WRKDIRPREFIX to directories under my homedir so I can build ports as an unprivileged user. -- 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: installer unable to find device node
On Wed, 20 Oct 2010 18:06:08 +0100 Martin Smith m...@rakupottery.org.uk wrote: I am attempting to install a recent snapshot on a Biostar GF7100P-M7S mobo, with an atapi cdrom and on sata hd, after setting up the slices and selecting the install medium I am presented with the following error: Unable to find device node for ad4s1b in dev! The creation of filesystems will be aborted. This also happened with an 8.0 installer, is this just me, is there something funny about this motherboard? Has the HDD previously been partitioned using GPT, or something other than a traditional MBR? -- 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
