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"
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: 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"
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: growisofs gives random error messages on 8.1 amd64
Hi, On Monday 26 July 2010 09:11:22 Polytropon wrote: > > Your command was > > growisofs -dvd-compat -speed=4 -Z /dev/cd0=imagefile.iso' > > You can omit the -speed parameter as growisofs usually (this means, > at least by my individual experience) will automatically determine > the correct writing speed. the speed parameter got stuck after I tried the lowest supported speed to exclude the speed as the cause. > > As writing started - your example did show that - I don't think > it's a problem with permissions (cd, pass, xpt devices). I did it as root. > > > On Mon, 26 Jul 2010 08:35:53 +0800, Erich Dollansky > wrote: > > The output is random. It even claimed once to have the DVD finished. > > > > But the DVD is not mountable. > > Check "file - < /dev/acd0" if an ISO file system has been written > to the DVD. > > > > > As it was never used to burn, it also could be a hardware problem. > > Reading was not a problem on 8.0. > > Could be, especially if you consider the range of errors, from "no > write at all" to "finished writing" (with no readable result). These optical media drive me crazy. I once have had a CD with a very fine crack. Once it worked, once it did not. Over time, the crack became visible. As it was an installation CD it caused a lot of problems before realising that the CD is the source. > > > > > I followed this advice: > > > > http://www.freebsd.org/gnome/docs/halfaq.html#q6 > > Just for testing, I would first eleminate HAL and all the "automation > magic". The test setting should be as "clean" as possible. > Ok, this is what I will do later when my main work has finished using X. > > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 My first BSD was running on a PDP-11 in 79. Some time has passed since then. Erich ___ 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: growisofs gives random error messages on 8.1 amd64
Sadly, I can't help you very much because I'm using a HAL/DBUS free system. That's why my assumption that HAL may be the source of your problem is just a wild guess. If it's possible, disable HAL, maybe even don't boot into Gnome, and run the growisofs as the manpage illustrates. See if the problem occurs then, too. Your command was growisofs -dvd-compat -speed=4 -Z /dev/cd0=imagefile.iso' You can omit the -speed parameter as growisofs usually (this means, at least by my individual experience) will automatically determine the correct writing speed. As writing started - your example did show that - I don't think it's a problem with permissions (cd, pass, xpt devices). On Mon, 26 Jul 2010 08:35:53 +0800, Erich Dollansky wrote: > The output is random. It even claimed once to have the DVD finished. > But the DVD is not mountable. Check "file - < /dev/acd0" if an ISO file system has been written to the DVD. > As it was never used to burn, it also could be a hardware problem. > Reading was not a problem on 8.0. Could be, especially if you consider the range of errors, from "no write at all" to "finished writing" (with no readable result). > I followed this advice: > > http://www.freebsd.org/gnome/docs/halfaq.html#q6 Just for testing, I would first eleminate HAL and all the "automation magic". The test setting should be as "clean" as possible. -- 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"
growisofs gives random error messages on 8.1 amd64
Hi, I am trying to get the DVD burner running on 8.1 The machine: 8.1-STABLE FreeBSD 8.1-STABLE #3: Sat Jul 24 20:56:05 SGT 2010 I have atapicam enabled. I lock HAL. Still, it seems I am missing something or there is a problem with my hardware. The command: hal-lock --interface org.freedesktop.Hal.Device.Storage --udi /org/freedesktop/Hal/devices/storage_model_DVDRAM_GH22NS40 --run 'growisofs -dvd-compat -speed=4 -Z /dev/cd0=imagefile.iso' Executing 'builtin_dd if=imagefile.iso of=/dev/pass0 obs=32k seek=0' The output: Executing 'builtin_dd if=imagefile.iso of=/dev/pass0 obs=32k seek=0' /dev/pass0: "Current Write Speed" is 4.1x1352KBps. 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/1604739072 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% :-( unable to wr...@lba=0h: Input/output error :-( write failed: Input/output error The output is random. It even claimed once to have the DVD finished. But the DVD is not mountable. As it was never used to burn, it also could be a hardware problem. Reading was not a problem on 8.0. Does anybody have any idea what I am missing? Erich PS: What I did: I added from the handbook atapicam according to the handbook: '18.6.9 Using the ATAPI/CAM Driver" I followed this advice: http://www.freebsd.org/gnome/docs/halfaq.html#q6 I tried to sent this question yesterday but most likely it never reached this list. ___ 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: Interpretting 3Ware error messages
Matthew Seaman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 18/05/2010 15:43:25, Doug Poland wrote: >> Hello, >> >> I have a 7.2-R i386 system running a 3ware 9500S-4LP SATA 150 >> controller with 4 SATA drives. I recently starting seeing the >> following in my logs >> >> smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Currently unreadable >> (pending) sectors >> smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Offline ^^^ >> uncorrectable sectors ^ I think this error usually indicates that there are sectors that are pending remap, but will not get remapped or marked out until the next write occurs to them. On blank space these can easily be gotten rid of with a write from dd, however you don't want to be messing with this around active data. >> Using the twi_cli program, I can examine the disk subsystem, but I do >> not see any issues with an underlying drive. >> >> Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) >> >> u0 RAID-10 OK - - - 64K 298.002 >> u0-0 RAID-1OK - - - - - >> u0-0-0 DISK OK - - p2- 149.001 >> u0-0-1 DISK OK - - p3- 149.001 >> u0-1 RAID-1OK - - - - - >> u0-1-0 DISK OK - - p0- 149.001 >> u0-1-1 DISK OK - - p1- 149.001 >> >> >> I suspect a disk problem, but cannot identify the individual disk or >> the nature of the problem. Can anyone shed some light on this? >> > Look at the SMART data for the disk(s) -- my guess is that you're seeing > sectors failing and being re-mapped by the drive firmware. If this is > happening to any significant extent the disk may well be reaching the > end of its usable life: happily you would seem to have been alerted to > that in time to do something about it without needing to run around in a > blind panic. If the remap area is not yet filled these should still get remapped at next write. If it is full replace the drive. > There's a background task you can set up on 3ware controllers that will > attempt to access all sectors of a disk specifically to bring to light > problems like this, which otherwise could go unnoticed for a long time > and lead to silent data corruption. Many controllers refer to this as 'disk scrub' or 'disk verify'. If the remap zone still has space available a scrub should juggle sectors around and clear this counter. Periodic scrubbing can find and fix the 'silent data corruption', which is data sectors which have failed between the time of the last write and the next read. When this pattern is spread out across multiple drives you won't know it until you have a drive go bad, pull it and replace, then find the array will not rebuild. I scrub my arrays every Friday night. -Mike ___ 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: Interpretting 3Ware error messages
On Tue, May 18, 2010 09:55, Matthew Seaman wrote: > > On 18/05/2010 15:43:25, Doug Poland wrote: >> Hello, >> >> I have a 7.2-R i386 system running a 3ware 9500S-4LP SATA 150 >> controller with 4 SATA drives. I recently starting seeing the >> following in my logs >> >> >> I suspect a disk problem, but cannot identify the individual disk >> or the nature of the problem. Can anyone shed some light on this? >> >> > > Look at the SMART data for the disk(s) -- my guess is that you're > seeing sectors failing and being re-mapped by the drive firmware. If > this is happening to any significant extent the disk may well be > reaching the end of its usable life: happily you would seem to have > been alerted to that in time to do something about it without needing > to run around in a blind panic. > > There's a background task you can set up on 3ware controllers that > will attempt to access all sectors of a disk specifically to bring to > light problems like this, which otherwise could go unnoticed for a > long time and lead to silent data corruption. > Will do, thanks for the info. -- Regards, Doug ___ 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: Interpretting 3Ware error messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18/05/2010 15:43:25, Doug Poland wrote: > Hello, > > I have a 7.2-R i386 system running a 3ware 9500S-4LP SATA 150 > controller with 4 SATA drives. I recently starting seeing the > following in my logs > > smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Currently unreadable > (pending) sectors > smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Offline > uncorrectable sectors > > Using the twi_cli program, I can examine the disk subsystem, but I do > not see any issues with an underlying drive. > > Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) > > u0 RAID-10 OK - - - 64K 298.002 > u0-0 RAID-1OK - - - - - > u0-0-0 DISK OK - - p2- 149.001 > u0-0-1 DISK OK - - p3- 149.001 > u0-1 RAID-1OK - - - - - > u0-1-0 DISK OK - - p0- 149.001 > u0-1-1 DISK OK - - p1- 149.001 > > > I suspect a disk problem, but cannot identify the individual disk or > the nature of the problem. Can anyone shed some light on this? > > Look at the SMART data for the disk(s) -- my guess is that you're seeing sectors failing and being re-mapped by the drive firmware. If this is happening to any significant extent the disk may well be reaching the end of its usable life: happily you would seem to have been alerted to that in time to do something about it without needing to run around in a blind panic. There's a background task you can set up on 3ware controllers that will attempt to access all sectors of a disk specifically to bring to light problems like this, which otherwise could go unnoticed for a long time and lead to silent data corruption. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvyqn8ACgkQ8Mjk52CukIyDJgCeI/olC6Qh4wA7nBfrUvfYy1fN a1gAn2f8oXQ4YaJc4WcXt6EmEYIoM+ia =qLER -END PGP SIGNATURE- ___ 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"
Interpretting 3Ware error messages
Hello, I have a 7.2-R i386 system running a 3ware 9500S-4LP SATA 150 controller with 4 SATA drives. I recently starting seeing the following in my logs smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Currently unreadable (pending) sectors smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Offline uncorrectable sectors Using the twi_cli program, I can examine the disk subsystem, but I do not see any issues with an underlying drive. Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) u0 RAID-10 OK - - - 64K 298.002 u0-0 RAID-1OK - - - - - u0-0-0 DISK OK - - p2- 149.001 u0-0-1 DISK OK - - p3- 149.001 u0-1 RAID-1OK - - - - - u0-1-0 DISK OK - - p0- 149.001 u0-1-1 DISK OK - - p1- 149.001 I suspect a disk problem, but cannot identify the individual disk or the nature of the problem. Can anyone shed some light on this? -- Regards, Doug ___ 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: ClamAV execusion died without error messages
I did not find any other error messages in log files. The following lines appeared in the section for "kernel log messages" in daily email message for Security Run Output. > pid 840 (freshclam), uid 1#: exited on signal 11 > pid 875 (clamd), uid 1#: exited on signal 10 I am not sure what they mean exactly. Thanks. - Ming -Original Message- From: Bill Moran [mailto:wmo...@potentialtech.com] Sent: Sunday, March 01, 2009 6:37 PM To: Ming Tang Cc: freebsd-questions@freebsd.org Subject: Re: ClamAV execusion died without error messages "Ming Tang" wrote: > > Bill, > > Thank you for the response. > > I tried and did not figure out where is the problem. I am attaching > the command line prompts and clamd.log and freshclam.log content here. > > ns1# > ns1# ./clamav-clamd.sh status > clamav_clamd is not running. > ns1# ./clamav-clamd.sh start > Starting clamav_clamd. > LibClamAV Warning: ** > LibClamAV Warning: *** The virus database is older than 7 days! *** > LibClamAV Warning: *** Please update it as soon as possible.*** > LibClamAV Warning: ** > ns1# ./clamav-clamd.sh status > clamav_clamd is not running. > ns1# > > ns1# cat clamd.log > +++ Started at Sat Feb 28 10:43:36 2009 > clamd daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Running as > user clamav (UID 1#, GID 1#) Log file size limited to 1048576 bytes. > Reading databases from /var/db/clamav > Not loading PUA signatures. > Loaded 455125 signatures. > LOCAL: Removing stale socket file /var/run/clamav/clamd.sock > LOCAL: Unix socket file /var/run/clamav/clamd.sock > LOCAL: Setting connection queue length to 15 > Limits: Global size limit set to 104857600 bytes. > Limits: File size limit set to 26214400 bytes. > Limits: Recursion level limit set to 16. > Limits: Files limit set to 1. > Archive support enabled. > Algorithmic detection enabled. > Portable Executable support enabled. > ELF support enabled. > Mail files support enabled. > OLE2 support enabled. > PDF support enabled. > HTML support enabled. > Self checking every 1800 seconds. > > .. > > ns1# > ns1# ./clamav-freshclam.sh status > clamav_freshclam is not running. > ns1# ./clamav-freshclam.sh start > Starting clamav_freshclam. > ns1# ./clamav-freshclam.sh status > clamav_freshclam is not running. > ns1# > > ns1# cat freshclam1.log > -- > freshclam daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) That's certainly strange. Try starting the processes manually instead of using the rc scripts, and see if they exit with an error of some sort. Also, I seem to remember having difficult with permissions under some circumstances, where the processes couldn't write to directories they needed -- check that both clamd and freshclam are running as the same user/group. See if you're getting core files anywhere (check /var/log/messages for coredump messages). Audit your config files and make sure nothing is out of sorts. Sorry I can't give you any more specific information, but I've not seen the problem you're having. -- Bill Moran http://www.potentialtech.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: ClamAV execusion died without error messages
In response to "Ming Tang" : > I did not find any other error messages in log files. The following lines > appeared in the section for "kernel log messages" in daily email message for > Security Run Output. > > > pid 840 (freshclam), uid 1#: exited on signal 11 This is a "segmentation violation". It means the program is trying to access memory that it never allocated (i.e., it's trying to access memory belonging to another process). This generally happens in 1 of 3 cases: 1) The program is a virus, etc trying to steal data from other programs. 2) The program was written poorly and has memory management bugs. 3) Your hardware (RAM) is buggy and memory bits are flipping by accident causing unpredictable memory access. http://en.wikipedia.org/wiki/Segmentation_violation > > pid 875 (clamd), uid 1#: exited on signal 10 This is a more unusual error, but still related to memory: http://en.wikipedia.org/wiki/Bus_error This error is more difficult to create using software than a segfault. My theory at this point is that you either a) downloaded precompiled packages that are not supported by your hardware. b) built these from ports with funky CFLAGS settings My recommendation would be to start out by deinstalling clam, and rebuilding it from ports, ensuring that your /etc/make.conf settings are all set to defaults. If the problem persists, install a program like memtest86, or use some other RAM tester to ensure that your hardware is solid. HTH -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: ClamAV execusion died without error messages
"Ming Tang" wrote: > > Bill, > > Thank you for the response. > > I tried and did not figure out where is the problem. I am attaching the > command line prompts and clamd.log and freshclam.log content here. > > ns1# > ns1# ./clamav-clamd.sh status > clamav_clamd is not running. > ns1# ./clamav-clamd.sh start > Starting clamav_clamd. > LibClamAV Warning: ** > LibClamAV Warning: *** The virus database is older than 7 days! *** > LibClamAV Warning: *** Please update it as soon as possible.*** > LibClamAV Warning: ** > ns1# ./clamav-clamd.sh status > clamav_clamd is not running. > ns1# > > ns1# cat clamd.log > +++ Started at Sat Feb 28 10:43:36 2009 > clamd daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) > Running as user clamav (UID 1#, GID 1#) > Log file size limited to 1048576 bytes. > Reading databases from /var/db/clamav > Not loading PUA signatures. > Loaded 455125 signatures. > LOCAL: Removing stale socket file /var/run/clamav/clamd.sock > LOCAL: Unix socket file /var/run/clamav/clamd.sock > LOCAL: Setting connection queue length to 15 > Limits: Global size limit set to 104857600 bytes. > Limits: File size limit set to 26214400 bytes. > Limits: Recursion level limit set to 16. > Limits: Files limit set to 1. > Archive support enabled. > Algorithmic detection enabled. > Portable Executable support enabled. > ELF support enabled. > Mail files support enabled. > OLE2 support enabled. > PDF support enabled. > HTML support enabled. > Self checking every 1800 seconds. > > .. > > ns1# > ns1# ./clamav-freshclam.sh status > clamav_freshclam is not running. > ns1# ./clamav-freshclam.sh start > Starting clamav_freshclam. > ns1# ./clamav-freshclam.sh status > clamav_freshclam is not running. > ns1# > > ns1# cat freshclam1.log > -- > freshclam daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) That's certainly strange. Try starting the processes manually instead of using the rc scripts, and see if they exit with an error of some sort. Also, I seem to remember having difficult with permissions under some circumstances, where the processes couldn't write to directories they needed -- check that both clamd and freshclam are running as the same user/group. See if you're getting core files anywhere (check /var/log/messages for coredump messages). Audit your config files and make sure nothing is out of sorts. Sorry I can't give you any more specific information, but I've not seen the problem you're having. -- Bill Moran http://www.potentialtech.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: ClamAV execusion died without error messages
Bill, Thank you for the response. I tried and did not figure out where is the problem. I am attaching the command line prompts and clamd.log and freshclam.log content here. ns1# ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ./clamav-clamd.sh start Starting clamav_clamd. LibClamAV Warning: ** LibClamAV Warning: *** The virus database is older than 7 days! *** LibClamAV Warning: *** Please update it as soon as possible.*** LibClamAV Warning: ** ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ns1# cat clamd.log +++ Started at Sat Feb 28 10:43:36 2009 clamd daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Running as user clamav (UID 1#, GID 1#) Log file size limited to 1048576 bytes. Reading databases from /var/db/clamav Not loading PUA signatures. Loaded 455125 signatures. LOCAL: Removing stale socket file /var/run/clamav/clamd.sock LOCAL: Unix socket file /var/run/clamav/clamd.sock LOCAL: Setting connection queue length to 15 Limits: Global size limit set to 104857600 bytes. Limits: File size limit set to 26214400 bytes. Limits: Recursion level limit set to 16. Limits: Files limit set to 1. Archive support enabled. Algorithmic detection enabled. Portable Executable support enabled. ELF support enabled. Mail files support enabled. OLE2 support enabled. PDF support enabled. HTML support enabled. Self checking every 1800 seconds. .. ns1# ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ./clamav-freshclam.sh start Starting clamav_freshclam. ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ns1# cat freshclam1.log -- freshclam daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Thanks. - Ming -Original Message- From: Bill Moran [mailto:wmo...@potentialtech.com] Sent: Friday, February 27, 2009 1:57 PM To: mtan...@comcast.net Cc: freebsd-questions@freebsd.org Subject: Re: ClamAV execusion died without error messages In response to mtan...@comcast.net: > > > My server is currently running on FreeBSD 5.4-RELEASE #0. > > > > I installed the port software, P5-Mail-ClamAV with sendmail along with > others: Spamassassin and Milter etc. Everything was compiled fine, and sendmail is working with Spamassin too. However, when I execute clamav-clamd.sh, clamav-freshclam.sh, both software start for a very short momonet and died without any complaims. I could not see any clamav items running by executing 'ps -axw'. > > > > My last executed piece software, clamav-milter.sh is complaining > missing and waiting for a socket, clam-milter.sorc. > > > > I did configuration for sendmail, but very littler on clamav. Can > anyone familiar with Clamav helps to provide a clue on what is going > wrong? The rc script isn't going to tell you anything. Look at your clamd.conf to see where it's logging to, then look at the log files to see what's going wrong. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: ClamAV execusion died without error messages
In response to mtan...@comcast.net: > > > My server is currently running on FreeBSD 5.4-RELEASE #0. > > > > I installed the port software, P5-Mail-ClamAV with sendmail along with > others: Spamassassin and Milter etc. Everything was compiled fine, and > sendmail is working with Spamassin too. However, when I > execute clamav-clamd.sh, clamav-freshclam.sh, both software start for a very > short momonet and died without any complaims. I could not see any clamav > items running by executing 'ps -axw'. > > > > My last executed piece software, clamav-milter.sh is complaining missing and > waiting for a socket, clam-milter.sorc. > > > > I did configuration for sendmail, but very littler on clamav. Can anyone > familiar with Clamav helps to provide a clue on what is going wrong? The rc script isn't going to tell you anything. Look at your clamd.conf to see where it's logging to, then look at the log files to see what's going wrong. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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"
ClamAV execusion died without error messages
My server is currently running on FreeBSD 5.4-RELEASE #0. I installed the port software, P5-Mail-ClamAV with sendmail along with others: Spamassassin and Milter etc. Everything was compiled fine, and sendmail is working with Spamassin too. However, when I execute clamav-clamd.sh, clamav-freshclam.sh, both software start for a very short momonet and died without any complaims. I could not see any clamav items running by executing 'ps -axw'. My last executed piece software, clamav-milter.sh is complaining missing and waiting for a socket, clam-milter.sorc. I did configuration for sendmail, but very littler on clamav. Can anyone familiar with Clamav helps to provide a clue on what is going wrong? Thank you! Ming Tang - Ming ___ 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: How can I see all of error messages about server's situation in a log file ?
Sometimes, when I monitor my server on the monitor, I see some messages which are about inform, warning or kernel messages. But I couldn't see these messages in /var/log/messages. by default syslog.conf direct them to many files depending of type. look at syslog.conf and check it, or maybe modify. personally i always change syslog.conf to put all to /var/log/messages How can I do that ? What do I need to set to this ? ___ 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: How can I see all of error messages about server's situation in a log file ?
Yavuz Maslak wrote: > I use freebsd7.1-release. > > Sometimes, when I monitor my server on the monitor, I see some > messages which are about inform, warning or kernel messages. > But I couldn't see these messages in /var/log/messages. > How can I do that ? > What do I need to set to this ? Edit /etc/syslog.conf You will some commented out entries like: #console.info /var/log/console.log Remove the hash, restart syslog (/etc/rc.d/syslogd restart) and these messages will get stored in /var/log/console.log ___ 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"
How can I see all of error messages about server's situation in a log file ?
I use freebsd7.1-release. Sometimes, when I monitor my server on the monitor, I see some messages which are about inform, warning or kernel messages. But I couldn't see these messages in /var/log/messages. How can I do that ? What do I need to set to this ? ___ 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"
Strange error messages in /var/log/messages
Hello My system: FreeBSD firewall.acutronic.ch 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Fri Dec 12 15:35:05 CET 2008 mar...@firewall.acutronic.ch:/usr/obj/usr/src/sys/FREEBSD_AMD64 amd64 Since I compiled the following options in my kernel [snip] # Firewall options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=5 options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options DUMMYNET <- this option! options HZ=1000 <- this option! [snip] I get the following in /var/log/messages (and various others like these): [snip] Dec 16 16:05:32 firewall kernel: A Dec 16 16:05:32 firewall kernel: 3 Dec 16 16:05:32 firewall kernel: 2 [snip] What I did wrong? Regards, -- Martin Schweizer PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch; public key : http://www.pc-service.ch/pgp/public_key.asc; fingerprint: EC21 CA4D 5C78 BC2D 73B7 10F9 C1AE 1691 D30F D239; ___ 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: ACPI CA Embedded Controller (EC) error messages MSI notebook
On Fri, Jun 20, 2008 at 11:46 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Fri, Jun 20, 2008 at 11:37 AM, Pietro Cerutti <[EMAIL PROTECTED]> wrote: >> |> I have a MSI-1034 (M662) Core2 Duo. Attached is my (patched) asl. Dunno >> |> if it can be of any use for you, though >> |> >> |> >> | >> | Thanks Pietro, I really appreciate this. Can I ask by chance, does this >> | turn on your battery indicator light on your front panel on your MSI >> | notebook? >> >> This was working anyway, IIRC. > > Ah yea well mine is now completely off charging or not :(! I > thought this could be related to the status handler for the battery > but on second thought this maybe something else. > >> | >> | Also, what's the downside of changing ASL? Can I brick my notebook? >> I just >> | have to ask since I am assuming I will be changing the underlying AML >> | generated which I suppose can cause chaos (i.e. I want to make sure I can >> | reset it). >> >> No, it just changes the ACPI code used by the operating system. It >> doesn't modify anything in your laptop. If it doesn't work, just disable >> it and reboot :) > > Ah, I got it. I get confused. The ASL is groked by the core CA > (which provides the main table API for the kernel). Duh! (my ACPI is > rusty) > > Ok, let me look at it some more and see if I can integrate it in for > the battery status section...I'd like to try to get this notebook to > be fully functional if possible! Well still no dice and my battery status light remains off. Question, how did you patch this (or where did you get it patched)? The issue is still CA complaining there isn't a handler for the region. -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI CA Embedded Controller (EC) error messages MSI notebook
On Fri, Jun 20, 2008 at 11:37 AM, Pietro Cerutti <[EMAIL PROTECTED]> wrote: > |> I have a MSI-1034 (M662) Core2 Duo. Attached is my (patched) asl. Dunno > |> if it can be of any use for you, though > |> > |> > | > | Thanks Pietro, I really appreciate this. Can I ask by chance, does this > | turn on your battery indicator light on your front panel on your MSI > | notebook? > > This was working anyway, IIRC. Ah yea well mine is now completely off charging or not :(! I thought this could be related to the status handler for the battery but on second thought this maybe something else. > | > | Also, what's the downside of changing ASL? Can I brick my notebook? > I just > | have to ask since I am assuming I will be changing the underlying AML > | generated which I suppose can cause chaos (i.e. I want to make sure I can > | reset it). > > No, it just changes the ACPI code used by the operating system. It > doesn't modify anything in your laptop. If it doesn't work, just disable > it and reboot :) Ah, I got it. I get confused. The ASL is groked by the core CA (which provides the main table API for the kernel). Duh! (my ACPI is rusty) Ok, let me look at it some more and see if I can integrate it in for the battery status section...I'd like to try to get this notebook to be fully functional if possible! -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI CA Embedded Controller (EC) error messages MSI notebook
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alexander Sack wrote:
|
|
| Pietro Cerutti-4 wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA512
|>
|> Alexander Sack wrote:
|> | Hello Folks:
|> |
|> | I have a MSI-1710A ("Megabook") which is Athlon X2 Turon based
|> | notebook (4GB RAM,
|> |
|> | Anyway during a 7.0-RELEASE-amd64 boot up I see:
|> |
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (evregion-0427): No handler for Region [EC__]
|> | (0xff00011cf680) [EmbeddedControl] [20070320]
|> | ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler
|> [20070320]
|> | ACPI Error (psparse-0626): Method parse/execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> | ACPI Error (uteval-0309): Method execution failed
|> | [\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
|> | AE_NOT_EXIST
|> |
|> | After looking at my ASL code, I noticed that YES this code was
|> | generated by the MSFT devkit which means its probably NOT spec
|> | compliant.
|> |
|> | RSDT: Length=64, Revision=1, Checksum=83,
|> | OEMID=MSI_NB, OEM Table ID=MEGABOOK, OEM Revision=0x7000725,
|> | Creator ID=MSFT, Creator Revision=0x97
|> | Entries={ 0xcffc0200, 0xcffc0390, 0xcffc03f0, 0xcffc0430,
|> | 0xcffce040, 0xcffc42f0, 0xcffc4330 }
|> |
|> | The pertinent section (DSDT) condensed is:
|> |
|> | _SB.PCI0.SBRG:
|> |
|> | Device (EC) {
|> | Device (BAT1) {
|> | Name (_HID, EisaId ("PNP0C0A"))
|> | Name (_UID, One)
|> | Name (_PCL, Package (0x01)
|> | {
|> | _SB
|> | })
|> | Method (_STA, 0, NotSerialized)
|> | {
|> |If (MYEC)
|> |{
|> | If (MBTS)
|> | {
|> | Return (0x1F)
|> | }
|> | Else
|> | {
|> | Return (0x0F)
|> | }
|> |}
|> |Else
|> |{
|> |
Re: ACPI CA Embedded Controller (EC) error messages MSI notebook
Else
> | {
> | Return (0x0F)
> | }
> |}
> |Else
> |{
> | Return (0x0F)
> |}
> | }
> | }
> |
> | I've read http://www.freebsd.org/doc/en/books/handbook/acpi-debug.html
> | which is very helpful. In any event should I attempt to try to
> | rewrite my ASL to make it more spec conforming so Intel's CA likes it
> | OR would it be better to try to work around it in the CA directly. I
> | believe I understand the problem but I'm still reading the spec
> | regarding embedded controller sections (which is a little different).
> |
> | I believe I'm probably not the only MSI FreeBSD owner so I figured I
> | would share!
>
> You're not the only one!
>
> I have a MSI-1034 (M662) Core2 Duo. Attached is my (patched) asl. Dunno
> if it can be of any use for you, though
>
>
Thanks Pietro, I really appreciate this. Can I ask by chance, does this
turn on your battery indicator light on your front panel on your MSI
notebook?
Also, what's the downside of changing ASL? Can I brick my notebook? I just
have to ask since I am assuming I will be changing the underlying AML
generated which I suppose can cause chaos (i.e. I want to make sure I can
reset it).
-aps
--
View this message in context:
http://www.nabble.com/ACPI-CA-Embedded-Controller-%28EC%29-error-messages-MSI-notebook-tp18031074p18032095.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI CA Embedded Controller (EC) error messages MSI notebook
Hello Folks:
I have a MSI-1710A ("Megabook") which is Athlon X2 Turon based
notebook (4GB RAM,
Anyway during a 7.0-RELEASE-amd64 boot up I see:
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (evregion-0427): No handler for Region [EC__]
(0xff00011cf680) [EmbeddedControl] [20070320]
ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
ACPI Error (uteval-0309): Method execution failed
[\\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xff00011d24c0),
AE_NOT_EXIST
After looking at my ASL code, I noticed that YES this code was
generated by the MSFT devkit which means its probably NOT spec
compliant.
RSDT: Length=64, Revision=1, Checksum=83,
OEMID=MSI_NB, OEM Table ID=MEGABOOK, OEM Revision=0x7000725,
Creator ID=MSFT, Creator Revision=0x97
Entries={ 0xcffc0200, 0xcffc0390, 0xcffc03f0, 0xcffc0430,
0xcffce040, 0xcffc42f0, 0xcffc4330 }
The pertinent section (DSDT) condensed is:
_SB.PCI0.SBRG:
Device (EC) {
Device (BAT1) {
Name (_HID, EisaId ("PNP0C0A"))
Name (_UID, One)
Name (_PCL, Package (0x01)
{
_SB
})
Method (_STA, 0, NotSerialized)
{
If (MYEC)
{
If (MBTS)
{
Return (0x1F)
}
Else
{
Return (0x0F)
}
}
Else
{
Return (0x0F)
}
}
}
I've read http://www.freebsd.org/doc/en/books/handbook/acpi-debug.html
which is very helpful. In any event should I attempt to try to
rewrite my ASL to make it more spec conforming so Intel's CA likes it
OR would it be better to try to work around it in the CA directly. I
believe I understand the problem but I'm still reading the spec
regarding embedded controller sections (which is a little different).
I believe I'm probably not the only MSI FreeBSD owner so I figured I
would share!
Thanks a lot!
-aps
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, se
Re: Shell scripting - suppressing and eliminating error messages
Paul Schmehl wrote:
> --On Tuesday, May 20, 2008 17:36:26 -0500 Paul Schmehl <[EMAIL PROTECTED]>
> wrote:
> > if ( ${BATCH} ); then
> > [...]
> > 1: not found
>
> Never mindforgot to use [ ] for test instead of ( ).
If the value of $BATCH is always either 0 and 1, a neat
trick is to define two shell functions:
0() { false; }
1() { true; }
Then you can savely write:
if ( $BATCH ); then
Or even:
if $BATCH; then
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"Clear perl code is better than unclear awk code; but NOTHING
comes close to unclear perl code" (taken from comp.lang.awk FAQ)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell scripting - suppressing and eliminating error messages
On Tue, May 20, 2008 at 05:36:26PM -0500, Paul Schmehl wrote:
> I'm using the following construction in a pkg-deinstall script for a port I
> maintain:
>
> if ( ${BATCH} ); then
This should read:
if [ -n "${BATCH}" ] ; then
--
Jonathan Chen <[EMAIL PROTECTED]>
--
"Irrationality is the square root of all evil"
- Douglas Hofstadter
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell scripting - suppressing and eliminating error messages
Hi, Paul--
On May 20, 2008, at 3:36 PM, Paul Schmehl wrote:
I'm using the following construction in a pkg-deinstall script for a
port I maintain:
if ( ${BATCH} ); then
[ ... ]
Why is this error printing to stdout and how can I suppress it? Or
is there a flaw in the logic that, if fixed, would resolve this
problem?
It's happening because the shell normally tries to run the command in
the if statement, and evaluate the return value. Your system doesn't
have a "1" or "0" command, so that produces the "1: not found"
message. For /bin/sh, use the test macro instead:
% BATCH=1
% if [ ${BATCH} -gt 0 ]; then echo yeah; fi
yeah
% BATCH=0
% if [ ${BATCH} -gt 0 ]; then echo yeah; fi
Another way to do this is to use string comparisons, especially if env
variable is supposed to either be defined or not defined, and what the
value it is set to if defined doesn't matter:
% unset BATCH
% if [ "x${BATCH}" != "x" ]; then echo yeah; fi
% BATCH=1
% if [ "x${BATCH}" != "x" ]; then echo yeah; fi
yeah
% BATCH=0
% if [ "x${BATCH}" != "x" ]; then echo yeah; fi
yeah
Regards,
--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell scripting - suppressing and eliminating error messages
--On Tuesday, May 20, 2008 17:36:26 -0500 Paul Schmehl <[EMAIL PROTECTED]>
wrote:
I'm using the following construction in a pkg-deinstall script for a port I
maintain:
if ( ${BATCH} ); then
The idea is, if you type make BATCH=1 deinstall, the port will deinstall
without running an interactive portion of the pkg-deinstall script. If you
type make deinstall, the pkg-deinstall script runs.
The script works, but, when you use BATCH=1, it generates an error message:
# make BATCH=1 deinstall clean
===> Deinstalling for security/sguil-server
===> Deinstalling sguil-server-0.7.0_1
Stopping sguild..
sguild not running?
1: not found
Why is this error printing to stdout and how can I suppress it? Or is there
a flaw in the logic that, if fixed, would resolve this problem?
Never mindforgot to use [ ] for test instead of ( ). My perl is getting in
the way of my shell. :-(
--
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Shell scripting - suppressing and eliminating error messages
I'm using the following construction in a pkg-deinstall script for a port I
maintain:
if ( ${BATCH} ); then
The idea is, if you type make BATCH=1 deinstall, the port will deinstall
without running an interactive portion of the pkg-deinstall script. If you
type make deinstall, the pkg-deinstall script runs.
The script works, but, when you use BATCH=1, it generates an error message:
# make BATCH=1 deinstall clean
===> Deinstalling for security/sguil-server
===> Deinstalling sguil-server-0.7.0_1
Stopping sguild..
sguild not running?
1: not found
Why is this error printing to stdout and how can I suppress it? Or is there a
flaw in the logic that, if fixed, would resolve this problem?
--
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
On Fri, May 16, 2008 at 01:52:50PM -0700, Chris St Denis wrote: > Doesn't seem to work with my IBM ServeRAID 8k > > CLI > open /readonly aac0 > Executing: open /readonly=TRUE "aac0" > Command Error: current controller software.> You can avoid this issue by building a kernel with the latest aac(4) driver from RELENG_6/RELENG_7/HEAD, but you're probably better off just using arcconf instead of aaccli. -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
Doesn't seem to work with my IBM ServeRAID 8k CLI > open /readonly aac0 Executing: open /readonly=TRUE "aac0" Command Error: current controller software.> Seems a little odd it's referencing a dll (which doesn't exist on the system) Dan Nelson wrote: In the last episode (May 16), Robert Jesacher said: On 06.05.2008, at 22:02, Ed Maste wrote: On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: I pulled out one of the raid5 drives to test the functionality and noticed that FreeBSD didn't seem to notice the disk failure at all. I was expecting kernel messages about it, but got nothing. This is missing functionality in the aac(4) driver. For now about the best you can do is regularly poll the status using Adaptec's CLI tool "arcconf." -ED The tool you need to look into is: sysutils/aaccli . I think arctool is only for arcmsr-devices. unfortunately aaccli doesn't provide the possibility to use it with parameters, so you probably need to use it with an expect-script. aaccli is most definitely scriptable: $ aaccli "open /readonly aac0 : enclosure show status : disk show smart : container list /full" -- Chris St Denis Programmer SmarttNet (www.smartt.com) Ph: 604-473-9700 Ext. 200 --- "Smart Internet Solutions For Businesses" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
In the last episode (May 16), Robert Jesacher said: > On 06.05.2008, at 22:02, Ed Maste wrote: >> On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: >>> I pulled out one of the raid5 drives to test the functionality and >>> noticed that FreeBSD didn't seem to notice the disk failure at all. >>> I was expecting kernel messages about it, but got nothing. >> >> This is missing functionality in the aac(4) driver. For now about >> the best you can do is regularly poll the status using Adaptec's CLI >> tool "arcconf." >> >> -ED > > The tool you need to look into is: sysutils/aaccli . I think arctool > is only for arcmsr-devices. unfortunately aaccli doesn't provide the > possibility to use it with parameters, so you probably need to use it > with an expect-script. aaccli is most definitely scriptable: $ aaccli "open /readonly aac0 : enclosure show status : disk show smart : container list /full" -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
On 06.05.2008, at 22:02, Ed Maste wrote: On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: I pulled out one of the raid5 drives to test the functionality and noticed that FreeBSD didn't seem to notice the disk failure at all. I was expecting kernel messages about it, but got nothing. This is missing functionality in the aac(4) driver. For now about the best you can do is regularly poll the status using Adaptec's CLI tool "arcconf." -ED The tool you need to look into is: sysutils/aaccli . I think arctool is only for arcmsr-devices. unfortunately aaccli doesn't provide the possibility to use it with parameters, so you probably need to use it with an expect-script. On the adaptec 2410SA I activated the "alarm" feature in the controller bios, which helps me, because its a home server but this will not help you if your server is sitting somewhere else. Because of this limitation (and a few other things with the controller) I'm certainly looking for an other solution. In my case a ZFS-based software RAID will suffice, but this might not be desirable for you. Take care & good luck, Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
Robert Jesacher wrote: On 06.05.2008, at 22:02, Ed Maste wrote: On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: I pulled out one of the raid5 drives to test the functionality and noticed that FreeBSD didn't seem to notice the disk failure at all. I was expecting kernel messages about it, but got nothing. This is missing functionality in the aac(4) driver. For now about the best you can do is regularly poll the status using Adaptec's CLI tool "arcconf." -ED The tool you need to look into is: sysutils/aaccli . I think arctool is only for arcmsr-devices. unfortunately aaccli doesn't provide the possibility to use it with parameters, so you probably need to use it with an expect-script. On the adaptec 2410SA I activated the "alarm" feature in the controller bios, which helps me, because its a home server but this will not help you if your server is sitting somewhere else. Because of this limitation (and a few other things with the controller) I'm certainly looking for an other solution. In my case a ZFS-based software RAID will suffice, but this might not be desirable for you. Take care & good luck, Robert arcconf from ports works fine. It hangs on exit but does die off eventually and doesn't do any harm sitting in background for a while when run from cron, and from the commandline I can just ^c it. Here is what I used in cron for anyone who is interested: /usr/local/sbin/arcconf GETCONFIG 1 LD | egrep '(name|Status)' It gives results like this which work well. Could probably be incorporated into the daily run output, but I don't know exactly how off hand. Logical device name : Boot mirror Status of logical device : Optimal Logical device name : Data raid5 Status of logical device : Optimal According to arcconf my card doesn't have an audible alarm :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: > I pulled out one of the raid5 drives to test the functionality and > noticed that FreeBSD didn't seem to notice the disk failure at all. I > was expecting kernel messages about it, but got nothing. This is missing functionality in the aac(4) driver. For now about the best you can do is regularly poll the status using Adaptec's CLI tool "arcconf." -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AAC driver. No kernel error messages for failed raid5?
I recently setup a new FreeBSD 7.0 AMD64 server with an IBM ServeRAID-8k configured with a raid5 for data and raid1 for OS. I pulled out one of the raid5 drives to test the functionality and noticed that FreeBSD didn't seem to notice the disk failure at all. I was expecting kernel messages about it, but got nothing. This is a bit concerning because I don't look at the server physically every day and want to know ASAP if a drive fails. I tried setting options AAC_DEBUG=1 but that produces a lot of messages even during normal use so I'd rather not leave that on. Is this a bug in the driver, or simply missing functionality? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
DDNS, ISC-DHCPD, and Bind... not working because of strange error messages
I did actually manage to get this to work, and I can't exactly work out
what changed to cause this error.
I set this up at the end of last year, and it worked- kind of. The
failure was my own by not using a proper FQDN, but it worked
unofficially anyway. Records were updating etc: all happy.
Anyway, I finally got the FQDN worked out (split horizon dns- external
and internal views), but I find that the ddns is not working: and not
because of the changes I made. I looked back and found the problem going
on for month. My messages file has these entries, and no amount of
googling has brought me any closer to finding out what they could mean,
or why my clients aren't updating:
Mar 27 16:18:54 {$HOSTNAME} dhcpd: pool.ntp.org: no A record associated
with address
I've edited the hostname to protect the innocent.
What I can't figure out is why would dhcpd be looking at pool.ntp.org? I
ran a dig on pool.ntp.org on the off chance it was busted- but of course
it was not. And this record pops up everytime I renew my ip addresses.
Weird...
Little help anyone?
Cheers
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord, CD-R error messages with 7.0-RELEASE
On Monday 10 March 2008, Wojciech Puchar wrote: > > DFLTPHYS(65536) > > cam_periph_mapmem: attempt to map 251904 bytes, which is greater than > > DFLTPHYS(65536) > > > > followed by lots more cam_periph_mapmem warnings. > > > > Desoite all this the CD verifies OK - should I worry? > > no :) > > but it is strange anyway. i use cdrecord sometimes and get no errors. I wonder if it's a hardware related issue with that particular drive. I think I might have a Mitsumi CD writer I could install as a temporary test in place of the Pioneer. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord, CD-R error messages with 7.0-RELEASE
DFLTPHYS(65536) cam_periph_mapmem: attempt to map 251904 bytes, which is greater than DFLTPHYS(65536) followed by lots more cam_periph_mapmem warnings. Desoite all this the CD verifies OK - should I worry? no :) but it is strange anyway. i use cdrecord sometimes and get no errors. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord, CD-R error messages with 7.0-RELEASE
On Sunday 09 March 2008, Wojciech Puchar wrote: > it's good idea to remove atapicd from kernel while using atapicam - don't > keep both. > > personally - i use only atapicam. I have a similar problem so tried removing atapicd from my kernel but still have the problem. At boot time I get: Waiting 5 seconds for SCSI devices to settle unknown: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 unknown: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: cd present [1592080 x 2048 byte records] Then when writing and verifying a CD I get: unknown: WARNING - unknown CMD (0xac) read data overrun 8>0 unknown: WARNING - unknown CMD (0xac) read data overrun 8>0 unknown: WARNING - unknown CMD (0xac) read data overrun 8>0 unknown: WARNING - unknown CMD (0xac) read data overrun 8>0 unknown: FAILURE - READ_DVD_STRUCTURE ILLEGAL REQUEST asc=0x30 ascq=0x02 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 unknown: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x4d 0x00 0x02 cam_periph_mapmem: attempt to map 262144 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 260096 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 258048 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 256000 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 253952 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 251904 bytes, which is greater than DFLTPHYS(65536) followed by lots more cam_periph_mapmem warnings. Desoite all this the CD verifies OK - should I worry? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord, CD-R error messages with 7.0-RELEASE
it's good idea to remove atapicd from kernel while using atapicam - don't keep both. personally - i use only atapicam. When trying to burn an ISO with cdrecord: cdrecord -v -sao fs=32m dev=1,0,0 speed=24 7.0-RELEASE-i386-disc1.iso I'm seeing these syslog messages: Mar 9 12:40:06 server kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 sks=0x00 0x00 0x0c Mar 9 12:40:06 server last message repeated 2 times Mar 9 12:40:06 server kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 sks=0x00 0x00 0x0a Mar 9 12:40:06 server kernel: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x20 ascq=0x00 Mar 9 12:40:06 server kernel: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x20 ascq=0x00 Mar 9 12:40:16 server kernel: acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x02 Mar 9 12:43:32 server kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 sks=0x00 0x00 0x07 The two CD-R's I've recorded verify with an md5 okay. Any ideas about these error messages? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cdrecord, CD-R error messages with 7.0-RELEASE
When trying to burn an ISO with cdrecord: cdrecord -v -sao fs=32m dev=1,0,0 speed=24 7.0-RELEASE-i386-disc1.iso I'm seeing these syslog messages: Mar 9 12:40:06 server kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 sks=0x00 0x00 0x0c Mar 9 12:40:06 server last message repeated 2 times Mar 9 12:40:06 server kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 sks=0x00 0x00 0x0a Mar 9 12:40:06 server kernel: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x20 ascq=0x00 Mar 9 12:40:06 server kernel: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x20 ascq=0x00 Mar 9 12:40:16 server kernel: acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x02 Mar 9 12:43:32 server kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 sks=0x00 0x00 0x07 The two CD-R's I've recorded verify with an md5 okay. Any ideas about these error messages? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gencat error messages during 6.3-STABLE buildworld
During a "make buildworld" in serial-make mode, I'm getting gencat error messages. Here is an excerpt from the output. ===> bin/csh (all) cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.dir.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.dol.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.err.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.exec.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.char.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.exp.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.file.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.func.c /usr/src/bin/csh/../../contrib/tcsh/sh.func.c: In function `iconv_catgets': /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2486: warning: passing arg 2 of pointer to function from incompatible pointer type cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.hist.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.init.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.lex.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.misc.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.parse.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.print.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.proc.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.set.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -c /usr/src/bin/csh/../../contrib/tcsh/sh.time.c cc -O2 -fno-strict-aliasing -pipe -march=prescott -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHE
Re: error messages
ivan dimitrov wrote: ACPI-0501: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE [snip] my question is - what they means and how to stop them ? I'm no expert on laptops, but it seems to me that you have either misconfigured ACPI or a laptop that doesn't support ACPI in the first place. My suggestion is that you turn off ACPI, at least until somebody who knows more about laptops than I do comes along to point out exactly what's wrong. In the meantime, perhaps APM will work properly. So you might want to give that a try. Hth, Fonz -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
error messages
hi list, on ttyv0 i am getting nonstop following messages: ACPI-0501: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SB_.C002.C003.C004.C158] (Node 0xc363e2a0), AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SB_.C158] (Node 0xc3642820), AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SB_.C15E._BST] (Node 0xc3642760), AE_NO_HARDWARE_RESPONSE my question is - what they means and how to stop them ? p.s. the bsd is "FreeBSD HP500 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #2: Tue Mar 27 22:28:16 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386" the computer is laptop HP500 thanks in advance i. - Looking for last minute shopping deals? Find them fast with Yahoo! Search. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Xorg crashing without overt error messages
At 10:31 AM 4/19/2007, Rob wrote: Hi All, I am having a problem with a new laptop where Xorg crashes but doesn't give any explicite info as to why. I have added at the end some of the output. Thanks! Rob Rob, I have seen this on some systems running nvidia drivers. I found if I cvsup'd and reinstalled the nvidia driver it would fire up just fine. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Xorg crashing without overt error messages
Hi All, I am having a problem with a new laptop where Xorg crashes but doesn't give any explicite info as to why. I have added at the end some of the output. Thanks! Rob www.empython.org Python for Electromagnetics Output from startx: Script started on Thu Apr 19 07:32:43 2007 xauth: creating new authority file /home/rob/.serverauth.67896 /usr/X11R6/bin/xauth: (argv):1: bad display name "Xenon:0" in "list" command /usr/X11R6/bin/xauth: (stdin):1: bad display name "Xenon:0" in "add" command X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: FreeBSD 6.2 i386 [ELF] Current Operating System: FreeBSD Xenon 6.2-STABLE-200704 FreeBSD 6.2-STABLE-200704 #0: Wed Apr 18 16:22:57 PDT 2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SMPROB i386 Build Date: 16 October 2006Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 19 07:32:43 2007 (==) Using config file: "/etc/X11/xorg.conf" Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! waiting for X server to shut down FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. /usr/X11R6/bin/xauth: (argv):1: bad display name "Xenon:0" in "remove" command Script done on Thu Apr 19 07:32:47 2007 End of /var/log/Xorg: **) Option "Protocol" "standard" (**) Keyboard1: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard1: XkbRules: "xorg" (**) Option "XkbModel" "pc104" (**) Keyboard1: XkbModel: "pc104" (**) Option "XkbLayout" "us" (**) Keyboard1: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard1: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. My xorg.conf: # File generated by xorgconfig. # # Copyright 2004 The X.Org Foundation # # Permission is hereby granted, free of charge, to any person obtaining # a copy of this software and associated documentation files (the # "Software"), to deal in the Software without restriction, including # without limitation the rights to use, copy, modify, merge, publish, # distribute, sublicense, and/or sell copies of the Software, and to # permit persons to whom the Software is furnished to do so, subject to # the following conditions: # # The above copyright notice and this permission notice shall be # included in all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, # EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. # IN NO EVENT SHALL # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, # ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR # OTHER DEALINGS IN THE SOFTWARE. # # Except as contained in this notice, the name of The X.Org Foundation # shall not be used in advertising or otherwise to promote the sale, use # or other dealings in this Software without prior written authorization # from The X.Org Foundation. # # ** # Refer to the xorg.conf(5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section "Module" # This loads the DBE extension module. Load"dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option"omit xfree86-dga" # don't initialise the DGA extensionEndSubSection # This loads the font modules Load"type1" #Load"speedo" Load"freetype" #Load"xtt" # This loads the GLX module Load "glx" # This loads the DRI module Load "dri" EndSection # ** # Files section. This allows default font a
Periodic Weekly Error Messages
FreeBSD seibercom.net 6.1-RELEASE-p3 FreeBSD 6.1-RELEASE-p3 #0: Sat Jul 8 04:30:13 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SEIBERCOM i386 After periodic weekly runs, the following is mailed to me via CRON. It appears to contain a considerable amount of error messages. I find it hard to believe that this is normal. Is there something wrong with my system configuration or what? Cleaning up kernel database files: Rebuilding locate database: Rebuilding whatis database: makewhatis: /usr/local/man/man8/cupsdisable.8: No such file or directory makewhatis: /usr/local/man/man8/reject.8: No such file or directory Reformatting manual pages: :108: warning [p 2, 6.5i]: can't break line Usage: .Ft function_type ... (#284) Usage: .Ft function_type ... (#348) :42: warning [p 1, 5.2i]: can't break line :42: warning [p 1, 5.2i]: can't break line :42: warning [p 1, 5.2i]: can't break line mdoc warning: A .Bl directive has no matching .El (#73) mdoc warning: A .Bl directive has no matching .El (#126) mdoc warning: A .Bl directive has no matching .El (#66) mdoc warning: A .Bl directive has no matching .El (#70) mdoc warning: A .Bl directive has no matching .El (#120) mdoc error: .It without preceding .Bl (#40) mdoc warning: A .Bl directive has no matching .El (#210) mdoc warning: A .Bl directive has no matching .El (#283) mdoc warning: A .Bl directive has no matching .El (#341) mdoc warning: A .Bl directive has no matching .El (#68) mdoc warning: A .Bl directive has no matching .El (#121) rm /usr/local/man/man1/[EMAIL PROTECTED] catman: /usr/local/man/man1/[EMAIL PROTECTED]: Permission denied rm /usr/local/man/man1/[EMAIL PROTECTED] catman: /usr/local/man/man1/[EMAIL PROTECTED]: Permission denied :260: warning [p 4, 1.7i]: can't break line :1: can't open `man1/megatron.1': No such file or directory rm /usr/local/man/man1/[EMAIL PROTECTED] catman: /usr/local/man/man1/[EMAIL PROTECTED]: Permission denied :1: can't open `man1/megatron.1': No such file or directory :1: can't open `man1/nbp.1': No such file or directory :1: can't open `man1/nbp.1': No such file or directory :1: can't open `man1/nbp.1': No such file or directory :1: can't open `man1/pap.1': No such file or directory mdoc warning: Empty input line #183 :1: can't open `man1/megatron.1': No such file or directory :535: warning [p 6, 9.0i]: can't break line :677: warning [p 7, 11.7i]: cannot adjust line :1: can't open `man1/snmptrap.1': No such file or directory :1: can't open `man1/megatron.1': No such file or directory :1: can't open `man1/megatron.1': No such file or directory :1: can't open `man1/megatron.1': No such file or directory rm /usr/local/man/man1/[EMAIL PROTECTED] catman: /usr/local/man/man1/[EMAIL PROTECTED]: Permission denied rm /usr/local/man/cat1/rar.1 :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :269: warning [p 5, 1.5i]: cannot adjust line :320: warning [p 4, 3.0i]: cannot adjust line :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :288: warning [p 4, 0.7i]: can't break line :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/mib_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_api.3': No such file or directory :1: can't open `man3/snmp_sess_api.3': No such file or directory :1: can't open `man3/snmp_sess_api.3': No such file or directory :1: can't open `man3/snmp_sess_api.3':
KLD error messages
Would someone on the -current list please get someone to fix the error message when loading KLD modules? After many years it still says "file not found" instead of "unresolved externals" and its really quit silly. DT __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail error messages
On Mar 27, 2006, at 3:26 PM, [EMAIL PROTECTED] wrote: Mar 25 23:28:15 sendmail[1181]: k2Q3wGR00214: SYSERR(root): hash map "Alias0": unsafe map file /etc/mail/aliases.db: World writable directory It repeats with IDs 1298 , 1328 , 1357 , 1439 , 1466 , & 1491 in the brackets after 'sendmail'. What significance is there to these numbers? Those of the process IDs of new sendmail child processes which start up and abort. I checked /etc/mail/aliases.db with 'll -d' and got -rw-r--r-- 1 root wheel 32768 Jun 12 2001 /etc/mail/aliases.db and as you can see it is not World writable. What is going on, and how do I stop these messages? See this section of /usr/src/contrib/sendmail/README: +---+ | DIRECTORY PERMISSIONS | +---+ Sendmail often gets blamed for many problems that are actually the result of other problems, such as overly permissive modes on directories. For this reason, sendmail checks the modes on system directories and files to determine if they can be trusted. For sendmail to run without complaining, you MUST execute the following command: chmod go-w / /etc /etc/mail /usr /var /var/spool /var/spool/ mqueue chown root / /etc /etc/mail /usr /var /var/spool /var/spool/ mqueue ...there's also a DontBlameSendmail option which disables the security checks, but you're better off fixing the issue directly. (You could also check out mtree.) -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sendmail error messages
I am running FreeBSD 4.3 (see uname -a below) and have recently started getting the following message: Mar 25 23:28:15 sendmail[1181]: k2Q3wGR00214: SYSERR(root): hash map "Alias0": unsafe map file /etc/mail/aliases.db: World writable directory It repeats with IDs 1298 , 1328 , 1357 , 1439 , 1466 , & 1491 in the brackets after 'sendmail'. What significance is there to these numbers? I checked /etc/mail/aliases.db with 'll -d' and got -rw-r--r-- 1 root wheel 32768 Jun 12 2001 /etc/mail/aliases.db and as you can see it is not World writable. What is going on, and how do I stop these messages? FreeBSD 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sending error messages to a cell phone?
On Sun, 2006-03-12 at 15:13 -0600, Nikolas Britton wrote: > I have an email address setup for my cell phone and I would like > FreeBSD to send critical error messages to this address. > > How do I tell FreeBSD to do this and more importantly should I do > this, because it costs 10 cents for each message? > > Nickolas, You can get all messages sent to root forwarded to another address by adding that address to the /etc/aliases file, this is read by sendmail or rather the database created when you run newaliases when it needs to know where to send mail. You can decide which messages to send too. As to the value - well that is up to you and how critical the machine is. hope this helps Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sending error messages to a cell phone?
I have an email address setup for my cell phone and I would like FreeBSD to send critical error messages to this address. How do I tell FreeBSD to do this and more importantly should I do this, because it costs 10 cents for each message? -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DNS nslint error messages
On 2006-02-02 17:54, Brad Gilmer <[EMAIL PROTECTED]> wrote: > Thanks Chuck and Gorgios for all your help. I was able to resolve all > of my problems with BIND and nslint. You're welcome :) > 6) And one last thing - be sure to increment the serial number on the > zone files to ensure that the new data is loaded. Heh! This is such a common catch, that I always forget about it ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DNS nslint error messages
--On Thursday, February 02, 2006 17:54:11 -0500 Brad Gilmer <[EMAIL PROTECTED]> wrote: 5) One more newbie comment - be sure to check /var/log/messages for errors. nslint does not catch everything. If you are pounding away making numerous changes, you can quickly check for log error messages by entering... # rndc reload This will cause BIND to re-read the zone files. You can also add this to /etc/rc.conf: named_flags=" -d 4" (or pick a number you like) which will start bind with the debug switch on and generate a great deal of traffic to your logs. Or you can do this: named_flags=" -d 4 -g", and rather than logging the traffic, bind will print it to stderr (your screen), and you can watch it as it runs. Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DNS nslint error messages
Thanks Chuck and Gorgios for all your help. I was able to resolve all of my problems with BIND and nslint. For the archives, I am running FreeBSD 5.4 RELEASE on an IBM 330 e-series server. I was getting numerous error messages when running nslint. The biggest problems were: 1) I have never configured BIND before, so this is all new stuff to me. Numerous errors from being a newbie in this area. 2) The FreeBSD distribution of BIND leaves some critical things out in the default installation (to be fair, maybe they are left out of all BIND9 installations - but maybe the FreeBSD community can do better than the original!). For example, there is no note in the /etc/namedb/named.conf file that you should add a 'localhost' zone. I am sure I will never forget this now that I have spent the better part of a week figuring it out, but it would be helpful if the sample named.conf included it. 3) The IPv6 stuff is turned on in named.conf by default, but I am not using IPv6 at all. So it never occurred to me that complaints from nslint such as... nslint: missing "a": localhost.org. -> 0.0.0.1 were being generated because of a bogus error in the default file /etc/namedb/master/host-v6.rev. In frustration I finally did a grep for 0.0.0.1, and there it was in this file. I fixed it by commenting out the IPv6 stuff in /etc/namedb/named.conf. 4) For other newbies, be aware that localhost. and localhost.EXAMPLE.COM are two different things. In my system I specifically point both of them to 127.0.0.1, which results in this complaint from nslint... nslint: 127.0.0.1 in use by localhost.EXAMPLE.COM. and localhost. but it seems that this error is okay. nslint is just telling you that you have two things pointing to the same IP address. 5) One more newbie comment - be sure to check /var/log/messages for errors. nslint does not catch everything. If you are pounding away making numerous changes, you can quickly check for log error messages by entering... # rndc reload This will cause BIND to re-read the zone files. 6) And one last thing - be sure to increment the serial number on the zone files to ensure that the new data is loaded. Brad ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DNS nslint error messages
Brad Gilmer wrote: > Chuck and Gorgios, > > Thank you very much for your suggestions. Sure. At least occasionally, we manage to be helpful. :-) [ ... ] > Chuck, you said, >> The second one (nslint error) recommends adding a line like: >> localhost IN A 127.0.0.1 > >> ... to your gilmer.org zone, using no "." at the end to create a > localhost.EXAMPLE.COM entry. > > But when I make this change to the localhost entry in the > /etc/namedb/master/gilmer.org file, nslint reports: > > nslint: missing "a": localhost. -> 127.0.0.1 This is the same issue as before; you don't have a "localhost" zone. > nslint: missing "ptr": localhost.gilmer.org. -> 127.0.0.1 This means that you don't have a reverse zone file for 127.in-addr.arpa: ; ; BIND reverse data file for local loopback interface ; $TTL 864000 @ IN SOA localhost. root.localhost. ( 1 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Default TTL ; @ NS localhost. 1.0.0 PTR localhost. > nslint: 127.0.0.1 in use by localhost.gilmer.org. and localhost. This means nslint is being too picky, but adding a reverse zone file with a PTR record might hush it up. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DNS nslint error messages
Brad Gilmer wrote: > I am running freebsd 5.4-STABLE on an IBM e-series 330 server. I have > recently started playing with DNS and have been largely successful. However, > nslint reports the following errors: > > nslint: missing "a": localhost. -> 127.0.0.1 > nslint: missing "a": localhost.org. -> 0.0.0.1 The first message means you're missing a localhost forward domain. Normally this won't matter, because you have a localhost entry in /etc/hosts, but you could add a localhost domain to named.conf which contains: ; ; BIND data file for local loopback interface ; $TTL 604800 @ IN SOA localhost. root.localhost. ( 1 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Default TTL @ NS localhost. @ A 127.0.0.1 The second one recommends adding a line like: localhost IN A 127.0.0.1 ... to your gilmer.org zone, using no "." at the end, to create a localhost.EXAMPLE.COM entry. > If I add the line: > > localhost. IN A 127.0.0.1 > > to my zone file, the first nslint error message goes away, but I then see the > following message in my /var/log/messages file upon named startup: > > Jan 30 18:58:55 gilmer named[15485]: master/gilmer.org:16: ignoring > out-of-zone data (localhost) > > So which is correct? named is correctly ignoring a forward A record which is out of zone. > Should I insert the A record in the zone file and ignore the nslint message, > or should I leave it out and ignore the named message? Is there something > else improperly configured on my system? > > What about the second nslint message above? Why am I getting a complaint > about 0.0.0.1? > > My /etc/namedb/master/gilmer.org file looks like this: > $TTL3600 > > gilmer.org. IN SOA ns1.gilmer.org. admin.gilmer.org. ( > 20060126; Serial > 3600; Refresh > 900 ; Retry > 360 ; Expire > 3600 ) ; Minimum > > ;DNS Servers > @ IN NS @ This should be: @ IN NS ns1.gilmer.org. ...and you ought to list at least one other NS record which points to a different nameserver. Note also that you only need to provide the "IN" column in the SOA record, it will default from there. So this: @ NS ns2.gilmer.org. ...should be OK, too. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DNS nslint error messages
On 2006-01-30 19:37, Brad Gilmer <[EMAIL PROTECTED]> wrote: > I am running freebsd 5.4-STABLE on an IBM e-series 330 server. I have > recently started playing with DNS and have been largely successful. > However, nslint reports the following errors: > > nslint: missing "a": localhost. -> 127.0.0.1 > nslint: missing "a": localhost.org. -> 0.0.0.1 > > If I add the line: > > localhost. IN A 127.0.0.1 > > to my zone file, the first nslint error message goes away, but I then > see the following message in my /var/log/messages file upon named > startup: > > Jan 30 18:58:55 gilmer named[15485]: master/gilmer.org:16: ignoring > out-of-zone data (localhost) In this case, I think named is right and nslint is doing something funny. > So which is correct? Should I insert the A record in the zone file > and ignore the nslint message, or should I leave it out and ignore the > named message? Is there something else improperly configured on my > system? I don't know why nslint expects to be able to resolve "localhost." from a zone file that contains records for "gilmer.org.". This is a bit silly, if you ask me. > What about the second nslint message above? Why am I getting a > complaint about 0.0.0.1? This is probably because of some problem with your `named.conf' file. > My /etc/namedb/master/gilmer.org file looks like this: > $TTL3600 > > gilmer.org. IN SOA ns1.gilmer.org. admin.gilmer.org. ( > 20060126; Serial > 3600; Refresh > 900 ; Retry > 360 ; Expire > 3600 ) ; Minimum > > ;DNS Servers > @ IN NS @ Not a good idea. To resolve a name in the 'gilmer.org.' domain, a remote name server has to contact the nameserver at 'gilmer.org.', but to resolve 'gilmer.org.' is first has to resolve 'gilmer.org.', which forms a nice and tight but annoying loop. I think it would be a better idea to just use the *real* IP address of the NS here. > ; Machine Names > localhost. IN A127.0.0.1 The "localhost." entry is not good here; it should go. > ns1 IN A69.46.128.60 > @ IN A69.46.128.60 > > ;Aliases > mailIN CNAME@ > www IN CNAME@ > > ; MX Record > @ IN MX 10@ The rest looks ok to me. > ; From: @(#)localhost.rev 5.1 (Berkeley) 6/30/90 > ; $FreeBSD: src/etc/namedb/PROTO.localhost.rev,v 1.6 2000/01/10 15:31:40 > peter Exp $ > ; > ; This file is automatically edited by the `make-localhost' script in > ; the /etc/namedb directory. > ; > > $TTL3600 > > @ IN SOA ns1.gilmer.org. admin.gilmer.org. ( > 20060126; Serial > 3600; Refresh > 900 ; Retry > 360 ; Expire > 3600 ) ; Minimum > > IN NS ns1.gilmer.org. > > 1 IN PTR localhost. Hmmm, why is a final dot required in this? This is probably because nslint reports that it cannot find information for "localhost.", as opposed to, say, "localhost.gilmer.org." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
DNS nslint error messages
I am running freebsd 5.4-STABLE on an IBM e-series 330 server. I have recently started playing with DNS and have been largely successful. However, nslint reports the following errors: nslint: missing "a": localhost. -> 127.0.0.1 nslint: missing "a": localhost.org. -> 0.0.0.1 If I add the line: localhost. IN A 127.0.0.1 to my zone file, the first nslint error message goes away, but I then see the following message in my /var/log/messages file upon named startup: Jan 30 18:58:55 gilmer named[15485]: master/gilmer.org:16: ignoring out-of-zone data (localhost) So which is correct? Should I insert the A record in the zone file and ignore the nslint message, or should I leave it out and ignore the named message? Is there something else improperly configured on my system? What about the second nslint message above? Why am I getting a complaint about 0.0.0.1? My /etc/namedb/master/gilmer.org file looks like this: $TTL3600 gilmer.org. IN SOA ns1.gilmer.org. admin.gilmer.org. ( 20060126; Serial 3600; Refresh 900 ; Retry 360 ; Expire 3600 ) ; Minimum ;DNS Servers @ IN NS @ ; Machine Names localhost. IN A127.0.0.1 ns1 IN A69.46.128.60 @ IN A69.46.128.60 ;Aliases mailIN CNAME@ www IN CNAME@ ; MX Record @ IN MX 10@ (Yes, I know this configuration is a little strange, but right now, I am using one server to do everything until I get the hang of DNS.) My /etc/namedb/master/localhost.rev file looks like this: ; From: @(#)localhost.rev 5.1 (Berkeley) 6/30/90 ; $FreeBSD: src/etc/namedb/PROTO.localhost.rev,v 1.6 2000/01/10 15:31:40 peter Exp $ ; ; This file is automatically edited by the `make-localhost' script in ; the /etc/namedb directory. ; $TTL3600 @ IN SOA ns1.gilmer.org. admin.gilmer.org. ( 20060126; Serial 3600; Refresh 900 ; Retry 360 ; Expire 3600 ) ; Minimum IN NS ns1.gilmer.org. 1 IN PTR localhost. Thanks for the help. Brad ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: Re: Disk error messages (ad0: HARD READ ERROR blk# xxxxxx)
On Tue, 3 Jan 2006 12:25 pm, Gayn Winters wrote: > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Russell J. Wood > > Sent: Monday, January 02, 2006 3:54 PM > > To: freebsd-questions@freebsd.org > > Subject: Re: Disk error messages (ad0: HARD READ ERROR blk# > > xx) > > > > On Mon, Jan 02, 2006 at 11:15:08PM +, [EMAIL PROTECTED] wrote: > > > Hi there, > > > > > > On my screen, there were messages like the followings > > > > comeing up. I have to > > > > > reboot mutiple times to get it boot up normally. Does this > > > > mean I have to > > > > > replace the disk which is a relatively new disk (1-2 > > > > years)? Any simple way to > > > > > fix it and to avoid the time consuming task? > > > > > > > > > ad0: 39205MB [79656/16/63] at ata0-master > > > WDMA2 ad0: HARD READ ERROR blk# 131199 > > > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > > > ad0: DMA problem fallback to PIO mode > > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > > > ad0: HARD READ ERROR blk# 3473535 status=59 error=40 > > > ad0: HARD READ ERROR blk# 9240703 status=59 error=40 > > > ad0: HARD READ ERROR blk# 17367167 status=59 error=40 > > > ad0: HARD READ ERROR blk# 17760383 status=59 error=40 > > > > I suspect that you have bad sectors on your hard disk drive > > (and many of > > them). A good tool to use is Segate's Seatools > > (http://www.seagate.com/support/seatools/index.html). Just > > burn the Seatools Desktop edition to CDROM and boot from it. > > > > - Russell > > After you've checked for loose cables, you might want to take > the drive out and check it in another system (using the > Seagate or other such tools). If indeed the problem is with > DMA, the drive might be ok but the MB is flakey. Perhaps the > PC or MB manufacturer has diagnosics with which you can zero > into the latter ugly possiblity. In any case, get yourself a > backup asap (at least of the user data so that you can recover > from a fresh installation.) Unless you are getting other > types of errors, it is probably still possible to copy the > drive with dd using bs=512b, and this would be your quickest > fix of a hard drive problem. Run fsck on your new disk after > the copy. > dd is generally not a good choice for copying disks (although it does sort of work). The new disk will appear unclean when copied from a live fs and may in fact have an odd instance of a file which has not yet been physically updated. And it just takes too long since you copy empty space as well as real data. Instead slice, partition the new disk and create newfs on the new partitions. And then pipe dump (using the snapshot option) through to restore for each fs on the disks. I have (successfully) used this approach extensively for cloning systems. Malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Disk error messages (ad0: HARD READ ERROR blk# xxxxxx)
> [mailto:[EMAIL PROTECTED] On Behalf Of > Russell J. Wood > Sent: Monday, January 02, 2006 3:54 PM > To: freebsd-questions@freebsd.org > Subject: Re: Disk error messages (ad0: HARD READ ERROR blk# xx) > > > On Mon, Jan 02, 2006 at 11:15:08PM +, [EMAIL PROTECTED] wrote: > > Hi there, > > > > On my screen, there were messages like the followings > comeing up. I have to > > reboot mutiple times to get it boot up normally. Does this > mean I have to > > replace the disk which is a relatively new disk (1-2 > years)? Any simple way to > > fix it and to avoid the time consuming task? > > > > > > ad0: 39205MB [79656/16/63] at ata0-master WDMA2 > > ad0: HARD READ ERROR blk# 131199 > > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > > ad0: DMA problem fallback to PIO mode > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > > ad0: HARD READ ERROR blk# 3473535 status=59 error=40 > > ad0: HARD READ ERROR blk# 9240703 status=59 error=40 > > ad0: HARD READ ERROR blk# 17367167 status=59 error=40 > > ad0: HARD READ ERROR blk# 17760383 status=59 error=40 > > I suspect that you have bad sectors on your hard disk drive > (and many of > them). A good tool to use is Segate's Seatools > (http://www.seagate.com/support/seatools/index.html). Just burn the > Seatools Desktop edition to CDROM and boot from it. > > - Russell After you've checked for loose cables, you might want to take the drive out and check it in another system (using the Seagate or other such tools). If indeed the problem is with DMA, the drive might be ok but the MB is flakey. Perhaps the PC or MB manufacturer has diagnosics with which you can zero into the latter ugly possiblity. In any case, get yourself a backup asap (at least of the user data so that you can recover from a fresh installation.) Unless you are getting other types of errors, it is probably still possible to copy the drive with dd using bs=512b, and this would be your quickest fix of a hard drive problem. Run fsck on your new disk after the copy. Good luck, -gayn Bristol Systems Inc. 714/532-6776 www.bristolsystems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disk error messages (ad0: HARD READ ERROR blk# xxxxxx)
On Mon, Jan 02, 2006 at 11:15:08PM +, [EMAIL PROTECTED] wrote: > Hi there, > > On my screen, there were messages like the followings comeing up. I have to > reboot mutiple times to get it boot up normally. Does this mean I have to > replace the disk which is a relatively new disk (1-2 years)? Any simple way > to > fix it and to avoid the time consuming task? > > > ad0: 39205MB [79656/16/63] at ata0-master WDMA2 > ad0: HARD READ ERROR blk# 131199 > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > ad0: DMA problem fallback to PIO mode > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > ad0: HARD READ ERROR blk# 3473535 status=59 error=40 > ad0: HARD READ ERROR blk# 9240703 status=59 error=40 > ad0: HARD READ ERROR blk# 17367167 status=59 error=40 > ad0: HARD READ ERROR blk# 17760383 status=59 error=40 I suspect that you have bad sectors on your hard disk drive (and many of them). A good tool to use is Segate's Seatools (http://www.seagate.com/support/seatools/index.html). Just burn the Seatools Desktop edition to CDROM and boot from it. - Russell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disk error messages (ad0: HARD READ ERROR blk# xxxxxx)
On Monday 02 January 2006 02:15 pm, [EMAIL PROTECTED] wrote: > Hi there, > > On my screen, there were messages like the followings comeing up. I have to > reboot mutiple times to get it boot up normally. Does this mean I have to > replace the disk which is a relatively new disk (1-2 years)? Any simple way > to fix it and to avoid the time consuming task? > > > ad0: 39205MB [79656/16/63] at ata0-master WDMA2 > ad0: HARD READ ERROR blk# 131199 > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > ad0: DMA problem fallback to PIO mode > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > ad0: HARD READ ERROR blk# 3473535 status=59 error=40 > ad0: HARD READ ERROR blk# 9240703 status=59 error=40 > ad0: HARD READ ERROR blk# 17367167 status=59 error=40 > ad0: HARD READ ERROR blk# 17760383 status=59 error=40 Check that your cables are tight. You might even try swapping your drive cable. Other than that it looks like your drive is failing. You do have backups don't you? Beech -- --- Beech Rintoul - System Administrator - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://akparadise.byethost33.com --- pgpwsowY81Mak.pgp Description: PGP signature
Disk error messages (ad0: HARD READ ERROR blk# xxxxxx)
Hi there, On my screen, there were messages like the followings comeing up. I have to reboot mutiple times to get it boot up normally. Does this mean I have to replace the disk which is a relatively new disk (1-2 years)? Any simple way to fix it and to avoid the time consuming task? ad0: 39205MB [79656/16/63] at ata0-master WDMA2 ad0: HARD READ ERROR blk# 131199 ad0: HARD READ ERROR blk# 131199 status=59 error=40 ad0: DMA problem fallback to PIO mode ad0: HARD READ ERROR blk# 11272319 status=59 error=40 ad0: HARD READ ERROR blk# 11272319 status=59 error=40 ad0: HARD READ ERROR blk# 11272319 status=59 error=40 ad0: HARD READ ERROR blk# 131199 status=59 error=40 ad0: HARD READ ERROR blk# 3473535 status=59 error=40 ad0: HARD READ ERROR blk# 9240703 status=59 error=40 ad0: HARD READ ERROR blk# 17367167 status=59 error=40 ad0: HARD READ ERROR blk# 17760383 status=59 error=40 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
KDE error messages
KDE loads and runs okay, although the Kontact mail program has become inop. When I close KDE I get this message in the console window repeated about four times: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 6 Minor opcode: 0 Resource id: 0x1eb I have the feeling that these error codes might be related to the inop Kontact mail program, because every time that I try to run that program I get an error message telling me that it is already running in another display window. Also it completely eats up the CPU, and I have to do a kill -9 to shut it down. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI error messages in dmesg on 6.0-BETA5
Hello, I am getting strange errors in dmesg on one of our servers. Are these errors something critical, or there is no need to pay attention to them? Errors are those with "looking up [] in namespace" as shown below. thank you, Martin FreeBSD 6.0-BETA5 #3: Thu Sep 22 09:31:10 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SERVER2 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3010.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x441d> Hyperthreading: 2 logical CPUs real memory = 1073414144 (1023 MB) avail memory = 1041219584 (992 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0438: *** Error: Looking up [CHAF] in namespace, AE_NOT_FOUND SearchNode 0xc232e780 StartNode 0xc232e780 ReturnNode 0 ACPI-0438: *** Error: Looking up [OC06] in namespace, AE_NOT_FOUND SearchNode 0xc23335c0 StartNode 0xc23335c0 ReturnNode 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR -- martin hudec * 421 907 303 393 * [EMAIL PROTECTED] * http://www.aeternal.net "Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws." Douglas Adams, "The Hitchhiker's Guide to the Galaxy" pgpZEJLHu41NU.pgp Description: PGP signature
Re: annoying dhclient error messages
Christopher Illies <[EMAIL PROTECTED]> writes: > I recently installed FreeBSD 5.3 on my desktop at work. DHCP was > configured with sysinstall (/etc/rc.conf: ifconfig_fxp0="DHCP"), and > /etc/dhclient.conf is empty. In fact I do have a good network > connection. The problem is that I get the following annoying error > messages about every two to five minutes: > > Nov 13 13:43:59 Klabautermann dhclient: slp-directory-agent: 4 extra > bytes at end of array > Nov 13 13:43:59 Klabautermann last message repeated 2 times > Nov 13 13:43:59 Klabautermann dhclient: parse_option_param: Bad format > a > Nov 13 13:46:26 Klabautermann dhclient: slp-directory-agent: 4 extra > bytes at end of array > Nov 13 13:46:26 Klabautermann last message repeated 2 times > Nov 13 13:46:26 Klabautermann dhclient: parse_option_param: Bad format > a > > These messages are more a nuisance than anything else, still I would > like to get rid of them. I updated the system last week (tag=RELENG_5), > but that did not help. Interestingly, I do not see these messages when > running Debian GNU/Linux on the very same computer. Google did not > reveal anything helpful. This really does look like the server is sending out some bad parameters. Probably you were using a different DHCP client on Linux. I'd suggest just changing the syslog configuration to filter those into a new log file, and block them from the console. Remember to check the file once in a while. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
annoying dhclient error messages
I recently installed FreeBSD 5.3 on my desktop at work. DHCP was configured with sysinstall (/etc/rc.conf: ifconfig_fxp0="DHCP"), and /etc/dhclient.conf is empty. In fact I do have a good network connection. The problem is that I get the following annoying error messages about every two to five minutes: Nov 13 13:43:59 Klabautermann dhclient: slp-directory-agent: 4 extra bytes at end of array Nov 13 13:43:59 Klabautermann last message repeated 2 times Nov 13 13:43:59 Klabautermann dhclient: parse_option_param: Bad format a Nov 13 13:46:26 Klabautermann dhclient: slp-directory-agent: 4 extra bytes at end of array Nov 13 13:46:26 Klabautermann last message repeated 2 times Nov 13 13:46:26 Klabautermann dhclient: parse_option_param: Bad format a These messages are more a nuisance than anything else, still I would like to get rid of them. I updated the system last week (tag=RELENG_5), but that did not help. Interestingly, I do not see these messages when running Debian GNU/Linux on the very same computer. Google did not reveal anything helpful. Thanks in advance for any help or pointers, Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How-to capture error messages from ... recent
Hello Toomas, Thanks a lot for your reply! > Before starting the installation, issue this command: > script /var/tmp/portinstall.log > After finishing the installation ... > exit That worked perfectly. There's a number of "Error code 1"s in there. But at least I can read up on 'em in a more leisurely fashion.:c) > Unfortunately I am not familiar with instant-workstation port > ... it may be safer to leave [various port configure options] > as defaults. I *had* been pretty much doing that. The Postfix config screen, though, presents a screen full of alphabet soup options. It was late. I was tired. I should've known better. I came across instant-workstation late last year while using Greg Lehey's Complete FreeBSD book to install 5.0-Release on my wife's dual-boot (Windows ME). The port installs fifteen/sixteen sub-ports (acroread, gimp, kde, etc.), and the postfix one gets installed towards the end of the instant-workstation install. I suspect I now have to go into each sub-port and 'make clean,' since the inst.-work. didn't get that far. > * Cannibal's recipe book: How to Serve Your Fellow Man. Thanks again. (Love the tagline!) -- df (dave) armour my real box calm! -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How-to capture error messages from ... recent instant-workst
Hello! > Can someone tell me where to look for how to capture the console > screens that fly by in the port install process? Before starting the installation, issue this command: script /var/tmp/portinstall.log After finishing the installation (successfully or unsuccessfully), issue this command: exit Then you can read everything that was printed on the console during installation from the file /var/tmp/portinstall.log (which may be pretty large!). Unfortunately I am not familiar with instant-workstation port so I can't comment on that specific situation. My only idle thought is that if you are not sure what various port configure options do it may be safer to leave them as defaults. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Cannibal's recipe book: How to Serve Your Fellow Man. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How-to capture error messages from ... recent instant-workstation
Full SubjectLine: How-to capture error messages from ... recent instant-workstation port "make install && make clean" failure on 5.3Beta6...newish, mid-range box. What's next, Ollie? I'm hoping this is the right place to ask this... BAD case of newbie- itis. And there I was thinking: this is working out all right... [enough whingiing] Straightforward installation via downloaded/burned mini-iso CD... - ftp ports: all binaries, source, X - left X for later install Package selection: cvsup_without_gui-16.h and, using /usr/share/examples/cvsup/ports-supfile finished successfully! Since this was an othewise new box, a recent beta release (when I started!?), & perhaps wrongly assuming I didn't need to run portupgrade, I went ahead and tried to install the instant-workstation _1.0.8 port. The machine began clunking away at 00:30 Fri, Oct 1, and was still churning away Sun, Oct. 3 when I left for work. I came back from work about 5:30 pm to find the Postfix config screen with all those [ ] SASL [ ] SASLKRB5 [ ] TLS [ ] DB42 [ ] LDAP [ ] PgSQL ...options As I had with most of the previous port-install config screens, I [X]'d as many of the options as I had ever seen/heard in my Time of Lurking/reading, pressed RETURN, and looked for- ward to the imminent conclusion of the port's installation. I got an install screen that said I had to choose between the DB options offered (4.0/4.2 etc.), but which then dumped me out of install process. Can someone tell me where to look for how to capture the console screens that fly by in the port install process? My scroll-locked look- back-at shows: <...paraphrasing> "Building for Postfix-2.1.4.1... <...couple of screens of gobbledygook> <...couple of screens of "/usr/lib/libkrb5.so. ... "...undefined reference to... "...'length_PA_ENC_TS_ENC' " "...'decode_EncTicketPart'"> <...several "Stop in /usr/ports/mail/postfix... <*** Error code 1">'s The screens also show that several of the port's components list- ed in Mr Lehey's Complete FreeBSD - acroread; bash; fetch- mail; grip; gimp; gv; ispell; mutt; mozilla; startkde -- installed successfully. (Logging in as a non-root user, for example, displays a bash prompt.) Maybe I can cd to /l/postfix and resume installing the postfix port separately? I don't need one of the three sub-ports that remain un-installed (mkisofs), since this machine doesn't have a burner. I *do* want to install gv and xtset, I think. But I'm still unclear on what role(s) postfix plays in the instant-workstation port, and/or just how much cleaning/tidying I will have to do manually. Any help greatly appreciated, although I should mention that, for my next trick, I'm looking to configure X... :c) Kind regards, Dave Other specs: AMD Duron 1.6 Ghz, 40 Gb HD, 512 K, SiS 740/741 on-board video.. output from "uname -a": FreeBSD S0106000d87ae2db6.gv.shawcable.net 5.3-BETA6 FreeBSD 5.3-BETA6 #0: Sat Sep 25 19:41:14 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 = df (dave) armour my real box calm! = # not... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lpr error messages
Adam Smith wrote: On Wed, Sep 29, 2004 at 07:21:16PM -0700, Gary Schenk said: I cannot print from either X or the command line. It was working fine until a few hours ago. Any suggestions on where to start on this would be much appreciated. LPR is a binary and so the output here is unexpected (as they look more like script errors). bash-2.05b$ lpr test.txt /usr/bin/lpr: line 12: */5: No such file or directory /usr/bin/lpr: line 15: 0: command not found /usr/bin/lpr: line 18: 1: command not found /usr/bin/lpr: line 19: 15: command not found /usr/bin/lpr: line 20: 30: command not found /usr/bin/lpr: line 25: 1,31: command not found /usr/bin/lpr: line 28: 1: command not found I'm thinking that /usr/bin/lpr must be corrupted. I'm not sure how to go about testing that theory, or what to do if that is the case. I've searched the list archives and googled to no avail. If you want to reinstall the lpr binary, you can either go through a make installworld process or install the binary on it's own by going into /usr/src/usr/sbin/lpr and doing a 'make install'. That will recompile and reinstall lpr. Yes, that fixed it. I did a stupid thing while root and hosed the lpr file. Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lpr error messages
Gary Schenk wrote: > I cannot print from either X or the command line. It was working > fine until a few hours ago. Any suggestions on where to start > on this would be much appreciated. > > Here is an example: > > bash-2.05b$ lpr test.txt > /usr/bin/lpr: line 12: */5: No such file or directory > /usr/bin/lpr: line 15: 0: command not found > /usr/bin/lpr: line 18: 1: command not found > /usr/bin/lpr: line 19: 15: command not found > /usr/bin/lpr: line 20: 30: command not found > /usr/bin/lpr: line 25: 1,31: command not found > /usr/bin/lpr: line 28: 1: command not found > > lptest > /dev/lpt0 produces output to the printer. > > bash-2.05b$ grep lpd_enable /etc/rc.conf > lpd_enable="YES" > > I'm thinking that /usr/bin/lpr must be corrupted. I'm not > sure how to go about testing that theory, or what to do > if that is the case. I've searched the list archives and > googled to no avail. The way I read this, lpr is expecting to get a PostScript file, and you are feeding it a TEST file. I'm even willing to bet that on line 12 of your text file, there is a */5, which lpr is valiantly attempting to interpret as a PostScript command. Similarly, the other lines mentioned in the error output above indicate that all the other lines in your text file start with integers such as 0, 1, 15, etc. So all you really need to do now is find some way to convert your TEXT file to a PostScript file. Or convince lpr that it should accept text files, and somehow convert them internally to PostScript. -- Like Music? http://l-i-e.com/artists.htm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lpr error messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 29, 2004, at 9:21 PM, Gary Schenk wrote: I cannot print from either X or the command line. It was working fine until a few hours ago. Any suggestions on where to start on this would be much appreciated. Here is an example: bash-2.05b$ lpr test.txt /usr/bin/lpr: line 12: */5: No such file or directory /usr/bin/lpr: line 15: 0: command not found /usr/bin/lpr: line 18: 1: command not found /usr/bin/lpr: line 19: 15: command not found /usr/bin/lpr: line 20: 30: command not found /usr/bin/lpr: line 25: 1,31: command not found /usr/bin/lpr: line 28: 1: command not found lptest > /dev/lpt0 produces output to the printer. bash-2.05b$ grep lpd_enable /etc/rc.conf lpd_enable="YES" I'm thinking that /usr/bin/lpr must be corrupted. I'm not sure how to go about testing that theory, or what to do if that is the case. I've searched the list archives and googled to no avail. Thanks in advance! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Looks to me like someone replaced your lpr binary with a script. Possibly one written for Linux, where the executables aren't where they're supposed to be. Try to read the lpr file from a text editor. Make sure your user's path is still correct, too. HTH - - Eric F Crist Secure Computing Networks -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iEYEARECAAYFAkFbcWIACgkQRAAY9knOW+rLOwCfWiML/yb0TSlCugK3TD+vG7tm 4EYAn3xkighfWWuMhoP6r97+B0J4Pa77 =Av3f -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lpr error messages
On Wed, Sep 29, 2004 at 07:21:16PM -0700, Gary Schenk said: > I cannot print from either X or the command line. It was working > fine until a few hours ago. Any suggestions on where to start > on this would be much appreciated. LPR is a binary and so the output here is unexpected (as they look more like script errors). > bash-2.05b$ lpr test.txt > /usr/bin/lpr: line 12: */5: No such file or directory > /usr/bin/lpr: line 15: 0: command not found > /usr/bin/lpr: line 18: 1: command not found > /usr/bin/lpr: line 19: 15: command not found > /usr/bin/lpr: line 20: 30: command not found > /usr/bin/lpr: line 25: 1,31: command not found > /usr/bin/lpr: line 28: 1: command not found > I'm thinking that /usr/bin/lpr must be corrupted. I'm not > sure how to go about testing that theory, or what to do > if that is the case. I've searched the list archives and > googled to no avail. If you want to reinstall the lpr binary, you can either go through a make installworld process or install the binary on it's own by going into /usr/src/usr/sbin/lpr and doing a 'make install'. That will recompile and reinstall lpr. -- Adam Smith Internode : http://www.internode.on.net Phone : (08) 8228 2999 Dog for sale: Eats lots and is fond of children. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lpr error messages
I cannot print from either X or the command line. It was working fine until a few hours ago. Any suggestions on where to start on this would be much appreciated. Here is an example: bash-2.05b$ lpr test.txt /usr/bin/lpr: line 12: */5: No such file or directory /usr/bin/lpr: line 15: 0: command not found /usr/bin/lpr: line 18: 1: command not found /usr/bin/lpr: line 19: 15: command not found /usr/bin/lpr: line 20: 30: command not found /usr/bin/lpr: line 25: 1,31: command not found /usr/bin/lpr: line 28: 1: command not found lptest > /dev/lpt0 produces output to the printer. bash-2.05b$ grep lpd_enable /etc/rc.conf lpd_enable="YES" I'm thinking that /usr/bin/lpr must be corrupted. I'm not sure how to go about testing that theory, or what to do if that is the case. I've searched the list archives and googled to no avail. Thanks in advance! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard drive problem... S-ATA/ATA and DMA error messages
On Mon, 5 Jul 2004 20:03:37 -0700 (PDT) peter lageotakes <[EMAIL PROTECTED]> hit the keyboard and punched: > --- Warren Block <[EMAIL PROTECTED]> wrote: > > > > -CURRENT (5.x) does have support for SATA, and may > > (probably does) > > work with the 8237. (I haven't tried it on this > > motherboard.) > > > > -Warren Block * Rapid City, South Dakota USA> > > > Should this be issued as a PR? According to the > hardware notes for 4.10: > http://www.freebsd.org/releases/4.10R/hardware-i386.html > "VIA 8233, 8235 ATA133, 8237 SATA150". > > Pete PR? What is that...? Are you suggesting that this is a bug in the kernel/driver rather than unsupported hardware? Well, dmesg atleast identifies the correct chipset/driver and it works. Bad, but it works. UDMA/33 isn't so nice and if I start a high-load disk operation the system is likely to freeze completely. If this is a bug, to whom/where should I report it? -- Rickard .--..--. .. | || | .-. | Rickard Borgmäster | | || |/ / | [EMAIL PROTECTED] | .-^ | .--. | < | http://doktorn.sub.nu/ | ( o | ( () ) | |\ \ `' `-' `--' `--' `--' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard drive problem... S-ATA/ATA and DMA error messages
--- Warren Block <[EMAIL PROTECTED]> wrote: > On Tue, 6 Jul 2004, Rickard [ISO-8859-1] Borgmäster > wrote: > > > atapci1: port > 0xfc00-0xfc0f at device 15.1 on > > pci0 > > ata0: at 0x1f0 irq 14 on atapci1 > > ata1: at 0x170 irq 15 on atapci1 > > [...] > > ad0: 156334MB [317632/16/63] at > ata0-master UDMA133 > > ad4: DMA limited to UDMA33, non-ATA66 cable or > device > > ad4: 152627MB [310101/16/63] at > ata2-master UDMA33 > > > > How come FreeBSD kernel thinks my S-ATA disk is > only capable of UDMA/33? > > FreeBSD 4.x doesn't have specific support for the > VIA 8237, and so > doesn't properly realize that it should be able to > do the faster DMA > modes. > > > Next thing is that I today tried to move ~70GB of > data from ad0 > > (ATA/UDMA133) to ad4 (S-ATA) disk. During the cp > process I got these > > messages: > > Jul 5 15:13:18 studsboll /kernel: > ad0s1e: hard error reading > > fsbn 390440063 of 19522-195220255 (ad0s1 bn > 390440063; cn 24303 tn 196 > > sn 20) trying PIO mode > > Jul 5 15:13:18 studsboll /kernel: > ad0: DMA problem fallback > > to PIO mode > > My MSI motherboard with the same VIA 8237 does the > same thing. > > -CURRENT (5.x) does have support for SATA, and may > (probably does) > work with the 8237. (I haven't tried it on this > motherboard.) > > -Warren Block * Rapid City, South Dakota USA> ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > Should this be issued as a PR? According to the hardware notes for 4.10: http://www.freebsd.org/releases/4.10R/hardware-i386.html "VIA 8233, 8235 ATA133, 8237 SATA150". Pete = ESCape with VI. Cheese A La mode. __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard drive problem... S-ATA/ATA and DMA error messages
On Mon, 5 Jul 2004 18:35:52 -0600 (MDT) Warren Block <[EMAIL PROTECTED]> hit the keyboard and punched: > FreeBSD 4.x doesn't have specific support for the VIA 8237, and so > doesn't properly realize that it should be able to do the faster DMA > modes. > > My MSI motherboard with the same VIA 8237 does the same thing. > > -CURRENT (5.x) does have support for SATA, and may (probably does) > work with the 8237. (I haven't tried it on this motherboard.) Doh! Should have checked that before... now I'm stuck with a system that more or less freezes during high-load disk operations :- Any workarounds? -- Rickard .--..--. .. | || | .-. | Rickard Borgmäster | | || |/ / | [EMAIL PROTECTED] | .-^ | .--. | < | http://doktorn.sub.nu/ | ( o | ( () ) | |\ \ `' `-' `--' `--' `--' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard drive problem... S-ATA/ATA and DMA error messages
On Tue, 6 Jul 2004, Rickard [ISO-8859-1] Borgmäster wrote: atapci1: port 0xfc00-0xfc0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 [...] ad0: 156334MB [317632/16/63] at ata0-master UDMA133 ad4: DMA limited to UDMA33, non-ATA66 cable or device ad4: 152627MB [310101/16/63] at ata2-master UDMA33 How come FreeBSD kernel thinks my S-ATA disk is only capable of UDMA/33? FreeBSD 4.x doesn't have specific support for the VIA 8237, and so doesn't properly realize that it should be able to do the faster DMA modes. Next thing is that I today tried to move ~70GB of data from ad0 (ATA/UDMA133) to ad4 (S-ATA) disk. During the cp process I got these messages: Jul 5 15:13:18 studsboll /kernel: ad0s1e: hard error reading fsbn 390440063 of 19522-195220255 (ad0s1 bn 390440063; cn 24303 tn 196 sn 20) trying PIO mode Jul 5 15:13:18 studsboll /kernel: ad0: DMA problem fallback to PIO mode My MSI motherboard with the same VIA 8237 does the same thing. -CURRENT (5.x) does have support for SATA, and may (probably does) work with the 8237. (I haven't tried it on this motherboard.) -Warren Block * Rapid City, South Dakota USA___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hard drive problem... S-ATA/ATA and DMA error messages
Hi, Having recently upgraded my motherboard to a brand new Asus P4V8X-X with S-ATA and added an S-ATA disk I experience some problems I find kind of weird. System is installed on 160MB S-ATA disk ad4 and my previous 160 ATA/UDMA133 is on ad0 mounted as /big. Booting up, dmesg gives me this confusing message: atapci1: port 0xfc00-0xfc0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 [...] ad0: 156334MB [317632/16/63] at ata0-master UDMA133 ad4: DMA limited to UDMA33, non-ATA66 cable or device ad4: 152627MB [310101/16/63] at ata2-master UDMA33 How come FreeBSD kernel thinks my S-ATA disk is only capable of UDMA/33? The S-ATA disk is connected to the motherboard by it's own S-ATA cable, thus not the problem of two disks with different speeds on same cable. Beeing new to S-ATA I may have misunderstood things, but the way I see it, the S-ATA bus and regular ATA bus is isolated and should not bother eachofter, right? Next thing is that I today tried to move ~70GB of data from ad0 (ATA/UDMA133) to ad4 (S-ATA) disk. During the cp process I got these messages: Jul 5 15:13:18 studsboll /kernel: ad0s1e: hard error reading fsbn 390440063 of 19522-195220255 (ad0s1 bn 390440063; cn 24303 tn 196 sn 20) trying PIO mode Jul 5 15:13:18 studsboll /kernel: ad0: DMA problem fallback to PIO mode Jul 5 15:13:18 studsboll last message repeated 6 times Jul 5 15:13:21 studsboll /kernel: ad0s1e: hard error reading fsbn 390440175 of 19522-195220255 (ad0s1 bn 390440175; cn 24303 tn 198 sn 6) status=59 error=40 Jul 5 15:13:24 studsboll /kernel: ad0s1e: hard error reading fsbn 390440271 of 195220096-195220255 (ad0s1 bn 390440271; cn 24303 tn 199 sn 39) status=59 error=40 Jul 5 15:13:27 studsboll /kernel: ad0s1e: hard error reading fsbn 390440271 of 195220096-195220223 (ad0s1 bn 390440271; cn 24303 tn 199 sn 39) status=59 error=40 Jul 5 16:34:39 studsboll /kernel: ad0s1e: hard error reading fsbn 228774239 of 114387008-114387263 (ad0s1 bn 228774239; cn 14240 tn 137 sn 8) status=59 error=40 Jul 5 16:34:42 studsboll /kernel: ad0s1e: hard error reading fsbn 228774271 of 114387040-114387263 (ad0s1 bn 228774271; cn 14240 tn 137 sn 40) status=59 error=40 Jul 5 16:34:44 studsboll /kernel: ad0s1e: hard error reading fsbn 228774399 of 114387168-114387263 (ad0s1 bn 228774399; cn 14240 tn 139 sn 42) status=59 error=40 Jul 5 16:34:47 studsboll /kernel: ad0s1e: hard error reading fsbn 228774399 of 114387168-114387263 (ad0s1 bn 228774399; cn 14240 tn 139 sn 42) status=59 error=40 There are 2 different errors here. First we have a "hard reading error" and then "DMA problem". The DMA problem, at ad0 (ATA/UDMA133 disk, weird enough) tells me that I might be wrong about that S-ATA and regular ATA disk does not bother eachother. Someone please explain this... the disk has been working 100% fine on my old motherboard afaik. The "hard reading error" is supposed to be about damaged sectors on the disk. Is it always like that, or could the errors come from some kind of bus error, ie same source of problems as the UDMA errors? The disk is rather new and shouldn't have broken sectors. I suppose. I'd really like som kind of tip on where to start. At the moment I can't think of anything that's wrong. Complete dmesg follows: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-STABLE #1: Wed Jun 2 21:26:45 CEST 2004 root@:/usr/obj/usr/src/sys/STUDSBOLL Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Celeron(R) CPU 2.80GHz (2799.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff real memory = 536018944 (523456K bytes) avail memory = 516935680 (504820K bytes) Preloaded elf kernel "kernel" at 0xc0481000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 10 entries at 0xc00f5a40 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pci1: at 0.1 ahc0: port 0xed00-0xedff mem 0xdfb0-0xdfb00fff irq 3 at device 11.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xdfd0-0xdfd0007f irq 10 at device 13.0 on pci0 xl0: Ethernet address: 00:01:02:fa:84:31 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xe800-0xe8ff,0xef90-0xef9f,0xefa8-0xefab,0xefa0-0xefa7,0xefac-0xefaf,0xe fe0-0xefe7 irq 10 at device 15.0 on pci0 ata2: at 0xefe0 on atapci0 ata3: at 0xefa0 on atapci0 atapci1: port 0xfc00-0xfc0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: port 0xeec0-0xeedf
Boot CD-ROM error messages
Anyone know why I get the messages below when I boot with an audio CD in a drive? It looks a though FreeBSD assumes that it is a data disk and tries to read it as such. Running FreeBSD redshift 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #19: Wed Mar 10 01:50:42 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REDSHIFT i386 TIA Regards, Mark - begin dmesg fragment - cd2 at ahc0 bus 0 target 5 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 5.000MB/s transfers (5.000MHz, offset 16) cd2: cd present [229700 x 2048 byte records] (cd2:ahc0:0:5:0): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 (cd2:ahc0:0:5:0): CAM Status: SCSI Status Error (cd2:ahc0:0:5:0): SCSI Status: Check Condition (cd2:ahc0:0:5:0): ILLEGAL REQUEST asc:64,0 (cd2:ahc0:0:5:0): Illegal mode for this track (cd2:ahc0:0:5:0): Unretryable error (cd2:ahc0:0:5:0): cddone: got error 0x6 back (cd2:ahc0:0:5:0): READ(10). CDB: 28 0 0 0 0 1 0 0 1 0 (cd2:ahc0:0:5:0): CAM Status: SCSI Status Error (cd2:ahc0:0:5:0): SCSI Status: Check Condition (cd2:ahc0:0:5:0): ILLEGAL REQUEST asc:64,0 (cd2:ahc0:0:5:0): Illegal mode for this track (cd2:ahc0:0:5:0): Unretryable error (cd2:ahc0:0:5:0): cddone: got error 0x6 back (cd2:ahc0:0:5:0): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 (cd2:ahc0:0:5:0): CAM Status: SCSI Status Error (cd2:ahc0:0:5:0): SCSI Status: Check Condition (cd2:ahc0:0:5:0): ILLEGAL REQUEST asc:64,0 (cd2:ahc0:0:5:0): Illegal mode for this track (cd2:ahc0:0:5:0): Unretryable error (cd2:ahc0:0:5:0): cddone: got error 0x6 back - end dmesg fragment - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New Error Messages :-(
"Simon" <[EMAIL PROTECTED]> writes: > Ops... I confused maxproc with cputime limit, sorry for the post. > The error message being new, made me confuse it with what > I thought replaced cputime limit error messages. I have a patch, anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New Error Messages :-(
Ops... I confused maxproc with cputime limit, sorry for the post. The error message being new, made me confuse it with what I thought replaced cputime limit error messages. -Simon On 24 Dec 2003 17:18:42 -0500, Lowell Gilbert wrote: >Lowell Gilbert <[EMAIL PROTECTED]> writes: > >> "Simon" <[EMAIL PROTECTED]> writes: >> >> > Before version 4.9, FBSD used to print/log: >> > pid 20055 (cmd), uid 1057, was killed: exceeded maximum CPU limit >> > Now, all it prints is: maxproc limit exceeded by uid 1203, please see tuning(7)... >> > making it impossible to identify which process was killed, am I missing something >> > in 4.9 which would make it print the PID killed as well? >> > >> > Any pointers would be appreciated. >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_fork.c?f=u&only_with_tag=RELENG_4&logsort=date >> >> The relevant change was Revision 1.72.2.15, which put a maxproc check >> in a place that hadn't had one at all before. This was a fix to a bug >> (which may have been theoretically present for a long time, but hadn't >> affected any hardware built until recently), so "fixing" this would be >> more complicated than just changing an error string... > >No, I think I'm wrong. The task context is, in fact, available at >that point. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
