Re: Understanding libpthread.so.2 undef reference error....
Norberto Meijome wrote:
On Mon, 05 Nov 2007 23:39:17 +0100
Kris Kennaway <[EMAIL PROTECTED]> wrote:
Hi Kris,
thanks for the explanation. I don't think I did that, as this is a 100% clean
install of 7,but maybe I bungled it somewhere.
is there a way to know what is cross linked? should I get rid of compat6x?
Well in that case you managed to somehow install a 6.x binary on there
(not compat6x), which is now being linked to 7.0 binaries (this should
never happen in a correctly functioning system). Either rerun
portupgrade -fa, or use pkg_which on the binaries and libraries that are
giving problems to try and track down which need to be reinstalled.
Thanks Kris, that's what I did.
for each of the messages that I got showing :
/usr/bin/ld: warning: libpthread.so.2, needed by
/usr/local/lib/libicui18n.so.36, not found (try using -rpath or -rpath-link
or similar, i did
pkg_info -W {Library}
( in this case /usr/local/lib/libicui18n.so.36 , which pointed to icu), and
rebuilt the package.
It seems I must have used portinstall -pP instead of -p in a couple of places
and managed to confuse the heck of my system.
Everything seems to be building ok so far :)
thanks so much for the pointer!
Hmm, portinstall -P should have still worked, unless your FTP mirror is
seriously out of date. Which one are you using? Or maybe you have old
local packages in your PKG_PATH?
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Tue, Nov 06, 2007 at 12:48:35PM +1100, Norberto Meijome wrote: > On Mon, 05 Nov 2007 14:24:09 -0600 > Doug Poland <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > I've been having frequent problems with BETA1 and now BETA2 > > "freezing". There is no diagnostic information, nothing in > > /var/log/messages, nothing, just a hung interface. I cannot ssh > > into the machine and it appears the box ceases to communicate on > > SSH. A couple of times I've had screen corruption on the laptop's > > LCD display. > > > > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, > > pidgin, and a bunch of xterms. > > > > Is there something I can do to diagnose this issue? > > > > hi Doug, > My laptops is freezing like this too - no corruption on display though > (this is the 2nd time i write this email, as it just happened ). I > am still not sure what the cause is...some things I've used / tried: > > I was using gjournal on my 80 GB /usr partition, with a 1.5 journal > to ad01sh . I was getting quite often lockups where it seemed the disk > subsystem would stall - anything in memory would work, but as soon as > disk access was needed, it'd stall too. Rebooting was not an option, > as the shutdown watchdog would timeout and stop it. > > furthermore, I'd have to go into single user and run fsck > /dev/ad0s1f.journal every time the laptop would crash. I seemed to > have much fewer bad information in the inodes (thanks to the journal), > but I was getting 4 or 6 crashes a day. Since I switched away from > gjournal, these crashes have completely gone away. since this is my > main machine, i cant experiment too much with it. > > I also had skype-1.4 running . One of its processes was spinning > completely out of control , when i wasn't using skype at all (other > than receiving text msgs). I sent an email about it to Multimedia.I've > since switched back to skype.1.2 and that problem is also gone. > > But i still get the occasional lockup. I have a feeling it is related > to using the sound card : > > $ cat /dev/sndstat > FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386) > Installed devices: > pcm0: at memory 0xb000 > irq 11 kld snd_hda [20071020_0048] [MPSAFE] (1p:10v/1r:6v channels duplex > default) > > Pretty much everytime I'm getting a lockup, i'm either streaming music > from my music box or on a skype call. Not much to go by, but there > isn't any logs left at all of the crash. It is not a panic (no writing > dump to disk when I press enter, Caps-lock is dead, even the Fn key > which is bound to the bios is dead). What I have noticed in these > cases is that there seems to be a lock upthen, about a minute or > so after it, the mouse seems to come back to life...but then there's > nothing more I can do - i've waited for over 5 minutes after this with > no more results > It's quite likely that I have streaming audio/video going on but am using mplayer exclusively. Am also using new HDA controller. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: date/time trouble - PST came too early
Hello, and thank you for your reply... Quoting Vivek Khera <[EMAIL PROTECTED]>: On Nov 2, 2007, at 3:30 AM, Chris H. wrote: FWIW The system already knows what timezone it lives in. It simply chose to change to PST according to the /normal/ standards. What happened here in the USA, is that president Bush decided that we'd be better served here if we waited an additional week to set our clocks back one hour. So. It seems this particular server decided to ignore our president (not that I blame it) Most of us went through this *last* year when the rules took effect. Did it not affect your system last year? Basically you need to get a corrected /etc/localtime and restart any long running programs that depend on time, notably cron. Ahh... I'm guessing that you missed the following post in this thread titled "date/time trouble - PST came too early [fixed]" posted 11-02. LI Xin offered the following solution, which solved my dilemma: Install /usr/ports/misc/zoneinfo or upgrade your system to a recent release (preferred), e.g. RELENG_6_2 aka FreeBSD 6.2-RELEASE. Re-run tzsetup and choose your time zone accordingly. You will need to restart the time-sensitive services afterward, or reboot the whole system :-) I chose the port && Re-run tzsetup && restart route. :) Thanks again for taking making the effort to respond. --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Tue, 6 Nov 2007 12:48:35 +1100
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> But i still get the occasional lockup. I have a feeling it is related to
> using the sound card :
>
> $ cat /dev/sndstat
> FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
> Installed devices:
> pcm0: at memory 0xb000
> irq 11 kld snd_hda [20071020_0048] [MPSAFE] (1p:10v/1r:6v channels duplex
> default)
>
> Pretty much everytime I'm getting a lockup, i'm either streaming music from
> my music box or on a skype call. Not much to go by, but there isn't any logs
> left at all of the crash. It is not a panic (no writing dump to disk when I
> press enter, Caps-lock is dead, even the Fn key which is bound to the bios is
> dead). What I have noticed in these cases is that there seems to be a lock
> upthen, about a minute or so after it, the mouse seems to come back to
> life...but then there's nothing more I can do - i've waited for over 5
> minutes after this with no more results
btw, I've resorted to NOT using XMMS - the issues were happening a LOT more
often when i use it instead of, say, vlc or beep.
I remember having this same issue on 6.2 with the drivers in the kernel. The
latest binary drivers from Ariff would work fine, though i had given up on xmms
by then and using vlc for a while.
cheers,
b
_
{Beto|Norberto|Numard} Meijome
If you find a solution and become attached to it, the solution may become your
next problem.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, 05 Nov 2007 14:24:09 -0600
Doug Poland <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've been having frequent problems with BETA1 and now BETA2 "freezing".
> There is no diagnostic information, nothing in /var/log/messages,
> nothing, just a hung interface. I cannot ssh into the machine and it
> appears the box ceases to communicate on SSH. A couple of times I've had
> screen corruption on the laptop's LCD display.
>
> Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin,
> and a bunch of xterms.
>
> Is there something I can do to diagnose this issue?
>
hi Doug,
My laptops is freezing like this too - no corruption on display though (this is
the 2nd time i write this email, as it just happened ). I am still not sure
what the cause is...some things I've used / tried:
I was using gjournal on my 80 GB /usr partition, with a 1.5 journal to ad01sh
. I was getting quite often lockups where it seemed the disk subsystem would
stall - anything in memory would work, but as soon as disk access was needed,
it'd stall too. Rebooting was not an option, as the shutdown watchdog would
timeout and stop it.
furthermore, I'd have to go into single user and run fsck /dev/ad0s1f.journal
every time the laptop would crash. I seemed to have much fewer bad information
in the inodes (thanks to the journal), but I was getting 4 or 6 crashes a day.
Since I switched away from gjournal, these crashes have completely gone away.
since this is my main machine, i cant experiment too much with it.
I also had skype-1.4 running . One of its processes was spinning completely out
of control , when i wasn't using skype at all (other than receiving text msgs).
I sent an email about it to Multimedia.I've since switched back to skype.1.2
and that problem is also gone.
But i still get the occasional lockup. I have a feeling it is related to using
the sound card :
$ cat /dev/sndstat
FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
Installed devices:
pcm0: at memory 0xb000 irq
11 kld snd_hda [20071020_0048] [MPSAFE] (1p:10v/1r:6v channels duplex default)
Pretty much everytime I'm getting a lockup, i'm either streaming music from my
music box or on a skype call. Not much to go by, but there isn't any logs left
at all of the crash. It is not a panic (no writing dump to disk when I press
enter, Caps-lock is dead, even the Fn key which is bound to the bios is dead).
What I have noticed in these cases is that there seems to be a lock upthen,
about a minute or so after it, the mouse seems to come back to life...but then
there's nothing more I can do - i've waited for over 5 minutes after this with
no more results
Not sure how I can diagnose / test this, but i'm willing to give them a try,
time permitting :)
thanks!
Beto
_
{Beto|Norberto|Numard} Meijome
Mary had a crypto key
she kept it in escrow
and everything that Mary said
the Feds were sure to know.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, Nov 05, 2007 at 11:14:13PM +0100, Ivan Voras wrote:
> Doug Poland wrote:
> > Hello,
> >
> > I've been having frequent problems with BETA1 and now BETA2
> > "freezing". There is no diagnostic information, nothing in
> > /var/log/messages, nothing, just a hung interface. I cannot ssh
> > into the machine and it appears the box ceases to communicate on
> > SSH. A couple of times I've had screen corruption on the laptop's
> > LCD display.
> >
> > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox,
> > pidgin, and a bunch of xterms.
> >
> > Is there something I can do to diagnose this issue?
>
> Only random generic troubleshooting items:
>
> - how's your heating?
>
the fan on the laptop runs continuously, sometimes on high speed. I
typically see temps between 140 (mostly idle) -> 165 (make -j4
buildworld) Fahrenheit.
> screen corruption looks like memory or bus errors.
>
In my situation, it usually manifests itself as the external LCD monitor
goes blank (says "no signal") and the bottom half of the internal LCD
gets weird, multi-colored square patterns.
> are you running powerd?
>
yes: I recently started running powerd, within the last couple of weeks
> - can you set up a serial or firewire connection to it and monitor the
> machine from there ("screen corruption" may also mean a kernel message
> being printed in text mode, in the part of memory now mapped for
> graphics - if this is the case you'll see the message over the serial
> console).
>
I've done serial console redirection before but this laptop has no
serial port. Can I get console redirection via firewire? Can you point
me at some docs?
--
Regards,
Doug
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, Nov 05, 2007 at 02:07:46PM -0800, Karol Mroz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Doug Poland wrote: > > Hello, > > > > I've been having frequent problems with BETA1 and now BETA2 > > "freezing". There is no diagnostic information, nothing in > > /var/log/messages, nothing, just a hung interface. I cannot ssh > > into the machine and it appears the box ceases to communicate on > > SSH. A couple of times I've had screen corruption on the laptop's > > LCD display. > > > > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, > > pidgin, and a bunch of xterms. > > > > Is there something I can do to diagnose this issue? > > > > Have you just migrated to CURRENT? Was this machine running fine under > STABLE? > I moved from 6.2-STABLE to 7.0-BETA using cvsup. I may had an infrequent problem in the 6.2-STABLE days, but I can't recall with certainty. > I had similar problems with a desktop of mine that was running 6.2. > Every now and then (sometimes days in between) it would freeze in X, > corrupt the screen, or at times would just reboot. There was no warning > and nothing of worth in any log files. > pretty much my experience here, except I have a laptop. > I had a feeling it might have been my video card, so after taxing it > really hard with gl apps and noticing artifacts on the screen, I > replaced the card. The system ran well for a few weeks, but the > problems persisted. Thought at this point it could be faulty ram, so > ran each half-gig stick on it's own until the next failure. Both > sticks showed failures. So then I moved the sticks out of slots 1,2 > and into 3,4... that was 4 months ago and all is well. > I suppose I could run memtest, although the RAM in this laptop was replaced in July (now running 4GB). > I guess what I'm aiming at here is that this could be a hardware issue > which can be a pain to diagnose. > Thanks for the suggestion. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Understanding libpthread.so.2 undef reference error....
On Mon, 05 Nov 2007 23:39:17 +0100
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > Hi Kris,
> > thanks for the explanation. I don't think I did that, as this is a 100%
> > clean install of 7,but maybe I bungled it somewhere.
> >
> > is there a way to know what is cross linked? should I get rid of compat6x?
> >
>
> Well in that case you managed to somehow install a 6.x binary on there
> (not compat6x), which is now being linked to 7.0 binaries (this should
> never happen in a correctly functioning system). Either rerun
> portupgrade -fa, or use pkg_which on the binaries and libraries that are
> giving problems to try and track down which need to be reinstalled.
Thanks Kris, that's what I did.
for each of the messages that I got showing :
/usr/bin/ld: warning: libpthread.so.2, needed by
/usr/local/lib/libicui18n.so.36, not found (try using -rpath or -rpath-link
or similar, i did
pkg_info -W {Library}
( in this case /usr/local/lib/libicui18n.so.36 , which pointed to icu), and
rebuilt the package.
It seems I must have used portinstall -pP instead of -p in a couple of places
and managed to confuse the heck of my system.
Everything seems to be building ok so far :)
thanks so much for the pointer!
B
_
{Beto|Norberto|Numard} Meijome
"Build a system that even a fool can use, and only a fool will want to use it."
George Bernard Shaw
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Understanding libpthread.so.2 undef reference error....
Norberto Meijome wrote: On Mon, 05 Nov 2007 11:43:32 +0100 Kris Kennaway <[EMAIL PROTECTED]> wrote: I don't ever remember getting this error before. I am pretty sure i'm using only binaries built on this machine for 7.0... have I missed anything? what's the cause of this error? FWIW, I have compat6x installed You missed the "portupgrade -fa" step of the upgrade from 6.x to 7.x. Those errors come from binaries linked to both 6.x and 7.x libraries. Hi Kris, thanks for the explanation. I don't think I did that, as this is a 100% clean install of 7,but maybe I bungled it somewhere. is there a way to know what is cross linked? should I get rid of compat6x? Well in that case you managed to somehow install a 6.x binary on there (not compat6x), which is now being linked to 7.0 binaries (this should never happen in a correctly functioning system). Either rerun portupgrade -fa, or use pkg_which on the binaries and libraries that are giving problems to try and track down which need to be reinstalled. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Poland wrote: > Hello, > > I've been having frequent problems with BETA1 and now BETA2 "freezing". > There is no diagnostic information, nothing in /var/log/messages, > nothing, just a hung interface. I cannot ssh into the machine and it > appears the box ceases to communicate on SSH. A couple of times I've had > screen corruption on the laptop's LCD display. > > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin, > and a bunch of xterms. > > Is there something I can do to diagnose this issue? > I'm curious if these problems arose with 7.0? Did you run 6.2 on this machine prior to 7.0? I had similar problems with a desktop of mine that was running 6.2. Every now and then (sometimes days in between) it would freeze in X, corrupt the screen, or at times would just reboot. There was no warning and nothing of worth in any log files. I had a feeling it might have been my video card, so after taxing it really hard with gl apps and noticing artifacts on the screen, I replaced the card. The system ran well for a few weeks, but the problems persisted. Thought at this point it could be faulty ram, so ran each half-gig stick on it's own until the next failure. Both sticks showed failures. So then I moved the sticks out of slots 1,2 and into 3,4... that was 4 months ago and all is well. I guess what I'm aiming at here is that this could be a hardware issue which can be a pain to diagnose. - -- Karol Mroz [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHL5Qyuoug78g/Mz8RAkEzAJ9yzGU1in5lrS3fUO0mfHfzCuYiqQCfRSn3 EkJrTLktOyfNddasgJPA4V8= =tbgK -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
Doug Poland wrote:
> Hello,
>
> I've been having frequent problems with BETA1 and now BETA2 "freezing".
> There is no diagnostic information, nothing in /var/log/messages,
> nothing, just a hung interface. I cannot ssh into the machine and it
> appears the box ceases to communicate on SSH. A couple of times I've had
> screen corruption on the laptop's LCD display.
>
> Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin,
> and a bunch of xterms.
>
> Is there something I can do to diagnose this issue?
Only random generic troubleshooting items:
- how's your heating? screen corruption looks like memory or bus errors.
are you running powerd?
- can you set up a serial or firewire connection to it and monitor the
machine from there ("screen corruption" may also mean a kernel message
being printed in text mode, in the part of memory now mapped for
graphics - if this is the case you'll see the message over the serial
console).
signature.asc
Description: OpenPGP digital signature
Re: Understanding libpthread.so.2 undef reference error....
On Mon, 05 Nov 2007 11:43:32 +0100
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > I don't ever remember getting this error before. I am pretty sure i'm using
> > only binaries built on this machine for 7.0... have I missed anything?
> > what's the cause of this error?
> >
> > FWIW, I have compat6x installed
>
> You missed the "portupgrade -fa" step of the upgrade from 6.x to 7.x.
> Those errors come from binaries linked to both 6.x and 7.x libraries.
Hi Kris,
thanks for the explanation. I don't think I did that, as this is a 100% clean
install of 7,but maybe I bungled it somewhere.
is there a way to know what is cross linked? should I get rid of compat6x?
thanks,
Beto
_
{Beto|Norberto|Numard} Meijome
Your reasoning is excellent -- it's only your basic assumptions that are wrong.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0-BETA2 Available - regression in unionfs+cd9660
Ken Smith wrote: > The 7.0-BETA2 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using cvsup use > RELENG_7 as the branch tag. Instructions on using FreeBSD Update to > perform a binary upgrade from FreeBSD 6.x to 7.0-BETA2 will be provided > via the freebsd-stable list when available. I'm reporting a regression between BETA1 and BETA2: I can no longer mount unionfs over cd9660 file system. The setup is like this: /- on cd9660, read-only /tmp - mdmfs /tmp/etc - just a directory "mount_unionfs /tmp/etc /etc" fails with the message "/etc: operation not supported by the device". This worked fine in BETA1 but fails in BETA2, built yesterday. I don't see in cvs logs what could provoke this bug, my possible candidates are vfs_mount.c by rodrigc and possibly maybe the big commit by rwatson (trustedbsd). signature.asc Description: OpenPGP digital signature
Re: [FreeBSD 7.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
Monday 05 November 2007 11:22:30 kirjutas Stefan Lambrev: > Hi, > > Andrei Kolu wrote: > > After some experimenting with BETA1/1.5 or whatever it is I encountered > > serious problems: > > > > 1. Emergency shell on tty3 is useless- not a single command is available. > > This is install CD not fixit CD. On istall CD emergency shell becomes > useful once you actually install those commands. > Install what? How, where? Why emergency shell works on snapshot release and not on beta? To me this is a BIG * BUG not a feature. > > 2. When tried to use installcd as livecd is asked me to insert livecd > > (there is plenty of free space available on installcd- why not use that > > usefully?). > > BETA ISOs are smaller only because packages are not included, and they > will be included for FreeBSD 7.0-RELEASE. > > > I am positive I was able to use emergency shell and livecd function on > > CURRENT september snapsot just fine (i386 version though). > > Yes you can use it and now after the install process is started. > I don't want to start install process, I want to restore bootloader. # boot0cfg -B ad0 And now I have to download 500+MB to do things I did without any problem for years?! Sry, I am pissed off... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-BETA1 & 2 occasionally freezing, how to diagnose?
Hello, I've been having frequent problems with BETA1 and now BETA2 "freezing". There is no diagnostic information, nothing in /var/log/messages, nothing, just a hung interface. I cannot ssh into the machine and it appears the box ceases to communicate on SSH. A couple of times I've had screen corruption on the laptop's LCD display. Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin, and a bunch of xterms. Is there something I can do to diagnose this issue? -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_7 jerky mouse and skipping sound
On Mon, Nov 05, 2007 at 09:15:39AM +0100, [LoN]Kamikaze wrote: > Does the problem persist for you? It's gone for me, even with moused. The sound skipping went away a while ago, but desktop performance is still lousy while compiling on a UP machine. Fiddling with X's rtprio can more or less fix the problem, but it's a pain to do it manually each time. If it were a scheduler issue, it would seem like the priority of make isn't getting bumped down enough and its children aren't being spawned with the appropriate lower priority - but it happens with both schedulers for me, so I don't know what's going on. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: date/time trouble - PST came too early
On Nov 2, 2007, at 3:30 AM, Chris H. wrote: FWIW The system already knows what timezone it lives in. It simply chose to change to PST according to the /normal/ standards. What happened here in the USA, is that president Bush decided that we'd be better served here if we waited an additional week to set our clocks back one hour. So. It seems this particular server decided to ignore our president (not that I blame it) Most of us went through this *last* year when the rules took effect. Did it not affect your system last year? Basically you need to get a corrected /etc/localtime and restart any long running programs that depend on time, notably cron. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0-BETA2 Available
This is a "it works!" report. :) > In <[EMAIL PROTECTED]> > Stefan Lambrev <[EMAIL PROTECTED]> wrote: > Instead of moaning we better start testing and report problems (and > whoever can send fixes) :) Well, I installed my snapshot of 6.2-STABLE on HP ML115 server and updated by 'make world'. There seems no problem. FreeBSD/amd64 7.0-BETA2 is fine. $ uname -a FreeBSD ML115.heimat.gr.jp 7.0-BETA2 FreeBSD 7.0-BETA2 #0: Sun Nov 4 00:13:22 JST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 I added ATI Radeon X1300 on it. Xorg 7.3 works well with this video card with vesa driver. I put the /var/run/dmesg.boot of ML115 at http://heimat.jp/~nakaji/FreeBSD/ML115/dmesg.boot -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ZFS - kmem_malloc too small
Hello I'm running 7.0-BETA1 with patch http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch -- without this patch, the panic come sooner. I setup my root fs under zfs. the boot fs is under gmirror+ufs. loader.conf: #--- Tuning for ZFS - http://wiki.freebsd.org/ZFSTuningGuide vm.kmem_size="600M" # Size of kernel memory vm.kmem_size_max="600M" # Max kmem size vfs.zfs.debug="0" # ZFS - debug messages vfs.zfs.prefetch_disable="1"# ZFS - disable prefetch vfs.zfs.arc_max="128M" # ZFS - maximum ARC size : 128MB #--- Mount root filesystem from ZFS zfs_load="YES" # Load ZFS module vfs.root.mountfrom="zfs:pool0" # Root filesystem is pool0 zpool status: pool: pool0 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM pool0 ONLINE 0 0 0 mirrorONLINE 0 0 0 da0s2 ONLINE 0 0 0 da1s2 ONLINE 0 0 0 errors: No known data errors pool: pool1 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM pool1 ONLINE 0 0 0 da0s3 ONLINE 0 0 0 da1s3 ONLINE 0 0 0 errors: No known data errors pool: pool2 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM pool2 ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad4s3 ONLINE 0 0 0 ad6s3 ONLINE 0 0 0 errors: No known data errors When copying avi files (~300MB each) from pool0 to a ufs under gjournal gjournal list Geom name: gjournal 2719642309 ID: 2719642309 Providers: 1. Name: ad4s2.journal Mediasize: 49384282112 (46G) Sectorsize: 512 Mode: r1w1e2 Consumers: 1. Name: ad4s2 Mediasize: 51531766272 (48G) Sectorsize: 512 Mode: r1w1e1 Jend: 51531765760 Jstart: 49384282112 Role: Data,Journal I got: Panic String: kmem_malloc(131072): kmem_map too small: 400539648 total allocated Just before the panic, I observe a freeze of 8 sec. as by the patch. Anyway, I'm quite pleased with zfs Henri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Understanding libpthread.so.2 undef reference error....
Norberto Meijome wrote: Hi list, I'm using 7.0-BETA2 on my laptop. While building different ports, i am encountering messages like the following (in particular the last line, the others are only warnings) /usr/bin/ld: warning: libstdc++.so.5, needed by /usr/local/lib/libicui18n.so.36, may conflict with libstdc++.so.6 /usr/bin/ld: warning: libm.so.4, needed by /usr/local/lib/libicui18n.so.36, may conflict with libm.so.5 /usr/bin/ld: warning: libm.so.4, needed by /usr/local/lib/libicui18n.so.36, may conflict with libm.so.5 /usr/local/lib/compat/libpthread.so.2: undefined reference to `__malloc_lock' gmake[1]: I don't ever remember getting this error before. I am pretty sure i'm using only binaries built on this machine for 7.0... have I missed anything? what's the cause of this error? FWIW, I have compat6x installed You missed the "portupgrade -fa" step of the upgrade from 6.x to 7.x. Those errors come from binaries linked to both 6.x and 7.x libraries. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Understanding libpthread.so.2 undef reference error....
Hi list,
I'm using 7.0-BETA2 on my laptop. While building different ports, i am
encountering messages like the following (in particular the last line, the
others are only warnings)
/usr/bin/ld: warning: libstdc++.so.5, needed
by /usr/local/lib/libicui18n.so.36, may conflict with
libstdc++.so.6
/usr/bin/ld: warning: libm.so.4, needed
by /usr/local/lib/libicui18n.so.36, may conflict with libm.so.5
/usr/bin/ld:
warning: libm.so.4, needed by /usr/local/lib/libicui18n.so.36, may conflict
with libm.so.5
/usr/local/lib/compat/libpthread.so.2: undefined reference to
`__malloc_lock' gmake[1]:
I don't ever remember getting this error before. I am pretty sure i'm using
only binaries built on this machine for 7.0... have I missed anything? what's
the cause of this error?
FWIW, I have compat6x installed
thanks!!
Beto
_
{Beto|Norberto|Numard} Meijome
"With COBOL, the job description of 'computer programmer' will be a thing
of the past. Everybody will program. The boss will dictate a program to
his secretary, who will keypunch it for him."
1960's quote about the upcoming COBOL language (thx. Lance N!)
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load
Oleg Derevenetz wrote: Anyway, I looked at the ddb output already, said that it looks as either driver or hw problem with very high confidence. I think the time of the project could be spent more productive elsewere, while submitter checks his hardware, for instance, by changing controller, disks, or controller type. I already said that: 1. This controller and disks succesfully works earlier with FreeBSD 4.6.2 without any problems; Yes, as Kostik says it may be a driver problem. Or it could be a hardware problem because the driver is quite different than in 4.x, and may be exercising the hardware in a different way that provokes a hardware bug. 2. I tried to replace a disk with another one (the same model), but it doesn't help. Unfortunately, I have no another free SCSI controller (but see #1); 3. I have another AMD64 machine with different hardware (including disks and SCSI controller) that periodically suffers from the same problem. Unfortunately, that machine is in production and heavily loaded, so I can't overload it even more with INVARIANTS, WITNESS, and DIAGNOSTIC - my clients will not forgive me for that. Many different problems can have similar symptoms when you do not look closely. Indeed, the PR you are replying to is itself a completely different issue that has nothing to do with your own bug report, and someone else also replied to it with what looks like yet another completely different issue. There is no evidence so far pointing anywhere apart from the mylex controller, so that argues against the hypothesis that your second problem is the same. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load
Anyway, I looked at the ddb output already, said that it looks as either driver or hw problem with very high confidence. I think the time of the project could be spent more productive elsewere, while submitter checks his hardware, for instance, by changing controller, disks, or controller type. I already said that: 1. This controller and disks succesfully works earlier with FreeBSD 4.6.2 without any problems; 2. I tried to replace a disk with another one (the same model), but it doesn't help. Unfortunately, I have no another free SCSI controller (but see #1); 3. I have another AMD64 machine with different hardware (including disks and SCSI controller) that periodically suffers from the same problem. Unfortunately, that machine is in production and heavily loaded, so I can't overload it even more with INVARIANTS, WITNESS, and DIAGNOSTIC - my clients will not forgive me for that. -- Oleg Derevenetz <[EMAIL PROTECTED]> OOD3-RIPE Phone: +7 4732 539880 Fax: +7 4732 531415 http://www.vsi.ru CenterTelecom Voronezh ISPhttp://isp.vsi.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0-BETA2 Available
Andrei Kolu wrote: Sunday 04 November 2007 18:04:55 kirjutas Ladislav Bodnar: On Sunday 04 November 2007, Ken Smith wrote: The 7.0-BETA2 builds have completed and are on many of the FreeBSD mirror sites. If you want to update an existing machine using cvsup use RELENG_7 as the branch tag. Instructions on using FreeBSD Update to perform a binary upgrade from FreeBSD 6.x to 7.0-BETA2 will be provided via the freebsd-stable list when available. These release announcements seem to be shorter and shorter with every release. Is there a changelog to see what has changed since BETA1? If so, would you please consider linking to it in future announcements? Why hurry with untested releases? I see so many obvious bugs and human errors during release builds. Where is quality assurance or release engineering? It smells more like ALPHA development not proper releasing... Thanks for your insights, have a nice day. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load
Kostik Belousov wrote: On Sun, Nov 04, 2007 at 11:26:20PM +0100, Kris Kennaway wrote: Oleg Derevenetz wrote: Dumpdev is swap partition on da0 (single physical disk) that connected to Mylex AcceleRAID 170 RAID controller. The problem arrives when I copy large amount of files from FTP to another disk (da1) that is connected to the same RAID controller. If the driver or controller is misbehaving it could explain both problems. Any chance you can get another disk in there on a different controller to dump onto? Yes, I got IDE disk and saved kernel dump for another static hang state on it. Here is the dump: ftp://oleg.vsi.ru/private/vmcore.0.zip Is this just the vmcore, or the debugging kernel also? Both are needed to make sense of the dump. Kernel binary with kernel config is here: ftp://oleg.vsi.ru/private/kernel.zip This kernel was built statically, and no modules loaded on boot at all. -- Oleg Derevenetz <[EMAIL PROTECTED]> OOD3-RIPE Phone: +7 4732 539880 Fax: +7 4732 531415 http://www.vsi.ru CenterTelecom Voronezh ISPhttp://isp.vsi.ru That kernel doesn't appear to match with the vmcore, are you sure it is the right one? Are you able to successfully run kgdb on these locally? Besides the matching kernel, kgdb also must be build from the same sources as the kernel to provide useful information from the core dump. Anyway, I looked at the ddb output already, said that it looks as either driver or hw problem with very high confidence. I think the time of the project could be spent more productive elsewere, while submitter checks his hardware, for instance, by changing controller, disks, or controller type. Yes, at this point it does seem to be related to the mylex controller. I hear from another developer that they are not considered to be high-quality hardware. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load
On Sun, Nov 04, 2007 at 11:26:20PM +0100, Kris Kennaway wrote: > Oleg Derevenetz wrote: > >Dumpdev is swap partition on da0 (single physical disk) that > >connected to Mylex AcceleRAID 170 RAID controller. The problem > >arrives when I copy large amount of files from FTP to another disk > >(da1) that is connected to the same RAID controller. > > If the driver or controller is misbehaving it could explain both > problems. Any chance you can get another disk in there on a > different controller to dump onto? > >>> > >>>Yes, I got IDE disk and saved kernel dump for another static hang > >>>state on it. Here is the dump: > >>> > >>>ftp://oleg.vsi.ru/private/vmcore.0.zip > >> > >>Is this just the vmcore, or the debugging kernel also? Both are > >>needed to make sense of the dump. > > > >Kernel binary with kernel config is here: > > > >ftp://oleg.vsi.ru/private/kernel.zip > > > >This kernel was built statically, and no modules loaded on boot at all. > > > >-- > >Oleg Derevenetz <[EMAIL PROTECTED]> OOD3-RIPE > >Phone: +7 4732 539880 > >Fax: +7 4732 531415 http://www.vsi.ru > >CenterTelecom Voronezh ISPhttp://isp.vsi.ru > > > > > > That kernel doesn't appear to match with the vmcore, are you sure it is > the right one? Are you able to successfully run kgdb on these locally? Besides the matching kernel, kgdb also must be build from the same sources as the kernel to provide useful information from the core dump. Anyway, I looked at the ddb output already, said that it looks as either driver or hw problem with very high confidence. I think the time of the project could be spent more productive elsewere, while submitter checks his hardware, for instance, by changing controller, disks, or controller type. pgpEc2mqJT3zK.pgp Description: PGP signature
FreeBSD hangs on Dell PE2850 needs usb keyboard to revive
Hi , I am facing a strange but critical issue. I have a FreeBSD 6.2 server ,this server runs on PE2850 with 4G ram and Dual Xeon's . Every once in a while the server will just hang , no network connectivity or anything else. if i plugin a USB keyboard , the server will come back to life as if nothing happend. the server works fine and with out a problem until next time. I tried diabeling ACPI but that did not change a thing. I have enbaled all *.* to all.log and been digging through logs to find a solution with no luck. at this point I am open to ANY suggestion . my dmesg output after keyboard inserted : ukbd0: DELL DELL USB Keyboard, rev 1.10/1.05, addr 2, iclass 3/1 kbd2 at ukbd0 my hardware : Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Sun Sep 2 14:49:17 GMT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CARP WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2783.82-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400> Logical CPUs per core: 2 real memory = 4026400768 (3839 MB) avail memory = 3942158336 (3759 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic1: Changing APIC ID to 9 ioapic1: Assuming intbase of 16 ioapic2: Changing APIC ID to 10 ioapic2: Assuming intbase of 32 ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard ioapic2 irqs 32-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cpu0 on motherboard cpu1 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib0: unable to route slot 15 INTA pci0: at device 4.0 (no driver attached) pci0: at device 4.1 (no driver attached) pci0: at device 4.2 (no driver attached) pci0: at device 14.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8b0-0x8bf at device 15.1 on pci0 ata0: on atapci0 ata1: on atapci0 ohci0: mem 0xfe10-0xfe100fff irq 5 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered isab0: at device 15.3 on pci0 isa0: on isab0 pcib3: pcibus 3 on motherboard pci3: on pcib3 bge0: mem 0xfcf1-0xfcf1 irq 28 at device 6.0 on pci3 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:11:43:d6:d0:e1 bge0: [GIANT-LOCKED] bge1: mem 0xfcf0-0xfcf0 irq 29 at device 8.0 on pci3 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:11:43:d6:d0:e2 bge1: [GIANT-LOCKED] pcib4: pcibus 4 on motherboard pci4: on pcib4 pcib5: at device 8.0 on pci4 pci5: on pcib5 aac0: mem 0xf000-0xf7ff irq 30 at device 8.1 on pci4 aac0: [FAST] aac0: Adaptec Raid Controller 2.0.0-1 pcib1: pcibus 1 on motherboard pci1: on pcib1 pcib2: pcibus 2 on motherboard pci2: on pcib2 pmtimer0 on isa0 orm0: at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xec000-0xe on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) ukbd0: DELL DELL USB Keyboard, rev 1.10/1.05, addr 2, iclass 3/1 kbd2 at ukbd0 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. acd0: CDROM at ata0-master UDMA33 aacd0: on aac0 aacd0: 69425MB (142182656 sectors) SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/aacd0s1a Accounting enabled ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0-BETA2 Available
Hi, Andrei Kolu wrote: Sunday 04 November 2007 18:04:55 kirjutas Ladislav Bodnar: On Sunday 04 November 2007, Ken Smith wrote: The 7.0-BETA2 builds have completed and are on many of the FreeBSD mirror sites. If you want to update an existing machine using cvsup use RELENG_7 as the branch tag. Instructions on using FreeBSD Update to perform a binary upgrade from FreeBSD 6.x to 7.0-BETA2 will be provided via the freebsd-stable list when available. These release announcements seem to be shorter and shorter with every release. Is there a changelog to see what has changed since BETA1? If so, would you please consider linking to it in future announcements? Why hurry with untested releases? I see so many obvious bugs and human errors during release builds. Where is quality assurance or release engineering? It smells more like ALPHA development not proper releasing... IMHO It will be better if you summarize all those BUGs that you see. Human errors can always happen. I guess BETA2 comes so short only because there was few major problems with BETA1, and BETA1.5 changed version to BETA1 after update, which was little weird, hence the need to bump version. So for me BETA2 is actually the real BETA1 :) I'm not part of re@ but this seems reasonable explanation. Also have in mind that this is voluntary project, and I think that the resources that it have are well used. Don't you think so? BTW snapshots are done every month, so it's just time for the next snapshot, that is called BETA2 ... Instead of moaning we better start testing and report problems (and whoever can send fixes) :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD 7.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
Hi, Andrei Kolu wrote: After some experimenting with BETA1/1.5 or whatever it is I encountered serious problems: 1. Emergency shell on tty3 is useless- not a single command is available. This is install CD not fixit CD. On istall CD emergency shell becomes useful once you actually install those commands. 2. When tried to use installcd as livecd is asked me to insert livecd (there is plenty of free space available on installcd- why not use that usefully?). BETA ISOs are smaller only because packages are not included, and they will be included for FreeBSD 7.0-RELEASE. I am positive I was able to use emergency shell and livecd function on CURRENT september snapsot just fine (i386 version though). Yes you can use it and now after the install process is started. Andrei ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[FreeBSD 7.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
After some experimenting with BETA1/1.5 or whatever it is I encountered serious problems: 1. Emergency shell on tty3 is useless- not a single command is available. 2. When tried to use installcd as livecd is asked me to insert livecd (there is plenty of free space available on installcd- why not use that usefully?). I am positive I was able to use emergency shell and livecd function on CURRENT september snapsot just fine (i386 version though). Andrei ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0-BETA2 Available
Sunday 04 November 2007 18:04:55 kirjutas Ladislav Bodnar: > On Sunday 04 November 2007, Ken Smith wrote: > > The 7.0-BETA2 builds have completed and are on many of the FreeBSD > > mirror sites. If you want to update an existing machine using cvsup use > > RELENG_7 as the branch tag. Instructions on using FreeBSD Update to > > perform a binary upgrade from FreeBSD 6.x to 7.0-BETA2 will be provided > > via the freebsd-stable list when available. > > These release announcements seem to be shorter and shorter with every > release. Is there a changelog to see what has changed since BETA1? If so, > would you please consider linking to it in future announcements? > Why hurry with untested releases? I see so many obvious bugs and human errors during release builds. Where is quality assurance or release engineering? It smells more like ALPHA development not proper releasing... IMHO ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Dimitry Andric wrote: Andreas Rudisch wrote: [...] There's no floppy drive in the X series ThinkPads, so you'll end up using an USB floppy drive. This will probably lead to the same BTX loader problem as with USB CD-ROM drives. The same is probably applicable to booting from USB sticks, and I'm not even sure FreeBSD supports booting off those. About a year ago I created USB stick with GRUB instead of BTX loader for booting on CD-ROM less Sun Fire servers. It works well. So this is the possible way to go. You can create just bootable USB stick from miniboot ISO (30MB) and then install from internal CD-ROM or from network (FTP, NFS...). Or you can create completely working instalation media with packeges etc on USB stick bigger than 512MB. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_7 jerky mouse and skipping sound
Marc Fonvieille wrote: > On Thu, Oct 18, 2007 at 05:53:47PM +0200, [LoN]Kamikaze wrote: >> Anish Mistry wrote: >>> On Thursday 18 October 2007, Marc Fonvieille wrote: On Wed, Oct 17, 2007 at 12:28:30PM -0400, Anish Mistry wrote: > I just updated to RELENG_7 from 6.2 and I'm running into some > really annoying issues with jerky mouse movement and skipping > sound. This seems to be similar to: > Re: SCHED_4BSD in RELENG_7 disturbs workflow > This happens both with 4BSD and ULE. > > I seems to happen when I'm compiling ports and a new cc/bzip2/sh > process fires off (I'm just watching top), I'll get the > skip/freezeup. [...] Using ULE and UP kernel (i.e. without SMP etc.) helped a bit the things but it's still very annoying to use firefox during ports build. I see this lag/freeze on all boxes I use with 7.0, but it's true that with a fast machine people can ignore the problem, it's less obvious than with a 1GHz box for example. >>> Yeah, I'm still seeing this behavior. Does anyone have suggestions on >>> debugging? >>> >>> Thanks, >>> >> I did post the solution in this thread. > > It has nothing to do with the mouse. > Does the problem persist for you? It's gone for me, even with moused. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
