Error messages when booting up machine and starting KDE
I have observed these messages being written to the system log when initially booting up the machine and then starting KDE. Oct 6 08:16:09 scorpio dbus[5896]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper) Oct 6 08:16:09 scorpio dbus[5896]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Oct 6 08:16:09 scorpio dbus[5896]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Oct 6 08:16:09 scorpio dbus[5896]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Oct 6 08:16:09 scorpio console-kit-daemon[5917]: WARNING: kvm_getenvv failed: Oct 6 08:17:32 scorpio console-kit-daemon[5917]: WARNING: Error waiting for native console 1 activation: Device not configured Oct 6 08:18:13 scorpio dbus[5896]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) Oct 6 08:18:13 scorpio dbus[5896]: [system] Successfully activated service 'org.freedesktop.UPower' Oct 6 08:18:14 scorpio dbus[5896]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Oct 6 08:18:14 scorpio org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave. Oct 6 08:18:14 scorpio dbus[5896]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Oct 6 08:18:20 scorpio kernel: pid 6286 (kwin_opengl_test), uid 1001: exited on signal 11 (core dumped) Oct 6 08:18:40 scorpio dbus[5896]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Oct 6 08:18:40 scorpio org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave. Oct 6 08:18:40 scorpio dbus[5896]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Oct 6 08:18:46 scorpio dbus[5896]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out Oct 6 08:18:55 scorpio pulseaudio[6346]: module.c: module-detect is deprecated: Please use module-udev-detect instead of module-detect! Oct 6 08:18:55 scorpio pulseaudio[6346]: oss-util.c: '/dev/dsp0' doesn't support full duplex Oct 6 08:18:55 scorpio pulseaudio[6346]: oss-util.c: '/dev/dsp1' doesn't support full duplex Oct 6 08:18:55 scorpio pulseaudio[6346]: oss-util.c: '/dev/dsp2' doesn't support full duplex Oct 6 08:18:55 scorpio pulseaudio[6346]: oss-util.c: '/dev/dsp3' doesn't support full duplex Oct 6 08:18:55 scorpio pulseaudio[6346]: oss-util.c: '/dev/dsp6' doesn't support full duplex Oct 6 08:18:56 scorpio pulseaudio[6352]: pid.c: Daemon already running. I am particularly interested in the two "WARNING" messages (5 & 6); the "core dump" (item 12); the "timed out" (item 16) and the last one, although that one appears to be harmless. Is there something I should be doing to correct these apparent problems? -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Can I avoid the display of pkg-messages in portmaster?
On 05/12/2013 12:37 AM, Leslie Jensen wrote: > > > I do some work on remote machines and sometimes I have a need to execute > additional commands after for example a portmaster -a command. > > Normally I use the "&&" to separate commands but this does not work when > portmaster displays pkg-messages. > > I cannot see in the portmaster manpage that there's a possibility to > make the choice on displaying pkg-messages. > > Maybe a suggestion to further enhance portmaster in the future. > > To work around this I was thinking of maybe making a script that ran > > portmaster -a then a command to "press space" until one is sure that all > messages has been displayed. > > On this I could need some help. My scripting skills are not that good. To avoid interaction when scripting or logging portmaster, in addition to the --no-confirm option, I usually set the following environment variables prior to invocation: BATCH=yes PAGER=cat The former should avoid any build-time port interaction (and mark the port BROKEN if it must, so I can deal with it manually); the latter causes portmaster to use 'cat' instead of 'more' to display the pkg-messages afterwards. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Can I avoid the display of pkg-messages in portmaster?
I do some work on remote machines and sometimes I have a need to execute additional commands after for example a portmaster -a command. Normally I use the "&&" to separate commands but this does not work when portmaster displays pkg-messages. I cannot see in the portmaster manpage that there's a possibility to make the choice on displaying pkg-messages. Maybe a suggestion to further enhance portmaster in the future. To work around this I was thinking of maybe making a script that ran portmaster -a then a command to "press space" until one is sure that all messages has been displayed. On this I could need some help. My scripting skills are not that good. Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Procmail Decoding Mime Messages
Polytropon writes: > On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote: >> Is there a filter that one can run in procmail in which >> base64 encoded data go in and text comes out so one can allow >> procmailrc to do its work? >> [...] >> Is there anything which will take a raw email message >> and spit out linear strings which can be processed like normal >> text? > > I think this is possible with uudecode, in this case b64decode. > See "man uuencode" for more information. uuencode predates MIME. Although there are MIME types defined for it, the base-system tools don't handle the MIME headers or section marking. For this purpose, a MIME-aware tool (such as ripmime, or metamail, or mmencode) will be much more useful as part of an automated filtering system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Procmail Decoding Mime Messages
On Wed, 24 Apr 2013, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? mail/maildrop has a reformime program which may be useful. maildrop itself is like a better and easier to use procmail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Procmail Decoding Mime Messages
Polytropon wrote:
> On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote:
> > Is there a filter that one can run in procmail in which
> > base64 encoded data go in and text comes out so one can allow
> > procmailrc to do its work?
Good question, I havent tried that yet, (but should),
but I have been demiming both to help majordomo on servers, & via procmail
on local (to reduce bulk on my future archives of personal mail).
2 tools worth knowing in /usr/ports/mail/ : demime emil
A few notes from my
http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/jhs/mail/Makefile.local
(where I've also more notes on eg much hated quoted-printable )
SUBDIR += emil
# A candidate to be assesed for stripping quoted-printable from
# majordomo on server, to help cluless people.
# Something needed to replace demime as demime has been removed.
# SUBDIR += mime4j
# "It won't do any decoding of base64 or quoted-printable
#encoded header fields and bodies."
SUBDIR += demime
# For majordomo on list servers,
# For all the many lazy & incompetents who cant turn off sending
# HTML to mail lists, despite having had a decade to learn.
# (& for a few people who do understand they should, have tried to, but
# can''t find where to turn off their HTML, if their ISP even allows.
# Missing in FreeBSD-9.1-RELEASE so see also SUBDIR += mail/emil
> > Is there anything which will take a raw email message
> > and spit out linear strings which can be processed like normal
> > text?
See man emil ; man demime
PS Trying to get procmail to work with a macro with a pipe defined
after + $RCVSTOREUNSEEN, was a long pain & I failed so I use a
longer version below which works, appended for syntax example.
RCVSTORE=/usr/local/libexec/nmh/rcvstore
RCVSTOREUNSEEN="$RCVSTORE -nounseen"
# A 2nd copy, just text, stripped of MIME enclosures is
# stored in $PRI_MAIL by $RCVSTOREUNSEEN
# The 2nd copy is stored with $RCVSTORE -nounseen so I dont have to
# click the archive copy from within exmh.
NOMIME="/usr/local/bin/demime -8 -"
# Demime is not in current after 9.1-RELEASE
# To not demime instead use NOMIME=cat
# NOMIME=cat
# NOMIME=/usr/local/bin/emil
# Emil converts a .jpg MIME to a uuencoded appended without MIME
# I can not seem to achieve something like this:
# XYZ="$NOMIME | $RCVSTOREUNSEEN"
{
:0 cw
| $NOMIME | $RCVSTOREUNSEEN +$PRI_MAIL/my/archive
:0 wc
| $RCVSTORE +$INBOX_PLAIN
}
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
Reply below not above, like a play script. Indent old text with "> ".
Send plain text. No quoted-printable, HTML, base64, multipart/alternative.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Procmail Decoding Mime Messages
On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote: > Is there a filter that one can run in procmail in which > base64 encoded data go in and text comes out so one can allow > procmailrc to do its work? > [...] > Is there anything which will take a raw email message > and spit out linear strings which can be processed like normal > text? I think this is possible with uudecode, in this case b64decode. See "man uuencode" for more information. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Procmail Decoding Mime Messages
Forgot to cc the list. On 04/24/2013 04:47 PM, Ryan Frederick wrote: I believe mimencode is in ports as converters/mmencode. It is also included as part of mail/metamail. Ryan On 04/24/2013 04:07 PM, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? Thank you. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Procmail Decoding Mime Messages
Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? Thank you. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re-sending selected e-mail messages
> Date: Thu, 14 Feb 2013 00:49:13 +0100
> From: Polytropon
> To: FreeBSD Questions
> Subject: Re-sending selected e-mail messages
>
> I need a way to automatically re-sent stored e-mail messages
> according to some criteria and like to ask for advice or
> suggestions for an already existing solution before I start
> reinventing the wheel. :-)
>
> The messages in question are stored in MH format.
>
> What is the easiest way to do this without reinventing the wheel,
> or should I? :-)
procmail is your friend.
cat ~/sent* |procmail -f resendrc
where resendrc is:
emailaddr="f...@bar.baz"
:0
*^To: *${emailaddr}
*^Subject:\/.*$
| formail -I "Subject: {resend} ${MATCH}" | $SENDMAIL -oi -t
Delete the 'formail' if you want the Subject: unmolested.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re-sending selected e-mail messages
On Feb 13, 2013 3:49 PM, "Polytropon" wrote: > > I need a way to automatically re-sent stored e-mail messages > according to some criteria and like to ask for advice or > suggestions for an already existing solution before I start > reinventing the wheel. :-) > > The messages in question are stored in MH format. This is a > tree where a mailbox equals a directory, and the individual > files in that directory equal the messages. They are numbered > 1, 2, 3, 4, ..., and so on. Each message is in > > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > or > > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > or maybe even > > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > text format. Some of them might contain an attachment, which > is "included" in the file with something like > > --Multipart=... > Content-Type: ...; > name="..." > Content-Disposition: attachment; > filename="..." > Content-Transfer-Encoding: base64 > --Multipart=...--- > > Some messages are "fully multipart". > > So when iterating on ~/Mail/sent/1,2,3,4,5,... I get all the > messages. Each third line, "To:", is the criteria to look at. > If it matches a given recipient, the mail should be sent again. > This can easily be done by the system's mailer which is properly > configured (and uses ISP's MX), so | mail -s "maybe new subject" > is possible. The message should already be properly pre-composed. > > What is the easiest way to do this without reinventing the wheel, > or should I? :-) > > > > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " freebsd-questions-unsubscr...@freebsd.org" I'm working on an email related project, you might hack it to work for you. https://github.com/waitman/elmboxo check out pmess.c it can do a single message. (the easy way to feed pmess a single message is actually to feed the single message to elmboxo as it is coded) anyway its built to stuff them in a mongodb db, but I.m working on a free nosql solution that works for my project. you can just chuck all those bits. an idea. Waitman Gobble San Jose California ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re-sending selected e-mail messages
Kurt Buff writes: > On Wed, Feb 13, 2013 at 3:49 PM, Polytropon wrote: >> I need a way to automatically re-sent stored e-mail messages >> according to some criteria and like to ask for advice or >> suggestions for an already existing solution before I start >> reinventing the wheel. :-) [...] > Perhaps mini_sendmail? Seems fairly capable, and scriptable. Or maybe procmail's tools (I'm thinking in particular of procmail, although there are some other bits and bobs that might relate also) would serve the particular selection criteria? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re-sending selected e-mail messages
On Wed, Feb 13, 2013 at 3:49 PM, Polytropon wrote: > I need a way to automatically re-sent stored e-mail messages > according to some criteria and like to ask for advice or > suggestions for an already existing solution before I start > reinventing the wheel. :-) > > The messages in question are stored in MH format. This is a > tree where a mailbox equals a directory, and the individual > files in that directory equal the messages. They are numbered > 1, 2, 3, 4, ..., and so on. Each message is in > > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > or > > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > or maybe even > > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > text format. Some of them might contain an attachment, which > is "included" in the file with something like > > --Multipart=... > Content-Type: ...; > name="..." > Content-Disposition: attachment; > filename="..." > Content-Transfer-Encoding: base64 > --Multipart=...--- > > Some messages are "fully multipart". > > So when iterating on ~/Mail/sent/1,2,3,4,5,... I get all the > messages. Each third line, "To:", is the criteria to look at. > If it matches a given recipient, the mail should be sent again. > This can easily be done by the system's mailer which is properly > configured (and uses ISP's MX), so | mail -s "maybe new subject" > is possible. The message should already be properly pre-composed. > > What is the easiest way to do this without reinventing the wheel, > or should I? :-) Perhaps mini_sendmail? Seems fairly capable, and scriptable. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re-sending selected e-mail messages
I need a way to automatically re-sent stored e-mail messages
according to some criteria and like to ask for advice or
suggestions for an already existing solution before I start
reinventing the wheel. :-)
The messages in question are stored in MH format. This is a
tree where a mailbox equals a directory, and the individual
files in that directory equal the messages. They are numbered
1, 2, 3, 4, ..., and so on. Each message is in
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
or
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
or maybe even
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
text format. Some of them might contain an attachment, which
is "included" in the file with something like
--Multipart=...
Content-Type: ...;
name="..."
Content-Disposition: attachment;
filename="..."
Content-Transfer-Encoding: base64
--Multipart=...---
Some messages are "fully multipart".
So when iterating on ~/Mail/sent/1,2,3,4,5,... I get all the
messages. Each third line, "To:", is the criteria to look at.
If it matches a given recipient, the mail should be sent again.
This can easily be done by the system's mailer which is properly
configured (and uses ISP's MX), so | mail -s "maybe new subject"
is possible. The message should already be properly pre-composed.
What is the easiest way to do this without reinventing the wheel,
or should I? :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: What tool is generating the various normal port install messages?
On 11/02/12 21:41, Ronald F. Guilmette wrote: > > I ran into something that looks like a small bug relating to install > of the ffmpeg port. (See below.) I will be filing of formal PR (shortly) > to report this bug, but usually, I do try to spend at least a few > minutes before I file any formal PR, trying to work out for myself > what the proper solution or workaround is. In this case however > I am utterly stumped. I can't even get to first base. This has > made me realize that I know a lot less about the FreeBSD ports > building system than I thought I did. > > So I'm asking: Which tool (or piece of code) is it, exactly, that > prints all these normal build messages when building or installing > a port? I mean specifically these ones: > > ===> Generating temporary packing list > > INSTALL <...> > > STRIP <...> > > Who generates those message? I don't know squat about the ports build but the Generating... string is from /usr/ports/Mk/bsd.port.mk Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
What tool is generating the various normal port install messages?
I ran into something that looks like a small bug relating to install of the ffmpeg port. (See below.) I will be filing of formal PR (shortly) to report this bug, but usually, I do try to spend at least a few minutes before I file any formal PR, trying to work out for myself what the proper solution or workaround is. In this case however I am utterly stumped. I can't even get to first base. This has made me realize that I know a lot less about the FreeBSD ports building system than I thought I did. So I'm asking: Which tool (or piece of code) is it, exactly, that prints all these normal build messages when building or installing a port? I mean specifically these ones: ===> Generating temporary packing list INSTALL <...> STRIP <...> Who generates those message? I scrounged around for a short while within the /usr/share/mk directory and I was just not able to find anyplace where these messages are being generated, so I'm stumped. Oh yea, and the ports(7) man page is of no help either. (In short, there does seem to me to be some important stuff missing from TFM. And we can include in that any & all information about how to properly build & install any arbitrary port with debugging information preserved.) = ... % cd /usr/ports/multimedia/ffmpeg % make WITH_DEBUG=yes STRIP= deinstall ... % make WITH_DEBUG=yes STRIP= reinstall ===> Installing for ffmpeg-0.7.13_6,1 ===> ffmpeg-0.7.13_6,1 depends on shared library: aacplus.2 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: faac.0 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: freetype.9 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: mp3lame.0 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: opencv_imgproc.2 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: openjpeg.2 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: schroedinger-1.0.11 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: theora.0 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: va.1 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: vorbisenc.2 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: vpx.1 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: x264.125 - found ===> ffmpeg-0.7.13_6,1 depends on shared library: xvidcore.4 - found ===> Generating temporary packing list INSTALL doc/ffmpeg.1 INSTALL doc/ffprobe.1 INSTALL libavdevice/libavdevice.a INSTALL libavdevice/libavdevice.so STRIP install-libavdevice-shared gmake: *** [install-libavdevice-shared] Segmentation fault: 11 (core dumped) *** Error code 2 Stop in /usr/ports/multimedia/ffmpeg. *** Error code 1 Stop in /usr/ports/multimedia/ffmpeg. *** Error code 1 Stop in /usr/ports/multimedia/ffmpeg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Strange system messages in 8.3
Hi, > Two night ago, I upgraded my main server to FreeBSD 8.3 and since, I > get those messages: > > Message from syslogd@banyan at Oct 19 01:15:32 ... > banyan kernel: ) >[...] > I have all my servers running the same release, and this is the only > on exibiting such behavious. > > FreeBSD banyan.cs.ait.ac.th 8.3-RELEASE-p4 FreeBSD 8.3-RELEASE-p4 #5: > Wed Oct 17 18:32:54 ICT 2012 > r...@banyan.cs.ait.ac.th:/usr/obj/usr/src/sys/CSIM amd64 > > The custom kernel only includes quota, nothing fancy, rest is generic. > > What these messages could be? I have updated to Samba 3.6 and still get the following errors. Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.566992, 1, pid=17753, effective(7186, 97), real(0, 0)] printing/printer_list.c:94(printer_list_get_printer) Oct 24 09:49:45 banyan smbd[17753]: Failed to fetch record! Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.606964, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/fault.c:51(fault_report) Oct 24 09:49:45 banyan smbd[17753]: === Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.606994, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/fault.c:52(fault_report) Oct 24 09:49:45 banyan smbd[17753]: INTERNAL ERROR: Signal 11 in pid 17753 (3.6.7) Oct 24 09:49:45 banyan smbd[17753]: Please read the Trouble-Shooting section of the Samba3-HOWTO Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.607020, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/fault.c:54(fault_report) Oct 24 09:49:45 banyan kernel: pid Oct 24 09:49:45 banyan kernel: 53O Oct 24 09:49:45 banyan kernel: 2 Oct 24 09:49:45 banyan kernel: (<1s18m>bd4 Oct 24 09:49:45 banyan kernel: 9:), Oct 24 09:49:45 banyan kernel: u0:4 Oct 24 09:49:45 banyan kernel: :4 e Oct 24 09:49:45 banyan syslogd: /dev/ttyp4: No such file or directory Oct 24 09:49:45 banyan syslogd: /dev/olivier:: No such file or directory Oct 24 09:49:45 banyan kernel: xi<1te18d >o5 Oct 24 09:49:45 banyan kernel: <6ba>nn Oct 24 09:49:45 banyan kernel: s<1i1g8>nay Oct 24 09:49:45 banyan kernel: an<6> l Oct 24 09:49:45 banyan kernel: 6<1 Oct 24 09:49:45 banyan kernel: 18>smbd[17753]: [2012/10/24 09:49:45.607020, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/fault.c:54(fault_report) Oct 24 09:49:45 banyan smbd[17753]: Oct 24 09:49:45 banyan smbd[17753]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.607044, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/fault.c:55(fault_report) Oct 24 09:49:45 banyan smbd[17753]: === Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.607068, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/util.c:1117(smb_panic) Oct 24 09:49:45 banyan smbd[17753]: PANIC (pid 17753): internal error Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.607142, 0, pid=17753, effective(7186, 97), real(0, 0)] lib/util.c:1221(log_stack_trace) Oct 24 09:49:45 banyan smbd[17753]: BACKTRACE: 0 stack frames: Oct 24 09:49:45 banyan smbd[17753]: [2012/10/24 09:49:45.607191, 0, pid=17753, effective(0, 0), real(0, 0)] lib/fault.c:416(dump_core) Oct 24 09:49:45 banyan smbd[17753]: dumping core in /var/log/samba/cores/smbd Oct 24 09:49:45 banyan smbd[17753]: Oct 24 09:49:45 banyan smbd[57965]: [2012/10/24 09:49:45.678295, 0, pid=57965, effective(0, 0), real(0, 0)] smbd/server.c:433(smbd_accept_connection) Oct 24 09:49:45 banyan smbd[57965]: open_sockets_smbd: accept: Software caused connection abort Help will be highly welcome. Best regards, Olivier > > Best regards, > > Olivier > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Strage system messages in 8.3
Hi, Two night ago, I upgraded my main server to FreeBSD 8.3 and since, I get those messages: Message from syslogd@banyan at Oct 19 01:15:32 ... banyan kernel: ) Message from syslogd@banyan at Oct 19 01:19:31 ... banyan kernel: :1b Message from syslogd@banyan at Oct 19 07:40:00 ... banyan kernel: 26, Message from syslogd@banyan at Oct 19 08:39:00 ... banyan kernel: 70t Message from syslogd@banyan at Oct 19 09:36:24 ... banyan kernel: ]:d Message from syslogd@banyan at Oct 19 09:59:45 ... banyan kernel: :5d I have all my servers running the same release, and this is the only on exibiting such behavious. FreeBSD banyan.cs.ait.ac.th 8.3-RELEASE-p4 FreeBSD 8.3-RELEASE-p4 #5: Wed Oct 17 18:32:54 ICT 2012 r...@banyan.cs.ait.ac.th:/usr/obj/usr/src/sys/CSIM amd64 The custom kernel only includes quota, nothing fancy, rest is generic. What these messages could be? Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
HWPstate error messages
Good morning - A couple of months past I wrote about an error message I was receiving. It was an hwpstate error message concerning setting the frequency of my AMD FX 8120 CPU. Ian Stewart seemed especially interested. I find that by enabling the HPC option in my BIOS [high performance computing] that the messages stop appearing. I have confirmed it with dmesg. Thanks for your interest. Steve -- Steve Poetry and commentary on the war; http://www.blueleafsyndicate.org Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages not reaching the lists
On Fri, 29 Jun 2012 05:55:20 -0500 Conrad J. Sabatier articulated: > Yes, I went and checked my options for questions@ and saw at the top > of the page that they had had a number of bounced e-mails from my > address recently. My computer was down for about a week or so > earlier this month (had to be repaired). I'm not sure what this > means exactly in terms of how the list server manages my > subscription, but perhaps it's being tentatively cautious and just > not sending any of my list submissions back to me(?). I don't know. Now this is the reason that you should have had some sort of backup plan in place in case your mail server goes down. There are methods of handling this problem and I am sure if you started a new thread and requested help that many knowledgeable users would be willing to lend you their expertise. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Revenge is a form of nostalgia. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages not reaching the lists
On Fri, 29 Jun 2012 04:55:51 -0500 (CDT) Robert Bonomi wrote: > > Damien Fleuriot wrote: > > On 6/29/12 6:40 AM, Conrad J. Sabatier wrote: > > > Lately I've been noticing that almost without fail, any messages > > > I send to the FreeBSD mailing lists never actually appear on the > > > list. > > > > > > We'll see if this one shows up. :-) > > > > I've been experiencing the same issue for a long time. > > > > My messages are sent, people seem to actually receive them, but I > > don't, although my subscription options state that I should receive > > copies of my own messages. > > One 'obvious' thing to try -- > Change the options so as to _not_ get copies of your own messages. > *SAVE* changes. > Change the options back. > Save again. Yes, I went and checked my options for questions@ and saw at the top of the page that they had had a number of bounced e-mails from my address recently. My computer was down for about a week or so earlier this month (had to be repaired). I'm not sure what this means exactly in terms of how the list server manages my subscription, but perhaps it's being tentatively cautious and just not sending any of my list submissions back to me(?). I don't know. I didn't actually change any settings while I was there, but that might be worth a try. We'll see if that helps. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages not reaching the lists
Damien Fleuriot wrote: > On 6/29/12 6:40 AM, Conrad J. Sabatier wrote: > > Lately I've been noticing that almost without fail, any messages I send > > to the FreeBSD mailing lists never actually appear on the list. > > > > We'll see if this one shows up. :-) > > I've been experiencing the same issue for a long time. > > My messages are sent, people seem to actually receive them, but I don't, > although my subscription options state that I should receive copies of > my own messages. One 'obvious' thing to try -- Change the options so as to _not_ get copies of your own messages. *SAVE* changes. Change the options back. Save again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages not reaching the lists
On Fri, 29 Jun 2012 11:24:56 +0200, Damien Fleuriot wrote: > On 6/29/12 6:40 AM, Conrad J. Sabatier wrote: >> Lately I've been noticing that almost without fail, any messages I send >> to the FreeBSD mailing lists never actually appear on the list. >> >> Just wondering if maybe my ISP (cox.net) has been flagged as a known >> spam source, or what? >> >> This is very strange! I'm still subscribed to all of the same lists >> I've been on for quite some time, and am receiving the lists' mail just >> fine. It's just my own messages that never show up here. >> >> We'll see if this one shows up. :-) >> >> > > I've been experiencing the same issue for a long time. > > My messages are sent, people seem to actually receive them, but I don't, > although my subscription options state that I should receive copies of > my own messages. I'm reading both your messages on gmane vi a newsreader (Pan) - my preferred method. No issues whatever. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages not reaching the lists
On 6/29/12 6:40 AM, Conrad J. Sabatier wrote: > Lately I've been noticing that almost without fail, any messages I send > to the FreeBSD mailing lists never actually appear on the list. > > Just wondering if maybe my ISP (cox.net) has been flagged as a known > spam source, or what? > > This is very strange! I'm still subscribed to all of the same lists > I've been on for quite some time, and am receiving the lists' mail just > fine. It's just my own messages that never show up here. > > We'll see if this one shows up. :-) > I've been experiencing the same issue for a long time. My messages are sent, people seem to actually receive them, but I don't, although my subscription options state that I should receive copies of my own messages. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Messages not reaching the lists
Lately I've been noticing that almost without fail, any messages I send to the FreeBSD mailing lists never actually appear on the list. Just wondering if maybe my ISP (cox.net) has been flagged as a known spam source, or what? This is very strange! I'm still subscribed to all of the same lists I've been on for quite some time, and am receiving the lists' mail just fine. It's just my own messages that never show up here. We'll see if this one shows up. :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: disable console messages
On Wed, 16 May 2012 00:27:07 -0700, mahdieh salamat wrote: > hi all. how I can disbale console messages and clear screen on boot? > Thanks The console messages can be suppressed by commenting out the line *.err;kern.warning;auth.notice;mail.crit/dev/console in /etc/syslog.conf; if you want the messages redirected to a file (instead of the screen), just provide a different target, such as *.err;kern.*;auth.notice;mail.crit;console.info/var/log/console.log Make sure /var/log/console.log does exist: run # touch /var/log/console.log There are more useful examples in that file. See "man 5 syslog.conf" for details. To also silence the kernel, you could add boot_mute="YES" or (and?) consolse="nullconsole" to /boot/loader.conf. See "man 8 loader" and "man 5 loader.conf" and "less /boot/defaults/loader.conf" for details. Finally: Add the command "clear" or "/usr/bin/tput clear" at the end of the /etc/rc script (not very clean, but works). A quick web search brings up some inspiration: http://lists.freebsd.org/pipermail/freebsd-questions/2003-October/022911.html http://forums.freebsd.org/showthread.php?t=10341 http://forums.freebsd.org/showthread.php?p=58256#post58256 You'll find a suggestion there on how to avoid fiddling with the /etc/rc boot script (which should stay untouched due to many reasons). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
disable console messages
hi all. how I can disbale console messages and clear screen on boot? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
4294967287 messages downloaded - Thunderbird
Hello list! What and why is this? 4294967287 messages downloaded It does not make sense. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sudo log messages
Коньков Евгений writes: > Здравствуйте, Polytropon. > > Вы писали 4 декабря 2011 г., 15:41:45: > > P> On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: >>> Tell me please how to stop sudo to food /var/log/messages? > > P> ADDITION: Of course I meant /usr/local/etc/sutoers, > P> NOT sudo.conf. > > P> Instead of logging via syslog (to /var/log/messages), > P> why not use a specific log file for sudo? Add those > P> lines to the sudoers file: > > P> Defaults logfile=/var/log/sudo.log > P> Defaults !syslog > > P> Make sure /var/log/sudo.log exists, and maybe use > P> newsyslog.conf to deal with log rotation and archiving. > P> However, you can easily purge sudo log information > P> this way, if required. > > P> The file /usr/local/share/doc/sudo/sample.sudoers > P> contains an example. > > yes, that is not problem, but I want to control logging in one place > not in each config file of service I have ran on machine. > > I have thought that this > !sudo > *.* /var/log/sudo.log > will take off logging in /var/log/messages but this work as > log to /var/log/messages and to /var/log/sudo.log =(( You are not clear about what you really want. If you want it to log to auth.log instead of messages, then you can use the following in your sudoers file: Defaults syslog=authpriv The sample file that was mentioned earlier is one source for information, but the best source is the sudoers(5) man page. Just search it for syslog and you will find several settings. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re[2]: sudo log messages
Здравствуйте, Polytropon. Вы писали 4 декабря 2011 г., 15:41:45: P> On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: >> Tell me please how to stop sudo to food /var/log/messages? P> ADDITION: Of course I meant /usr/local/etc/sutoers, P> NOT sudo.conf. P> Instead of logging via syslog (to /var/log/messages), P> why not use a specific log file for sudo? Add those P> lines to the sudoers file: P> Defaults logfile=/var/log/sudo.log P> Defaults !syslog P> Make sure /var/log/sudo.log exists, and maybe use P> newsyslog.conf to deal with log rotation and archiving. P> However, you can easily purge sudo log information P> this way, if required. P> The file /usr/local/share/doc/sudo/sample.sudoers P> contains an example. yes, that is not problem, but I want to control logging in one place not in each config file of service I have ran on machine. I have thought that this !sudo *.* /var/log/sudo.log will take off logging in /var/log/messages but this work as log to /var/log/messages and to /var/log/sudo.log =(( -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sudo log messages
On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: > Tell me please how to stop sudo to food /var/log/messages? ADDITION: Of course I meant /usr/local/etc/sutoers, NOT sudo.conf. Instead of logging via syslog (to /var/log/messages), why not use a specific log file for sudo? Add those lines to the sudoers file: Defaults logfile=/var/log/sudo.log Defaults !syslog Make sure /var/log/sudo.log exists, and maybe use newsyslog.conf to deal with log rotation and archiving. However, you can easily purge sudo log information this way, if required. The file /usr/local/share/doc/sudo/sample.sudoers contains an example. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sudo log messages
On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: > hi > > I add line to syslog.conf > and killall -HUP syslogd > > Tell me please how to stop sudo to food /var/log/messages? There is a short block for that functionality in the file /usr/local/etc/sudo.conf.sample which you can create your own sudo.conf file from. Also see the notes in "man sudo", section "SECURITY NOTES". Maybe you'll find something useful in the provided documentation at /usr/local/share/doc/sudo/. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
sudo log messages
hi I add line to syslog.conf and killall -HUP syslogd Tell me please how to stop sudo to food /var/log/messages? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
On Sat, 19 Nov 2011 04:54:18 -0600, Jukka A. Ukkonen wrote: Hello, Has anyone else noticed a similar odd behavior with AMD64 and 9.0 prerelease (as well as RCs and betas)? On my 12 core (2*4162EE) the whole system just freezes quite often without any warning, without any messages being logged. Neither is there any panic message from the kernel. The system just suddenly hangs such that there is no alternative but to reboot using the reset button. YES YES YES This is happening right now on my little Atom based ZFS NAS and it's driving me insane. 9.0-PRERELEASE compiled with Clang (don't think that matters though). However, mine doesn't fully panic and recovers. It justs completely freezes for like 5-10 seconds. Won't take any keyboard input, doesn't show anything on console/SSH, but is still pingable. Crazy! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
On Sat, 19 Nov 2011 12:54:18 +0200 (EET) j...@iki.fi (Jukka A. Ukkonen) wrote: > > Hello, > > Has anyone else noticed a similar odd behavior with AMD64 and 9.0 > prerelease (as well as RCs and betas)? Yes, I've seen a few of these myself, under both of the RCs and PRERELEASE. No idea what the cause is, though. Impossible to track down. > On my 12 core (2*4162EE) the whole system just freezes quite often > without any warning, without any messages being logged. Neither is > there any panic message from the kernel. The system just suddenly > hangs such that there is no alternative but to reboot using the > reset button. Yes, exactly the same here. Doesn't happen often, but it does happen. > At the moment I don't have any further info about the cause of the > problem, but quite often the freeze has happened when there has been > some network activity. > Does anyone have an idea how to start tracking down such a problem? > I mean anything in addition to this... > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Sorry, wish I had a clue as to how to pinpoint the cause of these hangs. There's no record anywhere of what may have gone wrong. If you find out anything, please let us know. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
On 11/19/11 03:54, Jukka A. Ukkonen wrote: Hello, Has anyone else noticed a similar odd behavior with AMD64 and 9.0 prerelease (as well as RCs and betas)? On my 12 core (2*4162EE) the whole system just freezes quite often without any warning, without any messages being logged. Neither is there any panic message from the kernel. The system just suddenly hangs such that there is no alternative but to reboot using the reset button. At the moment I don't have any further info about the cause of the problem, but quite often the freeze has happened when there has been some network activity. Does anyone have an idea how to start tracking down such a problem? I mean anything in addition to this... http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng& cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I experienced this a rather long time ago with an AMD X2600 (Barton?) processor. The machine would freeze when I did some rapid mousing/clicking in and out of a window. Nothing in the logs. If I stayed out of X things were just fine but this was my home machine and why should I have to stay out of X? I figured FBSD dev was just running behind the Intel dev and time would fix it. Or Xorg dev would even up. In any case it went away in the next release. It was never *that* much of a problem; consistent but not often. Your freezing appears to be more frequent than was mine. At this point in the release cycle I think the only issues they find are for weird corner cases. Perhaps you have one. Or it's hardware :( Try a different NIC for a while. r ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
Hello, Has anyone else noticed a similar odd behavior with AMD64 and 9.0 prerelease (as well as RCs and betas)? On my 12 core (2*4162EE) the whole system just freezes quite often without any warning, without any messages being logged. Neither is there any panic message from the kernel. The system just suddenly hangs such that there is no alternative but to reboot using the reset button. At the moment I don't have any further info about the cause of the problem, but quite often the freeze has happened when there has been some network activity. Does anyone have an idea how to start tracking down such a problem? I mean anything in addition to this... http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng & cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Accounting "disabled/enabled" messages
* Dan Nelson [2011-09-05 03:26 -0400]: > Assuming you have accounting enabled in /etc/rc.conf, that's to be > expected. Accounting is enabled on boot, disabled on shutdown, and > cycled twice during /var/account/acct rotation at 3am. See > /etc/rc.d/accounting and /etc/periodic/daily/310.accounting . Thanks! Apparently my digging in the source precluded me from looking in the normal places one would look to find these things out. ;) Appreciate the nudge. Regards, -- dave [ please don't CC me ] pgpVvZfgSxWfk.pgp Description: PGP signature
Re: Accounting "disabled/enabled" messages
In the last episode (Sep 05), David J. Weller-Fahy said: > I noticed today the following entries in my dmesg. > > #v+ > Accounting enabled > Accounting disabled > Accounting enabled > Accounting disabled > Accounting enabled > Accounting disabled > Accounting enabled > #v- > > The uname -a follows. > > FreeBSD NAStie 9.0-BETA1 FreeBSD 9.0-BETA1 #0: Thu Jul 28 16:34:16 UTC 2011 > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > I tracked the actual messages down to /usr/src/sys/kern/kern_acct.c, but > am not familiar enough with kernel internals to figure out why its > happening. It *looks* like its happening every time I reboot the system > (been playing around with the power). However, I want to be sure, and > figured I'd check with the list. > > So - are these messages something to be concerned about? Or something > to ignore? Or something to ignore in a BETA environment, and not in a > production environment? Assuming you have accounting enabled in /etc/rc.conf, that's to be expected. Accounting is enabled on boot, disabled on shutdown, and cycled twice during /var/account/acct rotation at 3am. See /etc/rc.d/accounting and /etc/periodic/daily/310.accounting . -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Accounting "disabled/enabled" messages
I noticed today the following entries in my dmesg. #v+ Accounting enabled Accounting disabled Accounting enabled Accounting disabled Accounting enabled Accounting disabled Accounting enabled #v- The uname -a follows. FreeBSD NAStie 9.0-BETA1 FreeBSD 9.0-BETA1 #0: Thu Jul 28 16:34:16 UTC 2011 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I tracked the actual messages down to /usr/src/sys/kern/kern_acct.c, but am not familiar enough with kernel internals to figure out why its happening. It *looks* like its happening every time I reboot the system (been playing around with the power). However, I want to be sure, and figured I'd check with the list. So - are these messages something to be concerned about? Or something to ignore? Or something to ignore in a BETA environment, and not in a production environment? Regards, -- dave [ please don't CC me ] pgpi0jn1szJzD.pgp Description: PGP signature
Re: System hanging, error messages with USB drive on FreeBSD 8.1
On 8/28/2011 11:20 AM, Brett Glass wrote: > At 11:43 PM 8/27/2011, Polytropon wrote: > >> I'm not sure if this will help you, but I also had similar >> problems with a Kingston USB stick (normal storage stick, >> no removable microSD card). It didn't work on any of my >> FreeBSD systems. So I finally returned it to the shop and >> got a Sony USB stick instead - no problems, works fine. >> >> So this is my assumption: Some hardware vendors maybe >> improperly implement the USB protocol in their devices, > > A Web search reveals that there are dozens which apparently > have problems with FreeBSD, while Windows has problems with > none of them. This leads me to believe that the problem is > in FreeBSD, not the hardware. The vendors most probably write their own drivers for windows. They do not for FreeBSD and its best effort for FreeBSD. I have yet to come across a USB umass device that needs a quirks setting to make it work. But I am sure there are many out there as there are dozens of different vendors/OEMs out there of all sorts of quality. Having to deal with the edge cases using a single command is perfectly acceptable to me. If setting a quirks value for FreeBSD is not workable for you, perhaps Windows is a better choice for your use. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System hanging, error messages with USB drive on FreeBSD 8.1
At 11:43 PM 8/27/2011, Polytropon wrote: >I'm not sure if this will help you, but I also had similar >problems with a Kingston USB stick (normal storage stick, >no removable microSD card). It didn't work on any of my >FreeBSD systems. So I finally returned it to the shop and >got a Sony USB stick instead - no problems, works fine. > >So this is my assumption: Some hardware vendors maybe >improperly implement the USB protocol in their devices, A Web search reveals that there are dozens which apparently have problems with FreeBSD, while Windows has problems with none of them. This leads me to believe that the problem is in FreeBSD, not the hardware. USB mass storage devices are, for some reason, handled by FreeBSD's SCSI/CAM subsystem, which seems to want to treat a USB storage device (a memory stick or a memory card in an adapter) as a full-out SCSI device when it is not. The SCSI commands which fail usually have to do with flushing the cache and/or other functions which just don't apply to a USB stick. It looks as if the devices which do not have trouble are just IGNORING the SCSI commands, not executing them. In short, FreeBSD really should not be trying to issue them in the first place. In short, this shouldn't be something that's handled by "quirks." Instead, the system simply should recognize that a USB memory stick is not a SCSI drive. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System hanging, error messages with USB drive on FreeBSD 8.1
On Sat, 27 Aug 2011 17:01:24 -0600, Brett Glass wrote: > I'm working with a FreeBSD 8.1-RELEASE/amd64 machine that's > attempting to write data to an ordinary Kingston 8 GB microSD card. > The card has been inserted into its USB adapter and plugged into a > USB port on the machine. The system is locking up repeatedly with > messages that say > > (da1:umass-sim1:1:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:umass-sim1:1:0:0): SCSI sense: Error code 0x52 > > A Web search reveals that problems like this have cropped up for > many, many FreeBSD users as far back as 4.x. But I can't seem to > find any solution (which amazes me; if there's a bug, one would > think it would have gotten some attention). Do I have to abandon > the use of FreeBSD with USB thumb drives (or maybe with USB > altogether)? Hope not, but I may have to if I can't get this fixed. I'm not sure if this will help you, but I also had similar problems with a Kingston USB stick (normal storage stick, no removable microSD card). It didn't work on any of my FreeBSD systems. So I finally returned it to the shop and got a Sony USB stick instead - no problems, works fine. So this is my assumption: Some hardware vendors maybe improperly implement the USB protocol in their devices, so any OS requiring standard conformation of the attached devices (which are malfunctioning according to the USB protocol specifications) signals an error. I also have a "multi card reader" (CF, SD, microSD and who knows what else, it's a "hama USB 2.0 Card Reader 35 in 1") which attaches per USB. It also does not work properly (also causes, at least when I tried it the last time on a 7-STABLE system). The built-in card reader of my home PC works fine instead. Recently, I had to access the USB stick of a friend. The stick didn't work at first try, and the friend told me to try multiple times; he stated that he would have to do that on his Linux system too. So I tried a second time - and magically, the stick worked as intended. Maybe this approach can help here too? But when you say that attaching the USB adaptor causes the system to _hang_, this means that the OS detected a severe hardware malfunction. The OS doesn't stop for no reason; it does so in order to prevent further damages. This behaviour is intended. What's _not_ intended is hardware manufacturers poorly caring for the implementation of the "software part" in their storage devices. Sadly that's not a typical sign of "el cheapo" stuff anymore - even expensive devices sometimes suffer from that poor quality, i. e. their _customers_ are suffering. :-( So if you have problems with such hardware, returning it is an option, and then try some different brand or model. It helps if you print out a dmesg report - looks exceptionally good when done on green-bar paper :-) - and use a red marker to highlight the USB related error messages. Then just say: "This USB adaptor is broken." No average salesman will disagree, and you should immediately get your money back. I've tried that, it works fine. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
System hanging, error messages with USB drive on FreeBSD 8.1
I'm working with a FreeBSD 8.1-RELEASE/amd64 machine that's attempting to write data to an ordinary Kingston 8 GB microSD card. The card has been inserted into its USB adapter and plugged into a USB port on the machine. The system is locking up repeatedly with messages that say (da1:umass-sim1:1:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): SCSI sense: Error code 0x52 A Web search reveals that problems like this have cropped up for many, many FreeBSD users as far back as 4.x. But I can't seem to find any solution (which amazes me; if there's a bug, one would think it would have gotten some attention). Do I have to abandon the use of FreeBSD with USB thumb drives (or maybe with USB altogether)? Hope not, but I may have to if I can't get this fixed. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Netlog update: 2 new messages
Hi Elias, You receive this mail because you're a Netlog member. Your Netlog account: http://en.netlog.com/shashatielias 2 new messages in your inbox.http://en.netlog.com/go/messages 3 Netlog members want to be your friends. http://en.netlog.com/go/friends/requests Status -- You don't have a profile picture yet. Add a profile picture: http://en.netlog.com/go/manage/photos/view=add In the last 30 days, your profile was visited 2 times. Upload a picture: http://en.netlog.com/go/manage/photos/view=add Write a blog message: http://en.netlog.com/go/manage/blog/view=add Shout @ your friends: http://en.netlog.com/shashatielias/shouts/view=withfriends&add=1 Top brands -- adidas: http://en.netlog.com/adidas sonyericsson: http://en.netlog.com/sonyericsson Pendulum: http://en.netlog.com/Pendulum puma: http://en.netlog.com/puma Predictor: http://en.netlog.com/Predictor These members have recently visited your profile -- poisonEN visited your profile on Thursday 11 August at 19:55 http://en.netlog.com/poisonEN parijanum visited your profile on Monday 4 July at 20:21 http://en.netlog.com/parijanum Popular videos -- http://en.netlog.com/go/explore/videos/videoid=en-3161877 Viewed 11 973 times http://en.netlog.com/go/explore/videos/videoid=en-3161502 Viewed 5 866 times http://en.netlog.com/go/explore/videos/videoid=en-2906976 Viewed 5 497 times http://en.netlog.com/go/explore/videos/videoid=en-2863556 Viewed 4 763 times the Netlog Team You receive this mail because you're a Netlog member. Your Netlog account: http://en.netlog.com/shashatielias You no longer want to receive these updates by e-mail? Edit your Settings: http://en.netlog.com/go/settings/email Massive Media NV E. Braunplein 18. B-9000 Gent. Belgium BE0859635972. abuse...@netlog.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what is causing this warning in /var/log/messages?
On Sun, 14 Aug 2011 12:18:03 +0100 Matthew Seaman wrote: [ detailed advice snipped for brevity ] Wow, thank you very much for that explanation. Much more than I had even hoped for. Appreciate it very much. I'll let you know how things turn out. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what is causing this warning in /var/log/messages?
On 14/08/2011 00:45, Conrad J. Sabatier wrote:
> Did you every get any response to this question? I'm seeing something
> very similar after just setting up named yesterday:
>
> Aug 13 18:06:39 serene named[1105]: managed-keys-zone ./IN: loading
> from master file managed-keys.bind failed: file not found
>
> I'm just trying to setup a simple caching nameserver (slave), using the
> auto_forward options.
>
That's a different problem to the one Gary had. It seems you have
options { ... dnssec-validation = yes; ... }; in your named.conf (ie.
check RRSIG data and ensure that there is a chain of trust from the root
or whatever trust anchor you prefer. This is a good thing and really
should be enabled in all recursive nameservers nowadays.)
In order to do that, you need to explicitly specify your trusted key
in named.conf -- or preferably an initial key, as named can track from
that key to the currently active ones automatically. There are two
important trust anchors: the dlv.isc.org key, and the root key. The
DLV key is built into the Bind sources -- all you need to do is add:
options { ... dnssec-lookaside auto; ... };
If you are really paranoid, then you can verify the PGP signature on,
and then add the DLV KSK key to your named.conf as described here:
http://www.isc.org/solutions/dlv#dlv_key
The root key is different. In this case, to verify the key, pull the
key data from the DNS and convert it into a DS (domain signing) record.
Then compare that to the signed data published by IANA. Once you're
satisfied, then add a managed-keys statement to named.conf like so:
managed-keys {
// The DNS root key -- see http://data.iana.org/root-anchors/
// Compare fingerprints with the key published in the DNS by:
//dig . dnskey | grep -w 257 > root.key
//dnssec-dsfromkey -2 root.key
// Verify DS record against the IANA root-anchors data using PGP.
. initial-key 257 3 8
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
FVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh/RStIoO8g0NfnfL2MTJRkxoX
bfDaUeVPQuYEhg37NZWAJQ9VnMVDxP/VHL496M/QZxkjf5/Efucp2gaD
X6RS6CXpoY68LsvPVjR0ZSwzz1apAzvN9dlzEheX7ICJBBtuA6G3LQpz
W5hOA2hzCTMjJPJ8LbqF6dsV6DoBQzgul0sGIcGOYl7OyQdXfZ57relS
Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
QxA+Uk1ihz0=";
};
Docco on managed-keys here:
http://ftp.isc.org/isc/bind9/cur/9.8/doc/arm/Bv9ARM.ch06.html#id2589494
Note that DNSSEC is one area that has seen a great deal of development
over the last several releases of BIND. It definitely works best in the
latest version, bind-9.8.x, although any of the versions bundled with
supported versions of FreeBSD will function correctly.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: what is causing this warning in /var/log/messages?
Did you every get any response to this question? I'm seeing something very similar after just setting up named yesterday: Aug 13 18:06:39 serene named[1105]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found I'm just trying to setup a simple caching nameserver (slave), using the auto_forward options. Quoted message (from mailing list search): Can anybody clue me in on how to get rid of the following? Jul 11 13:00:25 ethic named[40109]: managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what is causing this warning in /var/log/messages?
On Mon, Jul 11, 2011 at 05:53:57PM -0400, Mike L wrote: > Date: Mon, 11 Jul 2011 17:53:57 -0400 > From: Mike L > Subject: Re: what is causing this warning in /var/log/messages? > To: FreeBSD Mailing List > > you didn't google too hard because the very first thing I found on google > was this > http://groups.google.com/group/comp.protocols.dns.bind/browse_thread/thread/a50b760883ea08c6?pli=1 > courtesy of www.hereletmegooglethatforyou.com > > the url that you found was among the first that i found. nothing i tried resolved the bug ... so may this is once where the term 'bug' applies. > On Mon, Jul 11, 2011 at 4:16 PM, Gary Kline wrote: > > > > > Guys, > > > > Thanks to Matthew Seaman, my named.conf is that much closer to being > > set up correctly that I finally reinstalled dns/bind98; the _but_ is > > that the following log entry winds up in my messages log. > > > > I've googled until my fingers are falling off: no resolution. Yes, > > named runs and stuff more/less works. Can anybody clue me in on how > > to get rid of the following? > > > > > > > > Jul 11 13:00:25 ethic named[40109]: managed-keys-zone ./IN/internal: > > loading from master file > > 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys > > failed: file not found > > > > > > > > TIA for any help here, > > > > gary > > > > > > > > -- > > Gary Kline kl...@thought.org http://www.thought.org Public Service > > Unix > > Journey Toward the Dawn, E-Book: http://www.thought.org > > The 8.51a release of Jottings: http://jottings.thought.org > > > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > > freebsd-questions-unsubscr...@freebsd.org" > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what is causing this warning in /var/log/messages?
you didn't google too hard because the very first thing I found on google was this http://groups.google.com/group/comp.protocols.dns.bind/browse_thread/thread/a50b760883ea08c6?pli=1 courtesy of www.hereletmegooglethatforyou.com On Mon, Jul 11, 2011 at 4:16 PM, Gary Kline wrote: > > Guys, > > Thanks to Matthew Seaman, my named.conf is that much closer to being > set up correctly that I finally reinstalled dns/bind98; the _but_ is > that the following log entry winds up in my messages log. > > I've googled until my fingers are falling off: no resolution. Yes, > named runs and stuff more/less works. Can anybody clue me in on how > to get rid of the following? > > > > Jul 11 13:00:25 ethic named[40109]: managed-keys-zone ./IN/internal: > loading from master file > 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys > failed: file not found > > > > TIA for any help here, > > gary > > > > -- > Gary Kline kl...@thought.org http://www.thought.org Public Service > Unix > Journey Toward the Dawn, E-Book: http://www.thought.org > The 8.51a release of Jottings: http://jottings.thought.org > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
what is causing this warning in /var/log/messages?
Guys, Thanks to Matthew Seaman, my named.conf is that much closer to being set up correctly that I finally reinstalled dns/bind98; the _but_ is that the following log entry winds up in my messages log. I've googled until my fingers are falling off: no resolution. Yes, named runs and stuff more/less works. Can anybody clue me in on how to get rid of the following? Jul 11 13:00:25 ethic named[40109]: managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found TIA for any help here, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages from MCA in the kernel log
per...@pluto.rain.com writes:
> Frederic Perrin wrote:
>
>> ... I don't know what MCA, DRD, SNOOP and {D,G}CACHE stand for...
>
> MCA = Machine Check Architecture.
> DRD here probably refers to a data read cycle.
> SNOOP has to do with hardware-maintained cache coherency.
> DCACHE = data cache.
>
> Google and/or Wikipedia may help with the details.
Thanks for the pointers.
>> Is it a transient error?
>
> I _think_ the COR refers to a corrected error, but that could be
> either transient (a random bit-flip, possibly due to a cosmic
> ray hit) or permanent (a bit in the cache has gone bad). In the
> latter case I'd expect ongoing error messages, rather than just
> two isolated occurrences.
This server has been running since about 18 months, with a current
uptime of 75 days. This is the first time this message appeared, and has
not returned yet. I'll shrug it off as a one-time glitch.
Thanks for your comments. Have a nice day,
--
Frédéric Perrin -- http://tar-jx.bz
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Messages from MCA in the kernel log
Frederic Perrin wrote:
> ... I don't know what MCA, DRD, SNOOP and {D,G}CACHE stand for...
MCA = Machine Check Architecture.
DRD here probably refers to a data read cycle.
SNOOP has to do with hardware-maintained cache coherency.
DCACHE = data cache.
Google and/or Wikipedia may help with the details.
> Is it a transient error?
I _think_ the COR refers to a corrected error, but that could be
either transient (a random bit-flip, possibly due to a cosmic
ray hit) or permanent (a bit in the cache has gone bad). In the
latter case I'd expect ongoing error messages, rather than just
two isolated occurrences.
> Should I start screaming at my hosting provider so he changes my
> CPU?
I would say not, unless the errors become frequent or uncorrectable.
> +MCA: Bank 0, Status 0xcc0120040189
> +MCA: Global Cap 0x00180204, Status 0x
> +MCA: Vendor "GenuineIntel", ID 0xf49, APIC ID 0
> +MCA: CPU 0 COR OVER GCACHE L1 SNOOP error
> +MCA: Address 0x1015b00
> +MCA: Misc 0x140002d800aa0
> +MCA: Bank 1, Status 0x80200135
> +MCA: Global Cap 0x00180204, Status 0x
> +MCA: Vendor "GenuineIntel", ID 0xf49, APIC ID 0
> +MCA: CPU 0 COR DCACHE L1 DRD error
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Messages from MCA in the kernel log
Hello list,
The following appeared in the dmesg buffer of my FreeBSD server. From my
reading of x86/x86/mca.c, this means that the CPU had two (correctable)
cache errors. This doesn't help me much, as I don't know what MCA, DRD,
SNOOP and {D,G}CACHE stand for... Is it a transient error? Should I
start screaming at my hosting provider so he changes my CPU?
The box has an Intel Celeron CPU 2.66GHz. It runs FreeBSD 8.2. A dmesg
can be found at . It is a
'kimsufi' (the cheapest model as of 18 months ago, no longer featured on
kimsufi.com).
+MCA: Bank 0, Status 0xcc0120040189
+MCA: Global Cap 0x00180204, Status 0x
+MCA: Vendor "GenuineIntel", ID 0xf49, APIC ID 0
+MCA: CPU 0 COR OVER GCACHE L1 SNOOP error
+MCA: Address 0x1015b00
+MCA: Misc 0x140002d800aa0
+MCA: Bank 1, Status 0x80200135
+MCA: Global Cap 0x00180204, Status 0x
+MCA: Vendor "GenuineIntel", ID 0xf49, APIC ID 0
+MCA: CPU 0 COR DCACHE L1 DRD error
--
Frédéric Perrin -- http://tar-jx.bz
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel causes "GEOM: ada1: media size does not match label" messages
On Mon, 21 Mar 2011 06:40:51 -0400, Maxim Khitrov wrote: > I've been using 'dangerously dedicated' partitioning for years without > any issues. What problems have been reported by others? I think those "problems" originate from some operating systems not able to work with disks that do not come with a DOS-style partition table. This may be restricted to DOS-related operating systems (which I personally do not have to care about). For my needs, there has never been a problem booting from such a layout or accessing it. If you just have one slice (a.k.a. "DOS primary partition") and no other operating systems on the disk, there is _no_ particular requirement to create a slice, as far as I could experience. However, it may be needed in multi-boot constellations. The word "dangerous" (deserving the quotes) is, in my opinion, used to emphasize that there is the "danger" that *OTHER* operating systems can't deal with it. Those systems are traditionally located in MICROS~1 land. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel causes "GEOM: ada1: media size does not match label" messages
On Mon, Mar 21, 2011 at 12:30 AM, Carl Johnson wrote: > Maxim Khitrov writes: > >> On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov wrote: >>> Hi all, >>> >>> Executing the following commands on any valid storage device seems to >>> cause "media size does not match label" kernel messages (FreeBSD 8.2 >>> amd64). I understand why they happen - glabel metadata occupies the >>> last sector, so bsdlabel sees a device that is 1 sector smaller than >>> what the kernel sees. The question is whether there is some simple way >>> of suppressing these messages, since they come up every time the >>> system is booted or the partition is mounted/unmounted: >>> >>> # glabel label vol0 ada1 >>> # bsdlabel -w /dev/label/vol0 >>> GEOM: ada1: media size does not match label. >>> # newfs /dev/label/vol0a >>> # mount /dev/label/vol0a /mnt >>> GEOM: ada1: media size does not match label. >>> # umount /mnt >>> GEOM: ada1: media size does not match label. >>> >>> As you can see, I'm not using MBR or GPT partitioning schemes. I try >>> to avoid those unless I plan on sharing the media with another OS. >>> Even if using gpart would get rid of these errors (not sure, since >>> then you'll just have a partition whose size doesn't match), I would >>> still prefer to find some other way to suppress them. >>> >>> - Max > > I am not an expert, but that looks correct as you have it, so I would > expect some other problem. You are using vol0 as the partition for > newfs and its size should be correctly sized to allow for the last > sector of ada1 being used by glabel. I have heard comments that there > problems in what some call 'dangerously dedicated' partitions, so you > might want to create a single slice covering the whole disk and > partition that. I've been using 'dangerously dedicated' partitioning for years without any issues. What problems have been reported by others? > If you just want volume names for a filesystem, you might want to try > the -L option for either newfs or tunefs. The last example of the > glabel manpage shows using a ufs label to contrast it with glabel. I > use ufs labels for all of my filesystems and just use glabel for swap, > and I suspect that swapon wouldn't catch the type of problem that you > are seeing. I do use UFS labels where necessary. In this case, I'm writing a script that needs to access all bsdlabel partitions through a common name. >> Heh... In the process of searching for a solution to this, I decided >> to see what would happen if I used bsdlabel on ada1 rather than vol0 >> (in my example above), and created a 1-sector partition at the very >> end of the disk. So the layout would be something like this: >> >> # /dev/ada1: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: * * 4.2BSD >> c: * 0 unused >> h: 1 * unused >> >> The 'c' partition now covers the entire disk, which stops the kernel >> from complaining about media size not matching the label. At the same >> time, the 'h' partition will protect the last sector, which contains >> glabel metadata. >> >> The problem now is that the label is technically invalid for the vol0 >> device, which is what I'll be mounting. Indeed, bsdlabel complains >> when I run it for /dev/label/vol0: >> >> # /dev/label/vol0: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: 3907029151 16 4.2BSD 0 0 0 >> c: 3907029168 0 unused 0 0 >> h: 1 3907029167 unused 0 0 >> partition c: partition extends past end of unit >> bsdlabel: partition c doesn't cover the whole unit! >> bsdlabel: An incorrect partition c may cause problems for standard >> system utilities >> partition h: partition extends past end of unit >> >> I don't care about partition 'h'; it is there only to stop the >> preceding partition from covering the last sector. Are there any real >> issues with the 'c' partition being 1 sector too big for the vol0 >> device (but just the right size for ada1)? >> >> This is a bit of a hack, but I'll take it if it stops the kernel from >> complaining and doesn't create any new problems. > > I don't see where adding an extra partition at the end does anything to > protect the earlier partition. In my exam
Re: glabel causes "GEOM: ada1: media size does not match label" messages
Maxim Khitrov writes: > On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov wrote: >> Hi all, >> >> Executing the following commands on any valid storage device seems to >> cause "media size does not match label" kernel messages (FreeBSD 8.2 >> amd64). I understand why they happen - glabel metadata occupies the >> last sector, so bsdlabel sees a device that is 1 sector smaller than >> what the kernel sees. The question is whether there is some simple way >> of suppressing these messages, since they come up every time the >> system is booted or the partition is mounted/unmounted: >> >> # glabel label vol0 ada1 >> # bsdlabel -w /dev/label/vol0 >> GEOM: ada1: media size does not match label. >> # newfs /dev/label/vol0a >> # mount /dev/label/vol0a /mnt >> GEOM: ada1: media size does not match label. >> # umount /mnt >> GEOM: ada1: media size does not match label. >> >> As you can see, I'm not using MBR or GPT partitioning schemes. I try >> to avoid those unless I plan on sharing the media with another OS. >> Even if using gpart would get rid of these errors (not sure, since >> then you'll just have a partition whose size doesn't match), I would >> still prefer to find some other way to suppress them. >> >> - Max I am not an expert, but that looks correct as you have it, so I would expect some other problem. You are using vol0 as the partition for newfs and its size should be correctly sized to allow for the last sector of ada1 being used by glabel. I have heard comments that there problems in what some call 'dangerously dedicated' partitions, so you might want to create a single slice covering the whole disk and partition that. If you just want volume names for a filesystem, you might want to try the -L option for either newfs or tunefs. The last example of the glabel manpage shows using a ufs label to contrast it with glabel. I use ufs labels for all of my filesystems and just use glabel for swap, and I suspect that swapon wouldn't catch the type of problem that you are seeing. > Heh... In the process of searching for a solution to this, I decided > to see what would happen if I used bsdlabel on ada1 rather than vol0 > (in my example above), and created a 1-sector partition at the very > end of the disk. So the layout would be something like this: > > # /dev/ada1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a:**4.2BSD > c:*0unused > h:1*unused > > The 'c' partition now covers the entire disk, which stops the kernel > from complaining about media size not matching the label. At the same > time, the 'h' partition will protect the last sector, which contains > glabel metadata. > > The problem now is that the label is technically invalid for the vol0 > device, which is what I'll be mounting. Indeed, bsdlabel complains > when I run it for /dev/label/vol0: > > # /dev/label/vol0: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 3907029151 164.2BSD0 0 0 > c: 39070291680unused0 0 > h:1 3907029167unused0 0 > partition c: partition extends past end of unit > bsdlabel: partition c doesn't cover the whole unit! > bsdlabel: An incorrect partition c may cause problems for standard > system utilities > partition h: partition extends past end of unit > > I don't care about partition 'h'; it is there only to stop the > preceding partition from covering the last sector. Are there any real > issues with the 'c' partition being 1 sector too big for the vol0 > device (but just the right size for ada1)? > > This is a bit of a hack, but I'll take it if it stops the kernel from > complaining and doesn't create any new problems. I don't see where adding an extra partition at the end does anything to protect the earlier partition. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel causes "GEOM: ada1: media size does not match label" messages
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov wrote: > Hi all, > > Executing the following commands on any valid storage device seems to > cause "media size does not match label" kernel messages (FreeBSD 8.2 > amd64). I understand why they happen - glabel metadata occupies the > last sector, so bsdlabel sees a device that is 1 sector smaller than > what the kernel sees. The question is whether there is some simple way > of suppressing these messages, since they come up every time the > system is booted or the partition is mounted/unmounted: > > # glabel label vol0 ada1 > # bsdlabel -w /dev/label/vol0 > GEOM: ada1: media size does not match label. > # newfs /dev/label/vol0a > # mount /dev/label/vol0a /mnt > GEOM: ada1: media size does not match label. > # umount /mnt > GEOM: ada1: media size does not match label. > > As you can see, I'm not using MBR or GPT partitioning schemes. I try > to avoid those unless I plan on sharing the media with another OS. > Even if using gpart would get rid of these errors (not sure, since > then you'll just have a partition whose size doesn't match), I would > still prefer to find some other way to suppress them. > > - Max > Heh... In the process of searching for a solution to this, I decided to see what would happen if I used bsdlabel on ada1 rather than vol0 (in my example above), and created a 1-sector partition at the very end of the disk. So the layout would be something like this: # /dev/ada1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:**4.2BSD c:*0unused h:1*unused The 'c' partition now covers the entire disk, which stops the kernel from complaining about media size not matching the label. At the same time, the 'h' partition will protect the last sector, which contains glabel metadata. The problem now is that the label is technically invalid for the vol0 device, which is what I'll be mounting. Indeed, bsdlabel complains when I run it for /dev/label/vol0: # /dev/label/vol0: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 3907029151 164.2BSD0 0 0 c: 39070291680unused0 0 h:1 3907029167unused0 0 partition c: partition extends past end of unit bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition h: partition extends past end of unit I don't care about partition 'h'; it is there only to stop the preceding partition from covering the last sector. Are there any real issues with the 'c' partition being 1 sector too big for the vol0 device (but just the right size for ada1)? This is a bit of a hack, but I'll take it if it stops the kernel from complaining and doesn't create any new problems. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
glabel causes "GEOM: ada1: media size does not match label" messages
Hi all, Executing the following commands on any valid storage device seems to cause "media size does not match label" kernel messages (FreeBSD 8.2 amd64). I understand why they happen - glabel metadata occupies the last sector, so bsdlabel sees a device that is 1 sector smaller than what the kernel sees. The question is whether there is some simple way of suppressing these messages, since they come up every time the system is booted or the partition is mounted/unmounted: # glabel label vol0 ada1 # bsdlabel -w /dev/label/vol0 GEOM: ada1: media size does not match label. # newfs /dev/label/vol0a # mount /dev/label/vol0a /mnt GEOM: ada1: media size does not match label. # umount /mnt GEOM: ada1: media size does not match label. As you can see, I'm not using MBR or GPT partitioning schemes. I try to avoid those unless I plan on sharing the media with another OS. Even if using gpart would get rid of these errors (not sure, since then you'll just have a partition whose size doesn't match), I would still prefer to find some other way to suppress them. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: kern.crit messages
On Sun, 6 Feb 2011 12:21:02 -0600, Adam Vande More wrote: > On Sun, Feb 6, 2011 at 12:10 PM, Robert Fitzpatrick wrote: > > > Thanks. Can someone confirm these steps as the best way to attempt to > > get back to a 8.1 kernel I originally installed... > > > > 1. update my tag line to 8_1 > > 2. update my source tree > > > > For step 3, you can something like "make buildkernel && make installkernel" > but you may not have to do that if the /boot/kernel.old is a match your > currect userland as mentioned previously. simply move it /boot/kernel after > you have tested it. Refer to the comment section of /usr/src/Makefile for an explaination of the correct procedure of the updating process: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. & 4. can be combined by using the "kernel" target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster' (you may wish to use -U or -ai). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) You'll also see what the different make targets are representing (e. g. make world = "buildworld + installworld, no kernel"). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: kern.crit messages
On Sun, Feb 6, 2011 at 12:10 PM, Robert Fitzpatrick wrote: > Thanks. Can someone confirm these steps as the best way to attempt to > get back to a 8.1 kernel I originally installed... > > 1. update my tag line to 8_1 > 2. update my source tree > For step 3, you can something like "make buildkernel && make installkernel" but you may not have to do that if the /boot/kernel.old is a match your currect userland as mentioned previously. simply move it /boot/kernel after you have tested it. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: kern.crit messages
On 2/6/2011 12:20 PM, Vallo Kallaste wrote: > By using the line: > *default release=cvs tag=. > for src-all collection you definitely grabbed -current sources. I'm > not sure if downgrading by "make world" is supported but you could > try. Backup first, try later.. Thanks. Can someone confirm these steps as the best way to attempt to get back to a 8.1 kernel I originally installed... 1. update my tag line to 8_1 2. update my source tree 3. run 'make world' I have backup already. I ask because in the handbook it says 'Do not use make world'... http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I was going to just rebuild the kernel with the proper source tree. -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: kern.crit messages
On Sun, 06 Feb 2011 12:04:59 -0500 Robert Fitzpatrick wrote: > I have a server I installed 8.1-RELEASE on and believe I screwed up > when rebuilding the kernel to support QUOTA because now that I am > troubleshooting these weird messages in the log, I find I am actually > running 9.0-CURRENT. I had a ports file as below when I pulled the > source to rebuild the kernel... > > *default host=cvsup9.us.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=. > *default release=cvs delete use-rel-suffix compress > src-all > > Using the tag above caused my issue? Yes, with ports tag=. just means the latest version, with the base system it means the latest CURRENT, you should have used RELENG_8_1_0_RELEASE or RELENG_8_1 > Now I see some troubling messages > in my logs... I believe CURRENT has a lot of additional debug on by default, and presumably you now have a mismatched kernel and userland, so it's not surprizing. > Just looking for advice on what to do about all this, can someone > help? If you have only built the kernel and only built it once you should have the old 8.1 version as a backup. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: kern.crit messages
On Sun, Feb 06, 2011 at 12:04:59PM -0500, Robert Fitzpatrick wrote: > I have a server I installed 8.1-RELEASE on and believe I screwed up when > rebuilding the kernel to support QUOTA because now that I am > troubleshooting these weird messages in the log, I find I am actually > running 9.0-CURRENT. I had a ports file as below when I pulled the > source to rebuild the kernel... > > *default host=cvsup9.us.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=. > *default release=cvs delete use-rel-suffix compress > src-all > > Using the tag above caused my issue? Now I see some troubling messages > in my logs... > > Just looking for advice on what to do about all this, can someone help? > By using the line: *default release=cvs tag=. for src-all collection you definitely grabbed -current sources. I'm not sure if downgrading by "make world" is supported but you could try. Backup first, try later.. -- Vallo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
kern.crit messages
I have a server I installed 8.1-RELEASE on and believe I screwed up when rebuilding the kernel to support QUOTA because now that I am troubleshooting these weird messages in the log, I find I am actually running 9.0-CURRENT. I had a ports file as below when I pulled the source to rebuild the kernel... *default host=cvsup9.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default release=cvs delete use-rel-suffix compress src-all Using the tag above caused my issue? Now I see some troubling messages in my logs... > Feb 6 11:25:23 backup kernel: lock order reversal: > Feb 6 11:25:23 backup kernel: 1st 0xff8014bbbe58 bufwait > (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2659 > Feb 6 11:25:23 backup kernel: 2nd 0xff002b9d6400 dirhash > (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:283 > Feb 6 11:25:23 backup kernel: KDB: stack backtrace: > Feb 6 11:25:23 backup kernel: db_trace_self_wrapper() at > db_trace_self_wrapper+0x2a > Feb 6 11:25:23 backup kernel: _witness_debugger() at > _witness_debugger+0x2e > Feb 6 11:25:23 backup kernel: witness_checkorder() at > witness_checkorder+0x807 > Feb 6 11:25:23 backup kernel: _sx_xlock() at _sx_xlock+0x55 > Feb 6 11:25:23 backup kernel: ufsdirhash_acquire() at > ufsdirhash_acquire+0x33 > Feb 6 11:25:23 backup kernel: ufsdirhash_add() at > ufsdirhash_add+0x19 > Feb 6 11:25:23 backup kernel: ufs_direnter() at > ufs_direnter+0x662 > Feb 6 11:25:23 backup kernel: ufs_makeinode() at > ufs_makeinode+0x291 > Feb 6 11:25:23 backup kernel: VOP_CREATE_APV() at > VOP_CREATE_APV+0x8d > Feb 6 11:25:23 backup kernel: vn_open_cred() at > vn_open_cred+0x46a > Feb 6 11:25:23 backup kernel: kern_openat() at kern_openat+0x181 > Feb 6 11:25:23 backup kernel: syscallenter() at > syscallenter+0x1aa > Feb 6 11:25:23 backup kernel: syscall() at syscall+0x4c > Feb 6 11:25:23 backup kernel: Xfast_syscall() at > Xfast_syscall+0xe2 > Feb 6 11:25:23 backup kernel: --- syscall (5, FreeBSD ELF64, > open), rip = 0x80078118c, rsp = 0x7fffad48, rbp = 0x7fffb73f --- I also find this message with dmesg... > ad8: 152627MB at ata4-master UDMA100 SATA > ad9: 953869MB at ata4-slave UDMA100 SATA > GEOM: ad8s1: geometry does not match label (255h,63s != 16h,63s). > ad10: 152627MB at ata5-master UDMA100 SATA > ad11: 953869MB at ata5-slave UDMA100 SATA > GEOM: ad9s1: geometry does not match label (255h,63s != 16h,63s). > uhub0: 2 ports with 2 removable, self powered > uhub1: 2 ports with 2 removable, self powered > uhub2: 2 ports with 2 removable, self powered > uhub3: 2 ports with 2 removable, self powered > GEOM: ufsid/4c7aa872e9a44575: geometry does not match label (255h,63s != > 16h,63s). > GEOM: ad10s1: geometry does not match label (255h,63s != 16h,63s). > GEOM: ad11s1: geometry does not match label (255h,63s != 16h,63s). > uhub4: 8 ports with 8 removable, self powered > ar0: 152627MB status: READY > ar0: disk0 READY (master) using ad8 at ata4-master > ar0: disk1 READY (mirror) using ad10 at ata5-master > ar1: 953869MB status: READY > ar1: disk0 READY (master) using ad11 at ata5-slave > ar1: disk1 READY (mirror) using ad9 at ata4-slave > SMP: AP CPU #1 Launched! > WARNING: WITNESS option enabled, expect reduced performance. > ugen1.2: at usbus1 > ukbd0: on usbus1 > kbd2 at ukbd0 > ums0: on usbus1 > ums0: 5 buttons and [XYZ] coordinates ID=1 > Trying to mount root from ufs:/dev/ar0s1a > lock order reversal: > 1st 0xff0002cdd818 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:501 > 2nd 0xff801497ff78 bufwait (bufwait) @ > /usr/src/sys/ufs/ffs/ffs_softdep.c:11309 > 3rd 0xff0002d4fbd8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2111 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x807 > __lockmgr_args() at __lockmgr_args+0xd42 > ffs_lock() at ffs_lock+0x8c > VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b > _vn_lock() at _vn_lock+0x47 > vget() at vget+0x7b > vfs_hash_get() at vfs_hash_get+0xd5 > ffs_vgetf() at ffs_vgetf+0x48 > softdep_sync_metadata() at softdep_sync_metadata+0x5e3 > ffs_syncvnode() at ffs_syncvnode+0x213 > ffs_truncate() at ffs_truncate+0x557 > ufs_direnter() at ufs_direnter+0x47b > ufs_makeinode() at ufs_makeinode+0x291 > VOP_CREATE_APV() at VOP_CREATE_APV+0x8d > vn_open_cred() at vn_open_cred+0x46a > kern_openat() at kern_openat+0x181 > syscallenter() at syscallenter+0x1aa > syscall() at syscall+0x4c > Xfast_syscall() at Xfast_syscall+0xe2 > --- syscall (5, FreeBSD ELF64, open), rip = 0x80072f18c, rsp = > 0x7fffead8, rbp = 0 --- > lock order reversal: > 1st 0xff
Re: Colorized compiler/linker messages
On 01/23/2011 17:07, Mark Johnston wrote: On Sat, Jan 22, 2011 at 08:00:52PM -0600, Michael D. Norwick wrote: Good Day, I have seen this for some time when building ports and was wondering how it was done. GCC when compiling and linking certain programs, ebook for example, emits messages in various colors. How is that done? Where does one find what the various colors are supposed to signify? Or, is it just because it's more appealing? Thank You, Michael I'm not sure about ebook specifically, but there's a wrapper for gcc called colorgcc which colorizes the diagnostics and errors that gcc emits. The idea is that one can just do something like "CC=colorgcc make" when building. I'm sure there are other programs out there that do something similar, but colorgcc is the most common I think. Apparently there are similar wrappers for make and diff as well. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Thank You, I'll look up the man pages for colorgcc and see if it is installed on my system. This explains a lot. Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Colorized compiler/linker messages
On Sat, Jan 22, 2011 at 08:00:52PM -0600, Michael D. Norwick wrote: > Good Day, > > I have seen this for some time when building ports and was wondering > how it was done. GCC when compiling and linking certain programs, > ebook for example, emits messages in various colors. How is that > done? Where does one find what the various colors are supposed to > signify? Or, is it just because it's more appealing? > > Thank You, > > Michael I'm not sure about ebook specifically, but there's a wrapper for gcc called colorgcc which colorizes the diagnostics and errors that gcc emits. The idea is that one can just do something like "CC=colorgcc make" when building. I'm sure there are other programs out there that do something similar, but colorgcc is the most common I think. Apparently there are similar wrappers for make and diff as well. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Colorized compiler/linker messages
On 01/22/2011 22:22, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Sat Jan 22 20:10:21 2011 Date: Sat, 22 Jan 2011 20:00:52 -0600 From: "Michael D. Norwick" To: freebsd-questions@freebsd.org Subject: Colorized compiler/linker messages Good Day, I have seen this for some time when building ports and was wondering how it was done. GCC when compiling and linking certain programs, ebook for example, emits messages in various colors. How is that done? "Whatever it is" that is writing the messages is putting out 'terminal control' character strings that specify the color. Where does one find what the various colors are supposed to signify? Read the _complete_ documentation for 'whatever it is' that is producing the messages. The colors signify 'whatever it is' that the author of that software chose to represent with that color. There are *NO* "universal standards" for such things. Or, is it just because it's more appealing? (A) "appealing" is in the eye of the beholder. (B) *why* 'somebody' did something/anything is known *only* to the party that actually _did_ it. You can ether ask *them* or get uninformed speculation from third parties. In broad, diagsnotic messages can be divided into a minimum of 4 'classes' (finer gradation is always possible): diagnostic -- 'gory details' of what the program is doing internally, to find out where what it is actually doing is different from what one 'expects' it to be doing. informational -- things you might 'want to know about', but do not indicate potentially incorrect operation. warning -- things which *probably* indicate a problem, but might be 'as intended' error -- something which is, without question, incorrect, and prevents proper program operation. A developer -might- use different colors for different 'classes' of messages, so that an experienced user of that program (who 'knows' what color is used for what) can tell 'at a glance' the serverity of the thing being reported. [ see (B), above, as regards applicability to -your- situationn ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Sounds like you had a bad day yesterday. I'm sorry, I will try to scan any further e-mails for the appropriate intelligence. Isn't that why it's called FreeBSD-questions and not ab...@freebsd.org? And, yes, I read the docs. Thank You, Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bind97 from /bar/log/messages....
On 01/23/11 14:00, Gary Kline wrote: Can anybody spot what's messed up here and help me get back up? > From earlier errors I added and then removed an "A" address label before the "IN NS ns1.thought.org" ... That was the only thing I could think of, and things still failed. HEre is the apropos part of the log: Sometimes you just get to the point where you just want a straight-forward answer to things because you've had enough :) I'm there now myself, so I can relate. So... 1. Are you sure named (bind9.x's executable) is not already running? Usually if it is already running you would incant rndc reload. 2. You need an address record for named server host- ns1.thought.org. So you need in your zone file (this is taking a bit of remembering now- been a while since I had to edit mine... :) ): NS ns1.thought.org. ; don't forget the period at the end A ; OPTIONAL: this will allow users to just enter domain and go straight to the web server. You can also simply CNAME hosts with the same address. $ORIGIN thought.org. ; saves you typing - now just type in the hosts and domain will be auto added (again don't forget the period) ns1A That should get you out of trouble. The optional stuff makes it easier for your users, and for you to maintain. Don't forget to increment your serial :) Now, I think you should be checking your mail server ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Colorized compiler/linker messages
On Sat 22 Jan 2011 at 18:00:52 PST Michael D. Norwick wrote: Good Day, I have seen this for some time when building ports and was wondering how it was done. GCC when compiling and linking certain programs, ebook for example, emits messages in various colors. How is that done? Where does one find what the various colors are supposed to signify? Or, is it just because it's more appealing? CMake can be used to generate Makefiles that produce colorized output, and I would wager that it's being used by most of the ports where you're seeing color. But there are many tools a developer might use for this. For example, I found this in my bookmarks file: http://phil.freehackers.org/pretty-make/index.html I think it's mostly aesthetics, but some people claim that using different colors for different build steps makes it easier to monitor the progress of the build. For example, if the link or install steps are a different color than the configuration or compile steps, you can see that the build is in its final stages even if you're on the other side of the room. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
{kl...@thought.org} Your email is screwed up, AGAIN! ( Re: bind97 from /bar/log/messages....)
Date: Sat, 22 Jan 2011 22:42:16 -0600 (CST) Subject: Returned mail: see transcript for details - The following addresses had permanent fatal errors - kl...@thought.org (reason: 550 5.7.1 ... Relaying denied. Proper authentication required.) - Transcript of session follows - ... while talking to ethic.thought.org.: >>> DATA <<< 550 5.7.1 ... Relaying denied. Proper authentication required. 550 5.1.1 kl...@thought.org... User unknown <<< 503 5.0.0 Need RCPT (recipient) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bind97 from /bar/log/messages....
> From owner-freebsd-questi...@freebsd.org Sat Jan 22 22:08:52 2011
> Date: Sat, 22 Jan 2011 20:00:47 -0800
> From: Gary Kline
> To: FreeBSD Mailing List
> Cc:
> Subject: bind97 from /bar/log/messages
>
>
> Can anybody spot what's messed up here and help me get back up?
>
> >From earlier errors I added and then removed an "A" address label
> before the "IN NS ns1.thought.org" ... That was the only thing I could
> think of, and things still failed.
>
> Here is the apropos part of the log:
>
>
> Jan 22 19:44:54 ethic named[2069]: starting BIND 9.7.2-P3 -c
> /var/named/etc/namedb/named.conf
> Jan 22 19:44:54 ethic named[2069]: built with '--localstatedir=/var'
> '--disable-linux-caps' '--disable-symtable'
> '--with-randomdev=/dev/random' '--with-openssl=/usr'
> '--with-libxml2=/usr/local' '--without-idn' '--enable-threads'
> '--prefix=/usr/local' '--mandir=/usr/local/man'
> '--infodir=/usr/local/info/' '--build=i386-portbld-freebsd7.3'
> 'build_alias=i386-portbld-freebsd7.3' 'CC=cc' 'CFLAGS=-O2
> -fno-strict-aliasing -pipe' 'LDFLAGS=
> -rpath=/usr/lib:/usr/local/lib' 'CPP=cpp' 'CXX=c++' 'CXXFLAGS=-O2
> -fno-strict-aliasing -pipe'
> Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in
> use
> Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface address in use
> Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface em0 failed;
> interface ignored
**PROBLEM** _something_ is already using the port named is trying to listen
on, for an IPv4 address associated with interface em0
> Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in
> use
> Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface lo0 failed;
> interface ignored
**PROBLEM** _something_ is already listening on the specified port on the
loopback (lo0) interface, as well.
> Jan 22 19:44:54 ethic named[2069]: not listening on any interfaces
**PROBLEM** the 'something' beat this invocation of 'named' to the punch on
_all_ the interfaces it was trying to listen on for queries. dead in the water.
> Jan 22 19:44:54 ethic named[2069]: couldn't add command channel
> 127.0.0.1#953: address in use
> Jan 22 19:44:54 ethic named[2069]: couldn't add command channel ::1#953:
> address in use
> Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in
> use
> Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface em0 failed;
> interface ignored
**PROBLEM** _something_ is already using the 'control' port named is trying to
use, for an IPv4 address associated with interface em0
> Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in
> use
> Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface lo0 failed;
> interface ignored
**PROBLEM** _something_ is already using the 'control' port named is trying to
use, for an IPv4 address associated with the loopback interface.
> Jan 22 19:44:54 ethic named[2069]: zone thought.org/IN/internal: NS
> 'ns1.thought.org' has no address records (A or )
**PROBLEM** in the config file being used.
you have a line that declares "IN NS ns1.thought.org",
but *NO* line "ns1.thought.org IN A {IPv4 address}"
or "ns1.thought.org IN A {[IPv6 address]}"
>
> Jan 22 19:44:54 ethic named[2069]: zone thought.org/IN/internal: not loaded
> due to errors.
**PROBLEM** entire zone file ignored due to errors ini it.
> Jan 22 19:44:54 ethic named[2069]: managed-keys-zone ./IN/internal: loading
> from master file
> 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys
> failed: file not found
> Jan 22 19:44:54 ethic named[2069]: managed-keys-zone ./IN/external: loading
> from master file
> 3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys
> failed: file not found
> Jan 22 19:44:54 ethic named[2069]: running
Running, but doing nothing.
> And regarding the "managed-keys-zone" I have no clue. i do have a file
> named rndc.key or suchlike, but that is as close as I can come to
> anything to do with that string. ...So hope some of you DNS wizards
> know.
>
> tia,
>
> gary
>
>
>
>
> --
> Gary Kline kl...@thought.org http://www.thought.org Public Service
> Unix
>Journey Toward the Dawn, E-Book: http://www.thought.org The
>7.97a release of Jottings: http://jottings.thought.org
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions To
> unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
..
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Colorized compiler/linker messages
> From owner-freebsd-questi...@freebsd.org Sat Jan 22 20:10:21 2011 > Date: Sat, 22 Jan 2011 20:00:52 -0600 > From: "Michael D. Norwick" > To: freebsd-questions@freebsd.org > Subject: Colorized compiler/linker messages > > Good Day, > > I have seen this for some time when building ports and was wondering how > it was done. GCC when compiling and linking certain programs, ebook for > example, emits messages in various colors. How is that done? "Whatever it is" that is writing the messages is putting out 'terminal control' character strings that specify the color. >Where does > one find what the various colors are supposed to signify? Read the _complete_ documentation for 'whatever it is' that is producing the messages. The colors signify 'whatever it is' that the author of that software chose to represent with that color. There are *NO* "universal standards" for such things. >Or, is it just > because it's more appealing? (A) "appealing" is in the eye of the beholder. (B) *why* 'somebody' did something/anything is known *only* to the party that actually _did_ it. You can ether ask *them* or get uninformed speculation from third parties. In broad, diagsnotic messages can be divided into a minimum of 4 'classes' (finer gradation is always possible): diagnostic -- 'gory details' of what the program is doing internally, to find out where what it is actually doing is different from what one 'expects' it to be doing. informational -- things you might 'want to know about', but do not indicate potentially incorrect operation. warning -- things which *probably* indicate a problem, but might be 'as intended' error -- something which is, without question, incorrect, and prevents proper program operation. A developer -might- use different colors for different 'classes' of messages, so that an experienced user of that program (who 'knows' what color is used for what) can tell 'at a glance' the serverity of the thing being reported. [ see (B), above, as regards applicability to -your- situationn ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
bind97 from /bar/log/messages....
Can anybody spot what's messed up here and help me get back up? >From earlier errors I added and then removed an "A" address label before the "IN NS ns1.thought.org" ... That was the only thing I could think of, and things still failed. HEre is the apropos part of the log: Jan 22 19:44:54 ethic named[2069]: starting BIND 9.7.2-P3 -c /var/named/etc/namedb/named.conf Jan 22 19:44:54 ethic named[2069]: built with '--localstatedir=/var' '--disable-linux-caps' '--disable-symtable' '--with-randomdev=/dev/random' '--with-openssl=/usr' '--with-libxml2=/usr/local' '--without-idn' '--enable-threads' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=i386-portbld-freebsd7.3' 'build_alias=i386-portbld-freebsd7.3' 'CC=cc' 'CFLAGS=-O2 -fno-strict-aliasing -pipe' 'LDFLAGS= -rpath=/usr/lib:/usr/local/lib' 'CPP=cpp' 'CXX=c++' 'CXXFLAGS=-O2 -fno-strict-aliasing -pipe' Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in use Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface em0 failed; interface ignored Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in use Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface lo0 failed; interface ignored Jan 22 19:44:54 ethic named[2069]: not listening on any interfaces Jan 22 19:44:54 ethic named[2069]: couldn't add command channel 127.0.0.1#953: address in use Jan 22 19:44:54 ethic named[2069]: couldn't add command channel ::1#953: address in use Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in use Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface em0 failed; interface ignored Jan 22 19:44:54 ethic named[2069]: could not listen on UDP socket: address in use Jan 22 19:44:54 ethic named[2069]: creating IPv4 interface lo0 failed; interface ignored Jan 22 19:44:54 ethic named[2069]: zone thought.org/IN/internal: NS 'ns1.thought.org' has no address records (A or ) Jan 22 19:44:54 ethic named[2069]: zone thought.org/IN/internal: not loaded due to errors. Jan 22 19:44:54 ethic named[2069]: managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found Jan 22 19:44:54 ethic named[2069]: managed-keys-zone ./IN/external: loading from master file 3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys failed: file not found Jan 22 19:44:54 ethic named[2069]: running And regarding the "managed-keys-zone" I have no clue. i do have a file named rndc.key or suchlike, but that is as close as I can come to anything to do with that string. ...So hope some of you DNS wizards know. tia, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.97a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Colorized compiler/linker messages
Good Day, I have seen this for some time when building ports and was wondering how it was done. GCC when compiling and linking certain programs, ebook for example, emits messages in various colors. How is that done? Where does one find what the various colors are supposed to signify? Or, is it just because it's more appealing? Thank You, Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: warn messages
On 09/01/2011 19:47, Коньков Евгений wrote: is this critical to have those messages: pkg_add biabam-0.9.7_2.tbz pkg_add: warning: package 'bash-4.1.9' requires 'gettext-0.18.1.1', but 'gettext-0.18_1' is installed pkg_add: warning: package 'biabam-0.9.7_2' requires 'gettext-0.18.1.1', but 'gettext-0.18_1' is installed is here some risk of something will not work or I may ignore those messages? Thank you I don't think it's dangerous. The gettext version is 0.18 in any case so it should works. If you're afraid you can still upgrade the package biabam with the port and it will automatically pull the new gettext dependency version. Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
warn messages
is this critical to have those messages: pkg_add biabam-0.9.7_2.tbz pkg_add: warning: package 'bash-4.1.9' requires 'gettext-0.18.1.1', but 'gettext-0.18_1' is installed pkg_add: warning: package 'biabam-0.9.7_2' requires 'gettext-0.18.1.1', but 'gettext-0.18_1' is installed is here some risk of something will not work or I may ignore those messages? Thank you -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HDD READ/Timeout messages after 8.2 Upgrade
On Fri, Dec 31, 2010 at 1:52 PM, Vladislav V. Prodan wrote: > 31.12.2010 4:10, Derrick Ryalls wrote: > > Any pointers? > > Upgrade to an old build FreeBSD 8.1 > Similar problems with working HDD in 9.0-CURRENT > > Adding ahci_load="YES" to loader.conf solved the problem. Running a hdd test now but the system seems stable now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HDD READ/Timeout messages after 8.2 Upgrade
31.12.2010 4:10, Derrick Ryalls wrote: > Any pointers? Upgrade to an old build FreeBSD 8.1 Similar problems with working HDD in 9.0-CURRENT -- Vladislav V. Prodan VVP24-UANIC +38[067]4584408 +38[099]4060508 vla...@jabber.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
HDD READ/Timeout messages after 8.2 Upgrade
0: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f irq 17 at device 0.0 on pci4 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] pcib2: irq 18 at device 10.0 on pci0 pci3: on pcib2 pci3: at device 0.0 (no driver attached) atapci1: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7fa000-0xfe7fa3ff irq 19 at device 17.0 on pci0 atapci1: [ITHREAD] atapci1: AHCI v1.20 controller with 6 6Gbps ports, PM supported ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] ohci0: mem 0xfe7f7000-0xfe7f7fff irq 18 at device 18.0 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 ehci0: mem 0xfe7fa400-0xfe7fa4ff irq 17 at device 18.2 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci0 ohci1: mem 0xfe7f8000-0xfe7f8fff irq 18 at device 19.0 on pci0 ohci1: [ITHREAD] usbus2: on ohci1 ehci1: mem 0xfe7fa800-0xfe7fa8ff irq 17 at device 19.2 on pci0 ehci1: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci1 pci0: at device 20.0 (no driver attached) isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci2: on pcib3 dc0: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem 0xfe8fbc00-0xfe8fbcff irq 20 at device 5.0 on pci2 miibus0: on dc0 bmtphy0: PHY 1 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:a0:cc:d1:aa:ba dc0: [ITHREAD] vgapci0: mem 0xfe8fc000-0xfe8f,0xfd80-0xfdff irq 22 at device 7.0 on pci2 ohci2: mem 0xfe7f9000-0xfe7f9fff irq 18 at device 20.5 on pci0 ohci2: [ITHREAD] usbus4: on ohci2 pcib4: at device 21.0 on pci0 pci1: on pcib4 re0: port 0xc800-0xc8ff mem 0xfd7ff000-0xfd7f,0xfd7f8000-0xfd7fbfff irq 16 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x2c00 re0: MAC rev. 0x miibus1: on re0 rgephy0: PHY 1 on miibus1 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 20:cf:30:e1:f7:92 re0: [FILTER] ohci3: mem 0xfe7fb000-0xfe7fbfff irq 18 at device 22.0 on pci0 ohci3: [ITHREAD] usbus5: on ohci3 ehci2: mem 0xfe7fac00-0xfe7facff irq 17 at device 22.2 on pci0 ehci2: [ITHREAD] usbus6: EHCI version 1.0 usbus6: on ehci2 acpi_button0: on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] acpi_hpet1: iomem 0xfed0-0xfed003ff on acpi0 device_attach: acpi_hpet1 attach returned 12 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xc-0xc7fff,0xcc800-0xce7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ppc0: cannot reserve I/O port range acpi_throttle0: on cpu0 hwpstate0: on cpu0 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 ad6: 30533MB at ata3-master PIO4 SATA 3Gb/s ad8: 1907729MB at ata4-master PIO4 SATA 3Gb/s ad10: 1907729MB at ata5-master PIO4 SATA 3Gb/s ad12: 1907729MB at ata6-master PIO4 SATA 3Gb/s ad14: 1907729MB at ata7-master PIO4 SATA 3Gb/s ad16: 953869MB at ata8-master PIO4 SATA 1.5Gb/s SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! uhub4: 2 ports with 2 removable, self powered uhub5: 4 ports with 4 removable, self powered uhub0: 5 ports with 5 removable, self powered uhub2: 5 ports with 5 removable, self powered uhub6: 4 ports with 4 removable, self powered uhub1: 5 ports with 5 removable, self powered uhub3: 5 ports with 5 removable, self powered ugen0.2: at usbus0 ad6: TIMEOUT - READ retrying (1 retry left) LBA=575 Trying to mount root from ufs:/dev/label/rootfs ad6: TIMEOUT - READ retrying (1 retry left) LBA=3401887 ad6: TIMEOUT - READ retrying (1 retry left) LBA=3403135 ad6: TIMEOUT - READ retrying (1 retry left) LBA=3409375 ad6: TIMEOUT - READ retrying (1 retry left) LBA=3775391 ad6: TIMEOUT - READ retrying (1 retry left) LBA=388383 ad6: TIMEOUT - READ retrying (1 retry left) LBA=388427 ad6: TIMEOUT - READ retrying (1 retry left) LBA=388463 ad6: TIMEOUT - READ retrying (1 retry left) LBA=388495 ad6: TIMEOUT - READ retrying (1 retry left) LB
gnome-keyring-daemon errors in /var/log/messages
I have a lot of these errors in /var/log/messages gnome-keyring-daemon[2169]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files I don't use gnome-keyring but some of the ports I use has pulled it in. Uninstalling is not allowed pkg_delete gnome-keyring-2.32.1 pkg_delete: package 'gnome-keyring-2.32.1' is required by these other packages and may not be deinstalled: gnome-mount-0.8_7 py26-gnome-2.28.1_2 gvfs-1.6.6 libgnomeui-2.24.4 py26-gnome-extras-2.25.3_10 firefox-3.6.13,1 thunderbird-3.1.7 gimp-app-2.6.11,1 gimp-gutenprint-5.2.4_2 gimp-2.6.11,2 gramps-3.2.5_1 So can I get rid of the errors in any way? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Console Messages
Original Message- From: per...@pluto.rain.com Sent: Sunday, November 28, 2010 10:03 PM To: gp...@thenetnow.com Cc: freebsd-questions-lo...@be-well.ilk.org ; freebsd-questions@freebsd.org Subject: Re: Console Messages "Grant Peel" wrote: > ... You may need to go -hackers for this... What is -hackers? ... ? Yep. I've observed a tendency not to put full listn...@domain addresses in messages, perhaps in an attempt to avoid harvesting by spammers :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Indeed, I have have tendencies in the past to accidentally hit the reply all instead of the reply button will pay more attention in the future. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Console Messages
"Grant Peel" wrote: > > ... You may need to go -hackers for this... > > What is -hackers? freebsd-hack...@freebsd.org? Yep. I've observed a tendency not to put full listn...@domain addresses in messages, perhaps in an attempt to avoid harvesting by spammers :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Console Messages
-Original Message- From: Lowell Gilbert Sent: Sunday, November 28, 2010 10:23 AM To: Grant Peel Cc: freebsd-questions@freebsd.org Subject: Re: Console Messages "Grant Peel" writes: I am using FreeBSD 8.0 and am getting lots of these: negative sbsize for uid = 0 +negative sbsize for uid = 0 +negative sbsize for uid = 0 +negative sbsize for uid = 0 +negative sbsize for uid = 0 any ideas what it means or how to cure it? Hmm. Interesting. You may need to go -hackers for this... Apparently a socket buffer is claiming to use a negative amount of space. Offhand I'd guess that it wrapped around, but there seem to be checks in place to avoid that. It's something running as root, which should help you track it down (most network daemons should be run as other users anyway). Glibert, What is -hackers? freebsd-hack...@freebsd.org? Thanks for the reply :-) -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Console Messages
"Grant Peel" writes: > I am using FreeBSD 8.0 and am getting lots of these: > > negative sbsize for uid = 0 > +negative sbsize for uid = 0 > +negative sbsize for uid = 0 > +negative sbsize for uid = 0 > +negative sbsize for uid = 0 > > any ideas what it means or how to cure it? Hmm. Interesting. You may need to go -hackers for this... Apparently a socket buffer is claiming to use a negative amount of space. Offhand I'd guess that it wrapped around, but there seem to be checks in place to avoid that. It's something running as root, which should help you track it down (most network daemons should be run as other users anyway). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Console Messages
Hi all, I am using FreeBSD 8.0 and am getting lots of these: negative sbsize for uid = 0 +negative sbsize for uid = 0 +negative sbsize for uid = 0 +negative sbsize for uid = 0 +negative sbsize for uid = 0 any ideas what it means or how to cure it? -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BUG: wrong log messages
2010/11/19 Коньков Евгений > > Hi, Freebsd-questions. > > Nov 18 20:27:54 meta-up kernel: > Nov 18 20:29:11 meta-up kernel: <<110>ip11f0w>: ipfw: 102 102D enyD enTyCP > T1C9P 192.168.2.173:4425 192.168.168.155:445 out via re0 > Nov 18 20:32:30 meta-up kernel: <110 iefw: 102 Deny UDP 192.168.2.90:54625 > 192.168.1.33:59306 out via re0 > Nov 18 20:33:55 meta-up kernel: 1u0 ipa re0 > Nov 18 20:42:07 meta-up kernel: > Nov 18 20:47:34 meta-up kernel: <<11101>0i>ippffww:: 110022 DDeennyy > UUDDPP 118982..9136.86.23..41931::1500030698 11929.21.61868.. > 21..91073::1417464787 oouutt vviiaa rree00 > This particular bug of overlapping output from multiple-core machines has been around for years. I don't think it's going to get fixed anytime soon. -- Jonathan Chen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
BUG: wrong log messages
Hi, Freebsd-questions. Nov 18 20:27:54 meta-up kernel: Nov 18 20:29:11 meta-up kernel: <<110>ip11f0w>: ipfw: 102 102D enyD enTyCP T1C9P 192.168.2.173:4425 192.168.168.155:445 out via re0 Nov 18 20:32:30 meta-up kernel: <110 iefw: 102 Deny UDP 192.168.2.90:54625 192.168.1.33:59306 out via re0 Nov 18 20:33:55 meta-up kernel: 1u0 ipa re0 Nov 18 20:42:07 meta-up kernel: Nov 18 20:47:34 meta-up kernel: <<11101>0i>ippffww:: 110022 DDeennyy UUDDPP 118982..9136.86.23..41931::1500030698 11929.21.61868.. 21..91073::1417464787 oouutt vviiaa rree00 sources 17.11.2010 # uname -a FreeBSD meta-up 9.0-CURRENT FreeBSD 9.0-CURRENT #6: Wed Nov 17 17:35:17 EET 2010 a...@meta-up:/usr/obj/usr/src/sys/KES_KERN_v9 i386 -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Wednesday 08 September 2010 13:50:37 Steven Friedrich wrote: > On Wednesday 08 September 2010 11:15:03 Eitan Adler wrote: > > > I'm not familiar with portsnap, so I'll let someone else troublehoot > > > that. But I want to mention that the port was added to the tree six > > > months ago... > > > > I checked it out from CVS and installed the port. I'll test the wireless > > soon. > > As I recall, I had to add this line to loader.conf because it wouldn't > autoload it: > if_bwn_load="YES" # Broadcom BCM43xx IEEE 802.11 wireless NICs > > Someone may have fixed it by now. I was doing this back during the release > of 8.1 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" I'm sorry. I cut the wrong line from loader.conf. It should have been to load firmware. I know you've gotten past it, but I wanted to set the record straight, in case anyone needs help... bwn_v4_ucode_load="YES"# Broadcom BCM43XX firmware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
As I recall, I had to add this line to loader.conf because it wouldn't > autoload it: > if_bwn_load="YES" # Broadcom BCM43xx IEEE 802.11 wireless NICs > > Someone may have fixed it by now. I was doing this back during the release of > 8.1 > I already did $kldload if_bwn && kldload bwn_v4_ucode.ko && kldload bwn_v4_lp_ucode.ko -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Wednesday 08 September 2010 11:15:03 Eitan Adler wrote: > > I'm not familiar with portsnap, so I'll let someone else troublehoot > > that. But I want to mention that the port was added to the tree six > > months ago... > > I checked it out from CVS and installed the port. I'll test the wireless > soon. As I recall, I had to add this line to loader.conf because it wouldn't autoload it: if_bwn_load="YES" # Broadcom BCM43xx IEEE 802.11 wireless NICs Someone may have fixed it by now. I was doing this back during the release of 8.1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
> I'm not familiar with portsnap, so I'll let someone else troublehoot that. > But I want to mention that the port was added to the tree six months ago... > I checked it out from CVS and installed the port. I'll test the wireless soon. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Wednesday 08 September 2010 10:49:54 Eitan Adler wrote: > On Wed, Sep 8, 2010 at 10:44 AM, Steven Friedrich wrote: > > On Wednesday 08 September 2010 10:21:44 Eitan Adler wrote: > >> On Tue, Sep 7, 2010 at 10:24 PM, Steven Friedrich > >> > > > > wrote: > >> > On Tuesday 07 September 2010 21:46:43 Eitan Adler wrote: > >> >> When I attempt to use the if_bwn driver I get the following messages: > >> >> > >> >> Is my card not supported or am I missing a step or is it something > >> >> else? > >> > >> ... > >> > >> > You need a package or port of: > >> > bwn-firmware-kmod-0.1.0 Broadcom AirForce IEEE 802.11 Firmware Kernel > >> > Module > >> > >> The closest port I find is > >> > >> net/bwi-firmware-kmod > >> > >> > >> # locate bwn-|grep ports|wc -l > >>0 > >> > >> When I searched for firmware using make quicksearch key="firmware" I > >> found net/bwn-firmware-kmod but it does not exist > >> > >> ls -lao /usr/ports/net/bwn-firmware-kmod > >> ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory > > > > I'm sorry, I read your post too quickly and missed where you clearly > > stated the problem. > > > > You said: > >> ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory > > > > This indicates that you need to update your ports tree. Do you know how? > > [r...@alphabeta ~ ]# !portsn > [r...@alphabeta ~ ]# portsnap fetch update > Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. > Fetching snapshot tag from portsnap5.FreeBSD.org... done. > Latest snapshot on server matches what we already have. > No updates needed. > Removing old files and directories... done. > Extracting new files: > Building new INDEX files... done. > [r...@alphabeta ~ ]# grep "REFUSE" /etc/portsnap.conf > # can cause problems due to missing dependencies. If you have REFUSE > REFUSE arabic chinese french german hungarian japanese > REFUSE korean polish portuguese russian ukrainian vietnamese I'm not familiar with portsnap, so I'll let someone else troublehoot that. But I want to mention that the port was added to the tree six months ago... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Wed, Sep 8, 2010 at 10:44 AM, Steven Friedrich wrote: > On Wednesday 08 September 2010 10:21:44 Eitan Adler wrote: >> On Tue, Sep 7, 2010 at 10:24 PM, Steven Friedrich > wrote: >> > On Tuesday 07 September 2010 21:46:43 Eitan Adler wrote: >> >> When I attempt to use the if_bwn driver I get the following messages: >> >> >> >> Is my card not supported or am I missing a step or is it something else? >> >> ... >> >> > You need a package or port of: >> > bwn-firmware-kmod-0.1.0 Broadcom AirForce IEEE 802.11 Firmware Kernel >> > Module >> >> The closest port I find is >> >> net/bwi-firmware-kmod >> >> >> # locate bwn-|grep ports|wc -l >> 0 >> >> When I searched for firmware using make quicksearch key="firmware" I >> found net/bwn-firmware-kmod but it does not exist >> >> ls -lao /usr/ports/net/bwn-firmware-kmod >> ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory > > I'm sorry, I read your post too quickly and missed where you clearly stated > the problem. > > You said: >> ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory > This indicates that you need to update your ports tree. Do you know how? > [r...@alphabeta ~ ]# !portsn [r...@alphabeta ~ ]# portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap5.FreeBSD.org... done. Latest snapshot on server matches what we already have. No updates needed. Removing old files and directories... done. Extracting new files: Building new INDEX files... done. [r...@alphabeta ~ ]# grep "REFUSE" /etc/portsnap.conf # can cause problems due to missing dependencies. If you have REFUSE REFUSE arabic chinese french german hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Wednesday 08 September 2010 10:21:44 Eitan Adler wrote: > On Tue, Sep 7, 2010 at 10:24 PM, Steven Friedrich wrote: > > On Tuesday 07 September 2010 21:46:43 Eitan Adler wrote: > >> When I attempt to use the if_bwn driver I get the following messages: > >> > >> Is my card not supported or am I missing a step or is it something else? > > ... > > > You need a package or port of: > > bwn-firmware-kmod-0.1.0 Broadcom AirForce IEEE 802.11 Firmware Kernel > > Module > > The closest port I find is > > net/bwi-firmware-kmod > > > # locate bwn-|grep ports|wc -l >0 > > When I searched for firmware using make quicksearch key="firmware" I > found net/bwn-firmware-kmod but it does not exist > > ls -lao /usr/ports/net/bwn-firmware-kmod > ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory I'm sorry, I read your post too quickly and missed where you clearly stated the problem. You said: > ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory This indicates that you need to update your ports tree. Do you know how? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Wednesday 08 September 2010 10:21:44 Eitan Adler wrote: > On Tue, Sep 7, 2010 at 10:24 PM, Steven Friedrich wrote: > > On Tuesday 07 September 2010 21:46:43 Eitan Adler wrote: > >> When I attempt to use the if_bwn driver I get the following messages: > >> > >> Is my card not supported or am I missing a step or is it something else? > > ... > > > You need a package or port of: > > bwn-firmware-kmod-0.1.0 Broadcom AirForce IEEE 802.11 Firmware Kernel > > Module > > The closest port I find is > > net/bwi-firmware-kmod > > > # locate bwn-|grep ports|wc -l >0 > > When I searched for firmware using make quicksearch key="firmware" I > found net/bwn-firmware-kmod but it does not exist > > ls -lao /usr/ports/net/bwn-firmware-kmod > ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory See http://www.freebsd.org/cgi/ports.cgi?query=bwn-firmware-kmod+&stype=all You should have a directory under /usr/ports/net named bwn-firmware-kmod. If you don't, then you need to update your ports skeleton. You should also be able to just use a package, like: pkg_fetch bwn-firmware-kmod or with portupgrade -N bwn-firmware-kmod HTH. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Tue, Sep 7, 2010 at 10:24 PM, Steven Friedrich wrote: > On Tuesday 07 September 2010 21:46:43 Eitan Adler wrote: >> When I attempt to use the if_bwn driver I get the following messages: >> >> Is my card not supported or am I missing a step or is it something else? >> ... > You need a package or port of: > bwn-firmware-kmod-0.1.0 Broadcom AirForce IEEE 802.11 Firmware Kernel Module > The closest port I find is net/bwi-firmware-kmod # locate bwn-|grep ports|wc -l 0 When I searched for firmware using make quicksearch key="firmware" I found net/bwn-firmware-kmod but it does not exist ls -lao /usr/ports/net/bwn-firmware-kmod ls: /usr/ports/net/bwn-firmware-kmod: No such file or directory -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BWN driver error messages
On Tuesday 07 September 2010 21:46:43 Eitan Adler wrote: > When I attempt to use the if_bwn driver I get the following messages: > > Is my card not supported or am I missing a step or is it something else? > > > siba_bwn0: mem 0xf470-0xf4703fff > irq 1 8 at device 0.0 on pci4 > bwn0 on siba_bwn0 > bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf > 0x17f ver 0x2062 rev 2) > bwn0: DMA (64 bits) > bwn0: Using 1 MSI messages > bwn0: [FILTER] > wlan0: Ethernet address: 00:21:00:e7:75:20 > bwn_v4_lp_ucode15: could not load firmware image, error 2 > bwn0: the fw file(bwn_v4_lp_ucode15) not found > bwn-open_v4_lp_ucode15: could not load firmware image, error 2 > bwn0: the fw file(bwn-open_v4_lp_ucode15) not found You need a package or port of: bwn-firmware-kmod-0.1.0 Broadcom AirForce IEEE 802.11 Firmware Kernel Module ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
BWN driver error messages
When I attempt to use the if_bwn driver I get the following messages: Is my card not supported or am I missing a step or is it something else? siba_bwn0: mem 0xf470-0xf4703fff irq 1 8 at device 0.0 on pci4 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] wlan0: Ethernet address: 00:21:00:e7:75:20 bwn_v4_lp_ucode15: could not load firmware image, error 2 bwn0: the fw file(bwn_v4_lp_ucode15) not found bwn-open_v4_lp_ucode15: could not load firmware image, error 2 bwn0: the fw file(bwn-open_v4_lp_ucode15) not found -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Forged messages being posted to freebsd-questions
On Thu, 2010-08-19 at 09:33 -0400, Rod Person wrote: > Can some explain to me or know what criteria is used to determine > when a posting to the lists need moderation? > I have read post in the past that say the list is not moderated or > comments such as above. > > But, then I try to post something and I get a "you posting is > awaiting moderator approval". Then I get a email that > my posting was rejected with comments that state "I don't see what > this has to do with FreeBSD". But, then we have > these junk mail and forged mail issues, not to mention I see replies > that go way off topic of FreeBSD. > > Just wondering. I've received a response like that "awaiting moderator approval" when I've inadvertently sent a message to a list from other than my subscribed address. I don't recall ever seeing such a response from a non-subscription list (like -questions). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
