Re: ZFS PANIC: HELP.
Yes, I believe so. On Thu, Feb 24, 2022 at 7:42 AM Larry Rosenman wrote: > On 02/24/2022 10:36 am, Rob Wing wrote: > > You might try setting `sysctl vfs.zfs.recover=1` and `sysctl > vfs.zfs.spa.load_verify_metadata=0`. > > I had a similar error the other day (couple months ago). The best I did > was being able to import the pool read only. I ended up restoring from > backup. > > > > Are those tunables that I can set in loader.conf? > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: l...@lerctr.org > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 >
Re: ZFS PANIC: HELP.
You might try setting `sysctl vfs.zfs.recover=1` and `sysctl vfs.zfs.spa.load_verify_metadata=0`. I had a similar error the other day (couple months ago). The best I did was being able to import the pool read only. I ended up restoring from backup. On Thu, Feb 24, 2022 at 7:30 AM Alexander Motin wrote: > On 24.02.2022 10:57, Larry Rosenman wrote: > > On 02/23/2022 9:27 pm, Larry Rosenman wrote: > >> It crashes just after root mount (this is the boot pool and only pool > >> on the system), > >> seeL > >> https://www.lerctr.org/~ler/14-BOOT-Crash.png > > > > Where do I go from here? > > I see 2 ways: 1) Since it is only an assertion and 13 is working (so > far), you may just build 14 kernel without INVARIANTS option and later > recreate the pool when you have time. 2) You may treat it as metadata > corruption: import pool read-only and evacuate the data. If you have > recent enough snapshots you may be able to easily replicate the pool > with all the settings to some other disk. ZIL is not replicated, so > corruptions there should not be a problem. If there are no snapshots, > then either copy on file level, or you may be able to create snapshot > for replication in 13 (on 14 without INVARIANTS), importing pool > read-write. > > -- > Alexander Motin > >
Re: New panic in main-n253273-a52d8d4a6c6:
Hey Mike, Should be fixed in commit 0a2f498234023008d9a3b13ad7fc8fd81d384bab <https://cgit.freebsd.org/src/commit/?id=0a2f498234023008d9a3b13ad7fc8fd81d384bab> Thanks for the report -Rob On Mon, Feb 21, 2022 at 7:48 PM Rob Wing wrote: > Think that's it...thanks for testing for the patch. > > I opened up https://reviews.freebsd.org/D34335 for review. > > -Rob > > On Mon, Feb 21, 2022 at 6:05 PM Michael Jung < > mi...@paymentallianceintl.com> wrote: > >> Rob: >> >> >> >> I did not remove Hans earlier patch, but your “latest” patch applied and >> compiled with no errors. >> >> >> >> I can now watch and control a TTY (v0) or a SSH session (pts/1) without >> crashing. >> >> >> >> Anything else you would like me to try? >> >> >> >> --mikej >> >> >> >> >> >> *From:* Rob Wing [mailto:rob.fx...@gmail.com] >> *Sent:* Monday, February 21, 2022 9:30 PM >> *To:* Michael Jung >> *Cc:* Hans Petter Selasky ; freebsd-current < >> freebsd-current@freebsd.org> >> *Subject:* Re: New panic in main-n253273-a52d8d4a6c6: >> >> >> >> The previous attached patch should work for testing purposes, but it's >> incorrect if an error occurs. >> >> >> >> The fhold() should be below FILEDESC_SUNLOCK(), this patch addresses that. >> >> >> >> On Mon, Feb 21, 2022 at 5:18 PM Rob Wing wrote: >> >> try the attached patch >> >> >> >> On Mon, Feb 21, 2022 at 5:14 PM Michael Jung < >> mi...@paymentallianceintl.com> wrote: >> >> >> >> >> >> >> >> CONFIDENTIALITY NOTE: This message is intended only for the use >> of the individual or entity to whom it is addressed and may >> contain information that is privileged, confidential, and >> exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby >> notified that any dissemination, distribution or copying >> of this communication is strictly prohibited. If you have >> received this transmission in error, please notify us by >> telephone at (502) 212-4000 or notify us at: PAI, Dept. 99, >> 2101 High Wickham Place, Suite 101, Louisville, KY 40245 >> >> >> *From:* Michael Jung >> *Sent:* Monday, February 21, 2022 9:06 PM >> *To:* 'Hans Petter Selasky' ; freebsd-current < >> freebsd-current@freebsd.org> >> *Subject:* RE: New panic in main-n253273-a52d8d4a6c6: >> >> >> >> *From:* Hans Petter Selasky [mailto:h...@selasky.org ] >> *Sent:* Monday, February 21, 2022 8:34 PM >> *To:* Michael Jung ; freebsd-current < >> freebsd-current@freebsd.org> >> *Subject:* Re: New panic in main-n253273-a52d8d4a6c6: >> >> >> >> On 2/22/22 00:42, Michael Jung wrote: >> > Hi: >> > >> > I was trying to remember what I did that was odd when this crash >> occurred then it >> > hit me. You can repeat this panic by doing: >> > >> > # watch -I -W pts/0 >> > >> > Here is another panic that happened write after issuing "watch" for >> comparison. >> > >> > http://mail.mikej.com/core.txt.1 >> > >> > http://mail.mikej.com/info.1 >> > >> > http://mail.mikej.com/vmcore.1 >> > >> >> I also need your kernel and debug kernel to fully debug this. >> >> 1) Do ssh to machine. >> 2) watch -i -W pts/0 (does not panic over here) >> >> Can you explain what step 1 is? An scp ? >> >> Refcount is -1. >> f_count = 0x >> >> f_data = 0xf800158b0400 >> >> In your KGDB, can you enter: >> >> info 0x81b052d0 >> >> Does the attached patch make any difference? >> >> --HPS >> >> >> >> >> >> So sorry, yes step one, ssh to machine…. >> >> >> >> Even open a second console on the computer, no SSH and do “watch –I -W >> v0” it panics. >> >> >> >> Example of “watch –I –W v0” for comparison – kernel/kernel.full have not >> changed since .2 >> >> >> >> http://mail.mikej.com/core.txt.3 >> >> >> >> http://mail.mikej.com/info.3 >> >> >> >> http://mail.mikej.com/vmcore.3 >> >> >> >> >> >> >> >> >> >> *Disclaimer* >> >> The information contained in this communication from the send
Re: New panic in main-n253273-a52d8d4a6c6:
Think that's it...thanks for testing for the patch. I opened up https://reviews.freebsd.org/D34335 for review. -Rob On Mon, Feb 21, 2022 at 6:05 PM Michael Jung wrote: > Rob: > > > > I did not remove Hans earlier patch, but your “latest” patch applied and > compiled with no errors. > > > > I can now watch and control a TTY (v0) or a SSH session (pts/1) without > crashing. > > > > Anything else you would like me to try? > > > > --mikej > > > > > > *From:* Rob Wing [mailto:rob.fx...@gmail.com] > *Sent:* Monday, February 21, 2022 9:30 PM > *To:* Michael Jung > *Cc:* Hans Petter Selasky ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* Re: New panic in main-n253273-a52d8d4a6c6: > > > > The previous attached patch should work for testing purposes, but it's > incorrect if an error occurs. > > > > The fhold() should be below FILEDESC_SUNLOCK(), this patch addresses that. > > > > On Mon, Feb 21, 2022 at 5:18 PM Rob Wing wrote: > > try the attached patch > > > > On Mon, Feb 21, 2022 at 5:14 PM Michael Jung < > mi...@paymentallianceintl.com> wrote: > > > > > > > > CONFIDENTIALITY NOTE: This message is intended only for the use > of the individual or entity to whom it is addressed and may > contain information that is privileged, confidential, and > exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying > of this communication is strictly prohibited. If you have > received this transmission in error, please notify us by > telephone at (502) 212-4000 or notify us at: PAI, Dept. 99, > 2101 High Wickham Place, Suite 101, Louisville, KY 40245 > > > *From:* Michael Jung > *Sent:* Monday, February 21, 2022 9:06 PM > *To:* 'Hans Petter Selasky' ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* RE: New panic in main-n253273-a52d8d4a6c6: > > > > *From:* Hans Petter Selasky [mailto:h...@selasky.org ] > *Sent:* Monday, February 21, 2022 8:34 PM > *To:* Michael Jung ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* Re: New panic in main-n253273-a52d8d4a6c6: > > > > On 2/22/22 00:42, Michael Jung wrote: > > Hi: > > > > I was trying to remember what I did that was odd when this crash > occurred then it > > hit me. You can repeat this panic by doing: > > > > # watch -I -W pts/0 > > > > Here is another panic that happened write after issuing "watch" for > comparison. > > > > http://mail.mikej.com/core.txt.1 > > > > http://mail.mikej.com/info.1 > > > > http://mail.mikej.com/vmcore.1 > > > > I also need your kernel and debug kernel to fully debug this. > > 1) Do ssh to machine. > 2) watch -i -W pts/0 (does not panic over here) > > Can you explain what step 1 is? An scp ? > > Refcount is -1. > f_count = 0x > > f_data = 0xf800158b0400 > > In your KGDB, can you enter: > > info 0x81b052d0 > > Does the attached patch make any difference? > > --HPS > > > > > > So sorry, yes step one, ssh to machine…. > > > > Even open a second console on the computer, no SSH and do “watch –I -W > v0” it panics. > > > > Example of “watch –I –W v0” for comparison – kernel/kernel.full have not > changed since .2 > > > > http://mail.mikej.com/core.txt.3 > > > > http://mail.mikej.com/info.3 > > > > http://mail.mikej.com/vmcore.3 > > > > > > > > > > *Disclaimer* > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by Mimecast, a leader in email security and cyber > resilience. Mimecast integrates email defenses with brand protection, > security awareness training, web security, compliance and other essential > capabilities. Mimecast helps protect large and small organizations from > malicious activity, human error and technology failure; and to lead the > movement toward building a more resilient world. To find out more, visit > our website. > > > > *Disclaimer* > > The information contained in t
Re: New panic in main-n253273-a52d8d4a6c6:
The previous attached patch should work for testing purposes, but it's
incorrect if an error occurs.
The fhold() should be below FILEDESC_SUNLOCK(), this patch addresses that.
On Mon, Feb 21, 2022 at 5:18 PM Rob Wing wrote:
> try the attached patch
>
> On Mon, Feb 21, 2022 at 5:14 PM Michael Jung <
> mi...@paymentallianceintl.com> wrote:
>
>>
>>
>>
>>
>>
>> CONFIDENTIALITY NOTE: This message is intended only for the use
>> of the individual or entity to whom it is addressed and may
>> contain information that is privileged, confidential, and
>> exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby
>> notified that any dissemination, distribution or copying
>> of this communication is strictly prohibited. If you have
>> received this transmission in error, please notify us by
>> telephone at (502) 212-4000 or notify us at: PAI, Dept. 99,
>> 2101 High Wickham Place, Suite 101, Louisville, KY 40245
>>
>>
>>
>> *From:* Michael Jung
>> *Sent:* Monday, February 21, 2022 9:06 PM
>> *To:* 'Hans Petter Selasky' ; freebsd-current <
>> freebsd-current@freebsd.org>
>> *Subject:* RE: New panic in main-n253273-a52d8d4a6c6:
>>
>>
>>
>> *From:* Hans Petter Selasky [mailto:h...@selasky.org ]
>> *Sent:* Monday, February 21, 2022 8:34 PM
>> *To:* Michael Jung ; freebsd-current <
>> freebsd-current@freebsd.org>
>> *Subject:* Re: New panic in main-n253273-a52d8d4a6c6:
>>
>>
>>
>> On 2/22/22 00:42, Michael Jung wrote:
>> > Hi:
>> >
>> > I was trying to remember what I did that was odd when this crash
>> occurred then it
>> > hit me. You can repeat this panic by doing:
>> >
>> > # watch -I -W pts/0
>> >
>> > Here is another panic that happened write after issuing "watch" for
>> comparison.
>> >
>> > http://mail.mikej.com/core.txt.1
>> >
>> > http://mail.mikej.com/info.1
>> >
>> > http://mail.mikej.com/vmcore.1
>> >
>>
>> I also need your kernel and debug kernel to fully debug this.
>>
>> 1) Do ssh to machine.
>> 2) watch -i -W pts/0 (does not panic over here)
>>
>> Can you explain what step 1 is? An scp ?
>>
>> Refcount is -1.
>> f_count = 0x
>>
>> f_data = 0xf800158b0400
>>
>> In your KGDB, can you enter:
>>
>> info 0x81b052d0
>>
>> Does the attached patch make any difference?
>>
>> --HPS
>>
>>
>>
>>
>>
>> So sorry, yes step one, ssh to machine….
>>
>>
>>
>> Even open a second console on the computer, no SSH and do “watch –I -W
>> v0” it panics.
>>
>>
>>
>> Example of “watch –I –W v0” for comparison – kernel/kernel.full have not
>> changed since .2
>>
>>
>>
>> http://mail.mikej.com/core.txt.3
>>
>>
>>
>> http://mail.mikej.com/info.3
>>
>>
>>
>> http://mail.mikej.com/vmcore.3
>>
>>
>>
>>
>>
>>
>>
>>
>> *Disclaimer*
>>
>> The information contained in this communication from the sender is
>> confidential. It is intended solely for use by the recipient and others
>> authorized to receive it. If you are not the recipient, you are hereby
>> notified that any disclosure, copying, distribution or taking action in
>> relation of the contents of this information is strictly prohibited and may
>> be unlawful.
>>
>> This email has been scanned for viruses and malware, and may have been
>> automatically archived by Mimecast, a leader in email security and cyber
>> resilience. Mimecast integrates email defenses with brand protection,
>> security awareness training, web security, compliance and other essential
>> capabilities. Mimecast helps protect large and small organizations from
>> malicious activity, human error and technology failure; and to lead the
>> movement toward building a more resilient world. To find out more, visit
>> our website.
>>
>
diff --git a/sys/kern/tty.c b/sys/kern/tty.c
index ebb32f698e88..2c60a7e42580 100644
--- a/sys/kern/tty.c
+++ b/sys/kern/tty.c
@@ -2086,6 +2086,8 @@ ttyhook_register(struct tty **rtp, struct proc *p, int fd, struct ttyhook *th,
FILEDESC_SUNLOCK(fdp);
if (error != 0)
return (error);
+ if (!fhold(fp))
+ return (EBADF);
if (fp->f_ops == &badfileops) {
error = EBADF;
goto done1;
Re: New panic in main-n253273-a52d8d4a6c6:
try the attached patch On Mon, Feb 21, 2022 at 5:14 PM Michael Jung wrote: > > > > > > CONFIDENTIALITY NOTE: This message is intended only for the use > of the individual or entity to whom it is addressed and may > contain information that is privileged, confidential, and > exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying > of this communication is strictly prohibited. If you have > received this transmission in error, please notify us by > telephone at (502) 212-4000 or notify us at: PAI, Dept. 99, > 2101 High Wickham Place, Suite 101, Louisville, KY 40245 > > > > *From:* Michael Jung > *Sent:* Monday, February 21, 2022 9:06 PM > *To:* 'Hans Petter Selasky' ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* RE: New panic in main-n253273-a52d8d4a6c6: > > > > *From:* Hans Petter Selasky [mailto:h...@selasky.org ] > *Sent:* Monday, February 21, 2022 8:34 PM > *To:* Michael Jung ; freebsd-current < > freebsd-current@freebsd.org> > *Subject:* Re: New panic in main-n253273-a52d8d4a6c6: > > > > On 2/22/22 00:42, Michael Jung wrote: > > Hi: > > > > I was trying to remember what I did that was odd when this crash > occurred then it > > hit me. You can repeat this panic by doing: > > > > # watch -I -W pts/0 > > > > Here is another panic that happened write after issuing "watch" for > comparison. > > > > http://mail.mikej.com/core.txt.1 > > > > http://mail.mikej.com/info.1 > > > > http://mail.mikej.com/vmcore.1 > > > > I also need your kernel and debug kernel to fully debug this. > > 1) Do ssh to machine. > 2) watch -i -W pts/0 (does not panic over here) > > Can you explain what step 1 is? An scp ? > > Refcount is -1. > f_count = 0x > > f_data = 0xf800158b0400 > > In your KGDB, can you enter: > > info 0x81b052d0 > > Does the attached patch make any difference? > > --HPS > > > > > > So sorry, yes step one, ssh to machine…. > > > > Even open a second console on the computer, no SSH and do “watch –I -W > v0” it panics. > > > > Example of “watch –I –W v0” for comparison – kernel/kernel.full have not > changed since .2 > > > > http://mail.mikej.com/core.txt.3 > > > > http://mail.mikej.com/info.3 > > > > http://mail.mikej.com/vmcore.3 > > > > > > > > > *Disclaimer* > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by Mimecast, a leader in email security and cyber > resilience. Mimecast integrates email defenses with brand protection, > security awareness training, web security, compliance and other essential > capabilities. Mimecast helps protect large and small organizations from > malicious activity, human error and technology failure; and to lead the > movement toward building a more resilient world. To find out more, visit > our website. > diff --git a/sys/kern/tty.c b/sys/kern/tty.c index ebb32f698e88..e98b2d10b810 100644 --- a/sys/kern/tty.c +++ b/sys/kern/tty.c @@ -2083,6 +2083,8 @@ ttyhook_register(struct tty **rtp, struct proc *p, int fd, struct ttyhook *th, FILEDESC_SLOCK(fdp); error = fget_cap_locked(fdp, fd, cap_rights_init_one(&rights, CAP_TTYHOOK), &fp, NULL); + if (error == 0 && !fhold(fp)) + return (EBADF); FILEDESC_SUNLOCK(fdp); if (error != 0) return (error);
Re: New panic in main-n253273-a52d8d4a6c6:
kinda thinking this might be related to commit f40dd6c8034b ("tty: switch
ttyhook_register to use fget_cap_locked")
fget_unlocked() must have grabbed an extra reference count on the file
pointer that fget_cap_locked() doesn't get
On Mon, Feb 21, 2022 at 4:35 PM Hans Petter Selasky wrote:
> On 2/22/22 00:42, Michael Jung wrote:
> > Hi:
> >
> > I was trying to remember what I did that was odd when this crash
> occurred then it
> > hit me. You can repeat this panic by doing:
> >
> > # watch -I -W pts/0
> >
> > Here is another panic that happened write after issuing "watch" for
> comparison.
> >
> > http://mail.mikej.com/core.txt.1
> >
> > http://mail.mikej.com/info.1
> >
> > http://mail.mikej.com/vmcore.1
> >
>
> I also need your kernel and debug kernel to fully debug this.
>
> 1) Do ssh to machine.
> 2) watch -i -W pts/0 (does not panic over here)
>
> Can you explain what step 1 is? An scp ?
>
> Refcount is -1.
> f_count = 0x
>
> f_data = 0xf800158b0400
>
> In your KGDB, can you enter:
>
> info 0x81b052d0
>
> Does the attached patch make any difference?
>
> --HPS
Re: ThinkPad: reboots after successful shutdown -p
> Hi, > > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the > system would shut down and seemingly powered off, then it would restart > after about 5-10 seconds. > > Is this a known issue? Arguably this is not necessarily a FreeBSD > issue, but it seems that the Windows 10 installation doesn't have the > problem, so I guess there might be some difference between our and > Windows's shutdown sequence. Check to see if your ThinkPad has Wake On Lan set on. This is what happens to me when I forget to turn that off. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Cannot switch tty's after install xorg, gnome and gdm
On Sun, Jan 23, 2011 at 21:13, Warren Block wrote: > On Sun, 23 Jan 2011, Rob Farmer wrote: > >> On Sun, Jan 23, 2011 at 07:32, LOL wrote: >>> >>> Hi guys. >>> On every release of freebsd that i tried (-CURRENT, -STABLE, -RELEASE) >>> everything goes fine until I install xorg, gdm and gnome by packages >>> or not it does not make any difference. When I boot with >>> gnome_enable="YES" , and gdm start, when I try to change tty, on every >>> tty, its a black screen and my monitor tell me, power saving mode >>> enable until I switch back to gdm. I installed the xf86-video-ati >>> driver and I have an ati radeon HD 5770. >> >> The correct driver for recent ATI cards is xf86-video-radeonhd. And >> try the WITHOUT_NOUVEAU knob as David suggests. > > Actually, the radeon driver from xf86-video-ati is more solid and likely to > work reliably, even with newer cards. Features for 5000-series cards are > sparse, though. It appears that work on radeonhd has dropped off. > Sorry - I seem to have gotten confused between "radeon" (which comes from the ati package) and "radeonhd" which is separate - and just froze my system as I was figuring this out :). -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Cannot switch tty's after install xorg, gnome and gdm
On Sun, Jan 23, 2011 at 07:32, LOL wrote: > Hi guys. > On every release of freebsd that i tried (-CURRENT, -STABLE, -RELEASE) > everything goes fine until I install xorg, gdm and gnome by packages > or not it does not make any difference. When I boot with > gnome_enable="YES" , and gdm start, when I try to change tty, on every > tty, its a black screen and my monitor tell me, power saving mode > enable until I switch back to gdm. I installed the xf86-video-ati > driver and I have an ati radeon HD 5770. The correct driver for recent ATI cards is xf86-video-radeonhd. And try the WITHOUT_NOUVEAU knob as David suggests. ports or x11 are better lists for this - current is for things in the base system. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: RFC regarding usage of ISO 8601 throughout the tree
On Wed, Jan 5, 2011 at 05:21, Ulrich Spörlein wrote: > !ACHTUNG BIKESHED ALERT! > > Hello, > > With the recent changes to the committer graphs, I again was reminded > how much I hate the /MM/DD format (I can't help it ...). Given that > this almost looks like ISO 8601, but is an unreadable variant of it, I > would like to aggressively change this throughout the tree. > The current format is ISO 8601 compliant, because it allows omitting the hyphen for compactness in computer files that may be automatically processed. Also, adding the hyphen is a bit confusing, because many common (non-compliant) date systems use hyphens or slashes with the components in different orders. Omitting it is non-intuitive to everyone and thus least likely to cause confusion due to local assumptions in cases like 2001-01-02. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: TTY task group scheduling
On Thu, Nov 18, 2010 at 10:39, Chuck Swiger wrote: > Frankly, I'm also turned off by the attempt to popup a full page ad in > addition to the rest of the advertising content which surrounds what is > nominally supposed to be the real content. That doesn't mean there is > anything wrong with the patch or the notion of adjusting the scheduler, but I > don't see any value added from these phoronix.com links. Most stuff on Phoronix is of dubious value, and they have outright lied about stuff in the past, in order to drum up advertising business (such as Steam on Linux, which Value has consistently said isn't happening). -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 9-CURRENT: ports/net/kdenetwork3 does not compile
On Tue, Nov 2, 2010 at 11:38, David DEMELIER wrote: > A lot of ports will need some patches then, isn't it ? Most were taken care of back when it happened - many either included utmp.h and never used it or only used it trivially, so it was easy to fix (I submitted patches for some and I'm definitely not a great programmer). So the fact that it wasn't fixed either means nobody cares about that port (somewhat true here - most of the KDE people moved on to 4) or that the fix will be more involved (probably the case for this one). -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 9-CURRENT: ports/net/kdenetwork3 does not compile
On Mon, Nov 1, 2010 at 23:14, Matthias Apitz wrote: > Something wrong with 'struct utmp ubuf' in HEAD? It has been removed: http://lists.freebsd.org/pipermail/freebsd-current/2010-January/014893.html -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Small /etc/src.conf
On Sat, Oct 23, 2010 at 13:40, Sean Bruno wrote: > Anyone have a src.conf + make.conf that I can steal to build a small > installation of BSD? I've been trying to shrink the installation so I > can cram an ISO of BSD across the network into a remote installation > thing in an HP box. Have you checked this: http://phk.freebsd.dk/misc/build_options/ I'm not sure exactly what you're looking for, but in my experience (I care more about build time than size though, and still want a fairly functional system) these are the most important variables to set: NO_MODULES (stick everything in the kernel - tons of stuff is built twice, like ufs support) WITHOUT_PROFILE WITHOUT_LIB32 WITHOUT_CLANG WITHOUT_KERBEROS WITHOUT_CDDL Some of the options involving src/share like WITHOUT_LOCALES seem to kill a lot of files too. Everything else either just skips a couple files (of course, that can add up) or starts to cut into basic functionality (like no man pages), IMHO. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
"trying to mount root" message in single user mode
I just updated current from about a week ago to r214187. Now, when I boot, the kernel message has switched to: "Trying to mount root from ufs:/dev/ufs/root [rw]..." Problem is, it always prints [rw], even when booting single user, where [ro] is expected. The issue is only cosmetic - root is still mounted read only in single user, as before. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, Oct 17, 2010 at 16:18, Ralph Ellis wrote: > I am currently running the Nvidia 195 driver on amd64 9 - current from the > ports tree. It works without problems. > When I tried to compile the 256 driver, it would not compile and said that > it was not meant to work with 9 - current. Some necessary support was removed recently, but it has be re-added. See r213739. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is nvidia-driver 256.53 expected to work on -current?
On Sun, Oct 17, 2010 at 15:55, Doug Barton wrote: > Windows and linux (ubuntu, with the nvidia driver) work great on this same > hardware, so I'm pretty thoroughly convinced that the problem is with > freebsd/current somewhere. In addition to the -current partition I also > installed amd64 8.1-RELEASE so I'll give that a go next, but I wanted to ask > here first if anyone else was having problems on -current. I am running 256.53 on amd64 current (r213747). I don't use anything linux (the module isn't loaded) and built the driver with all options off except ACPI_PM. My custom kernel does not have "device agp". I use XFCE 4, don't really run anything graphically intense, and shutdown at night. I haven't had any problems, but IIRC from your past threads, the issues sort of build over time so I simply may not be aggravating the problem enough. The system is a HP Pavillion dv6405us laptop with a GeForce Go 6150. This is a pretty crappy card, even in Windows (the whole system was $500 3 years ago - it was one of those computers that supposedly was "Vista Ready" but could barely boot it), so I doubt I am gaining much over vesa though. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ZFS v28 and sendfile()
Seems to not work properly, at least as implemented in the nginx web server (specifically www/nginx-devel from ports). I have "sendfile on;" in my nginx.conf and files served from a ZFS filesystem are garbled in seemingly random ways (their md5 changes every time). Shutting it off resolves the problem. Using sendfile with a UFS partition on the same machine causes no problems. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: System reboots building mysql51-client with ZFS v28
On Thu, Sep 9, 2010 at 16:04, Xin LI wrote: > Note that on my kernel I have bumped FULLGRAPH_SBUF_SIZE to 131072 in > /sys/kern/subr_witness.c. I'm not sure if it's related but without that > I used get a few panics in the past. I have no idea what that does. Is it something you would recommend for general ZFS use on current? (I assume it only matters when WITNESS is enabled) -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: System reboots building mysql51-client with ZFS v28
On Thu, Sep 9, 2010 at 15:14, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, Rob, > > On 2010/09/09 15:01, Rob Farmer wrote: > [...] >>> Just a guess - are you compiling under X? If so what about if you >>> compile under text mode? >> >> Nope - this is a new install and X isn't running yet. It is installed, >> but not started yet. I ran across this building dependencies for KDE >> (why a desktop requires MySQL server is beyond me, but anyways). > > I just tried to compile MySQL 5.1 client but it passed on my test system > (the compile time option is slightly different as the VFS debugging is > not yet enabled). I'll do another round of test with these VFS options > enabled. Ok - so I shut the system down for about 15 minutes and then tried again and it worked. So maybe it was heat or something - I had reproduced it about 5 times back to back at the exact same spot. I didn't think this laptop had cooling problems but I will keep a closer eye on it in the future. Sorry about the noise. -- Rob Farmer > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.16 (FreeBSD) > > iQEcBAEBCAAGBQJMiVxTAAoJEATO+BI/yjfBrdwIALykmtHrgpaARlkBxAzzQFdu > +Ab0gvTBVrWMsyRHYqZgVhcD35ft80ItqYZOwH86/y1pqrvYTGXaexDMXDjwaG3/ > 9C7G73ZiKPWeEH7v0u1rInh8Ajz4+ZHjtpVRLBobk0Ef2F8pCU/0Yy3aLxa3z4Z4 > C2ej6oA/jznqnk+76Iu+RyURV7Nb460uRYK5hB6iSSGDsYvdUYCUp0fFPHe3w5N4 > aqhIZyGTo5MF/fgEmSXyWIHYvjiaj6IGSDILY0ju15HJajGmmkvSOo5wmxZWGGYH > jzskx5yUuv4ZAhZPCNeWPAgR2rWidgQ1k+95NZO7IvrXfMbUxh1oOe+fU31ukNc= > =jxCL > -END PGP SIGNATURE- > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: System reboots building mysql51-client with ZFS v28
On Thu, Sep 9, 2010 at 14:56, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 2010/09/09 14:51, Rob Farmer wrote: >> I am running a fairly recent current with the new ZFS patches: >> >> FreeBSD topaz.predatorlabs.net 9.0-CURRENT FreeBSD 9.0-CURRENT #0 >> r212312M: Wed Sep 8 02:03:34 PDT 2010 >> rfar...@topaz.predatorlabs.net:/usr/obj/usr/src/sys/TOPAZ amd64 >> >> When I try to build databases/mysql51-client from ports, the configure >> script runs for a while then prints: >> WARNING: Adding fix for interrupted reads >> >> Then the system reboots. The kernel doesn't panic or anything - the >> screen goes blank for about 5 seconds and the BIOS starts again. I >> have WITNESS and all the standard debugging stuff for current, plus >> the DUBUG_LOCKS and DEBUG_VFS_LOCKS options recommended in the ZFS >> patch posting. Hardware is a Lenovo Thinkpad T61 with a Core 2 Duo, >> 4GB of RAM, ahci is being used for the hard drive. There is a 1 GB ufs >> /boot, everything else is zfs (one drive, no mirroring, no snapshots, >> nothing complex). >> >> Port is up to date: >> # $FreeBSD: ports/databases/mysql51-client/Makefile,v 1.100 2010/08/25 >> 09:07:27 ale Exp $ >> >> Not sure if this is ZFS related or not. What can I do to collect some >> useful information here? This can be reproduced reliably. > > Just a guess - are you compiling under X? If so what about if you > compile under text mode? Nope - this is a new install and X isn't running yet. It is installed, but not started yet. I ran across this building dependencies for KDE (why a desktop requires MySQL server is beyond me, but anyways). -- Rob Farmer > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.16 (FreeBSD) > > iQEcBAEBCAAGBQJMiVf1AAoJEATO+BI/yjfB3pEH+wfej2GHUwBj3F4yPZjnUiTZ > B1X0FwzeWQWyRfl/FxF3X0LSH6s5Dc2y+QUd5e22yVfwUDV449+R53deCZesCtxm > IWabVgQKFJQF3rgdnC+fAy2kY5kaMGH/s/Ifq2GJcx8YnVLBPKQRcKHgHKAJ05l6 > 0G/Mr8YfGBXS7UvQJvSGqnfhLJjufBEe6dk/NTl2zguPAgWeo2z9e0xud9LYXBbH > RYGtFHzIxsvzTau4q8JVyvl6Uc5gNxvutNpOxwtWhX2lwbeqv2U+w1O9JjDCXP+e > 5zLH3hffk0wKysEXPVx+ltkFzjCUCuNYIYDuvBX3V8QsYE7s4PT/J3Rmc2gX6fE= > =mnSc > -END PGP SIGNATURE- > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
System reboots building mysql51-client with ZFS v28
I am running a fairly recent current with the new ZFS patches: FreeBSD topaz.predatorlabs.net 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r212312M: Wed Sep 8 02:03:34 PDT 2010 rfar...@topaz.predatorlabs.net:/usr/obj/usr/src/sys/TOPAZ amd64 When I try to build databases/mysql51-client from ports, the configure script runs for a while then prints: WARNING: Adding fix for interrupted reads Then the system reboots. The kernel doesn't panic or anything - the screen goes blank for about 5 seconds and the BIOS starts again. I have WITNESS and all the standard debugging stuff for current, plus the DUBUG_LOCKS and DEBUG_VFS_LOCKS options recommended in the ZFS patch posting. Hardware is a Lenovo Thinkpad T61 with a Core 2 Duo, 4GB of RAM, ahci is being used for the hard drive. There is a 1 GB ufs /boot, everything else is zfs (one drive, no mirroring, no snapshots, nothing complex). Port is up to date: # $FreeBSD: ports/databases/mysql51-client/Makefile,v 1.100 2010/08/25 09:07:27 ale Exp $ Not sure if this is ZFS related or not. What can I do to collect some useful information here? This can be reproduced reliably. Thanks, -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [head tinderbox] failure on amd64/amd64
On Wed, Sep 8, 2010 at 03:55, FreeBSD Tinderbox wrote: > TB --- 2010-09-08 10:15:01 - tinderbox 2.6 running on > freebsd-current.sentex.ca > TB --- 2010-09-08 10:15:01 - starting HEAD tinderbox run for amd64/amd64 > TB --- 2010-09-08 10:15:01 - cleaning the object tree > TB --- 2010-09-08 10:16:32 - cvsupping the source tree > TB --- 2010-09-08 10:16:32 - /usr/bin/csup -z -r 3 -g -L 1 -h > cvsup18.freebsd.org /tinderbox/HEAD/amd64/amd64/supfile > TB --- 2010-09-08 10:55:57 - WARNING: /usr/bin/csup returned exit code 1 > TB --- 2010-09-08 10:55:57 - ERROR: unable to cvsup the source tree > TB --- 2010-09-08 10:55:57 - 1.81 user 60.35 system 2456.66 real > > > http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > Is it possible to either have the tinderbox try multiple cvsup servers or just not send a message if cvsup fails? Counting all branches and all archs, there have been around 50 "ERROR: unable to cvsup the source tree" mails in the last week. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ports/150265: [patch] print/ghostscript8 disable bogus port conflicts in make release
On Sun, Sep 5, 2010 at 10:15, wrote: > > Rob, > > IMO the question is not if the problem _can_ be solved in the base build > system. I doubt you'll find many src committers willing to break other > peoples machines by using DISABLE_CONFLICTS as a general problem solver. > > It may well work for your machine and you're free to do that. > > The maintainer of ghostscript8 may check the issue but is free to close the > PR as WONTFIX (I suspect that will most likely happen). > > Instead of filing a PR for such problems, a discussion on our fine mailing > lists might be good. > > Thanks! > [adding a mailing list per your suggestion] I think you are misunderstanding the issue here. This is not a ghostscript issue and the maintainer of ghostscript isn't the right person to look at it. The same issue can appear with other ports used by make release, such as perl. In fact, there isn't any way for this to be solved in the ports tree short of removing the CONFLICTS handling (which is not what I am suggesting). What happens is the release building process uses certain ports to generate the HTML documentation (release notes, etc.) on the CDs. To insure a clean build environment, these ports are built and installed in a chroot away from the main system. However, prior to entering the chroot, the distfiles for these ports are fetched and checksummed with "make checksum-recursive". This process occurs outside the chroot, so the ports system looks for conflicts with what is installed in /usr/local, assuming that these distfiles are for ports to be installed in /usr/local. This assumption is flawed, since they will not be installed there and thus will not conflict. My patch runs the "make checksum-recursive" target with -DDISABLE_CONFLICTS to avoid these false positives. This will not "break other people's machines" as you state because the absolute worst case scenario with my patch is having a couple duplicate distfiles (such as perl5.10 and perl5.12). Nothing is built or installed with the DISABLE_CONFLICTS flag. What I'm asking you to do is revert the description, category, and assignment of the PR so that someone who is familiar with the release building process will see it. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS v28 is ready for wider testing.
On Thu, Sep 2, 2010 at 23:57, jhell wrote: > On 09/02/2010 04:55, Rob Farmer wrote: >> >> I tried applying the patch to r212087 to rule out recent changes to >> dtrace, but it made no difference. I used patch -E -p0 < patch. >> > > Hi Rob, > > I see that in your build error are a bunch of things to do with atomic.h > and I recalled a patch from pjd@ on current@ that he sent in the same > thread. I attached the downloaded patch. Maybe you can write back and > site if it helped at all so people have a reference. Yes, it worked. Since this is just a testing thing and pjd alredy knew about the problem and seemed confident about the solution I didn't bother to reply. -- Rob Farmer > > > Regards, > > -- > > jhell,v > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS v28 is ready for wider testing.
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek wrote: > > Ok, now that I know you read everything carefully, here is the patch: > > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 > buildworld on i386 (yes I know ZFS isn't ideal there): ===> cddl/lib/libdtrace (all) cc -O2 -fno-strict-aliasing -pipe -march=prescott -I/usr/obj/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/dev/dtrace/i386 -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/libdtrace/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libctf/common -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/intel -DDIS_MEM -DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-unknown-pragmas -c /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c In file included from /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/bitmap.h:36, from /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_impl.h:33, from /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c:33: /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:132: error: static declaration of 'atomic_cas_ptr' follows non-static declaration /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:42: error: previous declaration of 'atomic_cas_ptr' was here cc1: warnings being treated as errors /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h: In function 'atomic_cas_ptr': /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:133: warning: cast from pointer to integer of different size /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:134: warning: cast from pointer to integer of different size /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:134: warning: passing argument 1 of 'atomic_cas_32' from incompatible pointer type /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:134: warning: cast to pointer from integer of different size *** Error code 1 I tried applying the patch to r212087 to rule out recent changes to dtrace, but it made no difference. I used patch -E -p0 < patch. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Clock not moving in virtual machine
On Fri, Jul 16, 2010 at 2:05 PM, Bruce Cran wrote: > On Fri, Jul 16, 2010 at 11:47:23PM +0300, Alexander Motin wrote: >> >> It is probably hard to see pattern due to to very high clock frequency. >> But TSC timecounter is unreliable even on real SMP systems. What it >> counts on virtual SMP - even bigger question. As system seems never uses >> timecounters with negative quality - you've left with >> kern.timecounter.hardware=dummy - that's why time is not going. As last >> resort you may try to set sysctl kern.timecounter.hardware=TSC in run time. > > I came across the same problem on rootbsd a few days ago, and set the TSC > as the timecounter in /etc/sysctl.conf - I've since found it should be > possible to also set kern.timecounter.smp_tsc=1 in /boot/loader.conf to let > the TSC be chosen. The system's now been running for a day and I've not had > any warnings about the clock going backward, and since the time has > remained correct I guess Xen synchronises with the host? Should I still > switch back to using the i8254? > > -- > Bruce Cran > Setting kern.timecounter.smp_tsc=1 works for me. I put it in /boot/loader.conf so it would automatically work for single user mode too. I don't think the host automatically synchronizes the clock - their website recommends running ntp and I saw the clock drift a fair amount before I started doing that. Thanks for the tip. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Clock not moving in virtual machine
On Thu, Jul 15, 2010 at 11:33 PM, Alexander Motin wrote: > Rob Farmer wrote: >> I have a VPS from rootbsd.net which is running current, though I don't >> update it very often. I just built and installed a new world and >> kernel and now the clock will not move from the time the system was >> booted, ie: >> # date >> Thu Jul 15 16:15:58 PDT 2010 >> >> # date >> Thu Jul 15 16:15:58 PDT 2010 >> >> I have an old kernel from May 27 which doesn't have this problem. I >> noticed some clock related stuff changing in current in the last >> couple of weeks and suspect that their VM setup doesn't play well with >> these changes (their site says they use Xen, but several boot messages >> refer to QEMU). Officially, I think they only support running 8.0 so I >> thought I would ask here if anyone has any ideas before putting in a >> support request. >> >> Here's a diff of the dmesgs - I can post full copies if needed but >> didn't want to start with a ridicously long message: > >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> FreeBSD/SMP: 0 package(s) x 16 core(s) x 2 SMT threads >> cpu0 (BSP): APIC ID: 0 > > Probably not related, but funny. :) So you have two CPUs? Yes, there's 2 CPUs. It also gives the non uniform processors warning, but it has been like that forever. > >> @@ -81,7 +81,10 @@ >> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >> ppc0: [ITHREAD] >> ppbus0: on ppc0 >> -atrtc0: at port 0x70 irq 8 on isa0 >> +atrtc0: at port 0x70 irq 8 on isa0 >> +atrtc0: [FILTER] >> +Event timer "RTC" frequency 32768 Hz quality 0 >> +Starting kernel event timers: LAPIC @ 200Hz, RTC @ 128Hz >> Timecounters tick every 5.000 msec > > Everything seems reasonable there. Try to collect more information: > sysctl kern.timecounter > sysctl kern.eventtimer > vmstat -ia > systat -vm 1 (presence and frequencies of interrupts) > > It could be a bug in emulation of some timers or bug in respective timer > driver, which was not triggered before last changes. You may try switch > to different timecounter by setting kern.timecounter.hardware, or > different eventtimers by setting kern.eventtimer.timer1 and > kern.eventtimer.timer2 sysctls. > > -- > Alexander Motin > This is all on the new (not-working) kernel in single user mode: # sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) dummy(-100) kern.timecounter.hardware: dummy kern.timecounter.stepwarnings: 0 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 205772785 kern.timecounter.tc.TSC.frequency: 2261052646 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1 kern.timecounter.tc.TSC.counter changes everytime (205772785, 3200717147, 1205899870, ...) but I can't see any pattern. # sysctl kern.eventtimer kern.eventtimer.choice: LAPIC(500) RTC(0) kern.eventtimer.et.LAPIC.flags: 15 kern.eventtimer.et.LAPIC.frequency: 50001404 kern.eventtimer.et.LAPIC.quality: 500 kern.eventtimer.et.RTC.flags: 1 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.timer2: RTC kern.eventtimer.timer1: LAPIC kern.eventtimer.singlemul: 4 # vmstat -ia interrupt total rate ???0 0 irq1: atkbd0 339339 stray irq1 0 0 irq0: 0 0 stray irq0 0 0 irq3: 0 0 stray irq3 0 0 irq4: uart00 0 stray irq4 0 0 irq5: re0 0 0 stray irq5 0 0 irq6: 0 0 stray irq6 0 0 irq7: ppc0 0 0 stray irq7 0 0 irq8: atrtc0 24463 24463 stray irq8 0 0 irq9: 0 0 stray irq9 0 0 irq10: re1 0 0 stray irq100 0 irq11: 0 0 stray irq110 0 irq12: psm00 0 stray irq120 0 irq13: 0 0 stray irq130 0 irq14: ata0 224
Clock not moving in virtual machine
Hi, I have a VPS from rootbsd.net which is running current, though I don't update it very often. I just built and installed a new world and kernel and now the clock will not move from the time the system was booted, ie: # date Thu Jul 15 16:15:58 PDT 2010 # date Thu Jul 15 16:15:58 PDT 2010 I have an old kernel from May 27 which doesn't have this problem. I noticed some clock related stuff changing in current in the last couple of weeks and suspect that their VM setup doesn't play well with these changes (their site says they use Xen, but several boot messages refer to QEMU). Officially, I think they only support running 8.0 so I thought I would ask here if anyone has any ideas before putting in a support request. Here's a diff of the dmesgs - I can post full copies if needed but didn't want to start with a ridicously long message: --- dmesg.old 2010-07-15 17:45:20.0 -0700 +++ dmesg.new 2010-07-15 17:46:45.0 -0700 @@ -2,10 +2,9 @@ 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-CURRENT #0: Thu May 27 01:26:08 PDT 2010 +FreeBSD 9.0-CURRENT #0: Thu Jul 15 16:13:28 PDT 2010 rfar...@peridot.predatorlabs.net:/usr/obj/usr/src/sys/PERIDOT i386 -Timecounter "i8254" frequency 1193182 Hz quality 0 -CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (2261.02-MHz 686-class CPU) +CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (2261.59-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0x1781fbff Features2=0x80182201> @@ -13,9 +12,10 @@ AMD Features2=0x1 TSC: P-state invariant real memory = 268435456 (256 MB) -avail memory = 252473344 (240 MB) -ACPI Error: A valid RSDP was not found (20100428/tbxfroot-309) +avail memory = 252444672 (240 MB) +ACPI Error: A valid RSDP was not found (20100702/tbxfroot-309) MPTable: <_HVMCPU_ XEN > +Event timer "LAPIC" frequency 0 Hz quality 500 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 0 package(s) x 16 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 @@ -26,7 +26,7 @@ ioapic0: Assuming intbase of 0 ioapic0 irqs 0-47 on motherboard kbd1 at kbdmux0 -ACPI Error: A valid RSDP was not found (20100428/tbxfroot-309) +ACPI Error: A valid RSDP was not found (20100702/tbxfroot-309) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. pcib0: pcibus 0 on motherboard @@ -81,7 +81,10 @@ ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppc0: [ITHREAD] ppbus0: on ppc0 -atrtc0: at port 0x70 irq 8 on isa0 +atrtc0: at port 0x70 irq 8 on isa0 +atrtc0: [FILTER] +Event timer "RTC" frequency 32768 Hz quality 0 +Starting kernel event timers: LAPIC @ 200Hz, RTC @ 128Hz Timecounters tick every 5.000 msec ad0: 10240MB at ata0-master WDMA2 SMP: AP CPU #1 Launched! Thanks, -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make release broken
On Sun, May 23, 2010 at 11:02 PM, James R. Van Artsdalen wrote: > On 5/22/2010 8:25 PM, Rob Farmer wrote: >> make release is still broken on amd64 as of svn 208373 (2010-05-21 >>> 04:52:49 -0500) >>> >>> That patch seems unrelated? >>> >> What needs done is >> /src/release/$ARCH/boot_crunch.conf files need the relevant libraries >> added to the libs section. I haven't tested it, but I think adding >> -llzma there will fix the problems. > > That works for me, except that I had to add -lcrypto too? I don't know > if that's a good idea. Yeah, I found that out too when I tested it. I've submitted a PR with patches for all the archs: http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/146904 -- Rob Farmer > > Index: release/amd64/boot_crunch.conf > === > --- release/amd64/boot_crunch.conf (revision 208373) > +++ release/amd64/boot_crunch.conf (working copy) > @@ -41,4 +41,4 @@ > > libs -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph > libs -ldialog -lncurses -ldisk -lcam -lsbuf -lufs -ldevinfo > -libs -lbsdxml -larchive -lbz2 -lusb -ljail > +libs -lbsdxml -larchive -lbz2 -lusb -ljail -llzma -lcrypto > > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make release broken
On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen wrote: > On 5/18/2010 2:34 AM, jhell wrote: >> On Mon, May 17, 2010 at 10:35 PM, Rob Farmer >> wrote: >>>> make release is broken on current. Seems to be related to the lzma >>>> import. This is on i386: >>>> >>>> cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo >>>> test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo >>>> newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo >>>> sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd >>>> -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf >>>> -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail >>>> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): >>>> In function `archive_compressor_xz_init': >>>> : undefined reference to `lzma_lzma_preset' >>>> ... >> >> This URL looks to be the problem you are seeing above. >> >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=20426+0+current/freebsd-current >> > > make release is still broken on amd64 as of svn 208373 (2010-05-21 > 04:52:49 -0500) > > That patch seems unrelated? > That patch is unrelated - it is for building current on RELENG_7 or something like that. What needs done is /src/release/$ARCH/boot_crunch.conf files need the relevant libraries added to the libs section. I haven't tested it, but I think adding -llzma there will fix the problems. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
make release broken
Hi, make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): In function `archive_compressor_xz_init': : undefined reference to `lzma_lzma_preset' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x263): In function `archive_compressor_xz_init': : undefined reference to `lzma_alone_encoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x2c9): In function `archive_compressor_xz_init': : undefined reference to `lzma_stream_encoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x3ba): In function `drive_compressor': : undefined reference to `lzma_code' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x418): In function `drive_compressor': : undefined reference to `lzma_memusage' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x640): In function `archive_compressor_xz_finish': : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x9e8): In function `archive_write_mtree_finish_entry': : undefined reference to `SHA1_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa2e): In function `archive_write_mtree_finish_entry': : undefined reference to `RIPEMD160_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa78): In function `archive_write_mtree_finish_entry': : undefined reference to `MD5_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe43): In function `archive_write_mtree_data': : undefined reference to `SHA1_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe63): In function `archive_write_mtree_data': : undefined reference to `MD5_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe8b): In function `archive_write_mtree_data': : undefined reference to `RIPEMD160_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1297): In function `archive_write_mtree_header': : undefined reference to `SHA1_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12c7): In function `archive_write_mtree_header': : undefined reference to `RIPEMD160_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12f4): In function `archive_write_mtree_header': : undefined reference to `MD5_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x152): In function `xz_lzma_bidder_init': : undefined reference to `lzma_alone_decoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x18c): In function `xz_lzma_bidder_init': : undefined reference to `lzma_stream_decoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x2b1): In function `xz_filter_close': : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567): In function `xz_filter_read': : undefined reference to `lzma_code' *** Error code 1 Stop in /usr/obj/usr/src/release/boot_crunch. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: unzip in basesystem.
On Wed, May 5, 2010 at 2:30 AM, David DEMELIER wrote:
> 2010/5/5 David DEMELIER :
>> Hi,
>>
>> I noticed that unzip came into basesystem in src/usr.bin/unzip/. To
>> prevent port installing the ports/archivers/unzip one, I propose to
>> add this in bsd.port.mk
Unfortunately there are some problems with the base system unzip that
make it preferable to use the port. From the commit log for
bsd.port.mk:
9-CURRENT introduced unzip command to the base system. Unfortunately it is
not fully compatible with the archivers/unzip implementation and non-trivial
amount of ports fail to build when using it. Thus we will keep using
archivers/unzip for unzipping source in Ports Collection until someone
volunteer to fix all individual ports. Two most common problems with base
unzip are:
* extracting files without +x flag (some ports rely to execute unzipped
configure scripts, for example)
* different semantics of CR/LF conversion
Error logs of failed port builds with in-base unzip can be made available on
request to port...@.
With hat: portmgr
--
Rob Farmer
>>
>> .if defined(USE_ZIP) && !exists(/usr/bin/unzip)
>> EXTRACT_DEPENDS+= ${LOCALBASE}/bin/unzip:${PORTSDIR}/archivers/unzip
>> .endif
>>
>> Is that right ?
>>
>
> Sorry I gone too fast, I would add this in bsd.commands.mk too :
>
> .if exists(/usr/bin/unzip)
> UNZIP_CMD=/usr/bin/unzip
> .else
> UNZIP_CMD?= ${LOCALBASE}/bin/unzip
> .endif
>
> --
> Demelier David
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PF not working, with lock order reversal
On Wed, Mar 10, 2010 at 8:43 AM, Rob Farmer wrote: > Hi, > > I just updated a sparc64 Sun Netra X1 running current. I am using PF > (built into the kernel) and now I cannot connect to the machine while > PF is enabled (but outbound traffic from the machine works). The same > ruleset has worked fine for me for several years on this and other > systems. I'm getting the following LOR at boot and wonder if it is > related? > > lock order reversal: > 1st 0xc0424d28 pf task mtx (pf task mtx) @ > /usr/src/sys/contrib/pf/net/pf.c:6929 > 2nd 0xf800011954f8 radix node head (radix node head) @ > /usr/src/sys/net/route.c:360 > KDB: stack backtrace: > _witness_debugger() at _witness_debugger+0x84 > witness_checkorder() at witness_checkorder+0xafc > _rw_rlock() at _rw_rlock+0x44 > rtalloc1_fib() at rtalloc1_fib+0x124 > rtalloc_ign_fib() at rtalloc_ign_fib+0xac > pf_calc_mss() at pf_calc_mss+0xbc > pf_test_tcp() at pf_test_tcp+0xf04 > pf_test() at pf_test+0x10e8 > pf_check_in() at pf_check_in+0x14 > pfil_run_hooks() at pfil_run_hooks+0xb8 > ip_input() at ip_input+0x488 > netisr_dispatch_src() at netisr_dispatch_src+0xf0 > ether_demux() at ether_demux+0x2ac > ether_input() at ether_input+0x24c > dc_rxeof() at dc_rxeof+0x350 > dc_intr() at dc_intr+0x310 > intr_event_execute_handlers() at intr_event_execute_handlers+0xc4 > ithread_loop() at ithread_loop+0xe4 > fork_exit() at fork_exit+0x6c > fork_trampoline() at fork_trampoline+0x8 > > My pf.conf: > http://www.predatorlabs.net/dl/pf.conf > My kernel config: > http://www.predatorlabs.net/dl/NETRA > > Thanks, > -- > Rob Farmer > To follow up on this issue: I tried using the route.h patch Qing Li posted in another thread and I can access the system now with PF running. I still get the LOR but otherwise everything is working normally. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
PF not working, with lock order reversal
Hi, I just updated a sparc64 Sun Netra X1 running current. I am using PF (built into the kernel) and now I cannot connect to the machine while PF is enabled (but outbound traffic from the machine works). The same ruleset has worked fine for me for several years on this and other systems. I'm getting the following LOR at boot and wonder if it is related? lock order reversal: 1st 0xc0424d28 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:6929 2nd 0xf800011954f8 radix node head (radix node head) @ /usr/src/sys/net/route.c:360 KDB: stack backtrace: _witness_debugger() at _witness_debugger+0x84 witness_checkorder() at witness_checkorder+0xafc _rw_rlock() at _rw_rlock+0x44 rtalloc1_fib() at rtalloc1_fib+0x124 rtalloc_ign_fib() at rtalloc_ign_fib+0xac pf_calc_mss() at pf_calc_mss+0xbc pf_test_tcp() at pf_test_tcp+0xf04 pf_test() at pf_test+0x10e8 pf_check_in() at pf_check_in+0x14 pfil_run_hooks() at pfil_run_hooks+0xb8 ip_input() at ip_input+0x488 netisr_dispatch_src() at netisr_dispatch_src+0xf0 ether_demux() at ether_demux+0x2ac ether_input() at ether_input+0x24c dc_rxeof() at dc_rxeof+0x350 dc_intr() at dc_intr+0x310 intr_event_execute_handlers() at intr_event_execute_handlers+0xc4 ithread_loop() at ithread_loop+0xe4 fork_exit() at fork_exit+0x6c fork_trampoline() at fork_trampoline+0x8 My pf.conf: http://www.predatorlabs.net/dl/pf.conf My kernel config: http://www.predatorlabs.net/dl/NETRA Thanks, -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Buildworld Failure
Thomas T. Veldhouse wrote: cc -elf -ffreestanding -Os -fno-builtin -fno-guess-branch-probability -fomi t-frame-pointer -mno-align-long-strings -mrtd -DUFS1_AND_UFS2 -I/usr/src/ sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-de clarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow - Wstrict-prototypes -Wwrite-strings -ffreestanding -mpreferred-stack-boundary =2 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c /usr/src/sys/boot/i386/boot2/boot2.c: In function `load': /usr/src/sys/boot/i386/boot2/boot2.c:362: error: `RB_BOOTINFO' undeclared (first use in this function) /usr/src/sys/boot/i386/boot2/boot2.c:362: error: (Each undeclared identifier is reported only once /usr/src/sys/boot/i386/boot2/boot2.c:362: error: for each function it appears in.) *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ekg# ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" Cvsup again, It should be fixed now Rob bde 2003/11/10 22:27:35 PST FreeBSD src repository Modified files: sys/boot/i386/boot2 boot2.c Log: Include the definition of RB_BOOTINFO. The previous commit broke the world because it depended on namespace pollution that was only in my version of . The include was removed in rev.1.63 after the last reference to it went away in rev.1.61. Revision ChangesPath 1.66 +2 -0 src/sys/boot/i386/boot2/boot2.c ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random signals in {build,install}world recently?
From: Doug Rabson <[EMAIL PROTECTED]> I also get random segfaults and ICEs on my dual 1900+ system with recent current. It certainly isn't hardware problems since older kernels work very nicely. I haven't got around to trying to diagnose what is causing it yet though. I was planning to try disabling a few things like SSE, PSE etc and see if I could improve things. My kernel is dated from 1 October (I did try a bit later than that but those ones just paniced all over themselves, very messy). I've been seeing those on my laptop (PII-700 in an HP Omnibook 6000). What I did find is that if I disable SSE (options CPU_DISABLE_SSE) then I can build without issue. I haven't had to disable anything else. Credit for this goes to somebody else on the list (don't remember who) who said it worked for them. Please DO NOT send me ANY email directly unless it's a privacy issue. Reply-to mangled to assist those who don't read the above. -- Rob | What part of "no" was it you didn't understand? _ Hotmail messages direct to your mobile phone http://www.msn.co.uk/msnmobile ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata problem with 13/10/2003 current
From: Soren Schmidt <[EMAIL PROTECTED]> 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 - 1.8 +++ ata-queue.c 13 Oct 2003 13:05:01 - <---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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot hang: "ata1: resetting devices .. done"(5.1-CURRENT,IBMT30)
From: "Rob MacGregor" <[EMAIL PROTECTED]> Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to confirm that that's the last working version for me too. Backing out to 1.6 fixes the problem for me too... Please DO NOT send me ANY email directly unless it's a privacy issue. Reply-to mangled to assist those who don't read the above. -- Rob | What part of "no" was it you didn't understand? _ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot hang: "ata1: resetting devices .. done" (5.1-CURRENT,IBMT30)
From: "Steve Ames" <[EMAIL PROTECTED]> Anyone tried going forward to 1.8? Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to confirm that that's the last working version for me too. Please DO NOT send me ANY email directly unless it's a privacy issue. Reply-to mangled to assist those who don't read the above. -- Rob | What part of "no" was it you didn't understand? _ Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.1-CURRENT ATA problem
Since earlier this week I've suffered the same problem's others have reported with ata lockups (http://lists.freebsd.org/pipermail/freebsd-current/2003-October/011686.html, http://lists.freebsd.org/pipermail/freebsd-current/2003-October/011727.html). During boot if I have my CD ROM drive installed I get the following: GEOM: create disk ad0 dp=0xc496c670 ad0: 28615MV [58140/16/63] at ata0-master UDMA33 ata1: resetting devices .. done And then the laptop locks up and stays that way until I perform a power cycle. Same result with or without ACPI. Without the CD-ROM drive everything boots fine. Installing the CD ROM drive post boot results in a locked system too. The hardware is an HP Omnibook 6000 laptop with a GENERIC kernel. If people let me know what I can do to further identify the cause of this problem I'm happy to help. Having never played with -CURRENT before I'm a little out of my depth :) -- Rob | What part of "no" was it you didn't understand? _ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vinum problems with todays current
Hi all, After cvs'upping (about 12 hours ago) and building world/kernel vinum stopped working. It does show my two disks but nothing more. I also get an error message right after the bootloader: msgbuf cksum mismatch (read a5886, calc a5efb) -- The output of vinum: vinum -> list 2 drives: D b State: up /dev/ad6s1e A: 77903/77903 MB (100%) D a State: up /dev/ad4s1e A: 77903/77903 MB (100%) 0 volumes: 0 plexes: 0 subdisks: --- slopuh# uname -a FreeBSD slopuh.debank.tv 5.1-CURRENT FreeBSD 5.1-CURRENT #20: Tue Aug 5 20:13:13 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLOPUH i386 I don't have debugging configured in the kernel, but can recompile if usefull. Anyone with the same problems and/or ideas ? Rob Evers -- It is a book about a Spanish guy called Manual. You should read it. -- Dilbert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vinum problems with todays current
Greg 'groggy' Lehey wrote:
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
...
I noticed I had an older version of spec_vnops.c (1.205), so I
cvsupped again and build kernel, this gave me the same msgbuf error,
but with different values. Then I applied your patch and the error
messgae disapeared, but still my vinum doesn't come up.
Can I assume that this is related to GEOM, and not to Vinum?
Greg
--
See complete headers for address and phone numbers
After investigating a little further today, I found the config info on
the drives to be mangled.
--
# rm -f log
# for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
(dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo) >> log
done
# cat log
IN VINOx-server.debank.tvbC<>c3??Z${m5?
IN VINOx-server.debank.tvaC<><3?WPZ${m5?
--
I guess the drives can't be started again unless I have the parameters
which I used during install (please say I'm wrong).
Rob Evers
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vinum problems with todays current
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
Index: spec_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/specfs/spec_vnops.c,v
retrieving revision 1.206
diff -u -r1.206 spec_vnops.c
--- spec_vnops.c5 Aug 2003 06:43:56 - 1.206
+++ spec_vnops.c5 Aug 2003 19:33:06 -
@@ -505,9 +505,9 @@
devtoname(bp->b_dev), bp));
if ((dsw->d_flags & D_NOGIANT) && !(bp->b_flags & B_KEEPGIANT)) {
- DROP_GIANT();
+ /* DROP_GIANT(); */
DEV_STRATEGY(bp);
- PICKUP_GIANT();
+ /* PICKUP_GIANT(); */
} else
DEV_STRATEGY(bp);
Hi Poul,
I noticed I had an older version of spec_vnops.c (1.205), so I
cvsupped again and build kernel, this gave me the same msgbuf error,
but with different values. Then I applied your patch and the error
messgae disapeared, but still my vinum doesn't come up.
vinum -> list
2 drives:
D b State: up /dev/ad6s1e A: 77903/77903
MB (100%)
D a State: up /dev/ad4s1e A: 77903/77903
MB (100%)
0 volumes:
0 plexes:
0 subdisks:
If you need additional info, I'll be glad to provide such.
Rob Evers
--
It is a book about a Spanish guy called Manual. You should read it.
-- Dilbert
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/libexec/save-entropy problem
Simon L. Nielsen wrote: On 2003.06.25 18:38:59 +0200, Rob wrote: I get e-mails from my current boxes saying: "hostname: sethostname: Operation not permitted" (original message attached). I know this is the random seed saving instance of crontab, but what goes wrong here ? (why does it fail permission) The box is updated today and mergemaster was run (This didn't help a thing ;-)) What does your /etc/rc.conf contain ? Perhaps you have commands which sets the hostname in there ? Mmmph, I had the line: 'hostname slopuh.debank.tv' in my rc.conf, this ofcourse should have been 'hostname="slopuh.debank.tv"' The funny thing is that the host name did show up correct. Problem solved thx! Rob Evers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/usr/libexec/save-entropy problem
Hi all, I get e-mails from my current boxes saying: "hostname: sethostname: Operation not permitted" (original message attached). I know this is the random seed saving instance of crontab, but what goes wrong here ? (why does it fail permission) The box is updated today and mergemaster was run (This didn't help a thing ;-)) System: FreeBSD slopuh.debank.tv 5.1-CURRENT FreeBSD 5.1-CURRENT #16: Wed Jun 25 16:33:15 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLOPUH i386 Original Message Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy Date: Wed, 25 Jun 2003 16:00:00 +0200 (CEST) From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] hostname: sethostname: Operation not permitted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildkernel error in 5.1_RELEASE
I have downloaded the 5.1-RELEASE source via sysinstall and while world build fine, I have this error when trying to compile a new kernel from the downloaded source on Alpha: cc -c -O -pipe -mcpu=ev45 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror vers.c linking kernel init_main.o: In function `proc0_init': init_main.o(.text+0x424): undefined reference to `kse0_sched' init_main.o(.text+0x430): undefined reference to `ksegrp0_sched' init_main.o(.text+0x43c): undefined reference to `proc0_sched' init_main.o(.text+0x448): undefined reference to `thread0_sched' *** Error code 1 Stop in /usr/obj/usr/src/sys/AYLEE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. aylee# uname -a FreeBSD aylee.number6 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE-p7 #0: Mon May 5 23:29:58 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYLEE alpha cheers, Rob -- When in doubt, fuck it. When not in doubt ... get in doubt! This is random quote 1185 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ypserv and sshd not getting along in -current
At 11:59 AM 31/03/03, Glenn Johnson sent this up the stick: On Mon, Mar 31, 2003 at 10:46:07AM +1000, Rob B wrote: > At 02:55 PM 29/03/03, Terry Lambert sent this up the stick: > > > >man ypbind > > > >(-s is the magic incantation). > > Mar 31 10:10:39 erwin ypserv[92]: access to master.passwd.byuid denied -- > client 192.168.100.30:49255 not privileged > > Why would the request be coming from a high port when I have > specifically told it to bind to a low port? The answer (work around) is to turn off PrivelegeSeparation in your sshd_config file. That got it, thanks Rob -- Two prostitutes standing on a street corner. One says to the other, "Have you ever been picked up by the fuzz?" The other replies, "No, but I've been swung around by the boobs a few times!" This is random quote 1117 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ypserv and sshd not getting along in -current
At 02:55 PM 29/03/03, Terry Lambert sent this up the stick: Glenn Johnson wrote: > I can not login to a box with FreeBSD 5 -current via ssh because I get > the following error from ypserv: > > Mar 28 12:48:15 node1 ypserv[317]: access to master.passwd.byuid denied -- client 192.168.1.1:49344 not privileged man ypbind (-s is the magic incantation). I have the same issue, I tried Terry's suggestion but I don't think its working like it should: On the client: aylee # ps fax|grep yp 252 ?? Is 0:0.62 /usr/sbin/ypbind -s aylee # rpcinfo -p localhost|grep yp 17 2 udp 1022ypbind 17 2 tcp 1023ypbind Tailing the server's log: Mar 31 10:10:39 erwin ypserv[92]: access to master.passwd.byuid denied -- client 192.168.100.30:49255 not privileged Why would the request be coming from a high port when I have specifically told it to bind to a low port? Cheers, Rob -- On Earth there is no reckoning. This is random quote 883 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NIS/ssh problem -CURRENT client to 4.8-RC2 server
Not sure where to send this one, but this used to work when the client was 5.0-RC1. The server hasn't been modified at all since the client was upped to -CURRENT. Basically, the user I'm trying to logon as only exists locally on the server, and via NIS on the client Client: aylee# uname -a FreeBSD aylee.number6 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Mar 27 00:57:40 ES T 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYLEE alpha Server: FreeBSD erwin.number6 4.8-RC FreeBSD 4.8-RC #2: Sun Mar 16 03:35:25 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ERWIN alpha Logging in locally on the client is fine, as the NIS user, but I can't log in as the same user via ssh. Heres the corresponding logs from erwin (server) and aylee (client): Mar 27 09:46:05 erwin ypserv[92]: access to master.passwd.byuid denied -- client +192.168.100.30:49180 not privileged Mar 27 09:46:04 aylee sshd[23711]: fatal: login_get_lastlog: cannot find account for uid[1000] cheers, Rob -- A beautiful woman will enrich your life soon. This is random quote 120 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: NFS server vs YO (very long message)
At 01:43 AM 18/02/03, Erik Torres Serrano sent this up the stick: OK, after the weekend I'm here again. Those are the contents of my configuration files: 1) /etc/exports /localhome -maproot=0beta seems OK, maybe try adding the -alldirs switch /localhome -maproot=0 -alldirs beta 3) /etc/rc.conf hostname="mizar.cigb.edu.cu" ifconfig_xl0="DHCP" kern_securelevel_enable="NO" linux_enable="YES" moused_enable="YES" moused_type="auto" nfs_client_enable="YES" nfs_server_enable="YES" rpcbind_enable="YES" saver="logo" sendmail_enable="YES" sshd_enable="YES" usbd_enable="YES" moused_type="auto" moused_enable="YES" moused_port="/dev/cuaa0" moused_type="auto" rpc_lockd_enable="YES" This is a bit of a mess, try removing all the extra bits you don't need. If you are using DHCP, then make sure the hostnames match up in the dhcpd.conf file on the server as well as /etc/rc.conf I have the following nfs entries in my /etc/rc.conf nfs_server_enable="YES" rpcbind_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" 2) showmount -e mizar Exports list on mizar: So mizar isn't exporting anything . well, anything that can be seen by the client I get 6) mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1d on /localhome (ufs, local, soft-updates) Is this on the server? If so, it should look like: aylee% mount /dev/da0a on / (ufs, NFS exported, local) devfs on /dev (devfs, local) /dev/da0f on /tmp (ufs, local, soft-updates) /dev/da0e on /usr (ufs, NFS exported, local, soft-updates) /dev/da0g on /var (ufs, local, soft-updates) Also: 1) I'm sure I'm mounting as root. 2) As you can see both machines know the route for the other. Does the client have the following in /etc/rc.conf ? nfs_client_enable="YES" nfs_client_flags="-n 4" rpc_lockd_enable="YES" rpc_statd_enable="YES" cheers, Rob -- I'd give my right arm to be ambidextrous. This is random quote 649 of a collection of 1273 Distance from the centre of the brewing universe: [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: EINVAL when mounting root
Kris Kennaway wrote: Since upgrading to -current I get the following on my sparc at boot time: Mounting root from ufs:/dev/da0 Root mount failed: 22 (errno 22 is EINVAL). Someone told me this was already fixed (by which commit?), but cvsupping again did not fix the problem. Any ideas? Kris This should fix it (snip from cvs'upping) Edit src/sys/ufs/ffs/fs.h Add delta 1.37 2003.01.09.23.53.30 gordon Add delta 1.38 2003.01.10.06.59.34 marcel Compiling new world now so I don't know if it works For more inf look at the thread in freebsd-current mailing list named : HEADS UP: VFS changes breaks GPT Rob To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0-RC1: sysinstall changes disklabels on other slices?
I've seen a few discussions of sysinstall vs disklabels, but this problem looks a little different. I sliced up a 37G disk with 4.7-RELEASE on ad0s1, Win2k on ad0s[23] and ad0s4 empty. I installed grub-0.92, putting the bootloader in the MBR and config files in ad0s1a. Everything worked fine. Then I installed 5.0-RC1 on ad0s4. The next reboot, grub dumped me at the prompt, saying that there were no BSD partitions on ad0s1. It took a while to figure out the problem, but it seems that installing 5.0-RC1 on slice 4 rewrote the disklabel on slice 1. I wiped ad0s4 and reinstalled last night, saving the before and after disklabels. Here's ad0s1 (4.7): # /dev/ad0s1c: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1621 sectors/unit: 26057367 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD0 0 0 # (Cyl.0 - 261*) b: 2097152 4194304 swap# (Cyl. 261*- 391*) c: 260573670unused0 0 # (Cyl.0 - 1621*) e: 4194304 62914564.2BSD0 0 0 # (Cyl. 391*- 652*) f: 4194304 104857604.2BSD0 0 0 # (Cyl. 652*- 913*) g: 11377303 146800644.2BSD0 0 0 # (Cyl. 913*- 1621*) Here's ad0s4 (empty): # /dev/ad0s4c: type: ESDI disk: ad0s4 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1622 sectors/unit: 26057430 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 260574300unused0 0 # (Cyl.0 - 1621) And here's the config for sysinstall: # disk format disk=ad0 partition=existing bootManager=none diskPartitionEditor # disk slices ad0s4-1=ufs 4194304 / 1 # 2G+ soft updates ad0s4-2=swap2097152 none# 1G ad0s4-3=ufs 4194304 /var1 # 2G+ soft updates ad0s4-4=ufs 4194304 /usr1 # 2G+ soft updates ad0s4-5=ufs 0 /home 1 # free + soft updates diskLabelEditor # install system distSetEverything mediaSetCDROM installCommit # install packages package=lynx-2.8.4.1c packageAdd package=sudo-1.6.6 packageAdd After the installation, here's ad0s1 (4.7): # /dev/ad0s1c: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1621 sectors/unit: 26057367 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 41943040unused0 0 # (Cyl.0 - 261*) b: 2097152 4194304unused0 0 # (Cyl. 261*- 391*) c: 260573670unused0 0 # (Cyl.0 - 1621*) e: 4194304 6291456unused0 0 # (Cyl. 391*- 652*) f: 4194304 10485760unused0 0 # (Cyl. 652*- 913*) g: 11377303 14680064unused0 0 # (Cyl. 913*- 1621*) And ad0s4 (5.0-RC1): # /dev/ad0s4c: type: ESDI disk: ad0s4 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1622 sectors/unit: 26057430 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD0 0 0 # (Cyl.0 - 261*) b: 2097152 4194304 swap# (Cyl. 261*- 391*) c: 260574300unused0 0 # (Cyl.0 - 1621) d: 4194304 62914564.2BSD0 0 0 # (Cyl. 391*- 652*) e: 4194304 104857604.2BSD0 0 0 # (Cyl. 652*- 913*) f: 11377366 146800644.2BSD0 0 0 # (Cyl. 913*- 1621*) Notice that all the fstype values on ad0s1 have changed to 'unused' - this borks grub, because it can't find any FFS filesystems. So I installed boot0 (which didn't have any problem with the missing fstypes), rebooted into 4.7 and fixed things with disklabel -e. Once grub could see BSD partitions, I reinstalled it in the MBR and everything work
Re: NVIDIA driver
"Gernot A. Weber" wrote: > > > This is a FAQ and has been answered several times already. But I'll > > answer it again. > Nonsense. The whole nvidia situation is a can of worms with a number of answers to any given question. For example, stable is different than -current. Some mobo's just don't work. If I knew all the answers I'd write a HOWTO. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP-2 and Nvidia Geforce 4
Joe Marcus Clarke wrote: > > Sorry, just got power back after the ice storm. What modules do you > have loaded. I had the following, and the nv driver started right up: > > Section "Module" > Load"dbe" > Load"dri" > Load"extmod" > Load"glx" > Load"pex5" > Load"record" > Load"xie" > Load"bitmap" > Load"freetype" > Load"speedo" > Load"type1" > Load"vbe" > EndSection > > Joe > > > > > Rob. > -- Hi Joe, so thats why your web site was down. I will try the modules you have listed later tonight, that is if I don't fall asleep by 5pm. Was not an enjoyable night, but I would have been up all night anyway. Just couldn't sleep. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nvidia drivers hate me/ too!
Maxime Henrion wrote: > > Doug Barton wrote: > > The native nvidia drivers work great in RELENG_4 with my geforce 4 mmx, > > but in -current they hate me. I just upgraded to the latest -current and > > I'm using XFree compiled on -current, no joy. It's always the same error: > > > > panic: bremfree: bp 0xc7751bb8 not locked > > This is not the real panic(), the real one is an assertion failure in > vm_page_wire(). In -CURRENT, vm_page_wire() should be called with the > page queue mutex held. The nVidia driver lacks a fair amount of > vm_page_lock_queues() calls, and I wouldn't be surprised if it was > missing more things, with respect to locking. > > Cheers, > Maxime > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message Insomnia. I spent all of last night trying different things on -current to get the Geforce 2 on my laptop and the Geforce 4 in my main computer to work. Tried the nv.tar.gz patches. No good. Tried the NVidia driver with the mtrr patches. No good. It seems that the cvsup from last night is much worse than earlier builds. I did once get the nv.tar.gz method working on my laptop. That was from a cvsup the day after DP2 came out. Good grief, I couldn't even get grub to load so I could try out OpenBSD on drive #2. Time to do something else instead of computers. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP-2 and Nvidia Geforce 4
> > Ok, here is the error message. The server never even gets past go: > > "Symbol vgaHWUnmapMem from module > /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved!" > Fatal server error: > Caught signal 11. Server aborting. > > Rob. > > -- I got rid of the first error message by loading "vgahw" module. Now I just get Signal 11. I also went back and recompiled my X11 with no optimizations except -pipe -o, getting rid of the -march=athlon-xp, but no joy. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP-2 and Nvidia Geforce 4
Joe Marcus Clarke wrote: > > On Wed, 2002-12-04 at 22:46, Rob wrote: > > Rob wrote: > > > > > > Joe Marcus Clarke wrote: > > > > > > > > On Wed, 2002-12-04 at 17:04, Rob wrote: > > > > > Is there any solution to the above combo other than just waiting? > > > > > > > > I think you've seen my how-to at > > > > http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for > > > > your card, or are you referring to GeForce 4 with accelerated 3D > > > > support? > > > > > > > > Joe > > > > > > Hi Joe, > > > > I have confirmed that your procedure didn't work with my Asus V8170 > > Geforce 4 card. But its not a hardware issue. I'm getting undefined > > symbols in one of the libraries. I will later today boot into DP2 and > > see if I can put together a more meaningful report. I built the > > XFree86-4 metaport from a fresh ports directory. First make deinstall > > then make reinstall. > > I've seen that before. It usually can be fixed by making sure that the > correct X server modules are loaded. That is, of course, if you're > seeing unresolved symbols in X itself. > > Joe > > > > > Thanks, Rob. > > > > > > > > > > > > > > > > > thanks, Rob. > > > > -- > > > > PGP Key : http://www.marcuscom.com/pgp.asc > > > > > > Thanks Joe, > > > > > > I will check it out. I think I used your procedure to get the Geforce 2 > > > on my laptop -current working. But I tried a number of things for DP2 > > > on my big machine that didn't work. In that case I've got an Asus V8170 > > > Geforce 4 card that I got on the cheap. I can always go back to a Riva > > > TNT or something thats < $20 :) :) > > > > > > Rob. > > > > > > -- > > > - > > > The Numeric Python EM Project > > > > > > www.pythonemproject.com > -- > PGP Key : http://www.marcuscom.com/pgp.asc Ok, here is the error message. The server never even gets past go: "Symbol vgaHWUnmapMem from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved!" Fatal server error: Caught signal 11. Server aborting. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP-2 and Nvidia Geforce 4
Rob wrote: > > Joe Marcus Clarke wrote: > > > > On Wed, 2002-12-04 at 17:04, Rob wrote: > > > Is there any solution to the above combo other than just waiting? > > > > I think you've seen my how-to at > > http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for > > your card, or are you referring to GeForce 4 with accelerated 3D > > support? > > > > Joe > > Hi Joe, I have confirmed that your procedure didn't work with my Asus V8170 Geforce 4 card. But its not a hardware issue. I'm getting undefined symbols in one of the libraries. I will later today boot into DP2 and see if I can put together a more meaningful report. I built the XFree86-4 metaport from a fresh ports directory. First make deinstall then make reinstall. Thanks, Rob. > > > > > > > > > thanks, Rob. > > -- > > PGP Key : http://www.marcuscom.com/pgp.asc > > Thanks Joe, > > I will check it out. I think I used your procedure to get the Geforce 2 > on my laptop -current working. But I tried a number of things for DP2 > on my big machine that didn't work. In that case I've got an Asus V8170 > Geforce 4 card that I got on the cheap. I can always go back to a Riva > TNT or something thats < $20 :) :) > > Rob. > > -- > - > The Numeric Python EM Project > > www.pythonemproject.com -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP-2 and Nvidia Geforce 4
Joe Marcus Clarke wrote: > > On Wed, 2002-12-04 at 17:04, Rob wrote: > > Is there any solution to the above combo other than just waiting? > > I think you've seen my how-to at > http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for > your card, or are you referring to GeForce 4 with accelerated 3D > support? > > Joe > > > > > > > thanks, Rob. > -- > PGP Key : http://www.marcuscom.com/pgp.asc Thanks Joe, I will check it out. I think I used your procedure to get the Geforce 2 on my laptop -current working. But I tried a number of things for DP2 on my big machine that didn't work. In that case I've got an Asus V8170 Geforce 4 card that I got on the cheap. I can always go back to a Riva TNT or something thats < $20 :) :) Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DP-2 and Nvidia Geforce 4
Is there any solution to the above combo other than just waiting? thanks, Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck's, "current" vs "earlier releases"
Hi Garance, This happened to me also. The solution was to run fsck on the older versions, but tell it to use an alternate superblock. See man fsck. I forget the details, but it worked for me. Rob. Garance A Drosihn wrote: > > I'm playing around with installing a number of freebsd releases on > the same PC, and something came up which makes me a little uneasy. > I understand why I am seeing what I'm seeing, I'm just uneasy about > what it might mean for people who will pick up 5.0-release and start > testing it on their own machines. > > I have 4.6.2-release, 4.7-release, and 5.0-dp2-release on a single PC. > After some bouncing between versions, and an occasional 'disklabel' > command, I seem to have the partitions for 4.6.2 in an odd state. > Both 4.7 and 5.0-dp2 have no problem mounting them, but if I try to > boot up the 4.6.2 system it fails because 4.6.2 finds that "values > in super block disagree with those in first alternate". 4.6.2 wants > me to 'fsck' the partitions manually, but I *think* I remember that > using the older fsck might cause trouble. > > For my own PC none of this is critical, because I'm just doing a few > quick tests and at this point I don't even need to boot up 4.6.2. I > just wonder how much of an issue this will be for people who setup > their machines to dual-boot between 5.0-release (once it *is* released) > and "something a little older". 4.7 has no trouble, but even 4.6.2 > (which is not all that old) can be confused by the subtle changes in > UFS which will show up in 5.0-release. > > I am not suggesting we must do something about this, I'm just a > little uneasy about the situation. Okay, well maybe I should try at > least one suggestion. Should we tell people that they *must* update > 'fsck' on *other* (multi-boot) systems before installing 5.0-release? > > -- > Garance Alistair Drosehn= [EMAIL PROTECTED] > Senior Systems Programmer or [EMAIL PROTECTED] > Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2- can it be cvsup'd ??
John Baldwin wrote: > > On 22-Nov-2002 Rob wrote: > > Can DP2 be cvsup'd? > > Not directly, no. It was not done as a branch in CVS. However, > the differences between CVS and DP2 are relatively minor, mostly > just going around and change it to say 5.0-DP2 instead of > 5.0-CURRENT. :) > > -- > > John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ Thanks John, I will cvsup immediately, and build it later. I just didn't want to have to go in and reinstall a hundred programs :) Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DP2- can it be cvsup'd ??
Can DP2 be cvsup'd? Thanks, Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: src/games bikeshed time.
Hi all, I agree keeping these traditional toys in the base system won't help in a better OS (instead it makes it a bit bigger and older), agreed that they are some sort of 'folklore' putting them in a port makes a good solution. mzl! Rob Evers [EMAIL PROTECTED] Technological progress has merely provided us with more efficient means for going backwards. -- Aldous Huxley Mark Murray wrote Hi The current flare-up over src/games/wargames reminds me that we are carrying a bunch of Really Old Stuff in usr/games/. Yes folks, its that time of the year. I ask myself, "why are we wasting ``make world'' time and install bandwidth on 1970's-era games?". Some folks will answer "tradition". This argument holds little water. Programs come and go, and there is no firm reference or agreement as to what is "really traditional". This agument can be used to import emacs on the grounds that it is documented in the O'Reilly BSD 4.4 books. There are some games that are truly toys. Specifically I am referring to wargames(6), rain(6) and worms(6). The last two were written for 9600 baud terminals, and are _WAY_ to fast for current consoles, xterms, SSH sessions and the like. The fact that we have had no fixes for this should tell you how important they are to the future of BSD. Some of the games have useful information/utility content. Here I talk of things like pom(6), morse(6), primes(6) and the like. I have no intention of removing these. As fortune(6) has a strong maintainer and follower base, removing that would be premature. What remains? All the games that dm(6) oversees. Things like adventure(6), trek(6), battlestar(6) and so on. These are good candidates for ports IMO. Folks may want to play them, but there is no point in wasting time and space on them _by_default_. In some cases, better upgrades are already available in ports (hack --> nethack). I would like to make a port out of these and remove them from the base distribution. Let the bikeshed begin. Please try to keep some sense of focus. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0 release schedule?
David O'Brien wrote: > > On Wed, Aug 28, 2002 at 09:28:20AM -0400, Bosko Milekic wrote: > > > > I think we're on our way to stabilizing -CURRENT enough for a DP2 > > soon. I would sit and wait it out just a tad longer. :-) > > A 5.0 DP2 branch was created just yesterday. So how ever good > yesterday's -current was will affect DP2. I rather expected the release > engineers to at least querry the lists to ask what the known issues are > before picking which code to base DP2 on. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message I will wait for a while for things to be cleaned up, but what tags would I use for CVSUP to get that branch? Thanks, Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make: don't know how to make bsd.README. Stop
On Sat, 2002-08-03 at 00:45, karl agee wrote: > ok...its crashing here, now.I've deleted the /usr/src/gnu directory > and re-cvsuped it, but it still_crashes: > > Re-cvsup and try it again. I got that Thursday, but Friday it worked. Well, the system locked at loading the fxp driver, but it compiled and installed. -- Remember: the only difference between being the champ and the chump is u. signature.asc Description: This is a digitally signed message part
RE: Re: Be careful mounting -stable partitions on -current
I cvsup'd on Friday of last week, after I restored /usr. Did the fix come later than that? I'm kind of afraid to try it again :) Thanks, Rob. >- Original Message - >From: Dag-Erling Smorgrav <[EMAIL PROTECTED]> >To: rob <[EMAIL PROTECTED]> >Sent: 29 Jul 2002 18:26:23 > >rob <[EMAIL PROTECTED]> writes: >> I mounted my -stable /usr partition on -current >/mnt to copy over a >> kernel config file, and when I finally fired up >-stable, the /usr >> partition was borked. Fsck couldn't fix it >manually. Luckily I had >> backups. It said that the master record didn't >match the alternate. I >> might have rebooted without unmounting the >-stable partition. > >There's nothing wrong with your partition, but >there's a bug in your >version of fsck. You can "fix" your partition with >'fsck -b 32 -y', >but you really should update your system. > >DES >-- >Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Be careful mounting -stable partitions on -current
I mounted my -stable /usr partition on -current /mnt to copy over a kernel config file, and when I finally fired up -stable, the /usr partition was borked. Fsck couldn't fix it manually. Luckily I had backups. It said that the master record didn't match the alternate. I might have rebooted without unmounting the -stable partition. On my laptop (Sony FX290), each type of reboot has different consequences. "reboot" works as expected. CTRL-ALT-DEL does not- it syncs disks and then freezes. "Shutdown -p now" shuts down, but when you turn the laptop back on it freezes and you have to take the batteries out to get it working right again. Rob. (ps. this is the message I was trying to send that ended up as dozens of "QUIT" messages- sorry again) -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VESA 800x600 console not working
Maxim Sobolev wrote: > > David Xu wrote: > > > > Yes, this is a known problem. I have a patch for this, you may > > download it from here: > > http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz > > Any ideas why it isn't committed yet? > > -Maxim BTW, the VESA mode doesn't work on -stable now either. I knew I shouldn't have cvsup'd, with all the problem reports I'm seeing on the lists. Dohh! But I just ordered a Dell 8200, so maybe my problems will become "different" Rob. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
I did not send dozens of QUIT messages
This is either a problem with linux-netscape on -current, or a problem with the mta at Verio (on FBSD of course). Sorry for the inconvenience. I hope it isn't at Verio, or there will be another 30 messages. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
I didn't send dozens of QUIT emails
There was either a glitch at Verio's mta or possibly on Linux-Netscape in -current. I sent one message and it never went through. Sorry for the spam. It was an error message- get it? Rob. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
QUIT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
