freebsd-stable Digest, Vol 129, Issue 4
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. Re: lpt0 always busy (Daniel O'Connor)
2. Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
(Oleg Korecky)
3. Re: lpt0 always busy (Torfinn Ingolfsen)
4. Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
(Torfinn Ingolfsen)
5. Re: lpt0 always busy (stanley jobson)
6. Re: lpt0 always busy (stanley jobson)
7. increasing buffer cache (Petri Helenius)
8. USB Audio (Steve Webster)
9. IPv6 and DUMMYNET traffic shaping (Folkert Saathoff)
10. Re: IPv6 and DUMMYNET traffic shaping (Brooks Davis)
11. HEADSUP: bridge(4) removed from HEAD (Max Laier)
12. Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
(L?szl? K?roly)
13. eSafe alert (eS...@mtt.ru)
14. UFS2 vs UFS1 determination (Kenneth W Cochran)
15. Re: UFS2 vs UFS1 determination (David Kirchner)
16. Re: UFS2 vs UFS1 determination (Erik Trulsson)
17. Re: Re[2]: device polling and high load averages (Kevin Oberman)
18. problem with aac0 on FreeBSD 5.4 Stable#5 (martin)
19. Help With Word press Settup and confguration (Maher Mohamed)
20. Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
(Joel Wood)
21. Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
(Daniel O'Connor)
22. Re: IPv6 and DUMMYNET traffic shaping (Folkert Saathoff)
23. Re: HEADSUP: bridge(4) removed from HEAD (Maxim Sobolev)
24. Re: problem with aac0 on FreeBSD 5.4 Stable#5 (Scott Long)
25. (no subject) (jaredball)
26. Re: HEADSUP: bridge(4) removed from HEAD (Simon L. Nielsen)
27. Cue0 Panic (still) kern/75710 (Gray Lilley)
28. Strange interaction between rcNG and procfs (Matthew Seaman)
29. Re: HEADSUP: bridge(4) removed from HEAD (Peter Jeremy)
----------------------------------------------------------------------
Message: 1
Date: Tue, 27 Sep 2005 22:00:07 +0930
From: "Daniel O'Connor" <doco...@gsoft.com.au>
Subject: Re: lpt0 always busy
To: stanley jobson <stanley...@gmx.ch>
Cc: freebsd...@freebsd.org
Message-ID: <200509272200....@gsoft.com.au>
Content-Type: text/plain; charset="iso-8859-1"
On Tuesday 27 September 2005 17:56, stanley jobson wrote:
> > It seriously looks like the printer, cable or port are broken, or the
> > printer is very very special..
> >
> > What sort of printer is it?
>
> its a canon lbp 460 - ugly gdi printer :)
Hmm, well lots of printers these days are raster only..
I'd recommend buying an Epson since they are usually more functional than
Canon in !Win32.
> > You could try printing to /dev/lpt0.ctl since that will ignore BUSY
> > for the open.
>
> one can print using lpt0.ctl? - thx 4 the hint - i'll check this ...
Well, I'm pretty sure you can.
AFAIK the only difference is that lpt0.ctl ignores BUSY on open so lptcontrol
can use it.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050927/4c3f420d/attachment-0001.bin
------------------------------
Message: 2
Date: Tue, 27 Sep 2005 16:00:36 +0300
From: Oleg Korecky <kor...@dnepr.net>
Subject: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
To: freebsd...@freebsd.org
Message-ID: <43394274...@dnepr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Did somebody use LIRC on the FreeBSD ? Or what you can recommend instead
LIRC ?
Thanks !
------------------------------
Message: 3
Date: Tue, 27 Sep 2005 17:27:53 +0200
From: Torfinn Ingolfsen <torfinn....@broadpark.no>
Subject: Re: lpt0 always busy
To: freebsd...@freebsd.org
Message-ID: <20050927172753.09042...@broadpark.no>
Content-Type: text/plain; charset=US-ASCII
On Tue, 27 Sep 2005 10:26:36 +0200
stanley jobson <stanley...@gmx.ch> wrote:
> >
> > It seriously looks like the printer, cable or port are broken, or
> > the printer is very very special..
> >
> > What sort of printer is it?
>
> its a canon lbp 460 - ugly gdi printer :)
Aha, that explains wy it will not work. see this:
http://linuxprinting.org/show_printer.cgi?recnum=Canon-LBP-460
the printer can print ascii text at all, it is a raster-only win* gdi
printer. It is the driver who does all the work.
Always, always check LinuxPrinting.org before starting with an unknown
printer.
--
Regards,
Torfinn Ingolfsen,
Norway
------------------------------
Message: 4
Date: Tue, 27 Sep 2005 17:34:32 +0200
From: Torfinn Ingolfsen <torfinn....@broadpark.no>
Subject: Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
To: freebsd...@freebsd.org
Message-ID: <20050927173432.688ca...@broadpark.no>
Content-Type: text/plain; charset=US-ASCII
On Tue, 27 Sep 2005 16:00:36 +0300
Oleg Korecky <kor...@dnepr.net> wrote:
> Did somebody use LIRC on the FreeBSD ?
Yes, I have done that some time ago.
Note: some drivers are built-in in lirc (they are not part of the
parallel or serial drivers). the parallel and serial drivers was not
ported (last I looked at least), but that didn't stop me from getting a
remote working. I can't remember which remote just now.
Try Google (groups) for FreeBSD + lirc.
> Or what you can recommend instead LIRC ?
That I don't know about.
HTH
--
Regards,
Torfinn Ingolfsen,
Norway
------------------------------
Message: 5
Date: Tue, 27 Sep 2005 17:57:04 +0200
From: stanley jobson <stanley...@gmx.ch>
Subject: Re: lpt0 always busy
To: Torfinn Ingolfsen <torfinn....@broadpark.no>
Cc: freebsd...@freebsd.org
Message-ID: <20050927175704.24f6...@gmx.ch>
Content-Type: text/plain; charset=US-ASCII
> >
> > its a canon lbp 460 - ugly gdi printer :)
>
> Aha, that explains wy it will not work. see this:
> http://linuxprinting.org/show_printer.cgi?recnum=Canon-LBP-460
>
> the printer can print ascii text at all, it is a raster-only win* gdi
> printer. It is the driver who does all the work.
i know that this printer will never work with fbsd or even linux so i
hoped i could setup a qemu with win98 and just passing lpt0 throu ...
but unfort. this does not work :(
what i need is a possibility to give qemu/vmware access to lpt0 without
any checking done by fbsd
thx,
regards,
stan
------------------------------
Message: 6
Date: Tue, 27 Sep 2005 17:59:43 +0200
From: stanley jobson <stanley...@gmx.ch>
Subject: Re: lpt0 always busy
To: "Daniel O'Connor" <doco...@gsoft.com.au>
Cc: freebsd...@freebsd.org
Message-ID: <20050927175943.3c1e...@gmx.ch>
Content-Type: text/plain; charset=US-ASCII
>
> > > You could try printing to /dev/lpt0.ctl since that will ignore
> > > BUSY for the open.
> >
> > one can print using lpt0.ctl? - thx 4 the hint - i'll check this ...
>
> Well, I'm pretty sure you can.
> AFAIK the only difference is that lpt0.ctl ignores BUSY on open so
> lptcontrol can use it.
>
unfort. qemu is not able to open lpt0.ctl too (no perm prob) but i will
do some more testing in this direction ...
thx
regards,
stan
------------------------------
Message: 7
Date: Tue, 27 Sep 2005 19:40:09 +0300
From: Petri Helenius <pe...@he.iki.fi>
Subject: increasing buffer cache
To: freebsd...@freebsd.org
Message-ID: <433975E9...@he.iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I tried increasing buffer cache on machine with 4G ram and amd64 kernel
with the following in /boot/loader.conf;
kern.maxbcache=1250000000
kern.nbuf=65536
vm.kmem_size=1300000000
vm.kmem_size_max=1300000000
However the system panics on boot with a malloc error. Any other
parameters that need to be tuned?
Pete
------------------------------
Message: 8
Date: Tue, 27 Sep 2005 12:43:09 -0400 (EDT)
From: Steve Webster <sweb...@kinex.com>
Subject: USB Audio
To: freebsd...@freebsd.org
Message-ID: <2005092712...@sloe.dyndns.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Greetings,
I'm a newbie to FreeBSD, so please forgive me if I've posted to the wrong
list.
I'm trying to use an Audiotrak OptoPlay usb audio device, one that appears
as supported hardware in the handbook, in conjunction with mplayer. It
works great for tens of minutes and then it forces a reboot leading the
the following snippet in /var/log/messages:
> FreeBSD 5.4-RELEASE #3: Sat Sep 24 16:54:39 EDT 2005
> ugen0: Ego Systems Inc. AUDIOTRAK OptoPlay, rev 1.00/1.00, addr 2
> WARNING: / was not properly dismounted
> WARNING: /tmp was not properly dismounted
> WARNING: /usr was not properly dismounted
> WARNING: /var was not properly dismounted
> ugen0: at uhub0 port 1 (addr 2) disconnected
> ugen0: detached
> uaudio0: Ego Systems Inc. AUDIOTRAK OptoPlay, rev 1.00/1.00, addr 2
> uaudio0: audio rev 1.00
> pcm0: <USB Audio> on uaudio0
> usb0: isoc TD alloc failed
> usb0: isoc TD alloc failed
> panic: kmem_malloc(4096): kmem_map too small: 42991616 total allocated
> Uptime: 1h43m40s
> Cannot dump. No dump device defined.
> Automatic reboot in 15 seconds - press a key on the console to abort
I've done some research that has pointed at pcm and snd_uaudio things, but
I haven't found anything conclusive. The warnings above are probably
related to the machine coming down hard since this log is from the second
time the machine automatically rebooted. I appear to have a memory leak,
but I was wondering if others on this list had some pointers. I wanted to
try rebuilding a kernel from the stable branch, and I wanted to apply the
patch found at http://staff.mybsd.org.my/skywizard/FreeBSD/sound/, but
everything I've read has mentioned to rebuild world if I change from
release to stable. This machine needs to be production quality, so I'm
wary as to which course of action to take.
Thanks in advance,
Steve
------------------------------
Message: 9
Date: Tue, 27 Sep 2005 19:00:23 +0200
From: Folkert Saathoff <fol...@feedface.com>
Subject: IPv6 and DUMMYNET traffic shaping
To: snap-...@kame.net, freebsd...@freebsd.org
Message-ID: <F4A9DCEA-BB99-4760...@feedface.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello lists,
in order to evaluate the latency penalty induced by mobile IPv6,
i need some way to simulate different latencies between two nodes
in a laboratory environment.
Is it possible at the moment to shape IPv6 traffic with KAME SNAP
20050919
and FreeBSD 5.4-RELEASE?
If not, is there some other way to enforce latencies on an interface?
thnx,
/folkert
/*
_
_
*
_||
_
*
||
fol...@feedface.com *
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFDOXqrIA10xPlRIZURAgFtAKCKptm0fzMOKHx1fqF2nPvrC0/mhACgleZs
nT+1i69QZtmv2mbnAmbc3bc=
=/0RH
-----END PGP SIGNATURE-----
------------------------------
Message: 10
Date: Tue, 27 Sep 2005 10:52:25 -0700
From: Brooks Davis <bro...@one-eyed-alien.net>
Subject: Re: IPv6 and DUMMYNET traffic shaping
To: Folkert Saathoff <fol...@feedface.com>
Cc: freebsd...@freebsd.org, snap-...@kame.net
Message-ID: <20050927175...@odin.ac.hmc.edu>
Content-Type: text/plain; charset="us-ascii"
On Tue, Sep 27, 2005 at 07:00:23PM +0200, Folkert Saathoff wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Hello lists,
>
> in order to evaluate the latency penalty induced by mobile IPv6,
> i need some way to simulate different latencies between two nodes
> in a laboratory environment.
>
> Is it possible at the moment to shape IPv6 traffic with KAME SNAP
> 20050919
> and FreeBSD 5.4-RELEASE?
>
> If not, is there some other way to enforce latencies on an interface?
Upgrade to 6.0 and use the IPv6 support in ipfw/dummynet.
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050927/ce197a45/attachment-0001.bin
------------------------------
Message: 11
Date: Tue, 27 Sep 2005 20:26:13 +0200
From: Max Laier <m...@love2party.net>
Subject: HEADSUP: bridge(4) removed from HEAD
To: freebsd...@freebsd.org
Cc: freebsd...@freebsd.org
Message-ID: <20050927202...@love2party.net>
Content-Type: text/plain; charset="us-ascii"
All,
as discussed on -arch, the old bridge(4) implementation has been removed from
HEAD. The new if_bridge(4) is there to serve as a full functional
replacement. If you find anything that does not work with if_bridge(4) that
used to work with bridge(4), please let me or Andrew Thompson (thompsa@)
know. Thanks.
--
/"\ Best regards, | mla...@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mlaier@EFnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050927/6b4b3c09/attachment-0001.bin
------------------------------
Message: 12
Date: Tue, 27 Sep 2005 20:54:56 +0200
From: L?szl? K?roly <laszlo...@tvnetwork.hu>
Subject: Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
To: Oleg Korecky <kor...@dnepr.net>
Cc: freebsd...@freebsd.org
Message-ID: <43399580...@tvnetwork.hu>
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Oleg Korecky wrote:
> Did somebody use LIRC on the FreeBSD ? Or what you can recommend instead
> LIRC ?
> Thanks !
I have a Pinnacle remote controll with serial port connector. It works
fine (tested only with mPlayer): lircd --device=/dev/cuad0 --drive=pinsys
Best, Laci
- --
László Károly <laszlo...@tvnetwork.hu>
Department of Altaic Studies Egyetem str. 2.
University of Szeged H-6722 Szeged, Hungary
PGP/GnuPG key: 1024D/869D81C5
Fingerprint: 1E61 3205 8F5A 87E7 1269 3396 1C63 F9FF 869D 81C5
Encrypted e-mail preferred.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDOZWAHGP5/4adgcURAhdBAJ97+gg8cxUihSIXOv9gxFVlH1dfswCgoPBZ
WpqYLZ8HSbk2jBbi+EP5W+0=
=tw07
-----END PGP SIGNATURE-----
------------------------------
Message: 13
Date: 27 Sep 2005 22:59:22 +0400
From: eS...@mtt.ru
Subject: eSafe alert
To: freebsd...@freebsd.org
Message-ID: <POST2bN5E3JPP...@mailoffice.office.msk.mtt>
*** eSafe detected hostile content in this email. ***
Time: 27 Sep 2005 23:05:13
Scan result: Mail rejected
Protocol: SMTP in
File Name\Mail Subject: mail_1127842462: Mail Delivery
Source: freebsd...@freebsd.org
Destination: dmitri...@mtt.ru
Details: Mail infected with x-wav exploit \HTML Active Content: Found the following Html Tag Exploit: <A^sHREF^s=cid^s:*>
**************************************************************************************************
The contents of this email and any attachments are confidential.
They are intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to anyone or make copies.
** MTT AV system scanned this email for viruses, vandals and malicious content. **
inf...@mtt.ru
**************************************************************************************************
------------------------------
Message: 14
Date: Tue, 27 Sep 2005 15:37:42 -0400 (EDT)
From: Kenneth W Cochran <k...@TheWorld.com>
Subject: UFS2 vs UFS1 determination
To: freebsd...@freebsd.org
Message-ID: <20050927193...@shell.TheWorld.com>
Hello -stable:
How can I determine a filesystem's type in FreeBSD?
More specifically, how can I determine whether a filesystem is UFS1
or UFS2 (assuming, of course, that UFS2 is supported by the OS)?
FAQ/doc/RTFM pointers are welcome. :)
Thanks,
-kc
------------------------------
Message: 15
Date: Tue, 27 Sep 2005 12:45:55 -0700
From: David Kirchner <d...@dpk.net>
Subject: Re: UFS2 vs UFS1 determination
To: Kenneth W Cochran <k...@theworld.com>
Cc: freebsd...@freebsd.org
Message-ID: <35c231bf05092...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 9/27/05, Kenneth W Cochran <k...@theworld.com> wrote:
> Hello -stable:
>
> How can I determine a filesystem's type in FreeBSD?
> More specifically, how can I determine whether a filesystem is UFS1
> or UFS2 (assuming, of course, that UFS2 is supported by the OS)?
> FAQ/doc/RTFM pointers are welcome. :)
I dunno about FAQs about this, but check out "/sbin/dumpfs"
------------------------------
Message: 16
Date: Tue, 27 Sep 2005 22:06:04 +0200
From: Erik Trulsson <ertr...@student.uu.se>
Subject: Re: UFS2 vs UFS1 determination
To: Kenneth W Cochran <k...@TheWorld.com>
Cc: freebsd...@freebsd.org
Message-ID: <20050927200...@falcon.midgard.homeip.net>
Content-Type: text/plain; charset=us-ascii
On Tue, Sep 27, 2005 at 03:37:42PM -0400, Kenneth W Cochran wrote:
> Hello -stable:
>
> How can I determine a filesystem's type in FreeBSD?
> More specifically, how can I determine whether a filesystem is UFS1
> or UFS2 (assuming, of course, that UFS2 is supported by the OS)?
> FAQ/doc/RTFM pointers are welcome. :)
Run dumpfs(8) on the filesystem and look at the first line of the output.
--
<Insert your favourite quote here.>
Erik Trulsson
ertr...@student.uu.se
------------------------------
Message: 17
Date: Tue, 27 Sep 2005 14:12:05 -0700
From: "Kevin Oberman" <obe...@es.net>
Subject: Re: Re[2]: device polling and high load averages
To: peceka <pec...@gmail.com>
Cc: freebsd...@freebsd.org, Vlad GALU <vlad...@gmail.com>, Glenn
Dawson <gl...@antimatter.net>
Message-ID: <200509272112...@ptavv.es.net>
> Date: Tue, 27 Sep 2005 13:02:48 +0200
> From: peceka <pec...@gmail.com>
> Sender: owner-free...@freebsd.org
>
> Witaj Glenn,
>
> W Twoim li=9Ccie datowanym 27 wrze=9Cnia 2005 (12:14:25) mo=BFna przeczyta=
> =E6:
>
> > At 02:41 AM 9/27/2005, Vlad GALU wrote:
> >>On 9/27/05, peceka <pec...@gmail.com> wrote:
> >> > Hi,
> >> >
> >> > I've got:
> >> > fw3# uname -r
> >> > 5.4-RELEASE-p7
> >> >
> >> > in my kernel config i've set:
> >> > options HZ=3D1000
> >> > options DEVICE_POLLING
> >> >
> >> > fw3# cat /etc/rc.conf | grep ifconfig
> >> > ifconfig_em0=3D"inet 192.168.1.251 netmask 255.255.255.0 polling"
> >> >
> >> > fw3# cat /etc/sysctl.conf | grep poll
> >> > kern.polling.enable=3D1
> >> > kern.polling.idle_poll=3D1
> >> >
> >> > And all the time i've got:
> >> > fw3# uptime
> >> > 11:22AM up 1:59, 1 user, load averages: 1.00, 1.00, 0.96
> >> >
> >> > from top:
> >> > last pid: 88131; load averages: 1.00, 1.00, 0.96
> >> > 24 processes: 1 running, 23 sleeping
> >> > CPU states: 0.0% user, 0.0% nice, 99.2% system, 0.8%=20
> >> interrupt, 0.0% idle
> >> >
> >> > But this machine do nothing, just pure FBSD system. So why there is
> >> > such high load aver.?
> >> >
> >>
> >> Because of kern.polling.idle_poll.
>
> > and a load average of 1 isn't exactly "high" either...
>
> But for machine which does nothing?
> CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3200.13-MHz 686-class CPU)
> real memory =3D 1341063168 (1278 MB)
>
> What to do with kern.polling.idle_poll? It is needed to be set to 1?
> What does this do?
If your system is polling, it's not doing nothing. It's polling.
If you enable polling, the network interface is no longer interrupt
driven. Instead, the system will continually poll the interface to
check on the arrival of new packets.
Polling is a big win on busy network interfaces and it is much faster
than processing an interrupt, but it does generate a continual load
average of 1 since the system is always polling when nothing else is
going on. It does not matter what the speed of the system is as the
polling loop runs continually when the CPU is idle.
If you network is not very busy, you probably don't want polling.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: obe...@es.net Phone: +1 510 486-8634
------------------------------
Message: 18
Date: Tue, 27 Sep 2005 22:50:54 +0100
From: martin <mar...@hybyte.com>
Subject: problem with aac0 on FreeBSD 5.4 Stable#5
To: freebsd...@freebsd.org, freebs...@freebsd.org,
aic...@freebsd.org
Message-ID: <4339BEBE...@hybyte.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
>Synopsis: aac driver hangs under load
>Description:
I am having the same/very similiar problem as described in
http://lists.freebsd.org/pipermail/freebsd-current/2004-December/044613.html.
I have 2 identical boxes "dell poweredge 1750", with Atapdec raid
controller <Adaptec SCSI RAID 2200S> and external powervault 220s.
Everything is fine on FreeBSD 5.3 Stable #7 (the box has been 6 month
under load)
On FreeBSD 5.4 Stable #5 the aac0 hangs once a fortnight, alway during
large file copy operations (Mysql database running optimize on all
tables,one after another), several Gigabyte of data)
(The box also has a amr controlled raid (as boot partition and /var
/usr). I had one occasion, where the disks on the amr became
inaccessable, since this are the boot and logging disks, there is no
data about that)
Not exactly sure, what else to attach, thankfull for any advice.
Here are the relevant parts from the message log
1) Errors
2) Boot msgs
Sep 26 04:07:17 db02 kernel: aac0: COMMAND 0xc4f816d8 TIMEOUT AFTER 47
SECONDS
Sep 26 04:07:17 db02 kernel: aac0: COMMAND 0xc4f7fa40 TIMEOUT AFTER 47
SECONDS
Sep 26 04:07:17 db02 kernel: aac0: COMMAND 0xc4f7ece4 TIMEOUT AFTER 47
SECONDS
Sep 26 04:07:17 db02 kernel: aac0: WARNING! Controller is no longer
running! code= 0x100
Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f816d8 TIMEOUT AFTER 67
SECONDS
Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7fa40 TIMEOUT AFTER 67
SECONDS
Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7ece4 TIMEOUT AFTER 67
SECONDS
Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7f068 TIMEOUT AFTER 46
SECONDS
Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7e384 TIMEOUT AFTER 46
SECONDS
Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f815ac TIMEOUT AFTER 46
SECONDS
continued as above, until reboot
Sep 26 12:35:49 db02 kernel: Copyright (c) 1992-2005 The FreeBSD Project.
Sep 26 12:35:49 db02 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
1989, 1991, 1992, 1993, 1994
Sep 26 12:35:49 db02 kernel: The Regents of the University of
California. All rights reserved.
Sep 26 12:35:49 db02 kernel: FreeBSD 5.4-STABLE #5: Fri May 27 11:56:29
UTC 2005
Sep 26 12:35:49 db02 kernel:
ro...@db2.hybyte.net:/usr/obj/usr/src/sys/DB02
Sep 26 12:35:49 db02 kernel: Timecounter "i8254" frequency 1193182 Hz
quality 0
Sep 26 12:35:49 db02 kernel: CPU: Intel(R) Xeon(TM) CPU 3.20GHz
(3185.12-MHz 686-class CPU)
Sep 26 12:35:49 db02 kernel: Origin = "GenuineIntel" Id = 0xf25
Stepping = 5
Sep 26 12:35:49 db02 kernel:
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Sep 26 12:35:49 db02 kernel: Hyperthreading: 2 logical CPUs
Sep 26 12:35:49 db02 kernel: real memory = 3892146176 (3711 MB)
Sep 26 12:35:49 db02 kernel: avail memory = 3813191680 (3636 MB)
Sep 26 12:35:49 db02 kernel: ACPI APIC Table: <DELL PE1750 >
Sep 26 12:35:49 db02 kernel: FreeBSD/SMP: Multiprocessor System
Detected: 4 CPUs
Sep 26 12:35:49 db02 kernel: cpu0 (BSP): APIC ID: 0
Sep 26 12:35:49 db02 kernel: cpu1 (AP): APIC ID: 1
Sep 26 12:35:49 db02 kernel: cpu2 (AP): APIC ID: 6
Sep 26 12:35:49 db02 kernel: cpu3 (AP): APIC ID: 7
Sep 26 12:35:49 db02 kernel: ioapic0: Changing APIC ID to 8
Sep 26 12:35:49 db02 kernel: ioapic1: Changing APIC ID to 9
Sep 26 12:35:50 db02 kernel: ioapic2: Changing APIC ID to 10
Sep 26 12:35:50 db02 kernel: MADT: Forcing active-low polarity and level
trigger for SCI
Sep 26 12:35:50 db02 kernel: ioapic0 <Version 1.1> irqs 0-15 on motherboard
Sep 26 12:35:50 db02 kernel: ioapic1 <Version 1.1> irqs 16-31 on
motherboard
Sep 26 12:35:50 db02 kernel: ioapic2 <Version 1.1> irqs 32-47 on
motherboard
Sep 26 12:35:50 db02 kernel: npx0: <math processor> on motherboard
Sep 26 12:35:50 db02 kernel: npx0: INT 16 interface
Sep 26 12:35:50 db02 kernel: acpi0: <DELL PE1750> on motherboard
Sep 26 12:35:50 db02 kernel: acpi0: Power Button (fixed)
Sep 26 12:35:50 db02 kernel: Timecounter "ACPI-safe" frequency 3579545
Hz quality 1000
Sep 26 12:35:50 db02 kernel: acpi_timer0: <32-bit timer at 3.579545MHz>
port 0x808-0x80b on acpi0
Sep 26 12:35:50 db02 kernel: cpu0: <ACPI CPU> on acpi0
Sep 26 12:35:50 db02 kernel: cpu1: <ACPI CPU> on acpi0
Sep 26 12:35:50 db02 kernel: cpu2: <ACPI CPU> on acpi0
Sep 26 12:35:50 db02 kernel: cpu3: <ACPI CPU> on acpi0
Sep 26 12:35:50 db02 kernel: pcib0: <ACPI Host-PCI bridge> port
0xcf8-0xcff on acpi0
Sep 26 12:35:50 db02 kernel: pci0: <ACPI PCI bus> on pcib0
Sep 26 12:35:50 db02 kernel: pci0: <display, VGA> at device 14.0 (no
driver attached)
Sep 26 12:35:50 db02 kernel: atapci0: <ServerWorks CSB5 UDMA100
controller> port 0x8b0-0x8bf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at
device 15.1 on pci0
Sep 26 12:35:50 db02 kernel: ata0: channel #0 on atapci0
Sep 26 12:35:50 db02 kernel: ata1: channel #1 on atapci0
Sep 26 12:35:50 db02 kernel: pci0: <serial bus, USB> at device 15.2 (no
driver attached)
Sep 26 12:35:50 db02 kernel: isab0: <PCI-ISA bridge> at device 15.3 on pci0
Sep 26 12:35:50 db02 kernel: isa0: <ISA bus> on isab0
Sep 26 12:35:50 db02 kernel: pcib1: <ACPI Host-PCI bridge> on acpi0
Sep 26 12:35:50 db02 kernel: pci4: <ACPI PCI bus> on pcib1
Sep 26 12:35:50 db02 kernel: amr0: <LSILogic MegaRAID 1.51> mem
0xf7f00000-0xf7f3ffff,0xe8000000-0xefffffff irq 18 at device 3.0 on pci4
Sep 26 12:35:50 db02 kernel: amr0: <LSILogic PERC 4/Di> Firmware 412W,
BIOS H406, 128MB RAM
Sep 26 12:35:50 db02 kernel: pcib2: <ACPI Host-PCI bridge> on acpi0
Sep 26 12:35:50 db02 kernel: pci3: <ACPI PCI bus> on pcib2
Sep 26 12:35:50 db02 kernel: aac0: <Adaptec SCSI RAID 2200S> mem
0xf8000000-0xfbffffff irq 24 at device 6.0 on pci3
Sep 26 12:35:50 db02 kernel: aac0: Unknown processor 100MHz, 48MB cache
memory, optional battery present
Sep 26 12:35:50 db02 kernel: aac0: Kernel 4.1-0, Build 7244, S/N b764f4
Sep 26 12:35:50 db02 kernel: aac0: Supported
Options=11d7e<CLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD>
Sep 26 12:35:50 db02 kernel: aacp0: <SCSI Passthrough Bus> on aac0
Sep 26 12:35:50 db02 kernel: aacp1: <SCSI Passthrough Bus> on aac0
Sep 26 12:35:50 db02 kernel: pcib3: <ACPI Host-PCI bridge> on acpi0
Sep 26 12:35:50 db02 kernel: pci2: <ACPI PCI bus> on pcib3
Sep 26 12:35:50 db02 kernel: bge0: <Broadcom BCM5704C Dual Gigabit
Ethernet, ASIC rev. 0x2002> mem
0xfcf20000-0xfcf2ffff,0xfcf30000-0xfcf3ffff irq 16 at device 0.0 on pci2
Sep 26 12:35:50 db02 kernel: miibus0: <MII bus> on bge0
Sep 26 12:35:50 db02 kernel: brgphy0: <BCM5704 10/100/1000baseTX PHY> on
miibus0
Sep 26 12:35:50 db02 kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
Sep 26 12:35:50 db02 kernel: bge0: Ethernet address: 00:11:43:5a:68:70
Sep 26 12:35:50 db02 kernel: bge1: <Broadcom BCM5704C Dual Gigabit
Ethernet, ASIC rev. 0x2002> mem
0xfcf00000-0xfcf0ffff,0xfcf10000-0xfcf1ffff irq 17 at device 0.1 on pci2
Sep 26 12:35:50 db02 kernel: miibus1: <MII bus> on bge1
Sep 26 12:35:50 db02 kernel: brgphy1: <BCM5704 10/100/1000baseTX PHY> on
miibus1
Sep 26 12:35:50 db02 kernel: brgphy1: 10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
Sep 26 12:35:50 db02 kernel: bge1: Ethernet address: 00:11:43:5a:68:71
Sep 26 12:35:50 db02 kernel: pcib4: <ACPI Host-PCI bridge> on acpi0
Sep 26 12:35:50 db02 kernel: pci1: <ACPI PCI bus> on pcib4
Sep 26 12:35:50 db02 kernel: fdc0: <floppy drive controller> port
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0
Sep 26 12:35:50 db02 kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Sep 26 12:35:50 db02 kernel: atkbdc0: <Keyboard controller (i8042)> port
0x64,0x60 irq 1 on acpi0
Sep 26 12:35:50 db02 kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Sep 26 12:35:50 db02 kernel: kbd0 at atkbd0
Sep 26 12:35:50 db02 kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
Sep 26 12:35:50 db02 kernel: psm0: model Generic PS/2 mouse, device ID 0
Sep 26 12:35:50 db02 kernel: sio0: <16550A-compatible COM port> port
0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Sep 26 12:35:50 db02 kernel: sio0: type 16550A
Sep 26 12:35:50 db02 kernel: orm0: <ISA Option ROMs> at iomem
0xec000-0xeffff,0xd0000-0xd17ff,0xc9000-0xcd7ff,0xc8000-0xc8fff,0xc0000-0xc7fff
on isa0
Sep 26 12:35:50 db02 kernel: pmtimer0 on isa0
Sep 26 12:35:50 db02 kernel: sc0: <System console> at flags 0x100 on isa0
Sep 26 12:35:50 db02 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Sep 26 12:35:50 db02 kernel: sio1: configured irq 3 not in bitmap of
probed irqs 0
Sep 26 12:35:50 db02 kernel: sio1: port may not be enabled
Sep 26 12:35:50 db02 kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df
iomem 0xa0000-0xbffff on isa0
Sep 26 12:35:50 db02 kernel: Timecounters tick every 10.000 msec
Sep 26 12:35:50 db02 kernel: IP Filter: v3.4.35 initialized. Default =
pass all, Logging = enabled
Sep 26 12:35:50 db02 kernel: ipfw2 initialized, divert enabled,
rule-based forwarding enabled, default to accept, logging limited to
1024 packets/entry by default
Sep 26 12:35:50 db02 kernel: amrd0: <LSILogic MegaRAID logical drive> on
amr0
Sep 26 12:35:50 db02 kernel: amrd0: 34680MB (71024640 sectors) RAID 1
(optimal)
Sep 26 12:35:50 db02 kernel: aacd0: <RAID 5> on aac0
Sep 26 12:35:50 db02 kernel: aacd0: 419943MB (860045184 sectors)
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
Command. CDB: 12 1 80 0 ff 0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
asc:24,0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
Command. CDB: 12 1 80 0 ff 0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
asc:24,0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
Command. CDB: 12 1 80 0 ff 0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
asc:24,0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
Command. CDB: 12 1 80 0 ff 0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
asc:24,0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
Command. CDB: 12 1 80 0 ff 0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
asc:24,0
Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:1): AutoSense Failed
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:2): AutoSense Failed
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:3): AutoSense Failed
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:4): AutoSense Failed
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:5): AutoSense Failed
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:6): AutoSense Failed
Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:7): AutoSense Failed
Sep 26 12:35:50 db02 kernel: ses0 at amr0 bus 0 target 6 lun 0
Sep 26 12:35:50 db02 kernel: ses0: <PE/PV 1x3 SCSI BP 1.1> Fixed
Processor SCSI-2 device
Sep 26 12:35:50 db02 kernel: ses0: SAF-TE Compliant Device
Sep 26 12:35:50 db02 kernel: ses1 at aacp0 bus 0 target 6 lun 0
Sep 26 12:35:50 db02 kernel: ses1: <DELL PV22XS E.17> Fixed unknown
SCSI-3 device
Sep 26 12:35:50 db02 kernel: ses1: 3.300MB/s transfers
Sep 26 12:35:50 db02 kernel: ses1: SAF-TE Compliant Device
Sep 26 12:35:50 db02 kernel: SMP: AP CPU #2 Launched!
Sep 26 12:35:50 db02 kernel: SMP: AP CPU #1 Launched!
Sep 26 12:35:50 db02 kernel: SMP: AP CPU #3 Launched!
>How-To-Repeat:
>Fix:
------------------------------
Message: 19
Date: Wed, 28 Sep 2005 01:15:42 +0300
From: Maher Mohamed <mah...@gmail.com>
Subject: Help With Word press Settup and confguration
To: freebsd...@freebsd.org
Message-ID: <f34868a305092...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Does anyone has settup the word press, i am really having a tough time with
it
if you decided to help me then please right down the steps that i should use
to settup everything
I would apriciate some examples or some link
Thank you in advanced
--
Mohamed M. Maher
------------------------------
Message: 20
Date: Tue, 27 Sep 2005 16:17:39 -0700 (PDT)
From: Joel Wood <jw...@mail.ncircle.com>
Subject: Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
To: Oleg Korecky <kor...@dnepr.net>
Cc: freebsd...@freebsd.org
Message-ID: <2005092716...@mail.ncircle.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
I wrote a simple python program that interfaces directly with /dev/ugen0.1
to work with the usb rf ati remote wonder plus. Rather then interfacing
through lircd, I just output stuff in the format that lircd uses so that programs
like mplayer just work.
The format is something like:
hexcode repeat-count keybinding configfile
or:
'00000040151f0a00 00 MUTE /home/jwood/remotewonderplus.conf\n'
'00000040151f0a00 01 MUTE /home/jwood/remotewonderplus.conf\n'
'00000040151f0a00 02 MUTE /home/jwood/remotewonderplus.conf\n'
'00000040151f0a00 03 MUTE /home/jwood/remotewonderplus.conf\n'
if I were to hold the mute key down.
If anyone would like the code, reply to me off list, as I am not on the
list.
-Joel
On Tue, 27 Sep 2005, Oleg Korecky wrote:
> Did somebody use LIRC on the FreeBSD ? Or what you can recommend instead LIRC
> ?
> Thanks !
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
------------------------------
Message: 21
Date: Wed, 28 Sep 2005 11:17:19 +0930
From: "Daniel O'Connor" <doco...@gsoft.com.au>
Subject: Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
To: freebsd...@freebsd.org
Cc: Oleg Korecky <kor...@dnepr.net>
Message-ID: <200509281117....@gsoft.com.au>
Content-Type: text/plain; charset="iso-8859-1"
On Tuesday 27 September 2005 22:30, Oleg Korecky wrote:
> Did somebody use LIRC on the FreeBSD ? Or what you can recommend instead
> LIRC ?
I've used it with an IRMan compatible remote that I built
http://www.jaycar.com.au/productView.asp?ID=KC5366&CATID=&keywords=remote+control&SPECIAL=&form=KEYWORD&ProdCodeOnly=&Keyword1=&Keyword2=&pageNumber=&priceMin=&priceMax=&SUBCATID=
Note that you will probably want to use the version of LIRC in
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/86528 which is more up to
date than the ports one and has some fixes for the (pretty revolting) code
LIRC uses to lock the serial port.
I have this in /etc/rc.conf...
lircd_enable="YES"
lircd_flags="-H irman -d /dev/cuaa0 /usr/local/etc/lircd.conf"
/usr/local/etc/lircd.conf was generated using irrecord.
I have a patch for mplayer which enables LIRC support on FreeBSD which I
believe the maintainer will be committing RSN (when I get back to him
anyway :)
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050928/93d75746/attachment-0001.bin
------------------------------
Message: 22
Date: Wed, 28 Sep 2005 04:00:43 +0200
From: Folkert Saathoff <fol...@feedface.com>
Subject: Re: IPv6 and DUMMYNET traffic shaping
To: snap-...@kame.net, sta...@freebsd.org
Message-ID: <A1599609-2BE3-4823...@feedface.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Sep 27, 2005 at 07:00:23PM +0200, Folkert Saathoff wrote:
> Hello lists,
>
> in order to evaluate the latency penalty induced by mobile IPv6,
> i need some way to simulate different latencies between two nodes
> in a laboratory environment.
>
> Is it possible at the moment to shape IPv6 traffic with KAME SNAP
> 20050919
> and FreeBSD 5.4-RELEASE?
>
> If not, is there some other way to enforce latencies on an interface?
>
further testing revealed that it is in fact possible to enforce latency
on an ipv6-only interface with ipfw and dummynet:
sudo sysctl net.link.ether.ipfw=1
sudo ipfw pipe 1 config bw 100kbit/s
sudo ipfw add 1 pipe 1 layer2 xmit rl1
thnx for the replies :)
/folkert
/*
_
_
*
_||
_
*
||
fol...@feedface.com *
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFDOflOIA10xPlRIZURApfsAJ9zBrNd3s7LJTNaR1SqWX9yKZhhyACfa4HZ
JIRP9du59vNOedyZmyijmSg=
=Zxkd
-----END PGP SIGNATURE-----
------------------------------
Message: 23
Date: Tue, 27 Sep 2005 20:26:37 -0700
From: Maxim Sobolev <sob...@portaone.com>
Subject: Re: HEADSUP: bridge(4) removed from HEAD
To: Max Laier <m...@love2party.net>
Cc: freebsd...@FreeBSD.ORG, freebsd...@FreeBSD.ORG
Message-ID: <433A0D6D...@portaone.com>
Content-Type: text/plain; charset=KOI8-U; format=flowed
Max Laier wrote:
> All,
>
> as discussed on -arch, the old bridge(4) implementation has been removed from
> HEAD. The new if_bridge(4) is there to serve as a full functional
> replacement. If you find anything that does not work with if_bridge(4) that
> used to work with bridge(4), please let me or Andrew Thompson (thompsa@)
> know. Thanks.
Have you updated the handbook to reflect this change?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html
-Maxim
------------------------------
Message: 24
Date: Tue, 27 Sep 2005 22:41:58 -0600
From: Scott Long <sco...@samsco.org>
Subject: Re: problem with aac0 on FreeBSD 5.4 Stable#5
To: martin <mar...@hybyte.com>
Cc: freebs...@freebsd.org, freebsd...@freebsd.org,
aic...@freebsd.org
Message-ID: <433A1F16...@samsco.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Sorry, but I really cannot imagine what is going on here. According to
the messages, the card seems to have crashed. You're using firmware rev
7244 on it, and I can't say that I've ever been happy with the 7xxx
series firmware. Would it be possible to back down to rev 6011? I
believe that you can still get it from the Adaptec website. If not, let
me know and I'll see if I have a copy that I can share.
Scott
martin wrote:
>
>> Synopsis: aac driver hangs under load
>> Description:
>
>
> I am having the same/very similiar problem as described in
> http://lists.freebsd.org/pipermail/freebsd-current/2004-December/044613.html.
>
>
> I have 2 identical boxes "dell poweredge 1750", with Atapdec raid
> controller <Adaptec SCSI RAID 2200S> and external powervault 220s.
>
> Everything is fine on FreeBSD 5.3 Stable #7 (the box has been 6 month
> under load)
>
> On FreeBSD 5.4 Stable #5 the aac0 hangs once a fortnight, alway during
> large file copy operations (Mysql database running optimize on all
> tables,one after another), several Gigabyte of data)
>
> (The box also has a amr controlled raid (as boot partition and /var
> /usr). I had one occasion, where the disks on the amr became
> inaccessable, since this are the boot and logging disks, there is no
> data about that)
>
> Not exactly sure, what else to attach, thankfull for any advice.
>
> Here are the relevant parts from the message log
> 1) Errors
> 2) Boot msgs
>
> Sep 26 04:07:17 db02 kernel: aac0: COMMAND 0xc4f816d8 TIMEOUT AFTER 47
> SECONDS
> Sep 26 04:07:17 db02 kernel: aac0: COMMAND 0xc4f7fa40 TIMEOUT AFTER 47
> SECONDS
> Sep 26 04:07:17 db02 kernel: aac0: COMMAND 0xc4f7ece4 TIMEOUT AFTER 47
> SECONDS
> Sep 26 04:07:17 db02 kernel: aac0: WARNING! Controller is no longer
> running! code= 0x100
> Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f816d8 TIMEOUT AFTER 67
> SECONDS
> Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7fa40 TIMEOUT AFTER 67
> SECONDS
> Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7ece4 TIMEOUT AFTER 67
> SECONDS
> Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7f068 TIMEOUT AFTER 46
> SECONDS
> Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f7e384 TIMEOUT AFTER 46
> SECONDS
> Sep 26 04:07:37 db02 kernel: aac0: COMMAND 0xc4f815ac TIMEOUT AFTER 46
> SECONDS
>
> continued as above, until reboot
>
>
> Sep 26 12:35:49 db02 kernel: Copyright (c) 1992-2005 The FreeBSD Project.
> Sep 26 12:35:49 db02 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
> 1989, 1991, 1992, 1993, 1994
> Sep 26 12:35:49 db02 kernel: The Regents of the University of
> California. All rights reserved.
> Sep 26 12:35:49 db02 kernel: FreeBSD 5.4-STABLE #5: Fri May 27 11:56:29
> UTC 2005
> Sep 26 12:35:49 db02 kernel:
> ro...@db2.hybyte.net:/usr/obj/usr/src/sys/DB02
> Sep 26 12:35:49 db02 kernel: Timecounter "i8254" frequency 1193182 Hz
> quality 0
> Sep 26 12:35:49 db02 kernel: CPU: Intel(R) Xeon(TM) CPU 3.20GHz
> (3185.12-MHz 686-class CPU)
> Sep 26 12:35:49 db02 kernel: Origin = "GenuineIntel" Id = 0xf25
> Stepping = 5
> Sep 26 12:35:49 db02 kernel:
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>
>
>
>
> Sep 26 12:35:49 db02 kernel: Hyperthreading: 2 logical CPUs
> Sep 26 12:35:49 db02 kernel: real memory = 3892146176 (3711 MB)
> Sep 26 12:35:49 db02 kernel: avail memory = 3813191680 (3636 MB)
> Sep 26 12:35:49 db02 kernel: ACPI APIC Table: <DELL PE1750 >
> Sep 26 12:35:49 db02 kernel: FreeBSD/SMP: Multiprocessor System
> Detected: 4 CPUs
> Sep 26 12:35:49 db02 kernel: cpu0 (BSP): APIC ID: 0
> Sep 26 12:35:49 db02 kernel: cpu1 (AP): APIC ID: 1
> Sep 26 12:35:49 db02 kernel: cpu2 (AP): APIC ID: 6
> Sep 26 12:35:49 db02 kernel: cpu3 (AP): APIC ID: 7
> Sep 26 12:35:49 db02 kernel: ioapic0: Changing APIC ID to 8
> Sep 26 12:35:49 db02 kernel: ioapic1: Changing APIC ID to 9
> Sep 26 12:35:50 db02 kernel: ioapic2: Changing APIC ID to 10
> Sep 26 12:35:50 db02 kernel: MADT: Forcing active-low polarity and level
> trigger for SCI
> Sep 26 12:35:50 db02 kernel: ioapic0 <Version 1.1> irqs 0-15 on motherboard
> Sep 26 12:35:50 db02 kernel: ioapic1 <Version 1.1> irqs 16-31 on
> motherboard
> Sep 26 12:35:50 db02 kernel: ioapic2 <Version 1.1> irqs 32-47 on
> motherboard
> Sep 26 12:35:50 db02 kernel: npx0: <math processor> on motherboard
> Sep 26 12:35:50 db02 kernel: npx0: INT 16 interface
> Sep 26 12:35:50 db02 kernel: acpi0: <DELL PE1750> on motherboard
> Sep 26 12:35:50 db02 kernel: acpi0: Power Button (fixed)
> Sep 26 12:35:50 db02 kernel: Timecounter "ACPI-safe" frequency 3579545
> Hz quality 1000
> Sep 26 12:35:50 db02 kernel: acpi_timer0: <32-bit timer at 3.579545MHz>
> port 0x808-0x80b on acpi0
> Sep 26 12:35:50 db02 kernel: cpu0: <ACPI CPU> on acpi0
> Sep 26 12:35:50 db02 kernel: cpu1: <ACPI CPU> on acpi0
> Sep 26 12:35:50 db02 kernel: cpu2: <ACPI CPU> on acpi0
> Sep 26 12:35:50 db02 kernel: cpu3: <ACPI CPU> on acpi0
> Sep 26 12:35:50 db02 kernel: pcib0: <ACPI Host-PCI bridge> port
> 0xcf8-0xcff on acpi0
> Sep 26 12:35:50 db02 kernel: pci0: <ACPI PCI bus> on pcib0
> Sep 26 12:35:50 db02 kernel: pci0: <display, VGA> at device 14.0 (no
> driver attached)
> Sep 26 12:35:50 db02 kernel: atapci0: <ServerWorks CSB5 UDMA100
> controller> port 0x8b0-0x8bf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at
> device 15.1 on pci0
> Sep 26 12:35:50 db02 kernel: ata0: channel #0 on atapci0
> Sep 26 12:35:50 db02 kernel: ata1: channel #1 on atapci0
> Sep 26 12:35:50 db02 kernel: pci0: <serial bus, USB> at device 15.2 (no
> driver attached)
> Sep 26 12:35:50 db02 kernel: isab0: <PCI-ISA bridge> at device 15.3 on pci0
> Sep 26 12:35:50 db02 kernel: isa0: <ISA bus> on isab0
> Sep 26 12:35:50 db02 kernel: pcib1: <ACPI Host-PCI bridge> on acpi0
> Sep 26 12:35:50 db02 kernel: pci4: <ACPI PCI bus> on pcib1
> Sep 26 12:35:50 db02 kernel: amr0: <LSILogic MegaRAID 1.51> mem
> 0xf7f00000-0xf7f3ffff,0xe8000000-0xefffffff irq 18 at device 3.0 on pci4
> Sep 26 12:35:50 db02 kernel: amr0: <LSILogic PERC 4/Di> Firmware 412W,
> BIOS H406, 128MB RAM
> Sep 26 12:35:50 db02 kernel: pcib2: <ACPI Host-PCI bridge> on acpi0
> Sep 26 12:35:50 db02 kernel: pci3: <ACPI PCI bus> on pcib2
> Sep 26 12:35:50 db02 kernel: aac0: <Adaptec SCSI RAID 2200S> mem
> 0xf8000000-0xfbffffff irq 24 at device 6.0 on pci3
> Sep 26 12:35:50 db02 kernel: aac0: Unknown processor 100MHz, 48MB cache
> memory, optional battery present
> Sep 26 12:35:50 db02 kernel: aac0: Kernel 4.1-0, Build 7244, S/N b764f4
> Sep 26 12:35:50 db02 kernel: aac0: Supported
> Options=11d7e<CLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD>
>
>
>
>
> Sep 26 12:35:50 db02 kernel: aacp0: <SCSI Passthrough Bus> on aac0
> Sep 26 12:35:50 db02 kernel: aacp1: <SCSI Passthrough Bus> on aac0
> Sep 26 12:35:50 db02 kernel: pcib3: <ACPI Host-PCI bridge> on acpi0
> Sep 26 12:35:50 db02 kernel: pci2: <ACPI PCI bus> on pcib3
> Sep 26 12:35:50 db02 kernel: bge0: <Broadcom BCM5704C Dual Gigabit
> Ethernet, ASIC rev. 0x2002> mem
> 0xfcf20000-0xfcf2ffff,0xfcf30000-0xfcf3ffff irq 16 at device 0.0 on pci2
> Sep 26 12:35:50 db02 kernel: miibus0: <MII bus> on bge0
> Sep 26 12:35:50 db02 kernel: brgphy0: <BCM5704 10/100/1000baseTX PHY> on
> miibus0
> Sep 26 12:35:50 db02 kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX,
> 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
> Sep 26 12:35:50 db02 kernel: bge0: Ethernet address: 00:11:43:5a:68:70
> Sep 26 12:35:50 db02 kernel: bge1: <Broadcom BCM5704C Dual Gigabit
> Ethernet, ASIC rev. 0x2002> mem
> 0xfcf00000-0xfcf0ffff,0xfcf10000-0xfcf1ffff irq 17 at device 0.1 on pci2
> Sep 26 12:35:50 db02 kernel: miibus1: <MII bus> on bge1
> Sep 26 12:35:50 db02 kernel: brgphy1: <BCM5704 10/100/1000baseTX PHY> on
> miibus1
> Sep 26 12:35:50 db02 kernel: brgphy1: 10baseT, 10baseT-FDX, 100baseTX,
> 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
> Sep 26 12:35:50 db02 kernel: bge1: Ethernet address: 00:11:43:5a:68:71
> Sep 26 12:35:50 db02 kernel: pcib4: <ACPI Host-PCI bridge> on acpi0
> Sep 26 12:35:50 db02 kernel: pci1: <ACPI PCI bus> on pcib4
> Sep 26 12:35:50 db02 kernel: fdc0: <floppy drive controller> port
> 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0
> Sep 26 12:35:50 db02 kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> Sep 26 12:35:50 db02 kernel: atkbdc0: <Keyboard controller (i8042)> port
> 0x64,0x60 irq 1 on acpi0
> Sep 26 12:35:50 db02 kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
> Sep 26 12:35:50 db02 kernel: kbd0 at atkbd0
> Sep 26 12:35:50 db02 kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
> Sep 26 12:35:50 db02 kernel: psm0: model Generic PS/2 mouse, device ID 0
> Sep 26 12:35:50 db02 kernel: sio0: <16550A-compatible COM port> port
> 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
> Sep 26 12:35:50 db02 kernel: sio0: type 16550A
> Sep 26 12:35:50 db02 kernel: orm0: <ISA Option ROMs> at iomem
> 0xec000-0xeffff,0xd0000-0xd17ff,0xc9000-0xcd7ff,0xc8000-0xc8fff,0xc0000-0xc7fff
>
>
>
> on isa0
> Sep 26 12:35:50 db02 kernel: pmtimer0 on isa0
> Sep 26 12:35:50 db02 kernel: sc0: <System console> at flags 0x100 on isa0
> Sep 26 12:35:50 db02 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
> Sep 26 12:35:50 db02 kernel: sio1: configured irq 3 not in bitmap of
> probed irqs 0
> Sep 26 12:35:50 db02 kernel: sio1: port may not be enabled
> Sep 26 12:35:50 db02 kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df
> iomem 0xa0000-0xbffff on isa0
> Sep 26 12:35:50 db02 kernel: Timecounters tick every 10.000 msec
> Sep 26 12:35:50 db02 kernel: IP Filter: v3.4.35 initialized. Default =
> pass all, Logging = enabled
> Sep 26 12:35:50 db02 kernel: ipfw2 initialized, divert enabled,
> rule-based forwarding enabled, default to accept, logging limited to
> 1024 packets/entry by default
> Sep 26 12:35:50 db02 kernel: amrd0: <LSILogic MegaRAID logical drive> on
> amr0
> Sep 26 12:35:50 db02 kernel: amrd0: 34680MB (71024640 sectors) RAID 1
> (optimal)
> Sep 26 12:35:50 db02 kernel: aacd0: <RAID 5> on aac0
> Sep 26 12:35:50 db02 kernel: aacd0: 419943MB (860045184 sectors)
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
> Command. CDB: 12 1 80 0 ff 0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
> asc:24,0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
> Command. CDB: 12 1 80 0 ff 0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
> asc:24,0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
> Command. CDB: 12 1 80 0 ff 0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
> asc:24,0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
> Command. CDB: 12 1 80 0 ff 0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
> asc:24,0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Vendor Specific
> Command. CDB: 12 1 80 0 ff 0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): ILLEGAL REQUEST
> asc:24,0
> Sep 26 12:35:50 db02 kernel: (probe36:aacp0:0:6:0): Invalid field in CDB
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:1): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:2): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:3): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:4): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:5): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:6): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: (probe0:aacp0:0:6:7): AutoSense Failed
> Sep 26 12:35:50 db02 kernel: ses0 at amr0 bus 0 target 6 lun 0
> Sep 26 12:35:50 db02 kernel: ses0: <PE/PV 1x3 SCSI BP 1.1> Fixed
> Processor SCSI-2 device
> Sep 26 12:35:50 db02 kernel: ses0: SAF-TE Compliant Device
> Sep 26 12:35:50 db02 kernel: ses1 at aacp0 bus 0 target 6 lun 0
> Sep 26 12:35:50 db02 kernel: ses1: <DELL PV22XS E.17> Fixed unknown
> SCSI-3 device
> Sep 26 12:35:50 db02 kernel: ses1: 3.300MB/s transfers
> Sep 26 12:35:50 db02 kernel: ses1: SAF-TE Compliant Device
> Sep 26 12:35:50 db02 kernel: SMP: AP CPU #2 Launched!
> Sep 26 12:35:50 db02 kernel: SMP: AP CPU #1 Launched!
> Sep 26 12:35:50 db02 kernel: SMP: AP CPU #3 Launched!
>
>
>> How-To-Repeat:
>
>
>> Fix:
>
>
>
>
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
------------------------------
Message: 25
Date: Tue, 27 Sep 2005 22:09:46 -0700
From: jaredball <jare...@comcast.net>
Subject: (no subject)
To: freebsd...@freebsd.org
Message-ID: <433A259A...@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
------------------------------
Message: 26
Date: Wed, 28 Sep 2005 08:13:32 +0200
From: "Simon L. Nielsen" <si...@FreeBSD.org>
Subject: Re: HEADSUP: bridge(4) removed from HEAD
To: Maxim....@portaone.com
Cc: Max Laier <m...@love2party.net>, freebsd...@FreeBSD.ORG,
freebsd...@FreeBSD.ORG
Message-ID: <2005092806...@zaphod.nitro.dk>
Content-Type: text/plain; charset="us-ascii"
On 2005.09.27 20:26:37 -0700, Maxim Sobolev wrote:
> Max Laier wrote:
> >All,
> >
> >as discussed on -arch, the old bridge(4) implementation has been removed
> >from HEAD. The new if_bridge(4) is there to serve as a full functional
> >replacement. If you find anything that does not work with if_bridge(4)
> >that used to work with bridge(4), please let me or Andrew Thompson
> >(thompsa@) know. Thanks.
>
> Have you updated the handbook to reflect this change?
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html
Considering that we only (more or less) document -STABLE branches in
the Handbook it's not a big rush, as long as it's mentioned before 7.0
comes out, though documentation about if_bridge in the Handbook would
of cause be nice, considering it's also in 6.0 :-).
--
Simon L. Nielsen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050928/03e81b68/attachment-0001.bin
------------------------------
Message: 27
Date: Wed, 28 Sep 2005 07:36:51 +0100
From: "Gray Lilley" <gr...@mistaken-identity.co.uk>
Subject: Cue0 Panic (still) kern/75710
To: <freebsd...@freebsd.org>
Message-ID: <ACE436445E3CB14DB6B...@magnum.Home.local>
Content-Type: text/plain; charset="windows-1250"
Good Morning All,
Sorry if this ends up as a repost, my mail system bounced it back to me.
I've tried this on several machines now, all of different specification, manufacturer and am still coming across this same problem...
Whenever I try to ifconfig cue0 up the machine panics, hand typed panic message below.
Fatal trap 12: page fault while in kernel mode
Cpuid = 0;
apic id = 00
Fault virtual address = 0x8
Fault code = supervisor read, page not present
Instruction pointer = 0x8:0xc05d3960
Stack pointer = 0x10:0xca5f18bc
Frame pointer = 0x10:0xca5f18d4
Code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
Processor eflags = interrupt enabled, resume, IOPL=0
Current process = 116 (ifconfig) Trap number = 12
Panic: page fault
Cpuid = 0
I have filed a PR on this, but I have not had any responses from it (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/75710).
The panic there is from a compaq armada 110 notebook, but I get the same panic (same 3 pointers) on a toshiba satellite pro a40 and on a self built p4 machine along with several others.
It affects 5.x 6.0 (all the way up to BETA5) but it works flawlessly with 4.11-STABLE/RELEASE.
Does anyone have any new fresh ideas about this one?
This is 100% reproduceable so I can try this at anytime,
Best Regards,
Graham Lilley
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.7/112 - Release Date: 26/09/2005
------------------------------
Message: 28
Date: Wed, 28 Sep 2005 09:12:06 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Strange interaction between rcNG and procfs
To: freebsd...@freebsd.org
Message-ID: <20050928081...@lack-of-gravitas.thebunker.net>
Content-Type: text/plain; charset="us-ascii"
Dear all,
I just ran into an odd problem. In some circumstances it seems that
you will need to have /proc mounted in order for rcNG startup scripts
to work correctly. I ran into this while configuring mysql 4.1.14
server on a 'large' 5.4-RELEASE-p7 DB server (4GB RAM, MAXDSIZ and
MAXSSIZ bumped to 2GB in kernel config and mysql currently configured
to malloc about 1.8GB when it starts up) -- however smaller scale
mysql installations on other 5.4-RELEASE or 6.0-BETA don't exhibit the
same effect.
Without /proc mounted I get this:
zloty:~:# umount /proc
zloty:~:# /usr/local/etc/rc.d/mysql-server.sh start
Starting mysql.
zloty:~:# /usr/local/etc/rc.d/mysql-server.sh status
mysql is not running.
zloty:~:# ps -auxwwww | grep mysqld
mysql 7387 0.0 0.0 1660 1260 p1 S 8:57AM 0:00.01 /bin/sh /usr/local/bin/mysqld_safe --defaults-extra-file=/store/mysql-z-master/my.cnf --user=mysql --datadir=/store/mysql-z-master --pid-file=/store/mysql-z-master/zloty.hosted-at.thebunker.net.pid
mysql 7416 0.0 8.0 1925400 271848 p1 S 8:57AM 0:01.17 [mysqld]
root 7427 0.0 0.0 1444 912 p1 R+ 8:57AM 0:00.00 grep mysqld
Note that the process name of the real mysqld has been replaced by
[mysqld] -- I thought things in [square brackets] in ps output
indicatd kernel threads? This also prevents mysql server being
shutdown cleanly using the rcNG scripts:
zloty:~:# /usr/local/etc/rc.d/mysql-server.sh stop
mysql not running? (check /store/mysql-z-master/zloty.hosted-at.thebunker.net.pid).
Mounting /proc restores the expected behaviour:
zloty:~:# mount /proc
zloty:~:# /usr/local/etc/rc.d/mysql-server.sh status
mysql is running as pid 7416.
zloty:~:# ps -auxwwww | grep mysqld
mysql 7387 0.0 0.0 1660 1260 p1 I 8:57AM 0:00.01 /bin/sh /usr/local/bin/mysqld_safe --defaults-extra-file=/store/mysql-z-master/my.cnf --user=mysql --datadir=/store/mysql-z-master --pid-file=/store/mysql-z-master/zloty.hosted-at.thebunker.net.pid
mysql 7416 0.0 8.0 1925400 271848 p1 S 8:57AM 0:01.36 /usr/local/libexec/mysqld --defaults-extra-file=/store/mysql-z-master/my.cnf --basedir=/usr/local --datadir=/store/mysql-z-master --user=mysql --pid-file=/store/mysql-z-master/zloty.hosted-at.thebunker.net.pid --open-files-limit=8192 --port=3306 --socket=/tmp/mysql.sock
root 7468 0.0 0.0 1424 888 p1 RL+ 9:01AM 0:00.00 grep mysqld
Is this expected behaviour? Am I correct in my supposition that
effect occurs because of the large process size -- as I said above, I
don't see this at all with smaller mysql installations, where the rcNG
scripts work independently of /proc being mounted. Is it documented
anywhere? All I can find is the mention in the ps(1) man page that
/proc has to be mounted to get full functionality.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor
School Rd
PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone
Tel: +44 1304 617253 Kent, CT14 0JL UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050928/d7c95b4d/attachment-0001.bin
------------------------------
Message: 29
Date: Wed, 28 Sep 2005 18:43:55 +1000
From: Peter Jeremy <Peter...@optushome.com.au>
Subject: Re: HEADSUP: bridge(4) removed from HEAD
To: "Simon L. Nielsen" <si...@freebsd.org>
Cc: Max Laier <m...@love2party.net>, Maxim....@portaone.com,
freebsd...@freebsd.org, freebsd...@freebsd.org
Message-ID: <20050928084...@cirb503493.alcatel.com.au>
Content-Type: text/plain; charset=us-ascii
On Wed, 2005-Sep-28 08:13:32 +0200, Simon L. Nielsen wrote:
>Considering that we only (more or less) document -STABLE branches in
>the Handbook it's not a big rush, as long as it's mentioned before 7.0
>comes out, though documentation about if_bridge in the Handbook would
>of cause be nice, considering it's also in 6.0 :-).
bridge(4) no longer exists in -current and is (effectively) deprecated
in 6.x. It is desirable that this is documented in the handbook and
the filtering bridges article.
I though that the Project guidelines stated that deprecated features
had to be retained for a full major release but having checked the
Committers' Guide, it's only required that they be retained until the
next major release. This means that it's not essential that the
handbook be updated before 6.0-RELEASE but it is desirable that the
updates occur early in the 6.x-STABLE cycle to provide adequate notice.
There's no reason why the handbook can't mention both (or, preferably,
all three) bridging devices - it just needs to mention that if_bridge
doesn't exist in 5.x
--
Peter Jeremy
------------------------------
End of freebsd-stable Digest, Vol 129, Issue 4
**********************************************