On Tue, Jul 26, 2011 at 04:25:38PM +0200, Jerome Herman wrote:
> On 26/07/2011 15:16, Jeremy Chadwick wrote:
> >On Tue, Jul 26, 2011 at 02:50:28PM +0200, Jerome Herman wrote:
> >>[very large snip]
> >>
> >>So here I am starting to think that my disklabel and fsc
a
non-VGA-adapter in their PCIe x16 slot. Some Supermicro boards do have
PCIe x16 slots that can be used by non-VGA adapters, but I haven't seen
this on, say, Asus/Gigabyte/Dell/Intel motherboards.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networ
On Wed, Jul 27, 2011 at 10:38:36AM +0100, Tom Evans wrote:
> On Tue, Jul 26, 2011 at 11:55 PM, Jeremy Chadwick
> wrote:
> >
> > And before someone asks: in most cases you *cannot* use this card in a
> > PCIe x16 connector on a motherboard. ??Most generic motherboard
&
On Thu, Jul 28, 2011 at 02:31:20AM +1000, Jan Mikkelsen wrote:
> On 27/07/2011, at 8:12 PM, Jeremy Chadwick wrote:
>
> > On Wed, Jul 27, 2011 at 10:38:36AM +0100, Tom Evans wrote:
> >> On Tue, Jul 26, 2011 at 11:55 PM, Jeremy Chadwick
> >> wrote:
> >>&g
e/2011-July/thread.html
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, US |
| Making life hard for others since 1977.
ug mode
and/or verbose mode.
5) Why do you need to rotate logs every 5 minutes? Why do you need such
extreme levels of granularity in your rotated logs? Just how much data
are you logging via syslog? If a lot, why so much? It might be more
effective to consider expanding your logging infrastruct
ith -lvcb and include only the Intel NIC (em0).
Also please provide output from command "sysctl dev.em.0".
Thanks.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX System
avoid this
problem regardless of what filesystem is used? I just don't get it.
[1]: Applies to any filesystem, not just ZFS. There was a UFS one a
month or two ago too...
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking
On Tue, Aug 02, 2011 at 10:16:35AM +0100, seanr...@gmail.com wrote:
> On Tue, Aug 2, 2011 at 10:08 AM, Jeremy Chadwick
> wrote:
> > On Tue, Aug 02, 2011 at 08:39:03AM +0100, seanr...@gmail.com wrote:
> >> On my FreeBSD 8.2-S machine (built circa 12th June), I created
w much ARC uses, some ARC stats.
>
> Which sysctl's would you like?
Output from "sysctl vfs.zfs kstat.zfs" would be sufficient.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
|
it in Compatible mode (which makes SATA devices appear as classic PATA).
Alexander (mav@) should act as a more authoritative source for this.
However, I can tell you up front that booting verbose is your best
choice of option here, as it gives significant controller status/state
debug informa
t
into a 32GB swap slice?
I think what folks are saying is that if you use multiple swap slices
(e.g. two of 32GB each), you can achieve what you need.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.c
On Wed, Aug 10, 2011 at 08:27:27AM +, Holger Kipp wrote:
>
> Am 10.08.2011 um 10:09 schrieb Daniel Kalchev:
>
> > On 10.08.11 10:47, Jeremy Chadwick wrote:
> >> On Wed, Aug 10, 2011 at 10:13:14AM +0300, Daniel Kalchev wrote:
> >>> I am more concerned that
On Wed, Aug 10, 2011 at 01:42:11PM +0300, Daniel Kalchev wrote:
>
>
> On 10.08.11 11:47, Jeremy Chadwick wrote:
> >So we're back to where we started: swap slices/partitions can be
> >greater than 32GBytes in size, but "something" is limiting the
> >maxim
# Support DDB
options GDB # Support remote GDB
In combination with this, we use the following in /etc/rc.conf (the
dumpdev line is important, else savecore won't pick up anything):
dumpdev="auto"
ddb_enable="yes"
mpdev="NO" is the default, not "auto", since
on a system with no swap devices in /etc/fstab dumpdev="auto" should
behave the same. Possibly the idea of the default is to ensure that
savecore(8) never gets run (e.g. there's no guarantee someone has
/var/crash, or a /
On Wed, Aug 10, 2011 at 05:26:27PM +0100, Steven Hartland wrote:
> - Original Message - From: "Jeremy Chadwick"
> free...@jdc.parodius.com
>
> >>>In combination with this, we use the following in /etc/rc.conf (the
> >>>dumpdev line is impo
(But why has it changed...?)
On all our RELENG_8 systems (though I use bash), -tostop is default.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator
ot; from August 2009 is not
necessarily the same thing as "SKU ABCXYZ-1" from May 2010. ;-) This
is also why I prefer to buy/build my own systems, since I cannot trust
vendors to not mess about with settings w/out changing SKUs, P/Ns, or
revision numbers.
--
| Jeremy Chadwick
ars ago -- still
seems valid) and just how badly they can "wedge" a system. This is one
of the many (MANY!) reasons why we use rsnapshot/rsync instead. The
atime clobbering issue is the only downside.
I don't see what this has to do with "heavy WAN I/O" unless
On Wed, Aug 17, 2011 at 05:01:05PM -0700, Chip Camden wrote:
> Quoth Jeremy Chadwick on Wednesday, 17 August 2011:
> > >
> > > I'm also getting similar panics on 8.2-STABLE. Locks up everything and I
> > > have to power off. Once, I happened to be looking at
ith existing and legacy OSes.
I'm dreading the day the WD Caviar Black models succumb to all this
nonsense.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator
de, however, has been (since
8.2-RELEASE for sure). I think em(4) has as well. This may end up
being a case where running RELENG_8 is the fix, but I'd love to be able
to say that for certain.
"bt full" would be helpful but the above indicates the kernel might not
have debugging
is time and time again for folks on forums with
varying success.
I've also found some models of drives which claim there's suspect LBAs
yet an internal surface scan passes with no issues (and these are drives
which I myself have, the only difference between my drives and the
individuals&#x
I can accept that. If I have a drive that's been
in operation for 48 hours and it has 30 errors, that drive is getting
RMA'd.
When I get new or RMA'd/refurbished drives, I test them before putting
them to use. I do a read-only surface scan using SMART ("smartctl -t
select,0-max /
On Fri, Aug 19, 2011 at 09:39:17PM -0400, Dan Langille wrote:
>
> On Aug 19, 2011, at 7:21 PM, Jeremy Chadwick wrote:
>
> > On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote:
> >> System in question: FreeBSD 8.2-STABLE #3: Thu Mar 3 04:52:04 GMT 2011
> &g
e data
smartd gives you for it to be useful.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, US |
| Making life hard for ot
Dan, I will respond to your reply sometime tomorrow. I do not have time
to review the Email today (~7.7KBytes), but will have time tomorrow.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX
test and report LBAs
it couldn't read, but as I said, it's rare and varies from vendor to
vendor, drive to drive, and firmware to firmware. When it happened I
was very, very surprised (and delighted).
The only thing I can trust 100% of the time when it comes to surface
scans is SMART selecti
wrote:
> On Aug 19, 2011, at 11:24 PM, Jeremy Chadwick wrote:
> > The SMART error log also indicates an LBA failure at the 26000 hour mark
> > (which is 16 hours prior to when you did smartctl -a /dev/ad2). Whether
> > that LBA is the remapped one or the suspect one is unknown. Th
se what we're seeing is
just a batch of LBAs in a small region that are getting worse the more
they're read from (possible).
No idea if LBA 5566440 and LBA 786767 are anywhere near one another on
the physical media. I don't have a way to determine that (way too
complex).
T
On Sun, Aug 21, 2011 at 02:00:33AM -0700, per...@pluto.rain.com wrote:
> Jeremy Chadwick wrote:
>
> > ... using dd to find the bad LBAs is the only choice he has.
>
> or sysutils/diskcheckd. It uses a 64KB blocksize, falling back to
> 512 -- to identify the bad LBA(
y with uart(4). Does stty(4) throw up
> "isn't a terminal" errors against the .init and .lock devices
> relating to those ports? I would try this myself, but am very short
> of time at present.
>
>
> Though there is probably little more that I can add, please keep
rebuilding the
**kernel** would not solve anything. You would need to build world.
But again, there is no WITH_LIB32. If you build world on amd64 it will,
by default, attempt to build 32-bit versions of libraries so that you
can compile i386 binaries on amd64.
The kernel shims for 32-bi
t "sleep" and "standby" are two very
different things (they're separate ATA commands too). So if you're
using "camcontrol sleep" you probably should be using "camcontrol
standby". The man page is quite clear about the repercussions of the
former
On Tue, Aug 30, 2011 at 04:10:13PM -0700, Kevin Oberman wrote:
> On Tue, Aug 30, 2011 at 2:48 PM, Jeremy Chadwick
> wrote:
> > On Tue, Aug 30, 2011 at 01:29:02PM -0400, David Magda wrote:
> >> On Tue, August 30, 2011 11:50, Kevin Oberman wrote:
> >> [...]
> >&
On Tue, Aug 30, 2011 at 11:04:43PM -0700, Kevin Oberman wrote:
> >> On Tue, Aug 30, 2011 at 2:48 PM, Jeremy Chadwick
> >> wrote:
> > instead use UFS2 and see if the problem disappears? ?This is in no way a
> > permanent solution. ?If this workaround fixes the pro
On Wed, Sep 07, 2011 at 03:45:34PM +0700, Eugene Grosbein wrote:
> 01.08.2011 00:31, Jeremy Chadwick ?:
> > On Sun, Jul 31, 2011 at 11:51:40PM +0700, Eugene Grosbein wrote:
> >> Hi!
> >>
> >> Suppose, there is a machine which writes two kinds of log files
freebsd.org/pipermail/freebsd-stable/2011-September/063821.html
http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063823.html
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Admi
enoted in the man page?
I'm actually very surprised to hear there's an official FreeBSD driver
on Adaptec's site that's actually intended for FreeBSD 8.x. Last I knew
they had basically blown off FreeBSD support. I wonder who at Adaptec
is responsible
means starts behaving oddly. There is confirmed evidence
of this happening -- it doesn't affect "PATH problems" (for lack of
better phrasing; I hope folks know what I mean by this, I'm not implying
one's dot-files are wrong, etc.), but it does show up as files
(such as the need to
rm -fr /usr/share/man/* before doing the installworld phase, else you
can end up with stale man/catman pages), but the existing method works
reliably.
So what part of the picture am I missing? :-)
--
| Jeremy Chadwickjdc at parodius.com |
|
n't compatible, ruby shims, and other crap = not
worth it. Think the database ordeal is long over with/fixed/whatever?
It isn't[2].
[1]: http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/063052.html
[2]: http://www.dslreports.com/forum/r26304856-FreeBSD-defining-po
On Sun, Sep 18, 2011 at 08:47:13AM +0200, Ronald Klop wrote:
> On Sun, 18 Sep 2011 07:39:01 +0200, Jeremy Chadwick
> wrote:
>
> >On Sun, Sep 18, 2011 at 12:54:13AM -0400, Jason Hellenthal wrote:
> >>On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
> >
d to set up serial
console (both BIOS-level and bootloader-level) for remote debugging
capability. Jack, John, or someone familiar with kernel debugging is
probably going to need to get access to a machine which is experiencing
this problem so they can figure out what's going on.
The tri
---
> E1000_WRITE_REG(&adapter->hw, E1000_EIMC, que->eims);
> ++que->irqs;
>
> + if (!(adapter->ifp->if_drv_flags & IFF_DRV_RUNNING)) {
> + return;
> + }
> +
> + more_rx = igb_rxeof(que, adapter->r
guess: it's probably a revision of card that 8.1 did not
have proper code for.
As such, I would strongly suggest running 8.2. If the card doesn't
function correctly in 8.2, there are folks here on the mailing list who
can help with that.
--
| Jeremy Chadwick
On Sat, Sep 24, 2011 at 08:44:20AM -0300, Nenhum_de_Nos wrote:
>
> On Sat, September 24, 2011 08:12, Jeremy Chadwick wrote:
> > On Sat, Sep 24, 2011 at 05:56:00PM +0700, Eugene Grosbein wrote:
> >> > I have a box using this Realtek nic:
> >> >
> &g
e. For example *I* have no idea what
FreeBSD version they use, what custom modifications they have in place,
etc.. I follow FreeBSD, I don't follow pfSense. :-)
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.paro
? /data
>
> What should i look for to resolve it?
What version of FreeBSD exactly, and what build date?
Please provide output from "procstat -k -k 1666" (yes, two -k's).
--
| Jeremy Chadwickjdc at parodius.c
ars has been that truss on FreeBSD is extremely
buggy and cannot be relied upon (case in point). Such is still the case
on RELENG_8 as of today.
Use ktrace(1) instead. You'll find it to work pretty much in every
situation.
--
| Jeremy Chadwickjdc at parodiu
: service??? mi_switch+0x176
> sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 _cv_timedwait_sig+0x11d
> svc_run_internal+0x939 svc_thread_start+0xb fork_exit+0x114
> fork_trampoline+0xe
> ?1666 100446 nfsd nfsd: service??? mi_switch+0x176
> sleepq_catch_signals+0
On Tue, Sep 27, 2011 at 05:41:57AM -0700, Kirill Yelizarov wrote:
> From: Jeremy Chadwick
> To: Kirill Yelizarov
> Cc: rmack...@uoguelph.ca; freebsd-stable@freebsd.org
> Sent: Tuesday, September 27, 2011 3:59 PM
> Subject: Re: NFSD hang
>
> On Tue, Sep 27, 2011 at 04:
On Tue, Sep 27, 2011 at 09:28:56AM -0400, Mark Saad wrote:
> On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis wrote:
> > On 9/27/2011 1:10 PM, Jeremy Chadwick wrote:
> >>
> >> kill -9 your truss processes; the underlying processes which you are
> >> truss&#x
G **: getpwuid_r(): failed due
> to unknown user id (2139)
> ...
> I haven't explored the getpwuid_r thing.
Running "id 2139" should return something other than "no such user". If
not, your environment is looking up something that has such ownership.
I don
usr/obj/usr/src/sys/GENERIC amd64
>
> I did a make update and then compiled and installed, which took about 40
> minutes. The update was triggered by seeing the security fixes on the
> RSS feed.
>
> I can grab new sources and reinstall if you think it's worth it.
Did you
On Thu, Sep 29, 2011 at 02:40:09PM -0700, Ted Faber wrote:
> On Thu, Sep 29, 2011 at 01:05:40PM -0700, Jeremy Chadwick wrote:
> > On Thu, Sep 29, 2011 at 12:50:01PM -0700, Ted Faber wrote:
> > > (npviewer.bin:5430): GLib-WARNING **: getpwuid_r(): failed due
> > >
nt FreeBSD
> > version (of your branch), as in "with the recent security fixes"?
> > There are reports that one of them may have caused what you see.
> >
> > Bye,
> > Alexander.
> >
>
> Hi list,
>
> it seems that
> http://securit
e delays always 3 seconds? If so, that almost sounds like a
timeout of some kind. That's the thing about the kevent() call: I wish
I could see what's in the timespec struct, since that's what defines the
timeout values.
--
| Jeremy Chadwickjdc at paro
ive would be for me to make a CGI version where you could
just go my site and paste in the FreeBSD MCE and it would siphon it
through mcelog and give you the output.
Anyway now I'm rambling, but there ya go.
--
| Jeremy Chadwickjdc at parodius.com |
| Paro
the lookups.
> >
> >
> > Doug
> >
>
> Check your bind/unbound logs to ensure the queries are actually
> successful on their first try.
>
> Is your DNS using forwarders ? views ?
How would this explain 100% quick/reliable lookups when done from tool
On Sun, Oct 02, 2011 at 09:37:43AM +0200, Thomas Zander wrote:
> On Sat, Oct 1, 2011 at 12:23, Jeremy Chadwick
> wrote:
>
> > So what should you do? ?Replace the RAM. ?Which DIMM? ?Sadly I don't
> > know how to determine that. ?Some system BIOSes (particularly on AMD
, you're out of luck. It's extremely hit-or-miss
on FreeBSD (mostly miss).
The only alternative is to use pf(4) to block inbound IPv6 packets to
port 123. This won't stop ntpd from talking to IPv6 peers, but would
stop people from talking to it, if that's what you're tr
4
1428 root1 440 11900K 2860K select 0 0:17 0.00%
/usr/sbin/ntpd -c /conf/ME/ntp.conf -p /var/run/ntpd.pid -f
And "route -n monitor" shows no anomalies here.
Maybe you should tcpdump to find out if there is a client or peer which
is constantly pounding ntpd
On Wed, Oct 05, 2011 at 11:45:52PM +0100, Steven Hartland wrote:
> - Original Message - From: "Jeremy Chadwick"
>
>
> >1428 root1 440 11900K 2860K select 0 0:17 0.00%
> >/usr/sbin/ntpd -c /conf/ME/ntp.conf -p /var/run/ntpd.pid -f
> &g
behind", given that they only sync
with cvsup-master every so often. What's "every so often?" It varies
from public cvsup server to public cvsup server, and there's no way to
know. Great isn't it?
If you are syncing directly off of cvsup-master -- shame on yo
On Sat, Oct 08, 2011 at 10:29:19AM +0100, Chris Rees wrote:
> On 8 October 2011 03:25, Jeremy Chadwick wrote:
> > On Fri, Oct 07, 2011 at 02:36:25PM -0400, Aryeh Friedman wrote:
> >> Just a quick note the repo was synced about 15 mins before this
> >>
> >> O
AM, Chris Rees wrote:
>
> > On 8 October 2011 03:25, Jeremy Chadwick wrote:
> > > On Fri, Oct 07, 2011 at 02:36:25PM -0400, Aryeh Friedman wrote:
> > >> Just a quick note the repo was synced about 15 mins before this
> > >>
> > >> On Fri,
n the system? Be
sure to note if softupdates are in use or not too.
* Has this system crashed recently or even many months ago?
* If so, did you run fsck manually from single-user rather than rely
on background fsck? (There are confirmed cases of background fsck
not fixing everything)
* I
filesystem type, eh? Good thing I asked what your underlying
filesystem types were. Don't ever think that "it'll all just work".
:-)
I believe there are other issues/stipulations with nullfs (some have
been reported over the years), so I'm not too surprised by this
sr/obj/usr/src/sys/BORG-DTRACE amd64
> $
Can you please provide output from the following commands executed on
the machine showing the problem? The above commands show nothing
useful, other than the fact that one machine is at 100/full and the
other is at 1000/full (I don't know your netwo
t/net/NET-74-125-0-0-1
>
> Considering that Firefox by default will open up the Firefox Google page, I
> don't find this surprising at all.
More useful details:
http://www.google.com/support/bin/answer.py?hl=en&answer=174717
http://www.pcmech.com/article/the-my
by lsof -i
They aren't strange. Please see my explanation references:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064219.html
This has absolutely nothing to do with FreeBSD.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Netw
for that port
will remain the same after N years passed? Or that there aren't others
added/removed by then?
I do see the justification in what you want, however.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.
:)
>
> Anyway I found a "Rehook INT 19: disabled" setup option which, I
> think, simply disables legacy BIOS booting. I'll give it a try in
> the evening.
It's more likely that it provides the interrupt hook to getting a RAID
controller to boot from one o
x27;s functional.
Give it a try for yourself and see if it suffices.
[1]: The committer changed a bunch of things which were labelled "minor"
yet bother me enough that I'm forcing the OCD part of me to let them
slide.
--
| Jeremy Chadwickjdc at parodius
On Tue, Oct 18, 2011 at 06:26:49PM +1030, Daniel O'Connor wrote:
> On 18/10/2011, at 17:49, Jeremy Chadwick wrote:
> >> That would be absolutely helpful! After all, FreeBSD is primarily a
> >> server OS, and where would one have ECC if not on servers. Being able
> >
On Tue, Oct 18, 2011 at 11:31:37PM +1030, Daniel O'Connor wrote:
>
> On 18/10/2011, at 22:03, Jeremy Chadwick wrote:
> >> It would be _super_ neat if the mcelog port installed a devd rule which
> >> emailed root@ with the human readable version of an MCA exception
too given
the path change.
Worse, certain modules like either eAccelerator or ZendOptimizer (I forget
which of the two) make the downright assumption that they are in use on
a PHP system where debugging is not enabled, thus do not behave quite
right when placed there.
Having fun yet?
--
| Jere
rs,
If you guys can't get a good development environment going for
YongHyeon, let me know and I can invest in one of these motherboards and
either send it to YongHyeon (back in South Korea?) or I can set it up
locally and get him serial console access to boot.
Just let me know if all o
Finally, you can try disabling the "Onboard USB 3.0 Controller" to see
if somehow that's causing problems (especially if you have a USB-based
storage drive (Flash, etc.) hooked up at the time -- that might appear
as a bootable device to the bootloader).
All of this i
.
4) If replacing the Netgear product doesn't help, then your next step is
to replace the 3Com NIC with something newer. Intel makes many
PCI-based 100mbit and 1000mbit NICs that work wonderfully on FreeBSD via
the em(4) driver. They are affordable and reliable.
5) The xl(4) driver is extre
rrier
This is on RELENG_8 dated 2011/09/28.
If you want me to test it on my em0 interface (which is what actually has
an IP configured, etc.) and do a full reboot, I can do that. Let me
know.
So there may have been some rc.d framework changes that address your
problem. Are you running -RELEASE
On Sat, Oct 22, 2011 at 05:55:28AM -0700, Jeremy Chadwick wrote:
> On Sat, Oct 22, 2011 at 02:11:17PM +0200, sth...@nethelp.no wrote:
> > FreeBSD 8.x (well, at least 8.2) has the very nice feature of letting
> > you set an interface *description* (just like you can on any Jun
the time of FreeBSD 7.x.
The problem is that the networking layer is not TRULY available by the
time ntpd starts. This does have to do with NIC drivers, but the same
behaviour can be seen on all NICs, including excellent ones like em(4).
You can use the rc.conf netwa
On Tue, Oct 25, 2011 at 12:36:56AM +0100, Steven Hartland wrote:
> - Original Message - From: "Jeremy Chadwick"
>
>
> >The problem is that the networking layer is not TRULY available by the
> >time ntpd starts. This does have to do with NIC drivers, but th
On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote:
> On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
> > The one shortcoming of netwait is that it doesn't support waiting for
> > multiple NICs. Some people have dual-homed environments where t
> need to break into the loader and type..
> unload
> boot -s
> (or whatever options you want)
Yup, correct. The person who said "single-user mode doesn't read
loader.conf!" is absolutely incorrect.
--
| Jeremy Chadwickjdc at parodius.com
.html
>
> These may not be the same problem, but I think they are related (a not so well
> documented change in the kerm interface).
You want atapicam(4). This is not the same thing as "options ATA_CAM".
See /sys/conf/NOTES.
Whether or not it works with audio CDs is unknown to m
query the card using mfiutil, I currently have a cron
> doing this every 2 minutes to see if this has been coincidence or not.
>
>
> Any suggestions welcome and i'm happy to provide more info if i can but
> I dont have a duplicate to do too much debugging on, I'm ha
g/message/ch6w5gwne7rfzfz5
On "older" FreeBSD, failure to include these directives will result in
completely broken TCP socket behaviour:
http://permalink.gmane.org/gmane.os.freebsd.devel.pf4freebsd/3990
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking
rson's system.
Please run "gdb /usr/local/sbin/smartctl smartctl.core" and provide here
the function call stack. This will help determine if it's a bug in
smartctl or something FreeBSD-related. If it's a smartmontools problem,
you will need to report the bug to them direc
#28 0x in ?? ()
>#29 0x in ?? ()
>#30 0x in ?? ()
>#31 0x in ?? ()
>#32 0x in ?? ()
>#33 0x in ?? ()
>#34 0x0000 in ?? ()
>---Type
Forwarding my reply to Frank to the list, because he did not
reply-to-all when sending me the below mail.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator
Sending original copy to the list.
- Forwarded message from Frank Razenberg -
> From: Frank Razenberg
> To: Jeremy Chadwick
> Date: Thu, 03 Nov 2011 01:16:17 +0100
> Subject: Re: smartctl / mpt on 9.0-RC1
>
> Sorry, yes, there's actually a lot more, but there&
> segfaults.
I'm glad this patch fixes things for people, but does anyone have
insights to why the calling stack gets horribly corrupted on a segfault,
even with WITH_DEBUG (no optimisations and uses -g)? It makes
troubleshooting this kind of problem extremely diff
(sort of).
$ ls -ld /usr/share/locale/de_DE*
drwxr-xr-x2 root wheel 512 Sep 28 14:36
/usr/share/locale/de_DE.ISO8859-1/
drwxr-xr-x2 root wheel 512 Sep 28 14:36
/usr/share/locale/de_DE.ISO8859-15/
drwxr-xr-x2 root wheel 512 Sep 28 14:36
/usr/share/locale/de_
On Fri, Nov 04, 2011 at 07:49:52AM +0100, O. Hartmann wrote:
> Am 11/03/11 23:48, schrieb Jeremy Chadwick:
> > On Thu, Nov 03, 2011 at 11:17:08PM +0100, O. Hartmann wrote:
> >> Hello.
> >> I realised something weird in FreeBSD 10.-CURRENT/amd64 (CLANG
> >
0 499696 0
81665 0 500266 0
9 1666 0 499696 0
101666 0 500266 0
111667 0 499696 0
121667 0 500266 0
131668 0 473104 0
141668 0 473674 0
151668 0 4996
o boot into a Linux LiveCD and
install smartmontools (in RAM) and see if it provides the data.
My point: don't be so quick to assume smartmontools is responsible when
there are 4 (maybe even 5) "layers" to how SCSI I/O makes it to the
actual drive. This is one of the many reaso
201 - 300 of 2090 matches
Mail list logo
