On Tuesday 14 October 2003 17:40, freebsd-current-request_at_freebsd.org wrote: > Send freebsd-current mailing list submissions to > freebsd-current_at_freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-current > or, via email, send a message with subject or body 'help' to > freebsd-current-request_at_freebsd.org > > You can reach the person managing the list at > freebsd-current-owner_at_freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-current digest..." > > > Today's Topics: > > 1. Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken (Arjan van Leeuwen) > 2. Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken (Jeff Roberson) > 3. Re: cvs commit: src/sys/dev/sound/pci ich.c (Mark Santcroos) > 4. Re: boot hang: "ata1: resetting devices .. done" > (5.1-CURRENT, IBMT30) (Lee Damon) > 5. XFree86-4-clients port broken. (David Gilbert) > 6. Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken (Arjan van Leeuwen) > 7. Re: XFree86-4-clients port broken. (Peter Wemm) > 8. Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken (Jeff Roberson) > 9. Re: XFree86-4-clients port broken. (Kris Kennaway) > 10. Re: XFree86-4-clients port broken. (Eric Anholt) > 11. Re: XFree86-4-clients port broken. (Peter Wemm) > 12. Re: XFree86-4-clients port broken. (Eric Anholt) > 13. Re: XFree86-4-clients port broken. (David Gilbert) > 14. Re: XFree86-4-clients port broken. (David Gilbert) > 15. Re: XFree86-4-clients port broken. (Eric Anholt) > 16. Re: panic with cdrecord -- anybody else seeing this? > [backtrace obtained] (John Reynolds) > 17. Re: Interrupt statistics? (M. Warner Losh) > 18. [current tinderbox] failure on amd64/amd64 (Tinderbox) > 19. rijndael causes unaligned reference in kernel. (Marcel Moolenaar) > 20. Re: cvs commit: src/sys/dev/sound/pci ich.c (M. Warner Losh) > 21. sata stripe & dual boot (Putinas) > 22. Re: boot hang: "ata1: resetting devices .. done" > (5.1-CURRENT, IBMT30) (Jacek Serwatynski) > 23. LOR (tcp_input.c:654 <> tcp_usrreq.c:621). (Pawel Jakub Dawidek) > 24. Re: LOR (tcp_input.c:654 <> tcp_usrreq.c:621). (Tilman Linneweh) > 25. Re: panic: softdep_deallocate_dependencies: dangling deps > (Oliver Fischer) > 26. GEOM Gate. (Pawel Jakub Dawidek) > 27. ata problem with 13/10/2003 current (Matteo Riondato) > 28. Re: ata problem with 13/10/2003 current (Soren Schmidt) > 29. Re: [ALTQ/FreeBSD] Re: if_tun not altq enabled in pfaltq > patch? (Max Laier) > 30. Re: ata problem with 13/10/2003 current (Matteo Riondato) > 31. Re: ata problem with 13/10/2003 current (Rob MacGregor) > 32. Re: sata stripe & dual boot (Doug White) > 33. Re: sata stripe & dual boot (Putinas) > 34. sata + vinum + Asus p4p800 = :( (Balazs Nagy) > 35. Re: GEOM Gate. (Richard Tobin) > 36. Re: What's up with the IP stack? (Terry Lambert) > 37. Re: ata problem with 13/10/2003 current (Matteo Riondato) > 38. Re: What's up with the IP stack? (Kevin Oberman) > 39. Re: ata problem with 13/10/2003 current (Soren Schmidt) > 40. How to create distribution for later NFS sysinstall on other > box? (Chris Shenton) > 41. Re: BTX Halted (AMD 5x86 133MHz) (Giovanni P. Tirloni) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 Oct 2003 21:19:57 +0200 > From: Arjan van Leeuwen <avleeuwen_at_piwebs.com> > Subject: Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken > To: Jeff Roberson <jroberson_at_chesapeake.net> > Cc: current_at_freebsd.org > Message-ID: <200310132119.57735.avleeuwen_at_piwebs.com> > Content-Type: text/plain; charset="iso-8859-1" > > On Sunday 12 October 2003 23:21, Jeff Roberson wrote: > > I commited a fix that would have caused all of the jerky behaviors under > > some load. I was not able to reproduce this problem with kde running > > afterwards. > > Thanks for the fix! However, the problem is still here for me (using rev. > 1.58). I just noticed it when compiling Mozilla. I can also still see it > when logging out of GNOME. > > Arjan > > > ------------------------------ > > Message: 2 > Date: Mon, 13 Oct 2003 15:27:55 -0400 (EDT) > From: Jeff Roberson <jroberson_at_chesapeake.net> > Subject: Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken > To: Arjan van Leeuwen <avleeuwen_at_piwebs.com> > Cc: current_at_freebsd.org > Message-ID: <20031013152650.N56213-100000_at_mail.chesapeake.net> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Mon, 13 Oct 2003, Arjan van Leeuwen wrote: > > On Sunday 12 October 2003 23:21, Jeff Roberson wrote: > > > I commited a fix that would have caused all of the jerky behaviors > > > under some load. I was not able to reproduce this problem with kde > > > running afterwards. > > > > Thanks for the fix! However, the problem is still here for me (using rev. > > 1.58). I just noticed it when compiling Mozilla. I can also still see it > > when logging out of GNOME. > > Is it somewhat better? I specifically fixed the problem for Giant but > other locks could have the same issues. I suspect that they are far less > frequently held without Giant, but I could be wrong. > > > Arjan > > ------------------------------ > > Message: 3 > Date: Mon, 13 Oct 2003 22:45:41 +0200 > From: Mark Santcroos <marks_at_ripe.net> > Subject: Re: cvs commit: src/sys/dev/sound/pci ich.c > To: Nate Lawson <nate_at_root.org> > Cc: current_at_freebsd.org > Message-ID: <20031013204541.GA1601_at_laptop.6bone.nl> > Content-Type: text/plain; charset=us-ascii > > On Mon, Oct 13, 2003 at 09:47:45AM -0700, Nate Lawson wrote: > > It looks like you are resetting the BARs on resume. If that's all that's > > needed, I believe Warner was working on code to do this in the general > > case. > > Exactly, the thread[*] went on about pci power transitions in general. > Warner also responded to it. > > Without complaining too much, this subject needs to be opened up. > Every time someone does something in this area we are told to hold off > because "something" is coming. > (Last month I've been inactive, so if something has popped up, please > discard this message) > > Mark > > [*] "Subject: Correct PCI suspend and resume operations [ was Re: cirrus > ich3 doesn't work after suspend to disk ]" > > ------------------------------ > > Message: 4 > Date: Mon, 13 Oct 2003 14:51:43 -0700 > From: Lee Damon <nomad_at_castle.org> > Subject: Re: boot hang: "ata1: resetting devices .. done" > (5.1-CURRENT, IBMT30) > To: freebsd-current_at_freebsd.org > Cc: culverk_at_sweetdreamsracing.biz > Message-ID: <200310132151.h9DLphk6063083_at_castle.org> > Content-Type: text/plain; charset=us-ascii > > > > > > Backing out the most recent checkin to sys/dev/ata/ata-queue.c > > > > > (i.e. reverting to version 1.6) makes the problem go away. > > > > > > > > I upgraded from an Oct 1 -> Oct 12 kernel and saw the same hang. > > > > Backing out r1.6 fixed it for me too. > > > > Anyone tried going forward to 1.8? > > I just tried 1.8, it did not fix the problem. Symtoms are still the same, > > > > ad0: 35174MB <IC25N040ATCS05-0> [71465/16/63] at ata0-master UDMA100 > > > ata1: resetting devices .. > > > done > > Going back to 1.6 (apparently) does fix the problem. > > nomad > ----------- > The cry has been that when war is declared, all opposition should > therefore be hushed. A sentiment more unworthy of a free country could > hardly be propagated. If the doctrine be admitted, rulers have only to > declare war and they are screened at once from scrutiny ... In war, > then, as in peace, assert the freedom of speech and of the press. > Cling to this as the bulwark of all our rights and privileges. > -- William Ellery Channing > > ----------- - Lee "nomad" Damon - \ > play: nomad_at_castle.org or castle!nomad \ > work: nomad_at_ee.washington.edu \ > /\ > Seneschal, Castle PAUS. / \ > "Celebrate Diversity" / \ > > > > > ------------------------------ > > Message: 5 > Date: Mon, 13 Oct 2003 17:54:57 -0400 > From: David Gilbert <dgilbert_at_dclg.ca> > Subject: XFree86-4-clients port broken. > To: freebsd-current_at_freebsd.org > Message-ID: <16267.7985.702056.610331_at_canoe.dclg.ca> > Content-Type: text/plain; charset=us-ascii > > I don't really have a clue where to look for this fix as there seems > to be a serious amount of magic going into the divided XFree86-4 port > builds, but my XFree86-4-clients port fails saying: > > make: don't know how to make > /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop > > Dave. > > -- > =========================================================================== >= > > |David Gilbert, Independent Contractor. | Two things can only be > | | Mail: dave_at_daveg.ca | equal if and only if > | they | http://daveg.ca | are precisely > | opposite. | > > =========================================================GLO=============== >= > > ------------------------------ > > Message: 6 > Date: Tue, 14 Oct 2003 00:43:49 +0200 > From: Arjan van Leeuwen <avleeuwen_at_piwebs.com> > Subject: Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken > To: Jeff Roberson <jroberson_at_chesapeake.net> > Cc: current_at_freebsd.org > Message-ID: <200310140043.49108.avleeuwen_at_piwebs.com> > Content-Type: text/plain; charset="iso-8859-1" > > On Monday 13 October 2003 21:27, Jeff Roberson wrote: > > On Mon, 13 Oct 2003, Arjan van Leeuwen wrote: > > > On Sunday 12 October 2003 23:21, Jeff Roberson wrote: > > > > I commited a fix that would have caused all of the jerky behaviors > > > > under some load. I was not able to reproduce this problem with kde > > > > running afterwards. > > > > > > Thanks for the fix! However, the problem is still here for me (using > > > rev. 1.58). I just noticed it when compiling Mozilla. I can also still > > > see it when logging out of GNOME. > > > > Is it somewhat better? I specifically fixed the problem for Giant but > > other locks could have the same issues. I suspect that they are far less > > frequently held without Giant, but I could be wrong. > > Now that I looked at it better, yes, it does indeed seem better :). It > still seems to happen at the same places, but the jerkiness is less... > jerky. the position of the mouse pointer is updated more often than used to > be the case. > > Arjan > > > ------------------------------ > > Message: 7 > Date: Mon, 13 Oct 2003 15:51:06 -0700 > From: Peter Wemm <peter_at_wemm.org> > Subject: Re: XFree86-4-clients port broken. > To: David Gilbert <dgilbert_at_dclg.ca> > Cc: freebsd-current_at_freebsd.org > Message-ID: <20031013225106.CB0252A8D5_at_canning.wemm.org> > > David Gilbert wrote: > > I don't really have a clue where to look for this fix as there seems > > to be a serious amount of magic going into the divided XFree86-4 port > > builds, but my XFree86-4-clients port fails saying: > > > > make: don't know how to make > > /usr/ports/x11/XFree86-4-clients/work/xc/exports > > /lib/libfntstubs.a. Stop > > I ran into this on my amd64 box too. Is yours an i386? > > Cheers, > -Peter > -- > Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > ------------------------------ > > Message: 8 > Date: Mon, 13 Oct 2003 18:55:30 -0400 (EDT) > From: Jeff Roberson <jroberson_at_chesapeake.net> > Subject: Re: ULE status; interactivity fixed? nice uninvestigated, > HTT broken > To: Arjan van Leeuwen <avleeuwen_at_piwebs.com> > Cc: current_at_freebsd.org > Message-ID: <20031013185357.A56213-100000_at_mail.chesapeake.net> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Tue, 14 Oct 2003, Arjan van Leeuwen wrote: > > On Monday 13 October 2003 21:27, Jeff Roberson wrote: > > > On Mon, 13 Oct 2003, Arjan van Leeuwen wrote: > > > > On Sunday 12 October 2003 23:21, Jeff Roberson wrote: > > > > > I commited a fix that would have caused all of the jerky behaviors > > > > > under some load. I was not able to reproduce this problem with kde > > > > > running afterwards. > > > > > > > > Thanks for the fix! However, the problem is still here for me (using > > > > rev. 1.58). I just noticed it when compiling Mozilla. I can also > > > > still see it when logging out of GNOME. > > > > > > Is it somewhat better? I specifically fixed the problem for Giant but > > > other locks could have the same issues. I suspect that they are far > > > less frequently held without Giant, but I could be wrong. > > > > Now that I looked at it better, yes, it does indeed seem better :). It > > still seems to happen at the same places, but the jerkiness is less... > > jerky. the position of the mouse pointer is updated more often than used > > to be the case. > > Thanks. This feedback is very important for me to resolve this issues. I > think I know how to solve the issue now, I'm going to make the required > changes soon. I'll send a status update again when I do. > > Cheers, > Jeff > > > Arjan > > ------------------------------ > > Message: 9 > Date: Mon, 13 Oct 2003 15:56:00 -0700 > From: Kris Kennaway <kris_at_obsecurity.org> > Subject: Re: XFree86-4-clients port broken. > To: Peter Wemm <peter_at_wemm.org> > Cc: freebsd-current_at_freebsd.org > Message-ID: <20031013225600.GA43355_at_rot13.obsecurity.org> > Content-Type: text/plain; charset="us-ascii" > > On Mon, Oct 13, 2003 at 03:51:06PM -0700, Peter Wemm wrote: > > David Gilbert wrote: > > > I don't really have a clue where to look for this fix as there seems > > > to be a serious amount of magic going into the divided XFree86-4 port > > > builds, but my XFree86-4-clients port fails saying: > > > > > > make: don't know how to make > > > /usr/ports/x11/XFree86-4-clients/work/xc/exports > > > > /lib/libfntstubs.a. Stop > > > > I ran into this on my amd64 box too. Is yours an i386? > > The port is broken on all architectures. anholt is looking into it. > > Kris > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031013/963 >89b5d/attachment-0001.bin > > ------------------------------ > > Message: 10 > Date: Mon, 13 Oct 2003 16:01:09 -0700 > From: Eric Anholt <eta_at_lclark.edu> > Subject: Re: XFree86-4-clients port broken. > To: Peter Wemm <peter_at_wemm.org> > Cc: freebsd-current_at_freebsd.org > Message-ID: <1066086068.642.104.camel_at_leguin> > Content-Type: text/plain > > On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > > David Gilbert wrote: > > > I don't really have a clue where to look for this fix as there seems > > > to be a serious amount of magic going into the divided XFree86-4 port > > > builds, but my XFree86-4-clients port fails saying: > > > > > > make: don't know how to make > > > /usr/ports/x11/XFree86-4-clients/work/xc/exports > > > > /lib/libfntstubs.a. Stop > > > > I ran into this on my amd64 box too. Is yours an i386? > > This is a problem on ref5, too. I am testing a fix right now. The > confusing part is I can't find any change I (or anyone else) has made > that would have caused this. > > -- > Eric Anholt eta_at_lclark.edu > http://people.freebsd.org/~anholt/ anholt_at_FreeBSD.org > > > > ------------------------------ > > Message: 11 > Date: Mon, 13 Oct 2003 16:05:04 -0700 > From: Peter Wemm <peter_at_wemm.org> > Subject: Re: XFree86-4-clients port broken. > To: Eric Anholt <eta_at_lclark.edu> > Cc: freebsd-current_at_freebsd.org > Message-ID: <20031013230504.C54F32A8DF_at_canning.wemm.org> > > Eric Anholt wrote: > > On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > > > David Gilbert wrote: > > > > I don't really have a clue where to look for this fix as there seems > > > > to be a serious amount of magic going into the divided XFree86-4 port > > > > builds, but my XFree86-4-clients port fails saying: > > > > > > > > make: don't know how to make > > > > /usr/ports/x11/XFree86-4-clients/work/xc/exp > > orts > > > > /lib/libfntstubs.a. Stop > > > > > > I ran into this on my amd64 box too. Is yours an i386? > > > > This is a problem on ref5, too. I am testing a fix right now. The > > confusing part is I can't find any change I (or anyone else) has made > > that would have caused this. > > Does the port have any exposure to make(1) at all? Its been futzed with > fairly recently. I know it's supposed to use gmake, but perhaps there are > still some "make" references? > > Cheers, > -Peter > -- > Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > ------------------------------ > > Message: 12 > Date: Mon, 13 Oct 2003 16:22:05 -0700 > From: Eric Anholt <eta_at_lclark.edu> > Subject: Re: XFree86-4-clients port broken. > To: Peter Wemm <peter_at_wemm.org> > Cc: freebsd-current_at_freebsd.org > Message-ID: <1066087324.642.114.camel_at_leguin> > Content-Type: text/plain > > On Mon, 2003-10-13 at 16:05, Peter Wemm wrote: > > Eric Anholt wrote: > > > On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > > > > David Gilbert wrote: > > > > > I don't really have a clue where to look for this fix as there > > > > > seems to be a serious amount of magic going into the divided > > > > > XFree86-4 port builds, but my XFree86-4-clients port fails saying: > > > > > > > > > > make: don't know how to make > > > > > /usr/ports/x11/XFree86-4-clients/work/xc/exp > > > > orts > > > > > > /lib/libfntstubs.a. Stop > > > > > > > > I ran into this on my amd64 box too. Is yours an i386? > > > > > > This is a problem on ref5, too. I am testing a fix right now. The > > > confusing part is I can't find any change I (or anyone else) has made > > > that would have caused this. > > > > Does the port have any exposure to make(1) at all? Its been futzed with > > fairly recently. I know it's supposed to use gmake, but perhaps there > > are still some "make" references? > > No, actually it uses the system (bsd) make. It generally is pretty > resistant to differences with different types of make, though. > > Testing a new idea for a fix that will cut the build time/space > required, too. > > -- > Eric Anholt eta_at_lclark.edu > http://people.freebsd.org/~anholt/ anholt_at_FreeBSD.org > > > > ------------------------------ > > Message: 13 > Date: Mon, 13 Oct 2003 20:06:20 -0400 > From: David Gilbert <dgilbert_at_dclg.ca> > Subject: Re: XFree86-4-clients port broken. > To: Peter Wemm <peter_at_wemm.org> > Cc: freebsd-current_at_freebsd.org > Message-ID: <16267.15868.187828.297032_at_canoe.dclg.ca> > Content-Type: text/plain; charset=us-ascii > > >>>>> "Peter" == Peter Wemm <peter_at_wemm.org> writes: > > Peter> David Gilbert wrote: > >> I don't really have a clue where to look for this fix as there > >> seems to be a serious amount of magic going into the divided > >> XFree86-4 port builds, but my XFree86-4-clients port fails saying: > >> > >> make: don't know how to make > >> /usr/ports/x11/XFree86-4-clients/work/xc/exports > > Peter> /lib/libfntstubs.a. Stop > > Peter> I ran into this on my amd64 box too. Is yours an i386? > > Yes. I'm getting it on an intel centrino. > > Dave. > > -- > =========================================================================== >= > > |David Gilbert, Independent Contractor. | Two things can only be > | | Mail: dave_at_daveg.ca | equal if and only if > | they | http://daveg.ca | are precisely > | opposite. | > > =========================================================GLO=============== >= > > ------------------------------ > > Message: 14 > Date: Mon, 13 Oct 2003 20:10:16 -0400 > From: David Gilbert <dgilbert_at_dclg.ca> > Subject: Re: XFree86-4-clients port broken. > To: Peter Wemm <peter_at_wemm.org> > Cc: freebsd-current_at_freebsd.org > Message-ID: <16267.16104.137665.580328_at_canoe.dclg.ca> > Content-Type: text/plain; charset=us-ascii > > >>>>> "Peter" == Peter Wemm <peter_at_wemm.org> writes: > > Peter> Eric Anholt wrote: > >> On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > David Gilbert > >> wrote: > > I don't really have a clue where to look for this fix as > >> there seems > > to be a serious amount of magic going into the > >> divided XFree86-4 port > > builds, but my XFree86-4-clients port > >> > >> fails saying: > >> > > make: don't know how to make > >> > >> /usr/ports/x11/XFree86-4-clients/work/xc/exp > > Peter> orts > > >> > /lib/libfntstubs.a. Stop > >> > > >> > I ran into this on my amd64 box too. Is yours an i386? > >> > >> This is a problem on ref5, too. I am testing a fix right now. The > >> confusing part is I can't find any change I (or anyone else) has > >> made that would have caused this. > > Peter> Does the port have any exposure to make(1) at all? Its been > Peter> futzed with fairly recently. I know it's supposed to use > Peter> gmake, but perhaps there are still some "make" references? > > If you look at the port, it uses make fairly extensively now. The > Makefile (from my limited understanding) seems to charge into building > the port without calling gmake by adding sub directories much like the > /usr/src makefile seems to do. > > Dave. > > -- > =========================================================================== >= > > |David Gilbert, Independent Contractor. | Two things can only be > | | Mail: dave_at_daveg.ca | equal if and only if > | they | http://daveg.ca | are precisely > | opposite. | > > =========================================================GLO=============== >= > > ------------------------------ > > Message: 15 > Date: Mon, 13 Oct 2003 17:48:27 -0700 > From: Eric Anholt <eta_at_lclark.edu> > Subject: Re: XFree86-4-clients port broken. > To: David Gilbert <dgilbert_at_dclg.ca> > Cc: ports_at_FreeBSD.org > Message-ID: <1066092507.642.119.camel_at_leguin> > Content-Type: text/plain > > On Mon, 2003-10-13 at 14:54, David Gilbert wrote: > > I don't really have a clue where to look for this fix as there seems > > to be a serious amount of magic going into the divided XFree86-4 port > > builds, but my XFree86-4-clients port fails saying: > > > > make: don't know how to make > > /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop > > > > Dave. > > It should be fixed now. Please cvsup (in ~1hour) and try again. > > -- > Eric Anholt eta_at_lclark.edu > http://people.freebsd.org/~anholt/ anholt_at_FreeBSD.org > > > > ------------------------------ > > Message: 16 > Date: Mon, 13 Oct 2003 21:54:17 -0700 > From: John Reynolds <johnjen_at_reynoldsnet.org> > Subject: Re: panic with cdrecord -- anybody else seeing this? > [backtrace obtained] > To: Marius Strobl <marius_at_alchemy.franken.de> > Cc: bms_at_freebsd.org > Message-ID: <16267.33145.579918.418109_at_whale.home-net> > Content-Type: text/plain; charset=us-ascii > > > [ On Monday, October 13, Marius Strobl wrote: ] > > > And > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/57611 > > > > The latter is a bit more detailed and correct (it's not limited to ATAPI > > burners). It also doesn't seem to be limited to cdrecord, the latest > > ntpd also causes a panic when using mlockall(2) as reported on this list, > > however the backtrace looks different. > > Btw., the cdrtools-devel port contains a workaround. > > I can confirm that using the latest and greatest cdrtools-devel port works > around the bug, so it's a definite problem related to mlockall(2). I've > burned a cd with a kernel from Aug 19th, and also from Oct 11th and all > seems well with this work-around. > > If there are further patches to try and apply to the kernel to work-around > this issue or if people need further print's from gdb from my crash dumps, > please let me know! > > -Jr > > -- > John & Jennifer Reynolds johnjen at reynoldsnet.org > www.reynoldsnet.org Structural / Physical Design - ICG/PNG SCD jreynold > at sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. > FreeBSD: The Power to Serve! "Unix is user friendly, it's just particular > about the friends it chooses." > > ------------------------------ > > Message: 17 > Date: Mon, 13 Oct 2003 22:55:19 -0600 (MDT) > From: "M. Warner Losh" <imp_at_bsdimp.com> > Subject: Re: Interrupt statistics? > To: nate_at_root.org > Cc: current_at_freebsd.org > Message-ID: <20031013.225519.19308181.imp_at_bsdimp.com> > Content-Type: Text/Plain; charset=us-ascii > > In message: <20031013105145.J28323_at_root.org> > > Nate Lawson <nate_at_root.org> writes: > : Given that, my biggest concern now is IO corruption. Are there any > : devices that have a low interrupt rate (or bus mastering rate) that > : cannot handle a few hundred us latency added to their handler startup? > : I'm thinking something like a floppy drive where the time between > : interrupts is great enough that cpu_idle() is called but that need to be > : serviced quickly or data is over/underrun. > > sio/uart > > At 115200 baud, you have 173us to service the interrupt when the FIFO > interrupt level is set to HI. At 460800 at HI you have 43us. With > the more conservative MED settings, these numbers are 4 times better > (670us and 173us). 200us is smack dab in the middle of these times. > This is inbound data, so things could be idle and there be issues. > > Not sure about other devices. > > Warner > > ------------------------------ > > Message: 18 > Date: Tue, 14 Oct 2003 01:33:20 -0400 (EDT) > From: Tinderbox <des+tinderbox_at_freebsd.org> > Subject: [current tinderbox] failure on amd64/amd64 > To: current_at_freebsd.org, amd64_at_freebsd.org > Message-ID: <200310140533.h9E5XKvY096089_at_cueball.rtp.FreeBSD.org> > > > > ------------------------------ > > Message: 19 > Date: Mon, 13 Oct 2003 22:46:14 -0700 > From: Marcel Moolenaar <marcel_at_xcllnt.net> > Subject: rijndael causes unaligned reference in kernel. > To: current_at_FreeBSD.org > Cc: ia64_at_FreeBSD.org > Message-ID: <20031014054614.GA56455_at_dhcp01.pn.xcllnt.net> > Content-Type: text/plain; charset=us-ascii > > Gang, > > The rijndael code causes an unaligned reference prior to init(8). Sources > as of today. Please fix: > > > Timecounter "ITC" frequency 800025984 Hz quality 0 > Timecounters tick every 10.000 msec > > fatal kernel trap (cpu 0): > > trap vector = 0x1e (Unaligned Reference) > cr.iip = 0xe00000000418b9b0 > cr.ipsr = 0x1010080a6010 (mfl,ic,i,dt,dfh,rt,cpl=0,it,ri=0,bn) > cr.isr = 0x400000000 (code=0,vector=0,r,ei=0) > cr.ifa = 0xe0000000046fbf2d > curthread = 0xe0000000047029b0 > pid = 0, comm = swapper > > Stopped at rijndael_blockEncrypt+0x1f0: [MMI] ld4 r15=[r16];; > db> trace > rijndael_blockEncrypt(0xe0000000046fbf29, 0xe0000000046fbcf8, > 0xe0000000046fbcd8, 0xe00000000467f41c, 0xe0000000046fbcb8) at > rijndael_blockEncrypt+0x1f0 yarrow_encrypt(0xe0000000046fbcf8, > 0xe0000000046fbcd8, 0xe0000000046fbcb8, 0xe000000004188b60) at > yarrow_encrypt+0x40 read_random_real(0xe00000000467f420, 0x20) at > read_random_real+0x140 read_random(0xe00000000467f420, 0x20, > 0xe0000000043c2b90, 0x38b) at read_random+0x50 > arc4_randomstir(0xe00000000467f530, 0xe0000000045f1950, 0x20, > 0xe00000007efc18e0) at arc4_randomstir+0x20 arc4rand(0xe00000000467f540, > 0x4, 0x0) at arc4rand+0xb0 > arc4random() at arc4random+0x30 > frag6_init(0xe000000004452930, 0x208, 0xe000000004715100) at > frag6_init+0x60 ip6_init(0x18b, 0xe000000004360b60, 0x40b) at > ip6_init+0x310 > net_init_domain(0xe0000000046c6238, 0xe0000000046c5d28, 0xe0000000046c6230, > 0xe0000000046e8528) at net_init_domain+0x170 > net_add_domain(0xe0000000046c6208, 0xe000000004291050) at > net_add_domain+0x100 mi_startup(0xe0000000045fcce0, 0xe000000004703260, > 0xe000000004703268, 0x1) at mi_startup+0x2e0 ia64_init(0xe00000000471c838) > at ia64_init+0xca0 > __start() at __start+0xa0 > db> > > -- > Marcel Moolenaar USPA: A-39004 marcel_at_xcllnt.net > > ------------------------------ > > Message: 20 > Date: Tue, 14 Oct 2003 00:25:57 -0600 (MDT) > From: "M. Warner Losh" <imp_at_bsdimp.com> > Subject: Re: cvs commit: src/sys/dev/sound/pci ich.c > To: marks_at_ripe.net > Cc: current_at_freebsd.org > Message-ID: <20031014.002557.30651280.imp_at_bsdimp.com> > Content-Type: Text/Plain; charset=us-ascii > > In message: <20031013204541.GA1601_at_laptop.6bone.nl> > > Mark Santcroos <marks_at_ripe.net> writes: > : On Mon, Oct 13, 2003 at 09:47:45AM -0700, Nate Lawson wrote: > : > It looks like you are resetting the BARs on resume. If that's all > : > that's needed, I believe Warner was working on code to do this in the > : > general case. > : > : Exactly, the thread[*] went on about pci power transitions in general. > : Warner also responded to it. > : > : Without complaining too much, this subject needs to be opened up. > : Every time someone does something in this area we are told to hold off > : because "something" is coming. > : (Last month I've been inactive, so if something has popped up, please > : discard this message) > > Things have happened in p4. We're trying to work out some details. > But you are right a snapshot might be in order. > > Warner > > ------------------------------ > > Message: 21 > Date: Tue, 14 Oct 2003 10:10:31 +0200 > From: "Putinas" <pilkis_at_gmx.net> > Subject: sata stripe & dual boot > To: <freebsd-current_at_FreeBSD.ORG> > Message-ID: <000f01c3922a$a86997c0$1e64a8c0_at_spotripoli.local> > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > Just a quick question, I have setup SATA stripe from two disks, and I have > 3 partitions 4Gb each and the rest for data storing. If I boot in freebsd > from cdrom, I see two empty disks ad4 and ad6 and I guess if I create > something I will mess up with my raid setup. Only one way what I could > think off it would be to use atacontrol _before_ the installation to create > exactly same stripe, and probably then I would see real filesystems on ar0. > Or maybe there is any other way of easy ( or not ) doing this ? > > > Regards, > Putinas Piliponis > > > > ------------------------------ > > Message: 22 > Date: Tue, 14 Oct 2003 10:15:21 +0200 > From: Jacek Serwatynski <tutus_at_trynet.eu.org> > Subject: Re: boot hang: "ata1: resetting devices .. done" > (5.1-CURRENT, IBMT30) > To: freebsd-current_at_freebsd.org > Message-ID: <20031014081521.GA86509_at_trynet.eu.org> > Content-Type: text/plain; charset=iso-8859-2 > > Dnia Mon, Oct 13, 2003 at 02:51:43PM -0700, Lee Damon napisal: > > > Anyone tried going forward to 1.8? > > > > I just tried 1.8, it did not fix the problem. Symtoms are still the > > same, > > I use 1.8 and is working without problem. > -- > Jacek Serwatynski <tutus_at_trynet.eu.org> | PGP_key: > www.trynet.eu.org/pub.key ------ PGP_finger: 5E30 D9C4 976C E9B1 9920 B155 > 962A 737B 1EFA 5987 ------ > > ------------------------------ > > Message: 23 > Date: Tue, 14 Oct 2003 11:47:44 +0200 > From: Pawel Jakub Dawidek <nick_at_garage.freebsd.pl> > Subject: LOR (tcp_input.c:654 <> tcp_usrreq.c:621). > To: freebsd-current_at_freebsd.org > Cc: sam_at_errno.com > Message-ID: <20031014094743.GO520_at_garage.freebsd.pl> > Content-Type: text/plain; charset="iso-8859-2" > > Hello. > > I'm not sure if this was reported already. > > lock order reversal > 1st 0xc51046ec inp (inp) _at_ /usr/src/sys/netinet/tcp_input.c:654 > 2nd 0xc0642cac tcp (tcp) _at_ /usr/src/sys/netinet/tcp_usrreq.c:621 > Stack backtrace: > backtrace(c05d0e2c,c0642cac,c05d63bc,c05d63bc,c05d76ab) at backtrace+0x17 > witness_lock(c0642cac,8,c05d76ab,26d,74) at witness_lock+0x671 > _mtx_lock_flags(c0642cac,0,c05d76ab,26d,74) at _mtx_lock_flags+0xba > tcp_usr_rcvd(c5574400,80,c05d1437,db70ca84,3b9aca00) at tcp_usr_rcvd+0x30 > soreceive(c5574400,db70cac0,db70cacc,db70cac4,0) at soreceive+0x7ff > nfsrv_rcv(c5574400,c7a79480,4,c5105de8,18) at nfsrv_rcv+0x87 > sowakeup(c5574400,c557444c,c05d6dc0,446,108) at sowakeup+0x89 > tcp_input(c1bfc800,14,c06428d4,c05f066c,db70cc48) at tcp_input+0xed1 > ip_input(c1bfc800,0,c05d5bfc,89,0) at ip_input+0x81f > netisr_processqueue(c0641350,0,c05d5bfc,e5,c1bc8100) at > netisr_processqueue+0x8e > > swi_net(0,0,c05cb58d,215,c1bda974) at swi_net+0x8c > ithread_loop(c1bd8d80,db70cd48,c05cb3ff,314,c1bd8d80) at ithread_loop+0x172 > fork_exit(c047d9e0,c1bd8d80,db70cd48) at fork_exit+0xc0 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xdb70cd7c, ebp = 0 --- > > -- > Pawel Jakub Dawidek pawel_at_dawidek.net > UNIX Systems Programmer/Administrator http://garage.freebsd.pl > Am I Evil? Yes, I Am! http://cerber.sourceforge.net > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 305 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031014/446 >d1d81/attachment-0001.bin > > ------------------------------ > > Message: 24 > Date: Tue, 14 Oct 2003 12:04:58 +0200 > From: Tilman Linneweh <tilman_at_arved.de> > Subject: Re: LOR (tcp_input.c:654 <> tcp_usrreq.c:621). > To: Pawel Jakub Dawidek <nick_at_garage.freebsd.pl> > Cc: current_at_Freebsd.org > Message-ID: <20031014100458.GA26139_at_huckfinn.arved.de> > Content-Type: text/plain; charset="us-ascii" > > * Pawel Jakub Dawidek [Di, 14 Okt 2003 at 11:45 GMT]: > > I'm not sure if this was reported already. > > I think so, > http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008743.html > > regards > tilman > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031014/b91 >b0b65/attachment-0001.bin > > ------------------------------ > > Message: 25 > Date: Mon, 13 Oct 2003 13:46:02 +0200 > From: Oliver Fischer <plexus_at_snafu.de> > Subject: Re: panic: softdep_deallocate_dependencies: dangling deps > To: Jeff Roberson <jroberson_at_chesapeake.net> > Cc: freebsd-current_at_freebsd.org > Message-ID: <3F8A907A.5060000_at_snafu.de> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Jeff Roberson wrote: > > When are your sources from? > > My last cvs up is two days ago. > > Regards, > > Oliver Fischer > > > ------------------------------ > > Message: 26 > Date: Tue, 14 Oct 2003 14:47:47 +0200 > From: Pawel Jakub Dawidek <nick_at_garage.freebsd.pl> > Subject: GEOM Gate. > To: freebsd-hackers_at_freebsd.org > Cc: phk_at_phk.freebsd.dk > Message-ID: <20031014124747.GQ520_at_garage.freebsd.pl> > Content-Type: text/plain; charset="iso-8859-2" > > Hello hackers... > > Ok, GEOM Gate is ready for testing. > For those who don't know what it is, they can read README: > > http://garage.freebsd.pl/geom_gate.README > > and presentation from WIP/BSDCon03 session: > > http://garage.freebsd.pl/GEOM_Gate.pdf > > After compliation (cd geom_gate; make; make install) you should run > regression tests: > > # regression/runtests.sh > > If everything will went ok you can play with GEOM Gate and report any bugs. > > I've spend some time to made GEOM Gate force-remove-safe so using > '-f' option with ggc(8) should be always safe. > > Ah! Four manual pages are added, so feel free to read them first > (gg(4), geom_gate(4), ggc(8), ggd(8)) > > http://garage.freebsd.pl/geom_gate.tbz > > Enjoy! > > -- > Pawel Jakub Dawidek pawel_at_dawidek.net > UNIX Systems Programmer/Administrator http://garage.freebsd.pl > Am I Evil? Yes, I Am! http://cerber.sourceforge.net > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 305 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031014/9ff >6b09b/attachment-0001.bin > > ------------------------------ > > Message: 27 > Date: 14 Oct 2003 15:04:11 +0200 > From: Matteo Riondato <rionda_at_gufi.org> > Subject: ata problem with 13/10/2003 current > To: current_at_freebsd.org > Message-ID: <1066136658.2588.14.camel_at_kaiser.sig11.org> > Content-Type: text/plain > > After having update my -CURRENT box to yesterday afternoon (Central > Europe Time) sources, I can't get it to boot. It stops probing ata1: > GEOM: create disk ad0 dp=0xc4536a70 > ad0: 57259MB <MAXTOR 6L060J3> [116336/16/63] at ata0-master UDMA133 > GEOM: create disk ad1 dp=0xc4915a70 > ad1: 38172MB <QUANTUM FIREBALLP AS40.0> [77557/16/63] at ata0-slave \ > UDMA100 > ata1: resetting devices .. > acd0: FAILURE - SETFEATURES status=51 <READY,DSC,ERROR> error=4<ABORTED> > done > acd0: FAILURE - SETFEATURES device lockup-removed > > And it stops here. > > On ata1 there are a Liteon CD-ReWriter 48x12x48x (acd0) > and a LG DVD-ROM Drive DRD-8160B (acd1) > > I never had problem with ATAng before, so it is probably related to a > recent commit. > > Best Regards > > -- > Rionda aka Matteo Riondato > GUFI Staff Member (http://www.gufi.org) > > > > ------------------------------ > > Message: 28 > Date: Tue, 14 Oct 2003 15:09:58 +0200 (CEST) > From: Soren Schmidt <sos_at_spider.deepcore.dk> > Subject: Re: ata problem with 13/10/2003 current > To: Matteo Riondato <rionda_at_gufi.org> > Cc: current_at_FreeBSD.ORG > Message-ID: <200310141309.h9ED9wxc001775_at_spider.deepcore.dk> > Content-Type: text/plain; charset=ISO-8859-1 > > It seems Matteo Riondato wrote: > > After having update my -CURRENT box to yesterday afternoon (Central > > Europe Time) sources, I can't get it to boot. It stops probing ata1: > > GEOM: create disk ad0 dp=0xc4536a70 > > ad0: 57259MB <MAXTOR 6L060J3> [116336/16/63] at ata0-master UDMA133 > > GEOM: create disk ad1 dp=0xc4915a70 > > ad1: 38172MB <QUANTUM FIREBALLP AS40.0> [77557/16/63] at ata0-slave \ > > UDMA100 > > ata1: resetting devices .. > > acd0: FAILURE - SETFEATURES status=51 <READY,DSC,ERROR> error=4<ABORTED> > > done > > acd0: FAILURE - SETFEATURES device lockup-removed > > > > And it stops here. > > > > On ata1 there are a Liteon CD-ReWriter 48x12x48x (acd0) > > and a LG DVD-ROM Drive DRD-8160B (acd1) > > > > I never had problem with ATAng before, so it is probably related to a > > recent commit. > > Could you try this patch please: > > Index: ata-queue.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v > retrieving revision 1.8 > diff -u -r1.8 ata-queue.c > --- ata-queue.c 12 Oct 2003 12:38:03 -0000 1.8 > +++ ata-queue.c 13 Oct 2003 13:05:01 -0000 > _at__at_ -315,20 +315,21 _at__at_ > static void > ata_timeout(struct ata_request *request) > { > + struct ata_channel *ch = request->device->channel; > + int quiet = request->flags & ATA_R_QUIET; > + > /* clear timeout etc */ > request->timeout_handle.callout = NULL; > -#if 0 > - /* call interrupt to try finish up the command */ > - request->device->channel->hw.interrupt(request->device->channel); > > - if (request->device->channel->running == NULL) { > - if (!(request->flags & ATA_R_QUIET)) > + /* call hw.interrupt to try finish up the command */ > + ch->hw.interrupt(request->device->channel); > + if (ch->running != request) { > + if (!quiet) > ata_prtdev(request->device, > "WARNING - %s recovered from missing interrupt\n", > ata_cmd2str(request)); > return; > } > -#endif > > /* if this was a DMA request stop the engine to be on the safe side */ > if (request->flags & ATA_R_DMA) { > -Søren > > ------------------------------ > > Message: 29 > Date: Tue, 14 Oct 2003 15:20:41 +0200 > From: Max Laier <max_at_love2party.net> > Subject: Re: [ALTQ/FreeBSD] Re: if_tun not altq enabled in pfaltq > patch? > To: Michael Nottebrock <michaelnottebrock_at_gmx.net> > Cc: freebsd-altq_at_rofug.ro > Message-ID: <406622109.20031014152041_at_love2party.net> > Content-Type: text/plain; charset=us-ascii > > Hello Michael, > > Tuesday, October 14, 2003, 2:03:51 PM, you wrote: > >> I see it's patched and contains altq-code, but trying to apply the > >> classic ack-prioritizing ruleset gives me "pfctl: tun0: driver does not > >> support altq". Is this expected? > > MN> Okay, it seems pf didn't like the fact that my if_tun was a module. > In-kernel MN> seems to work. > > Yes, that is a general problem: We'd have to extensively patch all if_* > > module Makefiles to propagate the new option. There is: > > +------------------------------------------------------------------------ > >+ > > > > | Issue | Status | Responsible | Description > > | | > > | ---------------------+-----------+-----------------+------------------- > > |-| > > | > > | | | | Kernel modules are > > | | | | | currently built > > | | | | | independently > > | | | | from | a kernel > > | | | | | > > | | | | configuration, and > > | | | | | independently > > | | | | from | one another, > > | | | | | resulting > > | | | | in | > > | | | | substantially > > | | | | | redundant > > | | | | | compilation of > > | | | | | objects, as > > | | | | well | as the > > | | | | inability | to > > | | | | easily manage | > > | | | | compile-time > > | | | | | options for > > | | | | kernel | objects > > | | | | (such as | MAC, > > | | | | PAE, etc) | > > | > > | Revised kld build | -- | -- | that may require > > | | infrastructure | | | conditional > > | | > > | > > | | | | compilation in the > > | | | | | kernel modules. > > | | | | In | order to > > | | | | improve | build > > | | | | performance | and > > | | | | better support | > > | | | | options of this > > | | | | | sort, the KLD > > | | | | | build > > | | | | | infrastructure > > | | | | | needs to be > > | | | | | revamped. > > | | | | Peter | Wemm has > > | | | | done some | initial > > | | | | | > > | | | | prototyping, and > > | | | | | should be > > | | | | | contacted before > > | | | | | starting on > > | | | | this | work. > > | | | | | > > | > > |---------------------+-----------+-----------------+-------------------- > > || > > this topic from the 5.2-Release TODO applies here! If you are planning > to investigate in that area, I could offer some starting points. I am > unsure how to do this "right" so I didn't start anything myself, but I > have some ideas ... > > If anybody is going to put his head into it, feel free to contact me for > support. > > -- > Best regards, > Max mailto:max_at_love2party.net > > > ------------------------------ > > Message: 30 > Date: Tue, 14 Oct 2003 15:45:34 +0200 > From: Matteo Riondato <rionda_at_gufi.org> > Subject: Re: ata problem with 13/10/2003 current > To: freebsd-current_at_freebsd.org > Message-ID: <1066139134.789.4.camel_at_kaiser.sig11.org> > Content-Type: text/plain; charset=iso-8859-1 > > Il Mar, 2003-10-14 alle 15:09, Soren Schmidt ha scritto: > > It seems Matteo Riondato wrote: > > > I never had problem with ATAng before, so it is probably related to a > > > recent commit. > > > > Could you try this patch please:I > > > > Index: ata-queue.c > > ======================================================= > > I cannot patch my system: > kaiser# cd /usr/src/sys/dev/ata/ > kaiser# patch < /home/rionda/ata-patch.patch > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > > |Index: ata-queue.c > |=================================================================== > |RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v > |retrieving revision 1.8 > |diff -u -r1.8 ata-queue.c > |--- ata-queue.c 12 Oct 2003 12:38:03 -0000 1.8 > |+++ ata-queue.c 13 Oct 2003 13:05:01 -0000 > > -------------------------- > Patching file ata-queue.c using Plan A... > Hunk #1 failed at 315. > 1 out of 1 hunks failed--saving rejects to ata-queue.c.rej > done > kaiser# > > > -Søren > > Regards > -- > Rionda aka Matteo Riondato > G.U.F.I Staff Member (http://www.gufi.org) > BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) > GPG key at: http://www.riondabsd.net/riondagpg.asc > Sent from: kaiser.sig11.org running FreeBSD-5.1-CURRENT > > ------------------------------ > > Message: 31 > Date: Tue, 14 Oct 2003 16:15:27 +0000 > From: "Rob MacGregor" <rob_macgregor_at_hotmail.com> > Subject: Re: ata problem with 13/10/2003 current > To: sos_at_spider.deepcore.dk > Cc: current_at_FreeBSD.ORG > Message-ID: <BAY1-F101EzbwJp8keT0000f8d7_at_hotmail.com> > Content-Type: text/plain; format=flowed > > From: Soren Schmidt <sos_at_spider.deepcore.dk> > > >Could you try this patch please: > > > >Index: ata-queue.c > >=================================================================== > >RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v > >retrieving revision 1.8 > >diff -u -r1.8 ata-queue.c > >--- ata-queue.c 12 Oct 2003 12:38:03 -0000 1.8 > >+++ ata-queue.c 13 Oct 2003 13:05:01 -0000 > > <---SNIP---> > > Happy to say that this patch fixes the "resetting devices..." problem I'd > encountered. > > Thanks. > > -- > Rob | What part of "no" was it you didn't understand? > > _________________________________________________________________ > Sign-up for a FREE BT Broadband connection today! > http://www.msn.co.uk/specials/btbroadband > > > ------------------------------ > > Message: 32 > Date: Tue, 14 Oct 2003 09:18:56 -0700 (PDT) > From: Doug White <dwhite_at_gumbysoft.com> > Subject: Re: sata stripe & dual boot > To: Putinas <pilkis_at_gmx.net> > Cc: freebsd-current_at_FreeBSD.ORG > Message-ID: <20031014091715.O7973_at_carver.gumbysoft.com> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Tue, 14 Oct 2003, Putinas wrote: > > Just a quick question, I have setup SATA stripe from two disks, and I > > have 3 partitions 4Gb each and the rest for data storing. If I boot in > > freebsd from cdrom, I see two empty disks ad4 and ad6 and I guess if I > > create something I will mess up with my raid setup. > > How did you set up the stripe? It sounds like your SATA RAID controller's > format is not currently supported. > > > Only one way what I could think off it would be to use atacontrol > > _before_ the installation to create exactly same stripe, and probably > > then I would see real filesystems on ar0. Or maybe there is any other > > way of easy ( or not ) doing this ? > > 1. Boot into sysinstall and drop into fixit mode with the CD. That gets > you atacontrol. Atacontrol away. > 2. Reboot and sysinstall should see your ar* devices. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite_at_gumbysoft.com | www.FreeBSD.org > > ------------------------------ > > Message: 33 > Date: Tue, 14 Oct 2003 18:30:05 +0200 > From: "Putinas" <pilkis_at_gmx.net> > Subject: Re: sata stripe & dual boot > To: <current_at_freebsd.org> > Message-ID: <00d301c39270$6d611fe0$0464a8c0_at_spotripoli.local> > Content-Type: text/plain; charset="iso-8859-1" > > Yes this what I tried , just a question shouldn't it be good idea to add > ability use atacontrol from sysinstall ? ( lets say if I have two normal > disks ad0 and ad2 and I want to use them in stripe configuration ? ) > without downloading fixit cd image that not possible, because on fixit > floppy there is no atacontrol... > > ----- Original Message ----- > From: "Doug White" <dwhite_at_gumbysoft.com> > To: "Putinas" <pilkis_at_gmx.net> > Cc: <freebsd-current_at_FreeBSD.ORG> > Sent: Tuesday, October 14, 2003 18:18 PM > Subject: Re: sata stripe & dual boot > > > On Tue, 14 Oct 2003, Putinas wrote: > > > Just a quick question, I have setup SATA stripe from two disks, and I > > > have 3 partitions 4Gb each and the rest for data storing. If I boot in > > > freebsd from cdrom, I see two empty disks ad4 and ad6 and I guess if I > > > create something I will mess up with my raid setup. > > > > How did you set up the stripe? It sounds like your SATA RAID > > controller's format is not currently supported. > > > > > Only one way what I could think off it would be to use atacontrol > > > _before_ the installation to create exactly same stripe, and probably > > > then I would see real filesystems on ar0. Or maybe there is any other > > > way of easy ( or not ) doing this ? > > > > 1. Boot into sysinstall and drop into fixit mode with the CD. That gets > > you atacontrol. Atacontrol away. > > 2. Reboot and sysinstall should see your ar* devices. > > > > -- > > Doug White | FreeBSD: The Power to Serve > > dwhite_at_gumbysoft.com | www.FreeBSD.org > > _______________________________________________ > > freebsd-current_at_freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe_at_freebsd.org" > > ------------------------------ > > Message: 34 > Date: Tue, 14 Oct 2003 18:46:44 +0200 > From: Balazs Nagy <js_at_iksz.hu> > Subject: sata + vinum + Asus p4p800 = :( > To: freebsd-current_at_freebsd.org > Message-ID: <FE82BBB2-FE65-11D7-9020-000A956884B8_at_iksz.hu> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi, > > I had a -CURRENT setting with an Abit BE7-S and two SATA disks with > vinum configuration. It worked very well until a power failure, and > the mainboard died. Yesterday I got a replacement mainboard, the only > type met the requirements (eg. two SATA ports) in the store: an Asus > P4P800. > > My only problem is with the disks. I can use all USB ports (8; what a > server could do with eight USB ports?), the 3C940 Gigabit Ethernet port > (I disabled the sound subsystem), and everything works until the first > fsck, when the kernel paniced. Here is the dmesg: > > GEOM: create disk ad0 dp=0xc6b4bb70 > ad0: 4028MB <Maxtor 90422D2> [8184/16/63] at ata0-master UDMA33 > acd0: CDROM <GCR-8523B> at ata0-slave PIO4 > GEOM: create disk ad4 dp=0xc6b4b070 > ad4: 117246MB <Maxtor 6Y120M0> [238216/16/63] at ata2-master UDMA133 > GEOM: create disk ad6 dp=0xc6b4b170 > ad6: 117246MB <Maxtor 6Y120M0> [238216/16/63] at ata3-master UDMA133 > Mounting root from ufs:/dev/vinum/root > panic: ata_dmasetup: transfer active on this device! > > I did further investigation: I booted from ata0-master, and mounted > /dev/vinum/root as /mnt. A simple fsck -f -B /mnt killed the system. > I did the same with /dev/ad4s1a (this is the boot hack partition from > the handbook), then I switched off softupdates. No win. I tried to > boot with safe mode either, but it hung with page fault. > > What can I do? Besides, why my SATA interfaces are recognized as > UDMA133? > -- > jul > > > ------------------------------ > > Message: 35 > Date: Tue, 14 Oct 2003 17:56:20 +0100 (BST) > From: Richard Tobin <richard_at_cogsci.ed.ac.uk> > Subject: Re: GEOM Gate. > To: freebsd-hackers_at_freebsd.org > Cc: freebsd-current_at_freebsd.org > Message-ID: <200310141656.RAA28657_at_rhymer.cogsci.ed.ac.uk> > > > Ok, GEOM Gate is ready for testing. > > For those who don't know what it is, they can read README: > > Aaargh! It's the return of nd(4) from SunOS. > > (Sorry about that.) > > -- Richard > > ------------------------------ > > Message: 36 > Date: Tue, 14 Oct 2003 09:56:47 -0700 > From: Terry Lambert <tlambert2_at_mindspring.com> > Subject: Re: What's up with the IP stack? > To: Kevin Oberman <oberman_at_es.net> > Cc: Sam Leffler <sam_at_errno.com> > Message-ID: <3F8C2ACF.7AB166B_at_mindspring.com> > Content-Type: text/plain; charset=us-ascii > > Kevin Oberman wrote: > > When I see this I can reach some LAN hosts, but not others. I can > > always seem to reach the access point. I can usually, but not always, > > reach most other systems on the LAN, but not the gateway router, a > > Sonic Wall firewall. I have logged onto another system and then > > connected to the firewall, so it looks like the physical path is OK. > > > > The problem is intermittent and I have only scattered data. I've been > > seeing it sice about the beginning of October. I was blaming it on > > hardware, but now that I see these reports, maybe it's not. (I just > > replaced my Apple Airport AP with a D-Link, so there is something to > > suspect.) > > > > In may case things just start working again. The pause can vary from a > > few seconds to about 10 minutes. netstat -rnf inet and arp -a output > > both look to be fine. > > What about your IP address and default route? > > I've seen wireless cards, especially IBM ones, fail to get good > signal, leaving you with a link.local address, or a valid address, > but no default route. This may be your problem here. > > You might want to "just put the AirPort back"... > > -- Terry > > ------------------------------ > > Message: 37 > Date: Tue, 14 Oct 2003 19:08:02 +0200 > From: Matteo Riondato <rionda_at_gufi.org> > Subject: Re: ata problem with 13/10/2003 current > To: freebsd-current_at_freebsd.org > Cc: sos_at_spider.deepcore.dk > Message-ID: <1066151282.781.1.camel_at_kaiser.sig11.org> > Content-Type: text/plain > > Il Mar, 2003-10-14 alle 15:09, Soren Schmidt ha scritto: > > It seems Matteo Riondato wrote: > > > After having update my -CURRENT box to yesterday afternoon (Central > > > Europe Time) sources, I can't get it to boot. It stops probing ata1: > > > GEOM: create disk ad0 dp=0xc4536a70 > > > > > > I never had problem with ATAng before, so it is probably related to a > > > recent commit. > > > > Could you try this patch please: > > > > Index: ata-queue.c > > ========================================= > > It works perfectly and solves my problem. > Thanks. > Do you plan to commit it? > Best Regards > > -- > Rionda aka Matteo Riondato > G.U.F.I Staff Member (http://www.gufi.org) > BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) > GPG key at: http://www.riondabsd.net/riondagpg.asc > Sent from: kaiser.sig11.org running FreeBSD-5.1-CURRENT > > ------------------------------ > > Message: 38 > Date: Tue, 14 Oct 2003 10:10:52 -0700 > From: "Kevin Oberman" <oberman_at_es.net> > Subject: Re: What's up with the IP stack? > To: Terry Lambert <tlambert2_at_mindspring.com> > Cc: Sam Leffler <sam_at_errno.com> > Message-ID: <20031014171052.799C55D07_at_ptavv.es.net> > > > Date: Tue, 14 Oct 2003 09:56:47 -0700 > > From: Terry Lambert <tlambert2_at_mindspring.com> > > > > Kevin Oberman wrote: > > > When I see this I can reach some LAN hosts, but not others. I can > > > always seem to reach the access point. I can usually, but not always, > > > reach most other systems on the LAN, but not the gateway router, a > > > Sonic Wall firewall. I have logged onto another system and then > > > connected to the firewall, so it looks like the physical path is OK. > > > > > > The problem is intermittent and I have only scattered data. I've been > > > seeing it sice about the beginning of October. I was blaming it on > > > hardware, but now that I see these reports, maybe it's not. (I just > > > replaced my Apple Airport AP with a D-Link, so there is something to > > > suspect.) > > > > > > In may case things just start working again. The pause can vary from a > > > few seconds to about 10 minutes. netstat -rnf inet and arp -a output > > > both look to be fine. > > > > What about your IP address and default route? > > > > I've seen wireless cards, especially IBM ones, fail to get good > > signal, leaving you with a link.local address, or a valid address, > > but no default route. This may be your problem here. > > > > You might want to "just put the AirPort back"... > > The problem is that the Airport died. Looks like a power supply issue > or a bad cap as it fails whenever it's moving lots of data and then > recovers after several quite seconds. My wife's laptop link dies at > the same time, so that's why I bought the Linksys. (Sorry for saying > D-Link. I get them confused too often.) > > No. I am monitoring signal strength and it is excellent. I use a > static address and gateway and they're fine, too. Both 'arp -a' and > 'netstat -rnf inet' show what I would expect including the proper MAC > address for the firewall and the hub. > > I've been using this card for about a year and a half and this problem > has just shown up in the past few weeks.Received on Tue Oct 14 2003 - 12:01:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:25 UTC