Re: Deprecating base system ftpd?
Hi, > On 5 Apr 2021, at 20:01, Patrick M. Hausen wrote: > > Hi all, > >> Am 03.04.2021 um 22:39 schrieb Ed Maste : >> I'm happy to make a port for it if anyone needs it. Comments? > > A bit late to the party, but my take is: please just don't. +1 (later still) > I absolutely freaked out when Apple removed the telnet and ftp clients > from Mac OS and I needed to reinstall them via MacPorts. > > People who manage any larger collection of networking gear *depend* > on these outdated but simple services. Client and server side alike. > > TFTP is not going away, neither is FTP. I'm dead serious. Remote media > via Supermicro IPMI in 2021? SMB1. Firmware updates for my UPS? FTP. > Scanner/printer/fax all-in-one thingy? Uploads received fax transmissions > via FTP. PBX? Uploads usage reports via FTP. This stuff is here to stay. > In local networks, of course. > > But still even on "the Internet", FTP is the most used method for customers > of static website hosting. You cannot teach these people what an SSH key is. > Just my experience, but backed by a load of customer interactions over more > than 20 years ... > > Kind regards, > Patrick > -- > punkt.de GmbH > Patrick M. Hausen > .infrastructure > > Kaiserallee 13a > 76133 Karlsruhe > > Tel. +49 721 9109500 > > https://infrastructure.punkt.de > i...@punkt.de > > AG Mannheim 108285 > Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein > -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU3 ethernet can't transmit
Hi, FWIW I found that applying -lro didn’t work retrospectively, it had to be done when the interface was first configured. Might apply to other options too. -- Bob Bishop r...@gid.co.uk > On 22 Jan 2021, at 23:42, Graham Menhennitt wrote: > > Try "ifconfig $ifname -rxcsum -txcsum" and possibly " -vlanhwtso -tso4" as > well. > > Graham > > On 23/01/2021 8:10 am, Stefan Bethke wrote: >> I have a weird situation with an PCEngines APU3, where I can't seem to be >> able to transmit packets through either of the igb interfaces. With tcpdump, >> I can see packets arriving, and the interface flags appear to be just fine: >> >> options=e527bb >> ether 00:0d:b9:58:xx:xx >> inet6 fe80::20d:b9ff::%igb0 prefixlen 64 scopeid 0x1 >> inet6 2a02:8108:4840::::: prefixlen 64 autoconf >> inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 >> media: Ethernet autoselect (1000baseT ) >> status: active >> nd6 options=23 >> >> dhclient is running on that interfaces, and I got an IPv6 address through RA. >> >> Assigning an address manually doesn't change anything. >> >> igb0@pci0:1:0:0:class=0x02 card=0x8086 chip=0x157b8086 >> rev=0x03 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'I210 Gigabit Network Connection' >> class = network >> subclass = ethernet >> >> # freebsd-version >> 12.2-RELEASE >> >> I installed 12.2-REL a couple of weeks ago, and haven't done anything since. >> >> Tried the three different port with different cables on different switch >> ports, which are working fine with other machines. >> >> I'm installing updates now via a USB adapter. >> >> Any suggestions? >> >> >> Stefan >> >> -- >> Stefan BethkeFon +49 151 14070811 >> > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
Hi, > On 28 Aug 2020, at 19:47, Kurt Jaeger wrote: > > Hi! > >> I'd like to retire the spkr driver. It was a cute hack before sound cards >> were ubiquitous, but it's not been kept up to date, and it's not clear that >> it still works It is still Giant locked, and though it's not a huge >> effort to do the locking I literally have no way to test it that I trust... > > It works on PC Engines APU devices, and together with morse, it's > very, very cool 8-} > > So, please keep it and un-giant it, if possible. What he said. I’d be happy to test changes. > -- > p...@opsec.eu+49 171 3101372Now what ? -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: swap space issues
> On 26 Jun 2020, at 11:23, Peter Jeremy wrote: > > On 2020-Jun-25 11:30:31 -0700, Donald Wilde wrote: >> Here's 'pstat -s' on the i3 (which registers as cpu HAMMER): >> >> Device 1K-blocks UsedAvail Capacity >> /dev/ada0s1b 335544320 33554432 0% >> /dev/ada0s1d 335544320 33554432 0% >> Total671088640 67108864 0% > > I strongly suggest you don't have more than one swap device on spinning > rust - the VM system will stripe I/O across the available devices and > that will give particularly poor results when it has to seek between the > partitions. If you configure a ZFS mirror in bsdinstall you get a swap partition per drive by default. > Also, you can't actually use 64GB swap with 4GB RAM. If you look back > through your boot messages, I expect you'll find messages like: > warning: total configured swap (524288 pages) exceeds maximum recommended > amount (498848 pages). > warning: increase kern.maxswzone or reduce amount of swap. > or maybe: > WARNING: reducing swap size to maximum of MB per unit > > The absolute limit on swap space is vm.swap_maxpages pages but the realistic > limit is about half that. By default the realistic limit is about 4×RAM (on > 64-bit architectures), but this can be adjusted via kern.maxswzone (which > defines the #bytes of RAM to allocate to swzone structures - the actual > space allocated is vm.swzone). > > As a further piece of arcana, vm.pageout_oom_seq is a count that controls > the number of passes before the pageout daemon gives up and starts killing > processes when it can't free up enough RAM. "out of swap space" messages > generally mean that this number is too low, rather than there being a > shortage of swap - particularly if your swap device is rather slow. > > -- > Peter Jeremy -- Bob Bishop t: +44 (0)118 940 1243 r...@gid.co.uk m: +44 (0)783 626 4518 signature.asc Description: Message signed with OpenPGP
Re: OpenZFS port updated
Hi, > On 17 Apr 2020, at 19:35, Ryan Moeller wrote: > > FreeBSD support has been merged into the master branch of the openzfs/zfs > repository, and the FreeBSD ports have been switched to this branch. > > OpenZFS brings many exciting features to FreeBSD, including: > * native encryption > * improved TRIM implementation [etc] Note that unlike native ZFS, OpenZFS doesn’t (last time I looked) support autotrim by default - you have to enable it explicitly. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HOWTO donate CPU to the fight against the Corona-virus
Hi, Just a note that the client can grow its logfile at the rate of ~1GB a day. You’ll probably want to take avoiding action. > On 19 Mar 2020, at 07:57, Alexander Leidinger via freebsd-stable > wrote: > > Hi, > > if someone wants to donate some FreeBSD based CPU resources to the fight > against the Corona-virus, here is a quick HOWTO in terms of installing the > Folding@Home client on FreeBSD: > > https://www.leidinger.net/blog/2020/03/19/fighting-the-coronavirus-with-freebsd-foldinghome/ > > I tested this on a recent -current. > > If you are interested in how this helps in the fight against the virus, > please refer to the https://foldingathome.org/ website. In short and > over-simplified: they search for vaccines. > > Bye, > Alexander. > > -- > http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF -- Bob Bishop r...@gid.co.uk signature.asc Description: Message signed with OpenPGP
Re: ntp problems stratum 2 to 14?
Hi, > On 5 Mar 2020, at 06:33, Peter Jeremy wrote: > > Hi Dewayne, > > Sorry for the delay. Unfortunately, I can't really suggest anything - > it's not clear to me why ntpd would prefer a stratum 14 clock over a > stratum 2 clock. Have you tried looking through the debugging hints > page (https://www.eecis.udel.edu/~mills/ntp/html/debug.html)? > > I haven't seen that problem but I don't use the local clock. > > During startup, it would not seem unreasonable for the local clock to > become valid first because it will have a lower jitter. But ntpd > should switch to the stratum 2 clock and stay with in as the better > time source. One problem is that if ntpd decides to switch away from > the clock for any reason (eg a burst of jitter), it may get stuck on > the local clock as it drifts further from "real" time. Yes. I’ve had exactly that happen with a stratum 1 (GPS) server with only local as fallback. The GPS signal dropped for a while and the box drifted off sufficiently that it wouldn’t reacquire the accurate clock. The solution is to add a few pool (or whatever) servers into the config - you can still ‘prefer’ a local server but it ensures the box won’t drift off into the weeds. > -- > Peter Jeremy -- Bob Bishop r...@gid.co.uk signature.asc Description: Message signed with OpenPGP
Re: Running FreeBSD on M.2 SSD
Hi, > On 25 Feb 2020, at 01:35, Mario Olofo wrote: > > Hi Mike, thanks for the insight. > > I tried both, but not at the same time. > When I found that the ZFS was corrupting the filesystem, I reinstalled the > FreeBSD using UFS but no luck. > Ulf told me that he had the same problem and it turned out the problem was > a defective RAM, but here I just ran the test 2 times, > one from Dell BIOS Diagnostics Tool and other from mdsched.exe from Windos > 10, but here the RAM is ok… Software tests will not always find marginally faulty RAM. If you can, try swapping for known good RAM; or if you have lots of RAM installed, try taking half the RAM out at a time and see if that affects stability. > Thank you again, > > Mario > > Em seg., 24 de fev. de 2020 às 22:15, Mike Karels > escreveu: > [etc] -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Long-shot: repeatable macOS samba share unmounting during Lightroom import
Hi, > On 24 Nov 2019, at 02:33, Andrew Reilly wrote: [tale of woe trimmed] > I use Lightroom's > Import function to copy photos off SD cards using the mac's built-in > SD card reader and register with the catalogue. [etc] Long shot, but try using an external SD card reader. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
> On 9 May 2019, at 12:17, Michelle Sullivan wrote: > > > > Michelle Sullivan > http://www.mhix.org/ > Sent from my iPad > >> On 09 May 2019, at 17:46, Patrick M. Hausen wrote: >> >> Hi all, >> >>> Am 09.05.2019 um 00:55 schrieb Michelle Sullivan : >>> No, one disk in the 16 disk zRAID2 ... previously unseen but it could be >>> the errors have occurred in the last 6 weeks... everytime I reboot it >>> started resilvering, gets to 761M resilvered and then stops. >> >> 16 disks in *one* RAIDZ2 vdev? That might be the cause of your insanely >> long scrubs. In general it is not recommended though I cannot find the >> source for that information quickly just now. > > I have seen posts on various lists stating don’t go over 8.. I know people > in Oracle, the word is it should matter... who do you believe? Inter alia it depends on the quality/bandwidth of disk controllers. > Michelle > >> >> Kind regards, >> Patrick >> -- >> punkt.de GmbHInternet - Dienstleistungen - Beratung >> Kaiserallee 13aTel.: 0721 9109-0 Fax: -100 >> 76133 Karlsruhei...@punkt.dehttp://punkt.de >> AG Mannheim 108285Gf: Juergen Egeling >> > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Bob Bishop t: +44 (0)118 940 1243 r...@gid.co.uk m: +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS...
Hi, > On 2 May 2019, at 19:17, Julian H. Stacey wrote: > > Hi, Reference: >> From:"N.J. Mann" >> Date:Thu, 02 May 2019 18:18:16 +0100 > > "N.J. Mann" wrote: >> Hi, >> >> >> On Friday, May 03, 2019 03:00:05 +1000 Michelle Sullivan >> wrote: >>>>> I am sorry to hear about your loss of data, but where does the 11kV come >>>>> from? >>>>> I can understand 415V, i.e. two phases in contact, but the type of >>>>> overhead >>>>> lines in the pictures you reference are three phase each typically 240V to >>>>> neutral and 415V between two phases. >>>>> >>>> Bottom lines on the power pole are normal 240/415 .. top lines are the >>>> 11KV distribution network. >>> >>> Oh and just so you know, it’s sorta impossible to get 415 down a 240v >>> connection >> >> No it is not. As I said, if two phases come into contact you can have 415v >> between >> live and neutral. > > With 3 phase: > - 415 between each of the 3 live phases > - 240 between neutral & the 3 live phases ... and that’s RMS, so 586 and 325 peak respectively. > (To visualise: draw a circle of radius 12 cm, mark off dots on circle at > 120 degrees. measure between dots: 20.75cm, Neutral is compass hole in paper ) > > PS UK/Britain was nominal 240V, but EU inc UK is now nominal 230V +10%/-6% > https://en.wikipedia.org/wiki/Mains_electricity#Standardisation > > Cheers, > Julian > -- > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. > Lies bought; Campaigns fined; 1.9 M young had no vote, 1.3 M old leavers dead. > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: source upgrade FBSD10 -> 11 (then 12)
Hi, > On 28 Feb 2019, at 16:18, Lee Damon wrote: > > I have three old FBSD 10 boxes that I need to upgrade. Ordinarily I do this > by building a new box with the latest OS then migrating services and data. > Unfortunately I don't have that option this time, the upgrade has to happen > in-place. My plan is to go from 10 to 11 then from 11 to 12. > > I was looking at the "Upgrading FreeBSD" part of > https://www.freebsd.org/releases/11.1R/installation.html#upgrade but > unfortunately it seems to be missing a critical URL or two: > > "The procedure for doing a source code based update is described in and ." > > I tracked down where I think it points and the instructions appear to be just > for same-version updates. Can I safely move /usr/src out of the way then > check out the stable/11 and compile/install it or are there other things I > need to do? See the Handbook section 23.5: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > thanks, > nomad -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loss of network connectivity 12.0-RC1 / re0
> On 21 Nov 2018, at 21:04, Philip Homburg wrote: > >> Since installing one of the first betas of 12.0 and yesterday with RC1 I >> notice network connectivity failures every now and then. I have to >> see if I can find the time to find a reliable trigger. > > On a diffrent machine, this time with em0, starting tcpdump made IPv6 work > again. [etc] An effect of promiscuous mode is to disable any hardware filtering particularly of MAC addresses. If something in that area is awry then running tcpdump may well ‘fix’ it. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FCP-0101: Deprecating most 10/100 Ethernet drivers
> On 24 Oct 2018, at 01:23, Warner Losh wrote: > > On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes < > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > >> -- Start of PGP signed section. >>> On Tue, Oct 23, 2018 at 04:26:45PM -0700, Rodney W. Grimes wrote: >>>>> On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes < >>>>> freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: >>>>> >>>>>>> On Tue, Oct 23, 2018 at 11:33:35PM +0200, Julian H. Stacey wrote: >>>>>>>>> I'd also suggest that rl stands in stark contrast to the cs, >> wb, sn, >>>>>> smc, >>>>>>>>> sf, tl, tx and vr drivers, which nobody has mentioned in this >>>>>> thread, and >>>>>>>>> which I doubt are in use in any FreeBSD system of any age >> today. >>>>>>>> >>>>>>>> vr is used by my TV driver laptop: >>>>>>>> http://www.berklix.com/~jhs/hardware/laptops/novatech-8355/ >>>>>>>> vr0: flags=8843 metric >> 0 mtu >>>>>> 1500 >>>>>>>>options=82808 >>>>>>>>ether 00:40:d0:5e:26:38 >>>>>>>>inet 192.168.91.65 netmask 0xff00 broadcast >> 192.168.91.255 >>>>>>>>media: Ethernet autoselect (100baseTX >>>>>> ) >>>>>>>>status: active >>>>>>>> >>>>>>>> Which currently runs 8.4-RELEASE & eg xrandr, but I'll upgrade >> soon >>>>>>>> when I also configure it to receive from a raspberry-pi TV VPN >> server. >>>>>>> >>>>>>> The above was a typo. vr is on the the STAY list. >>>>>>> >>>>>>> -- Brooks >>>>>> Brooks, >>>>>>Is there a public revised version of FCP-0101 that >> reflects the >>>>>> feedback which is what core is voting on? >>>>>> >>>>> >>>>> Its on github, just like it's been the whole time for anybody to see, >>>>> submit pull requests against and track: >>>> >>>> I have no gh account, desires no gh account, so have no way to >>>> submit a change request other than through direct email to >>>> brooks or another gh user. This is fundementally flawed. >>>> >>>>> https://github.com/freebsd/fcp/blob/master/fcp-0101.md >>>> >>>> Thank you for the link, I had looked at it before MeetBSD, >>>> which did not have most of the recent changes done "a day ago". >>>> >>>> Isnt this document now in a frozen state while core reviews/votes? >>> >>> I sent it to a vote at c224c67557297d7cba909ad008542cb60980cc6b only >>> to notice a bug in table rendering. I submitted a pull request fix >>> that and a missing word which was merged since neither was material. I >>> suppose they could have waited or been skipped, but there's no value in >>> the FCP process being bound by the sort of pointless rigidity that led >>> to -DPOSIX_MISTAKE in every libc compile line. >> >> The FCP process itself is unclear on this point, >> I think this should be clarified. >> >> It is much more clear on post approval: >>Changes after acceptance >> >>FCPs may need revision after they have been moved into the >>accepted state. In such cases, the author SHOULD update the >>FCP to reflect the final conclusions. >>If the changes are major, the FCP SHOULD be withdrawn >>and restarted. >> > > Good point Rod. While common sense suggests that trivial changes during the > voting should be allowed for editorial purposes (eg fix grammar mistakes, > table rendering etc), it's better to spell that out so there's no confusion. > > diff --git a/fcp-.md b/fcp-.md > index b4fe0f3..c8cc6f7 100644 > --- a/fcp-.md > +++ b/fcp-.md > @@ -144,7 +144,10 @@ When the discussion of a change has come to a suitable > and acceptable close it > SHOULD be updated to the `vote` state. > > At this time the FreeBSD Core Team will vote on the subject of the FCP. The > -result of vote moves the FCP into the `accepted` or `rejected` state. > +result of vote moves the FCP into the `accepted` or `rejected` state. The > +core team MAY make minor edits to the FCP to
ZFS panic, ARC compression?
Hi, Anyone offer any suggestions about this? kernel: panic: solaris assert: arc_decompress(buf) == 0 (0x5 == 0x0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c, line: 4923 kernel: cpuid = 1 kernel: KDB: stack backtrace: kernel: #0 0x80aadac7 at kdb_backtrace+0x67 kernel: #1 0x80a6bba6 at vpanic+0x186 kernel: #2 0x80a6ba13 at panic+0x43 kernel: #3 0x8248023c at assfail3+0x2c kernel: #4 0x8218e2e0 at arc_read+0x9f0 kernel: #5 0x82198e5e at dbuf_read+0x69e kernel: #6 0x821b3db4 at dnode_hold_impl+0x194 kernel: #7 0x821a11dd at dmu_bonus_hold+0x1d kernel: #8 0x8220fb05 at zfs_zget+0x65 kernel: #9 0x82227d42 at zfs_dirent_lookup+0x162 kernel: #10 0x82227e07 at zfs_dirlook+0x77 kernel: #11 0x8223fcea at zfs_lookup+0x44a kernel: #12 0x822403fd at zfs_freebsd_lookup+0x6d kernel: #13 0x8104b963 at VOP_CACHEDLOOKUP_APV+0x83 kernel: #14 0x80b13816 at vfs_cache_lookup+0xd6 kernel: #15 0x8104b853 at VOP_LOOKUP_APV+0x83 kernel: #16 0x80b1d151 at lookup+0x701 kernel: #17 0x80b1c606 at namei+0x486 Roughly 24 hours earlier (during the scrub), there was: ZFS: vdev state changed, pool_guid=11921811386284628759 vdev_guid=1644286782598989949 ZFS: vdev state changed, pool_guid=11921811386284628759 vdev_guid=17800276530669255627 % uname -a FreeBSD xxx 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 % % zpool status pool: zroot state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: scrub repaired 15.7M in 2h37m with 1 errors on Sun Apr 1 09:44:39 2018 config: NAMESTATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p4 ONLINE 0 0 0 ada1p4 ONLINE 0 0 0 errors: 1 data errors, use '-v' for a list % The affected file (in a snapshot) is unimportant. This pool is a daily rsync backup and contains about 120 snapshots. No device or SMART errors were logged. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GPT partition gets erased on boot
Hi, > On 13 Nov 2017, at 04:59, Walter Parker wrote: > > Hi, > > I'm setting up an old Sunfire X4140 system with 4 SAS drives plugged into > the SUN STK controller. Each drive is configured as a separate device. > > I ran the FreeBSD 11.1 installer and picked guided ZFS install where I > selected RAID10 (2 2way mirrors) using aacd0, aacd1, aacd2, and aacd3. It > installed the system and rebooted. > > When the new system came up, zpool status complained that aacd0p3 was > unavailable. Looking at /dev, I noticed that the only dev file was aacd0 > (aacd0p* were all missing). Using gpart on aacd0 it said there was no geom. > I was able to run gpart create to recreate the drive geom and then gpart > add to readd all of the partitions. After recreating aacd0p3, I was even > able to run zpool replace -f zroot /dev/aacd0p3 and the pool resilvered and > stopped complaining. > > On the next boot, aacd0 was missing all of its partitions. > > What would cause the partitions on a ZFS drive to disappear? At a guess, the controller is writing its metadata to the disk and trampling on the gpart data. > Thank you, > > > Walter > > -- > The greatest dangers to liberty lurk in insidious encroachment by men of > zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Denverton CPU on FreeBSD
Hi, > On 7 Nov 2017, at 16:12, Cassiano Peixoto wrote: > > Hi guys, > > I'm backing to this thread because I had no success yet. There is an issue > with console boot on Intel Denverton. I've followed the instruction bellow: > > https://www.freebsd.org/doc/handbook/serialconsole-setup.html > > I tried using an IPMI card and worked fine. > > I don't know who is the maintainer for console code to get in touch. Can > some developer work on this issue? I can help making any test needed. > > Thank you. > > On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto > wrote: > >> Hi there, >> >> Is someone playing with Denverton CPU On FreeBSD? >> >> I'm trying to use serial console on FreeBSD with Denverton CPU but doesn't >> work. >> >> I can see the boot process but it stops and I do not have the login >> prompt. My keyboard doesn't answer as well. Have you set /etc/ttys entry for the serial port appropriately? https://www.freebsd.org/doc/handbook/term.html#term-config >> I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is >> working with Rangeley CPU. Maybe BIOS initialises the serial port differently? >> Any help is welcome. >> >> Thanks. >> > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop t: +44 (0)118 940 1243 r...@gid.co.uk m: +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Impending NATM removal
Hi, > On 7 Apr 2017, at 00:57, Brooks Davis wrote: > > As previously threatened, I plan to remove NATM support next week. This > includes the drivers en(4), fatm(4), hatm(4), and patm(4). None of > these devices have been manufactured in the last 20 years so it is time > to move on. I don’t have a dog in this fight, but for instance ProSum PROATM-E155 (patm(4)) still appear to be available. See http://www.prosum.net/en/products/atm-adapters > The planned commit can be seen at https://reviews.freebsd.org/D9883 > > -- Brooks -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: lots of security advisories rehashed
Hi, > On 12 Aug 2016, at 13:16, Matthew Seaman wrote: > > […] > Note that these are capturing the last several years worth of security > advisories for the base system into VuXML. This allows you to say, for > instance: > > pkg audit FreeBSD-10.3_2 > > which will tell you about a number of security advisories which have > come out since 10.3-RELEASE-p2. This is in anticipation of the base > system being packaged, which is due to come in with 11.1-RELEASE. > > See Mark Felder's announcement on questions@: Why is this hiding out on questions@ ? > https://lists.freebsd.org/pipermail/freebsd-questions/2016-August/273034.html > > As Mark says, this is not guaranteed to be either accurate or complete, > but it should be helpful in managing system upgrades. > > Cheers, > > Matthew > > -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-update to 10.2-RELEASE broken ?
> On 16 Aug 2015, at 23:08, Bjoern A. Zeeb > wrote: > > >> On 16 Aug 2015, at 21:16 , Christian Kratzer wrote: >> >> Hi, >> >> On Sun, 16 Aug 2015, Kurt Jaeger wrote: >>> Hi! >>> >>>> It could be the classic fall back to TCP on SRV records problem on >>>> your upstream DNS forwarder if you're using one: >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html >>> >>> If I query that same DNS resolver using the line from >>> the script, it works every time. It's a 10.1p16 host with >>> a very recent ports build, and directly connected (no NAT, no >>> fw etc). >>> >>> If that would be the problem, how could I diagnose it in depth ? >> >> freebsd-update upgrade just failed on 3 other vm even when I explicitly >> specified the server using freebsd-update -s. >> >> I had success on another vm when I changed to using google dns. >> >> I am not aware that anything would be blocking tcp dns in my setups. >> >> Must be something else dns related. >> >> Perhaps I will run a local resolver in a vm and logg all queries and dns >> traffic. > > Or run tcpdump for port 53; also curious if it might be an IPv4 vs. IPv6 > issue? I saw the issue on machines with IPv4/IPv6 and IPv4 only. > — > Bjoern A. Zeeb Charles Haddon Spurgeon: > "Friendship is one of the sweetest joys of life. Many might have failed > beneath the bitterness of their trial had they not found a friend." > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Bob Bishop +44 (0)118 940 1243 r...@gid.co.ukfax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-update to 10.2-RELEASE broken ?
Hi, > On 16 Aug 2015, at 18:16, Christian Kratzer wrote: > > Hi, > > I have been trying to update several of my FreeBSD 10.1 amd64 VM to > 10.2-RELEASE with freebsd-update and have been failing with an incorrect hash > error. > > This is what happens with a plain vanilla 10.1-RELEASE vm when I try to > update to 10.2-RELEASE > > --snipp— […] > Applying patches... done. > Fetching 2356 files... > 068eb594e5f6b97554750a8321892e4c229a6f26455f40e4d8e4e7a79577c673 has > incorrect hash. > root@test10:~ck # > --snipp-- > > I get the is on all kinds of VM with different patchlevels of 10.1-RELEASE. > Some of them have /usr/src, some of them don't. > > The hash seems to be different every time round. > > Could this be an issue with one of the mirrors ? > > Has anybody had success yet with an update to 10.2-RELEASE using > freebsd-update ? FWIW I had the same issue yesterday on a couple of systems. Repeating freebsd-update worked after two or three goes. > Greetings > Christian > > -- > Christian Kratzer CK Software GmbH > Email: c...@cksoft.de Wildberger Weg 24/2 > Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden > Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart > Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer > Web: http://www.cksoft.de/ > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS Woes... Guru needed
Hi, > On 11 Jul 2015, at 14:19, Holm Tiffe wrote: > > So I looked at the bad disks and found one with defective electronics > and one with defective platters and exchanged the controllers (all Disks > are in "real life ST373453LC disks, original with 534 Byte sector size > or so). Can’t comment on the ZFS aspects, but I’m not sure you can rely on swapping drive electronics these days. I believe that in at least some cases boards are parameterised for the particular platters and heads during production. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Booting from ZFS
Hi,
> On 25 Mar 2015, at 04:56, Greg Rivers wrote:
>
> I'm trying to build a bootable ZFS system on a USB drive. Using the
> procedure below results in the following error when I try to boot:
>
> gptzfsboot: error 66 LBA 48
> gptzfsboot: error 66 LBA 1
> gptzfsboot: No ZFS pools located, can't boot
Presumably gptzfsboot relies on the BIOS mapping the USB device into a DOS
device. Do you have that support turned on in the BIOS?
> I'm using the dist files from the latest STABLE snapshot on a system running
> 10.1-STABLE r279968 amd64. I've tried it with and without file system
> compression. I found a similar report[1] in the FreeBSD Forums, but there
> was no conclusion to that posting.
>
> What am I doing wrong?
>
> [1]
> https://forums.freebsd.org/threads/freebsd-10-w-fresh-root-on-zfs-fails-to-boot.47651/#post-266106
> ---
> #!/bin/ksh
> set -x -e
>
> DISK=diskid/DISK-4C530009730530116424
> TMPDIR=/mnt
>
> gpart destroy -F ${DISK} || :
> gpart create -s GPT ${DISK}
> gpart add -a 4k -s 512k -t freebsd-boot ${DISK} # p1
> gpart add -a 4k -s 1g -t freebsd-swap ${DISK} # p2
> gpart add -a 4k -t freebsd-zfs ${DISK}# p3
> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ${DISK}
>
> sysctl vfs.zfs.min_auto_ashift=12
> zpool create -o altroot=${TMPDIR} -m none -f syspool ${DISK}p3
> zfs create -o mountpoint=none syspool/ROOT
> zfs create -o mountpoint=/ -o compression=lz4 syspool/ROOT/default
> zpool set bootfs=syspool/ROOT/default syspool
> zfs create -o mountpoint=/var -o compression=lz4 syspool/var
> zfs create -o mountpoint=/usr -o compression=lz4 syspool/usr
> zfs create -o mountpoint=/home -o compression=lz4 syspool/home
>
> for DIST in base kernel lib32 games doc
> do
> fetch -o -
> ftp://ftp.freebsd.com/pub/FreeBSD/snapshots/amd64/amd64/10.1-STABLE/${DIST}.txz
> | tar -C ${TMPDIR} -x -f -
> done
>
> cat <<\! >${TMPDIR}/boot/loader.conf
> zfs_load="YES"
> !
> cat <<\! >${TMPDIR}/etc/rc.conf
> zfs_enable="YES"
> !
> cat <<\! >${TMPDIR}/etc/fstab
> # Device Mountpoint FStype Options DumpPass#
> /dev/da0p2noneswapsw 0 0
> tmpfs /tmptmpfs rw 0 0
> procfs/proc procfs rw 0 0
> fdescfs /dev/fd fdescfs rw 0 0
> !
>
> zpool export syspool
> ---
> --
> Greg Rivers
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
--
Bob Bishop
r...@gid.co.uk
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue?
Hi, On 18 Jul 2013, at 08:29, Dr Josef Karthauser wrote: > Hi there, > > I'm scratching my head. I've just migrated to a super micro chassis and at > the same time gone from FreeBSD 9.0 to 9.1-RELEASE. > > The machine in question is running a ZFS mirror configuration on two ada > devices (with a 8gb gmirror carved out for swap). > > Since doing so I've been having strange drop outs on the drives; the just > disappear from the bus like so: > > (ada2:ahcich2:0:0:0): removing device entry > (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 > (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error > (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 (ABRT ) > (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff > (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted > (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 > (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error > (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 (ABRT ) > (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff > (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted > > > At first I though it was a failing drive - one of the drives did this, and I > limped on a single drive for a week until I could get someone up to the rack > to plug a third drive in. We resilvered the zpool onto the new device and > ran with the failed drive still plugged in (but not responding to a reset on > the ada bus with camcontrol) for a week or so. > > Then, the new drive dropped out in exactly the same way, followed in short > order by the remaining original drive!!! > > After rebooting the machine, and observing all three drives probing and > available, I resilvered the gmirror and zpool again on the two devices > expected that I thought were reliable, but before the resilvering was > completed the new drive dropped out again. > > I'm scratching my head now. I can't imagine that it's a wiring problem, as > they are all on individual SATA buses and individually cabled. > > Smart isn't reporting an drive issues either…. :/ > > So, I'm wondering, is it a driver issuer with 9.1-RELEASE, if I upgrade to > 9-RELENG would I expect that to resolve the problem? (Have there been any > reported ada bus issuer reported since last December?) > > The hardware in question is: > > ahci0: port > 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f mem > 0xdfb02000-0xdfb027ff irq 19 at device 31.2 on pci0 > ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich2: at channel 2 on ahci0 > ahcich3: at channel 3 on ahci0 > ahcich4: at channel 4 on ahci0 > ahcich5: at channel 5 on ahci0 > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad4 > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: 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: 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 > > > Any ideas would be greatly welcomed. > > Thanks, > Joe Me too (over a long period, with various hardware). There is a general problem with energy-saving drives that controllers don't understand them. Typically the drive decides to go into some power-saving mode, the controller wants to do some operation, the drive takes too long to come ready, the controller decides the drive has gone away. You have to persuade the controller to wait longer for the drive to come ready, and/or persuade the drive to stay awake. This isn't necessarily easy, eg the controller's ready wait may not be programmable. (Or avoid such drives like the plague, life's too short). -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Spontaneous reboots on Intel i5 and FreeBSD 9.0
>>> being >>> initiated when an old one is still running. >>> >>> zfSnap has its -S switch to prevent actions during a scrub which you >>> should >>> use if you haven't already. >>> >>> >> Hi John, >> >> Thanks for the hints. It was a long time since I've setup zfSnap and I've >> just checked the configuration and I am using the "-s -S" flags, so there >> should be no overlapping. >> >> Meanwhile I've updated to 9.1-RELEASE, but then I hit an issue when trying >> to reboot the system (which appears to be discussed a lot in a separate >> thread). >> >> Then I've updated to stable/9, so at the least the reboot issue is now >> solved. Since I've to stable/9 I'm monitoring the system's memory usage and >> so far it's been pretty stable, so I'll keep an eye of an update to >> stable/9 has actually fixed this strange issue. >> >> Thanks again, >> Marin >> >> >>> Since making these changes, a machine that would have to be rebooted >>> several >>> times a week has now been up 61 days. >>> >>> John Theus >>> TheUs Group >>> >> >> >> >> -- >> Marin Atanasov Nikolov >> >> dnaeon AT gmail DOT com >> http://www.unix-heaven.org/ >> > > > > -- > Marin Atanasov Nikolov > > dnaeon AT gmail DOT com > http://www.unix-heaven.org/ > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop +44 (0)118 940 1243 r...@gid.co.ukfax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using dhclient on WAN if on a box serving DHCP to LAN if
Hi, On 7 Dec 2012, at 11:38, Tom Evans wrote: > Hi all > > Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare > for 9.1, but I think it should be largely irrelevant of version. > > I have a freebsd router that provides all the things a soho router > should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface > connects to a ADSL modem operating in bridge mode. > > My ISP has recently forced a change on to me, in order to get service > I have to connect via DHCP, in order for them to give me my static IP. > Apparently this makes their lives a lot easier. Even knowing the IP, > netmask, broadcast and router is not enough, no service will flow > unless a DHCP request has been registered. > > Relevant rc.conf, ale0 is the WAN, em0 is the LAN > > ifconfig_ale0="DHCP" > ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0" > gateway_enable="YES" > > dhcpd_enable="YES" > dhcpd_flags="-q" > dhcpd_ifaces="em0" > dhcpd_conf="/usr/local/etc/dhcpd.conf" > > With this configuration, the default route is over the LAN iface. This > causes the dhclient for ale0 to get a response from the local dhcpd > server, not the ISP dhcpd server. This drove me potty! Can anyone > explain why dhcpd, having been told only to listen for DHCP on em0, > responds to ale0? Could this be related to my pf rules, or is it down > to the default route being incorrect? > > Changing rc.conf to this allows the network to come up correctly: > > ifconfig_ale0="inet xx.xx.110.172 netmask 255.255.255.0 broadcast > xx.xx.110.255 DHCP" > defaultrouter="xx.xx.110.1" > > This relies on me knowing that these are the values that dhclient on > the WAN iface will receive from my ISP's DHCP server. How would I > achieve this setup if this information was dynamic or otherwise > unknowable? My ISP could easily change my gateway IP, the only > guarantee I have is that my allocated IP is static. > > So: > > 1) Why does the LAN dhcpd respond to the WAN dhclient? Maybe DHCP requests are getting passed across the gateway. Try setting gateway_enable="NO" temporarily, if that stops the unwanted behaviour then configure pf to block DHCP requests crossing the gateway. > 2) Is there a better way of specifying this setup, so that it does not > have hard coded addresses in there? > > Thanks in advance for any pointers. > > Tom > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD and IPMI how-to (was Re: su problem)
Hi, On 15 Jun 2012, at 02:27, Matthew X. Economou wrote: > Would some kind soul point me to a howto for configuring IPMI on > FreeBSD? I have a Dell PowerEdge 840 that supports IPMI, but I have > no idea how to set it up - either in the BIOS or in FreeBSD. I've > messed around with ipmitools a little, but I haven't gotten it to > work. To get things like remote management and serial over LAN working, the config has to be right on both the OS and the platform. Others have addressed the FreeBSD end; configuration of the platform is documented here: http://support.dell.com/support/edocs/software/smbmcmu but you'll have to figure out which version is applicable to your box. When you have ipmitool working, the output of `ipmitool mc info' may help with that. Also, it seems like your box implements IPMI v1.5, which is rather less friendly than v2. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Intel 525MW and FreeBSD 9.0R
Hi, On 25 May 2012, at 20:26, Nenhum_de_Nos wrote: > hail, > > I got issues with port multiplier and was told to update to 9-STABLE. But I > can't. > > I get this error when trying to compile world: > > panic: vm_page_inserted: page already inserted > cpuid=0 > > I tried 3 times. > > my system is Intel 525MW, 4GB Ram. I had various problems with mine, fixed by updating the BIOS. > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 >r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1800.10-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x106ca Family = 6 Model = 1c Stepping = 10 > > Features=0xbfebfbff > Features2=0x40e31d > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant, performance statistics > real memory = 4294967296 (4096 MB) > avail memory = 4077744128 (3888 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > > > It looks its not the first time this happens in this family: > http://sourceforge.net/apps/phpbb/freenas/viewtopic.php?f=104&t=10900 and > http://forums.freenas.org/showthread.php?250-panic-vm_page_insert-page-already-inserted-cpuid-3, > but no solution so far. > > is there anything to solve this, any hint or has anyone also seen this ? > > thanks, > > matheus > > > -- > We will call you Cygnus, > The God of balance you shall be > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > http://en.wikipedia.org/wiki/Posting_style -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Console options for legacy-free mini-itx server?
Hi, Your board has a serial port: > [stuff deleted] > /var/run/dmesg.boot: > > Copyright (c) 1992-2010 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.1-STABLE #7: Mon Nov 15 15:09:08 EST 2010 >r...@johnny.reilly.home:/usr/obj/usr/src/sys/GENERIC amd64 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz (2933.46-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x20652 Family = 6 Model = 25 Stepping = 2 > > Features=0xbfebfbff > > Features2=0x98e3bd > AMD Features=0x28100800 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 4294967296 (4096 MB) > avail memory = 3894886400 (3714 MB) > ACPI APIC Table: [...more stuff deleted...] > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart0: [FILTER] [etc] The diagram on page 12 of http://downloadmirror.intel.com/18702/eng/DH57JG_ProductGuide03_English.pdf shows the connector (labelled R). -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: My kernel panics sucked, but they seem to be gone now.
Hi, On 13 Aug 2010, at 04:33, William D. Colburn (Schlake) wrote: > A rehash of the problem: > > If my computer was plugged into the UPS and sitting on my metal desk > the drive controllers would fail and cause a panic almost immediately > when booted. If my computer was plugged into wall power and sitting > on a wooden table, the machine ran flawlessly. > > New information: > > Removing the UPS, but leaving the computer on the metal desk make the > panics happen a lot less, about every four to seven days. Sometimes > after a crash it couldn't boot because no hard drives could be found > at all, but that always went away with a few power cycles. Is your metal desk earthed? > One of my SATA cards has been with me since 2005. It was a rock solid > card on my old FreBSD install...as long as I didn't plug anything into > SATA port 2. I always had this feeling that something wasn't quite > right with port 2 and that I should avoid it. But I'm running FreeBSD > 8 now, and having strange problems. So I removed the card completely > and my system hasn't crashed since. Which still doesn't prove it was > the card. Removing the card could just have made it even more > intermittent. > > In summary: I hate hardware almost as much as I hate linux. :-) > -- > -- Schlake -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
Hi, On 22 Jun 2010, at 08:45, Jeremy Chadwick wrote: > On Mon, Jun 21, 2010 at 10:33:12PM +0100, Matthew Lear wrote: >> [tale of woe elided] > > I don't really have any other thoughts on the matter, sadly. > [helpful suggestions elided] > > Anyone else have ideas/recommendations? The disks sure look OK. I wouldn't rule out the controller(s), I've had various chipsets fail in odd ways. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.2 filesystem corruption
On 21 May 2010, at 09:21, Charles Sprickman wrote: > On Fri, 21 May 2010, Bob Bishop wrote: > >> Hi, >> >> On 21 May 2010, at 09:04, Charles Sprickman wrote: >> >>> Hello all, >>> >>> [...]I have a box (Dell PE 2970) running FreeBSD 7.2/amd-64. 6 GB of ECC >>> RAM, and a Dell-branded LSI RAID controller (mpt driver). [tale of woe >>> elided] >> >> For any case of spooky behaviour involving SCSI, make completely sure that >> the SCSI cabling is above suspicion. If it isn't, your sanity will be the >> first casualty. > > FWIW, this is SATA. [etc] I've had problems with some SATA drives either going `not ready' for a short time, or not going ready within the time expected by the controller. This can make some RAID controllers drop the disk for instance. As discussed elsewhere, error handling by some drivers leaves something to be desired. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.2 filesystem corruption
Hi, On 21 May 2010, at 09:04, Charles Sprickman wrote: > Hello all, > > [...]I have a box (Dell PE 2970) running FreeBSD 7.2/amd-64. 6 GB of ECC > RAM, and a Dell-branded LSI RAID controller (mpt driver). [tale of woe elided] For any case of spooky behaviour involving SCSI, make completely sure that the SCSI cabling is above suspicion. If it isn't, your sanity will be the first casualty. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: What happened to DVD writing?
Hi, On 20 Sep 2009, at 19:58, Warren Block wrote: [...]This drive has probably written under 50 DVDs, all ISOs used for backup. It's a Lite-On DH-20A4P bought in August 2008. It's looking like the drive itself has failed. Which seems odd, since I thought it could still burn CDs. Have you tried a cleaning disk on it? -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Blocked process
On 20 Aug 2009, at 12:06, Daniel O'Connor wrote: On Thu, 20 Aug 2009, Daniel O'Connor wrote: On Thu, 20 Aug 2009, Bob Bishop wrote: On 20 Aug 2009, at 08:25, Daniel O'Connor wrote: This is running in 6.2 ish using 4BSD, I was under the impression ULE wasn't very stable in 6.2. I could probably try it though... Hmm. ISTR having similar problems around the 6.1-2 era. You might try 6.4 if that's possible for you. Someone is going to visit it, but if I can't solve it remotely I'll probably just update it to 7.2 or so. What sort of problems did you have BTW? Things like ls on the console might take several seconds to respond when the box didn't seem to be very busy (but wasn't idle, maybe serving a little NFS). It wasn't the shell getting swapped out or anything else obvious. This was on SMP, not using X. The problem went away with 6.4R (had to stay with 6.x for unrelated reasons). -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Blocked process
On 20 Aug 2009, at 08:25, Daniel O'Connor wrote: This is running in 6.2 ish using 4BSD, I was under the impression ULE wasn't very stable in 6.2. I could probably try it though... Hmm. ISTR having similar problems around the 6.1-2 era. You might try 6.4 if that's possible for you. -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Blocked process
Hi, On 20 Aug 2009, at 03:34, Daniel O'Connor wrote: [...] The problem appears to now be that the userland process that reads data out of the kernel is being stalled for over 4 seconds. This process reads from the kernel and does some minor processing and then writes it out to a child process to do some more work on it. [...] Given that renice'ing has an effect it seems to be a scheduler problem, [etc] Which scheduler are you using? Have you tried the other one? -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: IPMI and Dell ERA/O
Hi, On 29 Aug 2008, at 08:44, Jeremy Chadwick wrote: [...]That said, the feature you're referring to (IPMI piggybacking on top of an existing NIC on the mainboard) is called "ASF" from a NIC driver perspective. In implementations I've looked at, the interfaces really are distinct hardware but they use a common phy. It's just about transparent to software. The NIC driver for the OS *must* have full awareness of said piggybacking, and if it doesn't, a couple different things can happen: a) NIC simply does not work b) NIC works, but behaves oddly -- usually this is tracked down to the local network seeing the MAC address continually change for the IP address associated with the machine That might just be be misconfiguration: the IPMI interface should have an IP address distinct from (any address of) the 'proper' interface. c) NIC works, but IPMI and other features do not work There are a couple different drivers for FreeBSD which have ASF knowledge; bge(4) does, and I believe em(4) does (I could be wrong here). em(4) does indeed work, we are using it on a couple of dozen boxes. bge(4) has a loader.conf tunable that tells the driver to understand ASF or not. In general, it's horrible, and I feel sorry for driver authors having to deal with it. The only problem I have seen on em is that by default the driver resets the phy during boot which confuses IPMI; if a SOL console session is active, the driver is signalled not to do the reset. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED] " -- Bob Bishop [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Hi, On 1 Aug 2008, at 13:20, Martin wrote: Hello, I don't remember anymore when I reported it the first time. I think it was around 4.x or something like that. The em(4) bug is still there after years. Hasn't anyone really noticed yet that em(4) only appears when you boot FreeBSD with the interface physically attached to a switch for example? If you attach it later, after boot up, the interface won't power up and appear in the interface list (ifconfig)? Steps to reproduce: 1) Switch your PC/laptop off. Really OFF, no reboot. 2) Disconnect the em(4) NIC from your switch. 3) Boot FreeBSD. 4) Plug in the ethernet cable. 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) unless you reboot your machine. Something is not being initialized properly on em(4) devices, it seems. I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's extremely annoying on Thinkpads, when you just want to plug in your laptop somewhere. Well it's not a problem for my TP T41 (just tested with 5.0R and 7.0R), the NIC probes as: Version - 6.7.3> and I've never seen it on sundry other boxes with em. That doesn't mean it can't happen, of course. -- Martin -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED]fax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
em vs IPMI
Hi, Under 7.0R, I've had problems with IPMI over LAN failing across reboot on an Intel S3200SH m/b. I see the following at line 669 of if_em.c: /* Indicate SOL/IDER usage */ if (e1000_check_reset_block(&adapter->hw)) device_printf(dev, "PHY reset is blocked due to SOL/IDER session.\n"); Two questions: 1. Am I correct to infer that PHY reset will kill the IPMI LAN setup? 2. Does the above mean I don't have to worry about losing IPMI if I have an established SOL session? I'm particularly concerned about getting into single user. I figured out how to reestablish access using ipmitool to poke the IPMI LAN setup, but of course I can only get in to do that if the box is up multiuser. I'd find out the answers by experiment, but the box is in production in a colo so it's not so easy. Thanks -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED]fax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PAE vs USB
Hi, Is anyone successfully using USB (particularly umass) under PAE on 7.0R? Or, can anyone say for sure that it's not safe? TIA -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Allowing access to IP/MAC pairs only
Hi, On 31 Jan 2008, at 18:30, Szemerédy Gábor wrote: Hello list! We have feeBSD 6.2 machines with local subnets on the servers and would like to allow access to the internet only for workstations with exact IP/MAC pairs and deny access for not predefined pairs. Is there a solution in firewall settings? In ipfw, something like: allow ip from to any mac any allow ip from to any mac any ... deny ip from any to any Beware that MAC addresses are given in the order dest, src. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD
Hi, FWIW, we are seeing 2 x quad-core 2.66GHz outperform (per core) 2 x dual-core 3GHz on the same type of m/b, apparently because of better bandwidth to memory. However, this is on a compute-intensive workload running 1 job per core so would be pretty insensitive to scheduler/ locking issues. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Harddisk failure causes system crash, please help
Hi, On 8 Nov 2007, at 20:40, David Naylor wrote: [possible disk problem] I have no idea what is wrong (if the disk has corrupted should the kernel not display error messages?). Can you please help/advise? A flaky disk drive (rather than a corrupt filesystem on a good disk) will not necessarily talk enough sense for drivers to behave as we'd all like. If you suspect the disk hardware, your first recourse should be to the manufacturer's diagnostic tool - they all have one, usually a bootable floppy (or CD these days), look on the disk manufacturer's website. SMART is fine if the disk is working and may even help with an incipient failure that hasn't done any serious damage yet. Otherwise the manufacturer's diagnostic is your best bet. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best way to use more that 4 gigs of memory ?
Hi, On 4 Nov 2007, at 21:11, Pete French wrote: I have been doing some experiments with runnign 32 bit processed on and amd64 kernel over the last couple of days and am wondering what the general feel is for the best way to use over 4 gigs of memory. As far as I can see I have 3 options: 1) amd64 kernel + 64 bit processes 2) amd64 kernel + 32 bit processes 3) i386 kernel with PAE and 32 bit processes I was initially thinking that option 1 was the best, but benchmarking it the programs take 3 times longer to run that option 2! This astounds me and I intend to investigate why, but given it is rue then that rules it out as a viable solution for deploying stuff. I had similar results, I surmise (without evidence) it's to do with cache usage. Which leaves either 32 bit processes on a 64 bit kernel or alternatively running under PAE on a 32 bit kerenel. I don't know a lot about PAE and was wondering if anyone had any advice either way as to which wouldbe the most stable and/or best performing. If your workload is CPU-intensive it probably doesn't matter; if it isn't, I'd do some more experiments. cheers, -pcf. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default dns config change causing major poolpah
Hi, Regardless of the technicalities and politics, this change is obviously a major POLA violation which is a good enough reason to back it out. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel Matrix RAID (ICH8R) rebuild?
On 21 May 2007, at 12:52, Krassimir Slavchev wrote: Bob Bishop wrote: Hi, On 21 May 2007, at 10:07, Krassimir Slavchev wrote: Hello, I have problems rebuilding RAID1 array. The bios shows status 'Rebuild' and 'Volumes with "Rebuild" status will be rebuilt within the operating system'. When I try to do 'atacontrol rebuild ar0': atacontrol: ioctl(IOCATARAIDREBUILD): Device not configured From the output below, assuming the system is running OK, the RAID doesn't need rebuilding. The BIOS is just confused about the state of the array, it will probably still boot from it OK. Yes, it boots OK but the RAID need rebuilding. This status is result of disconnecting the second disk, booting, create some files and then reconnect the second disk. [etc] OK. You need to follow the steps in http://www.freebsd.org/doc/ en_US.ISO8859-1/books/handbook/raid.html section 18.4.3. Be careful to detach/reattach the right disk :-) When the rebuild has finished you may find that the BIOS doesn't realize the array has been rebuilt, but that may not matter (much). -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel Matrix RAID (ICH8R) rebuild?
Hi, On 21 May 2007, at 10:07, Krassimir Slavchev wrote: Hello, I have problems rebuilding RAID1 array. The bios shows status 'Rebuild' and 'Volumes with "Rebuild" status will be rebuilt within the operating system'. When I try to do 'atacontrol rebuild ar0': atacontrol: ioctl(IOCATARAIDREBUILD): Device not configured From the output below, assuming the system is running OK, the RAID doesn't need rebuilding. The BIOS is just confused about the state of the array, it will probably still boot from it OK. [I've got a system with Intel ESB2 in the same state, anyone who knows how to make the BIOS see sense (short of a full rebuild) please tell.] I run 6.2-STABLE: dmesg: ... atapci1: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe41f mem 0xfebff800-0xfebf irq 19 at device 31.2 on pci0 atapci1: AHCI Version 01.10 controller with 6 ports detected ata5: on atapci1 ata6: on atapci1 ata7: on atapci1 ata8: on atapci1 ata9: on atapci1 ata10: on atapci1 ... ad10: 152627MB at ata5-master SATA300 ad12: 152627MB at ata6-master SATA300 ar0: 152625MB status: READY ar0: disk0 READY (master) using ad10 at ata5-master ar0: disk1 READY (mirror) using ad12 at ata6-master pciconf -lv: [EMAIL PROTECTED]:31:2:class=0x010400 card=0x81ec1043 chip=0x28228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = RAID atacontrol status ar0: ar0: ATA RAID1 subdisks: ad10 ad12 status: READY The motherboard is Asus P5-E. How to rebuild my RAID? Thanks in advance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable- [EMAIL PROTECTED]" -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IT8212F PCI Raid Card
Hi, On 14 Apr 2007, at 14:52, Gary wrote: Hi, Does FreeBSD support an IT8212F based PCI Raid card? Yes: atapci1: port 0xac00-0xac07,0xb000-0xb003,0xb400-0xb407,0xb800- 0xb803,0xbc00-0xbc0f irq 11 at device 10.0 on pci0 ata2: on atapci1 ata3: on atapci1 ad4: 39205MB at ata2-master UDMA133 ad6: 39205MB at ata3-master UDMA133 ar0: 39205MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master [...] However /dev/ is void of any new drive entries.[etc] Try giving it an "atacontrol create ..." with appropriate parameters, and reboot. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror or ata problem
Hi, At 08:54 30/01/2007, Oliver Fromme wrote: Hi, This is strange. gmirror just detached one of its disks for no apparent reason. [etc] I've seen similar symptoms on different hardware with ataraid. I suspect that SATA disks occasionaly fail to make their bus timings and (some?) controllers are completely intolerant. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel S5000PAL board, onboard ether gige interfaces working?
Hi, At 17:05 27/10/2006, Kurt Jaeger wrote: Hi! Can someone report success with the onboard GigE ports of an Intel S5000PAL board ? [etc] The standard ports Just Work with the em driver on a recent RELENG_6. IPMI access to the BMC via the piggybacked MAC addresses also works. We haven't tried the AXXGBIOMOD integrated dual GigE port expansion module. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone with an ste(4) card?
Hi, At 14:46 26/08/2005, John Baldwin wrote: Is there anyone with an ste(4) ethernet adapter? I have some fixes to the locking for HEAD so that it runs without Giant and no one has stepped up to test them. If no one has the hardware and is willing to test the patches then I'll remove the driver from HEAD in a few weeks. I can do some testing on this. One question: did you really mean to post this to -stable? -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TinyBSD Call For Testers
At 08:01 20/07/2005, Dmitriy Kirhlarov wrote: Hi Igor! On Tue, 19 Jul 2005, Igor Pokrovsky wrote: [...] > What's wrong with PicoBSD? AFAIR, PicoBSD not maintable on FreeBSD 5 and higher. # sysctl kern.version kern.version: FreeBSD 5.3-RELEASE #0: Wed Jul 6 14:47:03 BST 2005 [EMAIL PROTECTED]:/usr/home/rb/build_dir-pxe_install/PICOBSD-pxe_install (with only very minor hacking). -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[4]: ATA_DMA errors (and fs corruption!)
At 13:19 20/06/2005, Tony Byrne wrote: Hello Bob, BB> It didn't to me either. Note the use of 'mysterious' :-) BB> I'd eliminated drives and cables, and then did it all over again when the BB> failure went hard, leaving the controller (or something else on the mobo). BB> With a new mobo all the annoying timeouts which I'd put down to driver BB> misbehaviour just went away. Did you replace the motherboard with one of the same brand and model? No, but as it happened they both have the same SATA controller chip. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[3]: ATA_DMA errors (and fs corruption!)
At 12:12 20/06/2005, Tony Byrne wrote: Hello Bob, >>can be hardware reasons for timeouts such as a dying disk or cable, >>but I think we've eliminated these in our case. [etc] BB> Don't ignore the possibility of failing controller hardware. We had BB> comparable mysterious problems on a client system, causing a lot of BB> head-scratching. Eventually the failure went hard and we had to replace the BB> motherboard. I hear ya! However, moving back to an older kernel changes the severity of the problem from a timeout every 2 to three minutes during heavy activity to about 4 or 5 in a 24 hour period. That doesn't sound like hardware to me. It didn't to me either. Note the use of 'mysterious' :-) I'd eliminated drives and cables, and then did it all over again when the failure went hard, leaving the controller (or something else on the mobo). With a new mobo all the annoying timeouts which I'd put down to driver misbehaviour just went away. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: ATA_DMA errors (and fs corruption!)
At 11:09 20/06/2005, Tony Byrne wrote: [...] Of course, there can be hardware reasons for timeouts such as a dying disk or cable, but I think we've eliminated these in our case. [etc] Don't ignore the possibility of failing controller hardware. We had comparable mysterious problems on a client system, causing a lot of head-scratching. Eventually the failure went hard and we had to replace the motherboard. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot loader cant identify ntfs?
At 01:56 19/05/2005, Ian Dowse wrote: [...] BTW, one potential improvement to the current boot0 situation would be to have boot0cfg dynamically generate the OS table based on what partition types actually exist on the disk. [etc] That would be just plain unhelpful in the case where a partition gets retyped subsequently. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel NTP flipping between FLL and PLL modes
Hi, At 18:21 06/04/2005, Jon Noack wrote: [...] I only got resets on the SMP/ULE machine. Perhaps SMP or ULE make the issue worse? I'm seeing it on both SMP and UP boxes on the same LAN, not running ULE. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel NTP flipping between FLL and PLL modes
Hi, At 11:45 06/04/2005, Andriy Gapon wrote: I can not explain it, but I've suddenly got a gut feeling that the subject discussed might be a result of revision 1.53 of sys/kern/kern_ntptime.c Nope. Tried that (backed it out to 1.52), no improvement. I'm currently runnning a 5.3 with the ntpd from 5.2.1 (ie version 4.1.1 not 4.2.0); looks good so far, I'll report back after a sensible interval. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel NTP flipping between FLL and PLL modes
Hi, At 18:42 01/04/2005, Roland Smith wrote: On my amd64 box I also get the mode flipping, but I don't get resets. Hmm. I am getting resets on my amd64. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel NTP flipping between FLL and PLL modes
Hi, At 17:38 01/04/2005, Andriy Gapon wrote: [...] I suppose that it might be possible that the root cause is in my local network conditions, [etc] Unlikely I think. As I said, I've got several machines on the same LAN: the 5.3's misbehave; the others don't. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel NTP flipping between FLL and PLL modes
Hi, At 14:04 01/04/2005, David Magda wrote: On Apr 1, 2005, at 05:45, Peter Jeremy wrote: Any suggestions as to why this is happening? (And how I can stop it regularly flipping) I don't think this is really an issue. [etc] I think this is an issue: - As stated, machines running 4.x don't seem to do it - In addition to the mode schizophrenia, undex 5.3 I'm also seeing resets of several seconds which don't happen on identical hardware running 4.11 in the same rack. Yes I know the clock drifts will be different, but ntp.drift is very close on the two boxen. I believe something's broken. More datapoints: - I'm seeing it under 5.3R both on i386 and amd64 but not i386/4.11 on the same LAN - I'm not seeing it on 5.1R on a remote system -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Save the Demon!
At 06:32 10/02/2005, Peter Jeremy wrote: On 2005-Feb-10 04:39:13 +0100, Bj?rn K?nig <[EMAIL PROTECTED]> wrote: >David Magda wrote: > >>It's "daemon", not "demon". Or even "dæmon" >It's a question whether you are British or American or understand it as >a proper name. ;-) My dictionary has both as headwords with a reference from demon to daemon (but not vice versa) and lists "a service program that is called into action by the operating system" under daemon. The etymology is from greek "daimon" via latin "daemon". FWIW, Concise Oxford has: demon n. ... 5 (also daemon) a) an inner or attendant spirit; a genius (the demon of creativity). b) a divinity or supernatural being in ancient Greece. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No RAID for VT8237?
Hi, At 07:04 30/11/2004, Mike Jakubik wrote: Ash said: > Mike, > > I'm not sure what the status of RAID on a VT8237 is, but is it possible > the array(s) is(are) there and you are not noticing them? No, there is no ar. Just the individual disks. > Most of these lower end PATA/SATA "RAID" controllers are doing their > work in software. As such you will be able to see (not to mention mount, > modify, etc...) the physical RAID components in addition to the actual > array. Yes, i understand that. I have many other servers with supported ATA raid. You might try an 'atacontrol create '. I had a problem where I'd defined RAID1 in the BIOS, but 5.3 wouldn't see it (specifically saw the drives individually but no ar0); after atacontrol create... it all works. Go fig. -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bad em NIC or new unrecognized NIC ?
Hi again, At 19:57 26/2/04, Mike Tancsa wrote: At 02:26 PM 26/02/2004, Bob Bishop wrote: Hi, At 18:25 26/2/04, Mike Tancsa wrote: em0: The EEPROM Checksum Is Not Valid [etc] FWIW I get something very similar under 5.2.1-RC2 on my shiny new ThinkPad T41, so it's likely just not recognised. Actually, I worked around the problem by swapping its location with an fxp next to it. For some reason the em does not seem to like sharing its interrupt with agp0 ? The fxp seems happy enough to do it however. On my T41, hw.pci.allow_unsupported_io_range="1" in /boot/loader.conf fixed it, so maybe the IRQ wasn't the problem. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: very old bug
Hi, At 01:55 11/04/02 +0100, Ian Dowse wrote: >In message <[EMAIL PROTECTED]>, "Vladislav V. Zhuk" writes: > >After attempt to write data to write-protected floppy > >(or diskette with bad blocks) FreeBSD die. > > > >It's VERY VERY annoying... :( > > > >Who can fix this bug?? > >Unfortunately, this is believed to be very hard to fix, so the best >recommendation is that you avoid mounting filesystems from floppy >disks. [etc] IMHO, panic or hang is an unacceptable response to a media bad block (except possibly in the case of the root filesystem). The write-protect thing is hard but not impossible. The problem is that most floppy drives will only tell you about write-protect in response to a write attempt, by which time (in the case of a mount) it's a bit late. On our (picoBSD-powered) routers, we use a script that checks the write protection before attempting to mount the floppy. The test is to read block 0 off the raw flop and attempt to write it back. This will trip the write-protect check reliably. I entertain the theory that the floppy driver could do this test on open for write. To make it harder to shoot oneself in the foot, use an fstab entry like: /dev/fd0a /flop ro,noauto 0 0 and mount /flop, followed by mount -uw if you really want to write. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Realtek 8139
Hi, At 10:13 29/11/01 -0200, Luiz Gustavo (Berrão) wrote: >I'm still having problems with the realtek ethernet card. One of my friends >told me that the rl0 module doesn't work fine with other modules (like, if I >want two ethernet cards or both are rl0 or none is). Is it true? Well, the following seems to work just fine here (on 4.3R): >Jul 24 08:43:49 goliath /kernel: fxp0: >port 0xd000-0xd03f mem 0xd600-0xd60f,0xd6202000-0xd6202fff irq 12 >at device 13.0 on pci0 >Jul 24 08:43:49 goliath /kernel: fxp0: Ethernet address 00:e0:81:02:8a:73 >Jul 24 08:43:49 goliath /kernel: fxp1: >port 0xd400-0xd43f mem 0xd610-0xd61f,0xd6201000-0xd6201fff irq 10 >at device 14.0 on pci0 >Jul 24 08:43:49 goliath /kernel: fxp1: Ethernet address 00:e0:81:02:8a:74 >Jul 24 08:43:49 goliath /kernel: rl0: port >0xe000-0xe0ff mem 0xd6203000-0xd62030ff irq 10 at device 16.0 on pci0 >Jul 24 08:43:49 goliath /kernel: rl0: Ethernet address: 00:50:bf:32:ca:e9 >Jul 24 08:43:49 goliath /kernel: miibus0: on rl0 >Jul 24 08:43:49 goliath /kernel: rlphy0: interface> on miibus0 >Jul 24 08:43:49 goliath /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, >100baseTX-FDX, auto >Jul 24 08:43:49 goliath /kernel: rl1: port >0xe400-0xe4ff mem 0xd6204000-0xd62040ff irq 11 at device 17.0 on pci0 >Jul 24 08:43:49 goliath /kernel: rl1: Ethernet address: 00:50:bf:32:ca:ee >Jul 24 08:43:49 goliath /kernel: miibus1: on rl1 >Jul 24 08:43:49 goliath /kernel: rlphy1: interface> on miibus1 >Jul 24 08:43:49 goliath /kernel: rlphy1: 10baseT, 10baseT-FDX, 100baseTX, >100baseTX-FDX, auto -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
