Hello!
I wanted to take an old laptop with me for a trip, but decided to update
the OS on it (it was running 8.1).
Long story short, both 11.2 and 12.0 panic on boot... I can boot 8.2 via
pxeboot (dmesg attached) off of my server, which is neat, but that's it.
When it crashes -- and it
Hello!
Last night I was trying to get KDE5 to start up on my new machine, and a
couple of KDE's processes kept crashing, dumping cores like the one below:
-rw--- 1 mi wheel 45780992 Jul 23 22:28 ksplashqml.core
After, maybe, 10 such rounds -- each generating two core-dump -- ZFS
On 12.08.2017 19:16, Michael Tuexen wrote:
Just my luck -- deciding to update to the latest 10.x today...
sys/netinet/tcp_syncache.c:280:50: error: implicit conversion from 'long long'
to 'time_t' (aka 'int') changes value from -9223372036854775808 to 0
[-Werror,-Wconstant-conversion]
Just my luck -- deciding to update to the latest 10.x today...
sys/netinet/tcp_syncache.c:280:50: error: implicit conversion from 'long
long' to 'time_t' (aka 'int') changes value from -9223372036854775808 to
0 [-Werror,-Wconstant-conversion]
V_tcp_syncache.hashbase[i].sch_last_overflow =
On 08.06.2016 18:24, Mark Johnston wrote:
>> Is it yet to recover from the "out of swap" situation? I'm sure, a
>> > reboot will fix everything, but I expected FreeBSD to be better than
>> > that... Running 10.3-stable from April 18 here. Thanks!
> There was a memory leak in CAM at that point.
In my absence my desktop managed to run out of memory and had to kill a
number of processes:
pid 47493 (firefox), uid 105, was killed: out of swap space
pid 1665 (thunderbird), uid 105, was killed: out of swap space
pid 975 (kdeinit4), uid 105, was killed: out of swap space
pid 1344
Hello!
I have an older Dell laptop with an SSD-drive (LITEONIT LCT-256M3S-41 7mm 256GB
FDE SRDB). I installed 10.3-RC2 on it and then used ``tunefs -t enable’’ to
turn trimming on for all of the filesystems on the drive (/, /home, and /var).
Things work, but every once in a while kernel logs
I was copying /home from an old server (narawntapu) to a new one
(aldan). The narawntapu:/home is mounted on aldan as /mnt with flags
ro,intr. On narawntapu /home was simply located on an SSD, but on aldan
I created a ZFS filesystem for it.
The copying was started thus:
root@aldan:/home
On 28.11.2015 17:41, Jilles Tjoelker wrote:
> Although cp -R will normally copy a fifo by calling mkfifo at the
> destination, it may open one if a regular file is replaced with a fifo
> between the time it reads the directory and it copies that file.
The sole fifo under /home here was
All my drives here are using ahci and the currently-used 9.2-PRERELEASE
kernel sees them thus:
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada3 at ahcich4 bus 0 scbus4 target 0 lun 0
I'm
Hello!
I'm seeing a strange problem with clang-compiled binaries on 9.x/i386
system. Here it is: if a shared library A needs a symbol provided by a
shared library B, libA will fail to load into a process even if the
executable is linked with libB. The only fix (work-around?) is to relink
10/14/13 4:31 PM, Dimitry Andric ???(??):
There is a problem when clang does tail-call optimization on i386 with
PIC in effect, and it emits GOT relocations for the tail-called
functions, instead of PLT relocations. In some scenarios, such as with
the way X.org does lazy dynamic linking,
Hello!
I have my FreeBSD-server dump nightly backups onto an entertainment device
running embedded Linux.
The device has no NFS-server, but does run Samba (3.0.30). It allows access to
its internal hard-drive, which my server mounts as:
//dune/hdd750_..._32 /dune smbfs
15.02.2013 08:49, John Baldwin ???(??):
Were you able to test this patch?
Yes, with the patch my laptop boots -- even after I removed the
work-around (hint.ichss.0.disabled=1 from device.hints). powerd is
also able to regulate the frequency -- I'm not sure, how else to test
the functionality.
20.02.2013 15:41, Peter Jeremy ???(??):
You left out:
4. Code relies on language features that are not supported by the compiler.
(It's not a bug that gcc 4.2.1 (eg) doesn't suppert C++11)
If a compiler does not support a feature, it is supposed to error-out
upon encountering it, not
18.02.2013 15:26, Chris Rees ???(??):
I'm sure you understand that our compiler in base is rather elderly,
and that a project as insanely huge as Libreoffice is going to be
highly sensitive to minute changes.
No, Chris... I do not understand this wonderfully PR-esque response.
See, my
On 19.02.2013 09:45, Chris Rees wrote:
a. The code is buggy.
b. The compiler is buggy.
c.Both of the above.
My question was, which is it?
My answer is that it is almost certainly (b).
Are there identified, known problems with the version? From what little I've
heard, our cc had some
On 19.02.2013 12:23, Adrian Chadd wrote:
I bet *office just uses a bunch of either horrible syntax that breaks
things, or newer C/C++ features that are buggy in older compilers.
Well, yes, this is, what I wanted to find out -- which case is it. There was a
point, when we had a special
On 19.02.2013 13:19, Ian Lepore wrote:
All strike me as being complaints, but if that seems like a
mis-characterization to you, then I apologize.
These were, indeed, complaints, but not about the port not working after I
broke it. My complaint is that, though the port works out of the box, the
On 19.02.2013 14:15, Jung-uk Kim wrote:
What do we go from here? I don't know. One thing I know for sure is
we cannot support every possible build/runtime environment.
Feel free to suggest your ideas and thoughts.
Well, support for every possible combination is, of course, a toll order, but
On 19.02.2013 14:45, Jung-uk Kim wrote:
Actually, I tried very hard to build sane LO with gcc 4.2 but it
wasn't fruitful. Eventually, I gave up on adding kludges after
kludges because LO is moving away from pre-C++11 compilers anyway.:-(
Should not a pre-C++11 compiler simply /fail/ upon
On 19.02.2013 14:54, Jeremy Chadwick wrote:
Licensing zealotism benefits no user, but I can
see it benefiting certain companies whose commercial products are
reliant on FreeBSD. So out with it already.
But support from (and even mere adoption by) large companies benefits FreeBSD in
a number of
19.02.2013 17:30, Jung-uk Kim ???(??):
I really love to build LO with GCC 4.2, too. I really do. However, I
don't see much point of mentioning that fact in PR.
You mentioned earlier, that you believe there were plenty PRs already.
Are the patches contained in them currently in the port's
Hello!
I just finished building editors/libreoffice with gcc-4.2.1 -- had to
edit the port's Makefile to prevent it from picking a different
compiler. Everything built and installed, but libreoffice dies on
start-up (right after flashing the splash-window):
(gdb) where
#0
On 07.02.2013 13:16, John Baldwin wrote:
Can you get pciconf -lc output?
Here:
hostb0@pci0:0:0:0: class=0x06 card=0x
chip=0x11308086 rev=0x02 hdr=0x00
cap 09[88] = vendor (length 4) Intel cap 15 version 1
cap 02[a0] = AGP 4x 2x 1x SBA disabled
On 06.02.2013 02:13, YongHyeon PYUN wrote:
Disabling Wake on LAN in the BIOS solved this problem. Now xl0 is seen
and functional. Solved.
Because I added WOL support xl(4) in the past I'm interested in
knowing whether that change broke your controller when BIOS enables
WOL.
I can not reproduce
Hello!
I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it).
FreeBSD 6.3-STABLE was running fine on it, but I decided to update the
machine to 9.1-STABLE.
Well, neither my own custom kernel, nor even the official 9.1-RELEASE
CD1 would boot... In both cases the boot process runs
On 05.02.2013 23:50, Erich Dollansky wrote:
USB?
That would be a shame -- I'm dressing up this old machine to be used
with a couple of USB-devices.
I have had a Fujitsu LifeBook which I only could use with 7.x out for
the same reason.
Is there a PR? Thanks,
-mi
On 05.02.2013 23:38, Mikhail T. wrote:
What happened between 6.x and 7.x?
Ok, what happened is that device cpufreq is now in GENERIC and the
ichss0 along with it.
Setting
set hint.ichss.0.disabled=1
on the loader prompt allows me to boot -- both my own kernel as well as
the 9.1-RELEASE
On 06.02.2013 01:24, Mikhail T. wrote:
Now, if only I could figure out, why my network card (3COM's 3C556
Mini PCI) is not seen by the 9.1...
Disabling Wake on LAN in the BIOS solved this problem. Now xl0 is seen
and functional. Solved.
I struggle to understand, how a less seasoned user could
On 06.02.2013 01:57, Erich Dollansky wrote:
I have had a Fujitsu LifeBook which I only could use with 7.x out
for the same reason.
Is there a PR? Thanks,
No. I did not want to bother people for such an old device.
You should have. If it is listed as supported, it should be working.
And
On 23.12.2012 11:48, Chris Rees wrote:
They involve a lot of thought to get right, as well as chmod g-w on
something where you probably meant chmod go-w is a disastrous but
(perhaps) common error. Chris
Well, in (over 20) years of dealing with Unix, I've never made a mistake
like that, nor
On 23.12.2012 03:05, Charlie Root wrote:
Checking negative group permissions:
8903027 -rw--w-r-- 1 miwww794277 Oct 23 07:47:45 2007
/home/mi/public_html/syb/order/download.log
Hello!
The above started to appear in the daily security run output after I
upgraded to 9.1. I don't
Hello!
I've set up several nightly backups all using the pipe-chain of dump |
xz -9 | ccrypt /remote/backups/fs.xz.cpt
On one system these just work every night without a problem. On another
I see xz SEGFAULT-ing about 90% through almost every night for one of
the filesystems (the bigger
On 22.12.2012 11:39, Adrian Chadd wrote:
Is it dumping core?
Yes, and, as I type this, I'm trying to reproduce the crash using the
version of liblzma.so.5 compiled with -O0 -g (under valgrind). So far
(25%) everything is clean and valgrind has no complaints either.
Yours,
-mi
Following
On FreeBSD/amd64 8.2-STABLE as of Sun Feb 27. I dismissed this problem the first
time (a week or two ago), but just saw it again. Something triggers syslogd into
spinning all available CPU -- while not logging anything.
Attempts to log anything -- such as by invoking logger(1) -- simply hang.
My laptop's kernel config file reads:
device wlan# 802.11 support
device ath
device ath_ar5212
device ath_rate_onoe
Config raises no objections and the compilation succeeds, but linking
the kernel breaks:
...
linking
On 8/25/2010 8:27 AM, John Baldwin wrote:
You are missing:
options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors
But I don't have the ar5416 chipset... Mine is AR2312... And it is an
option, so should not it be optional? Anyway, I tried adding that option
and the error is
23.08.2010 08:17, John Baldwin написав(ла):
With some trickery (had to define: WITHOUT_CDDL, WITHOUT_SSP, WITH_GCC3,
NO_WERROR) I upgraded my laptop directly from 6.3 to 8.1-STABLE. It now
boots nicely.
I'd like to make another round of buildworld/buildkernel -- using the
existing
Hello!
With some trickery (had to define: WITHOUT_CDDL, WITHOUT_SSP, WITH_GCC3,
NO_WERROR) I upgraded my laptop directly from 6.3 to 8.1-STABLE. It now
boots nicely.
I'd like to make another round of buildworld/buildkernel -- using the
existing tools... That, however, breaks in the most
31.07.2010 01:17, Peter Jeremy написав(ла):
kenv(1) (in the base) should as well.
Cool! Here it is:
smbios.bios.reldate=08/13/2003
smbios.bios.vendor=American Megatrends Inc.
smbios.bios.version=3.13
smbios.chassis.maker=Chassis Manufacture
smbios.chassis.serial=Chassis
09.07.2010 05:49, Peter Jeremy ???(??):
I doubt I'm personally in a position to debug this and don't personally
use splash screens. Can you reproduce it using an image that you can
re-distribute?
Ok, the splash-screen problem went away after I put back the original
video-card. The one
Some part of KDE4's kdm crashed at start-up and seems to have taken the
entire machine with it:
kgdb /boot/kernel/kernel /var/crash/vmcore.22
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
20.07.2010 12:47, Alan Cox написав(ла):
Historically, this panic has indicated flakey memory. This panic
occurs because a memory location within a page table has unexpectedly
changed to zero.
Ouch... Thanks for the hint (maybe, the panic should say something like
that?)
In any case, is
An 8.1-prerelease machine I have throws the panic in subject quite
often. Does anyone care? Is this evidence of some filesystem corruption
here, or a known problem that's (almost) solved already?
The stacks all look the same:
panic: handle_written_inodeblock: bad size
19.07.2010 07:31, Jeremy Chadwick написав(ла):
If you boot the machine in single-user, and run fsck manually, are there
any errors?
Thanks, Jeremy... I wish, there was a way to learn, /which/ file-system
is giving trouble... However, after sending the question out last night,
I tried to
On 17.07.2010 09:41, Jeremy Chadwick wrote:
The test system is amd64. I'm not doubting the issue may be more
apparent/easier to occur on i386, but pure luck on amd64 is a bit
surprising.
I'll build an i386 version of my testbox and start the procedure over
again.
Set the malloc(3) flags to
08.07.2010 09:53, Jeremy Chadwick написав(ла):
Then don't modify loader.conf. Instead, once the Welcome to FreeBSD!
portion of loader appears, press 6 to shell to the loader prompt
and type:
set vfs.root.mountfrom=ufs:/dev/md0
boot
Yes, that works... It just should not be necessary. Red
08.07.2010 12:40, Jeremy Chadwick написав(ла):
set vfs.root.mountfrom=ufs:/dev/md0
boot
Yes, that works... It just should not be necessary.
Okay, so let me get this straight. First the complaint was that you had
to modify loader.conf, which involved extracting the CD image,
08.07.2010 17:06, Peter Jeremy написав(ла):
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com wrote:
In no particular order:
1. A picture, that one of the systems was displaying at boot (and
then used as a screen-saver), stopped showing properly. The
08.07.2010 17:36, Lucas Holt написав(ла):
Most of us work on open source for free in our own time, and it's
impossible to test every possible configuration before a release.
I tested several particular configurations -- on several machines -- and
reported the overlooked issues. I didn't write
12.07.2010 13:11, Adam Vande More wrote:
Roll it into your media
You lost me right here... Rolling one's own media (for every release and
release-candidate) may be Ok for someone in charge of making, at least,
several installations per week.
For someone like myself, who just wanted to use a
The sshd would not start after the upgrade from 7.x to 8.1 on one of the
systems:
Starting sshd.
cipher_encrypt: bad plaintext length 553
/etc/rc.d/sshd: WARNING: failed to start sshd
Archiving the 3-year old /etc/ssh/ssh_host_rsa_key and having it
recreated solved the immediate
A laptop I'm helping configure (remotely) just crashed under me... Upon
reboot I found the following in the messages file (quite amazed, that
the message got there, actually):
Jul 12 22:06:01 s syslogd: kernel boot file is /boot/kernel/kernel
Jul 12 22:06:01 s kernel: panic:
07.07.2010 14:30, Randi Harper написав(ла):
8.
I tried to do an install on one of the systems via netbooting
(pxeload) the disk1-image. It booted, but the sysinstall had to be
started manually and, once started, did not act the same as when
booted off of CD-ROM.
07.07.2010 16:00, Randi Harper написав(ла):
So you're complaining that you have to modify the loader.conf? I
fail to see the problem. This is by design, and isn't a lack of
progress.
Yes, I complain, that I have to modify a loader.conf embedded in a
CD-image. If extracting hundreds of
07.07.2010 16:50, Marcel Moolenaar написав(ла):
Not to mention that if you change uart(4) to create dev entries like sio(4)
after uart(4) has been in the tree for more than 6 years creating ttyu*
entries, you actually introduce a gratuitous change.
If sio and uart could co-exist, then you'd
I'm upgrading several systems these days to the 8.1 (pre-release) and
have hit the following troubles... I could file a formal PR for each, I
suppose, but, maybe, this way will get the right people's attention sooner.
In no particular order:
1.
A picture, that one of the systems was
07.07.2010 14:59, Jeremy Chadwick ???(??):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config files, that worked with
7.x, break without this option in them (in addition to all the
nuisance, that's documented in
07.07.2010 16:34, Randi Harper ???(??):
Attached is the kernel config-file (i386), that worked fine under 7.x. The
kernel-compile will break (some *freebsd7* structs undefined), without the
COMPAT_FREEBSD7 option. Try it for yourself...
Don't use a kernel config from 7. We've
Hello!
I'm suffering from a fully reproducible panic, that strikes, when I
connect a umass storage device (Blackberry Pearl with a mini-SD card
inserted) to the EHCI USB port.
The system runs a freshly rebuilt 7.3-stable/amd64. The crash is
somewhere inside USB-stack. The stack, as produced by
Jeremy Chadwick написав(ла):
Regarding your problem: it likely has nothing to do with SMP, so don't
worry about that aspect of it.
Thanks for the reassuring response, Jeremy. If this is not about SMP,
then there is a (bad) regression -- the 7.2-kernel from March 5 never
crashed this way... I
Hello!
I just rebuilt my system from 7.2-stable to 7.3. The first thing to fail
upon restart was the PostgreSQL-server. But there are other failures --
for example, webmin is unreachable at its usual https://localhost:1/
ktrace-ing postgres reveals:
19875 postgres CALL
Jeremy Chadwick написав(ла):
Check ifconfig -a and make sure lo0 appears / has a correct IP address,
and the interface is up.
You are right, it is not up:
lo0: flags=8008LOOPBACK,MULTICAST metric 0 mtu 16384
Manually running `ifconfig lo0 127.0.0.1' fixed the problem for the time
01/14/10 21:56, Matthew Dillon написав(ла):
This would explain why the performance is not as bad as linux but
is not as good as a properly pipelined case.
For what it may be worth, here are the stats for Solaris as well:
* Solaris 8, native, 32-bit binary (using -lcrypto instead
03/25/06 14:03, John-Mark Gurney wrote:
The other useful/interesting number would be to compare system time
between the mmap case and the read case to see how much work the
kernel is doing in each case...
After adding begin- and end-offset options to md5(1) -- implemented
using mmap (see
01/14/10 17:15, Andrew Snow wrote:
Hi Mikhail, I assume these tests were done on UFS. Have you tried ZFS?
I'm curious to see the results.
I suspect, it would be harder for me to setup ZFS, than for you to apply
my patch for to md5.c :-)
-mi
Hello!
I'm trying to start OOo, and it hangs at start-up -- after popping up
its banner page.
ktrace shows the following, slowly repeating, sequence of events:
[...]
32726 soffice.bin CALL
_umtx_op(0x805d09060,0x8,0x1,0x805d09040,0x7fbfeef0)
32726 soffice.bin RET
Hello!
I'm investigating a problem caused by (what seems like a spurious)
SIGPIPE. The program creates a child process using pipe, exchanges a few
messages with the child (via write and read) and closes the pipe.
Some times -- in about 60% of the cases -- this causes a SIGPIPE to be
delivered to
Kostik Belousov написав(ла):
Take ktrace of both parent and child.
Great idea! Here is the kdump's listing for both (after ktrace -i):
http://aldan.algebra.com/~mi/tmp/tclx-kdump.txt
(it is large, so be sure to use a compressing browser). Once loaded,
look for substring:
Error
Kostik Belousov написав(ла):
Take ktrace of both parent and child.
I can see the curious piece right here:
The child exits:
92723 tclsh8.5 CALL exit(0)
The parent masks SIGPIPE (as part of my workaround):
92722 tclsh8.5 CALL sigaction(SIGPIPE,0x7fffa9e0,0)
92722 tclsh8.5 RET
Jilles Tjoelker написав(ла):
It seems unwise to assume that a write(2) of 0 bytes is a noop.
Even if it is, doing it is a waste of a system call.
This is not my code -- it is part of the implementation of Tcl's
close command. I'm trying to unravel, where this write coming from,
but, meanwhile,
Kostik Belousov написав(ла):
This 0-size write must be part of the pipe-closing -- descriptors 4 and
5 must be the pipe's:
92722 tclsh8.5 CALL write(0x4,0x800e24028,0)
92722 tclsh8.5 RET write -1 errno 32 Broken pipe
92722 tclsh8.5 PSIG SIGPIPE caught handler=0x800f126d0 mask=0x0
Hello!
I noticed, that my build of KDE4 ports got suspiciously quiet...
Pressing Ctrl-T shows:
load: 0.01 cmd: automoc4 78507 [umtxn] 0.00u 0.00s 0% 3552k
According to gdb, the process' stack is:
#0 0x000800d9620a in __error () from /lib/libthr.so.3
#1 0x000800d95f0c in
Greg Black написав(ла):
Sorry, this person is *not* making backups in any meaningful fashion.
Unless you verify regularly (preferably every time you make a backup)
that you can restore both parts of the backup and the entire thing, you
are not making backups.
To qualify for your (and your
Andrew Snow написав(ла):
Mikhail T. wrote:
To qualify for your (and your kind's) recognition then, a person
needs to have at least as much extra storage capacity as the
largest filesystem they are backing up. They also need
non-trivial scripting abilities, because the OS doesn't
include
Greg Black написав(ла):
On 2009-03-24, Mikhail T. wrote:
That's true. I just wanted to point out, that someone running dump only
(to make backups) is not going to know, whether his dumps are usable
(for whichever of the two reasons), until he needs them...
Such a person is not making
Daniel O'Connor написав(ла):
On Tuesday 24 March 2009 11:55:07 Mikhail T. wrote:
I'm trying to migrate a filesystem from one disk to another using:
dump a0hCf 0 32 - /old | restore -rf -
(/old is already mounted read-only). The process runs for a while and
then stops
Danny Braniss написав(ла):
Daniel O'Connor написав(ла):
On Tuesday 24 March 2009 11:55:07 Mikhail T. wrote:
I'm trying to migrate a filesystem from one disk to another using:
dump a0hCf 0 32 - /old | restore -rf -
(/old is already mounted read-only). The process runs for a while
Danny Braniss написав(ла):
can you try splitting it in 2, ie no pipe?
dump a0f some.file /old (or dump 0f - /old | gzip -c file.dump.gz)
restore rf some.file
Same problem:
restore -rf ibmo.0.2009-03-24.dump
load: 0.55 cmd: restore 11303 [nbufkv] 3.53u 3.91s 4%
Andrew Snow написав(ла):
Mikhail T. wrote:
dump 0aCf 64 /ibm/ibmo.0.2009-03-24.dump /old
DUMP: WARNING: should use -L when dumping live read-write
filesystems!
I thought you said it was a read-only filesystem?
It was yesterday. Today I remounted it rw to remove some junk-files
Daniel O'Connor написав(ла):
morning is still hanging (in sbwait) -- I've never seen this before. I'm
also very troubled, that such an important functionality (dump/restore!)
is sooo problem-prone, and yet so few people seem to care...
Well, works for me.
Well, would like a login on
Yoshihiro Ota написав(ла):
No big difference:
dump a0f - /old | restore -rf -
[...]
DUMP: 17.25% done, finished in 3:27 at Tue Mar 24 05:42:00 2009
DUMP: 20.36% done, finished in 3:09 at Tue Mar 24 05:28:13 2009
DUMP: 23.83% done, finished in 2:50 at Tue Mar 24
Andrew Snow написав(ла):
Mikhail T. wrote:
Now can one get /real/ support for the most basic functionality of the
most advanced modern Unix in the world? Thanks,
I think before this goes any further, you will need to try
rebooting/unmouting it, running fsck on it, and then dump
Daniel O'Connor написав(ла):
That said, I point out, that for me, dump is not failing (although it
did hang this morning). It is the restore, which fails to read dump's
output:
You can't tell the difference between dump producing mangled output or restore
bombing out on valid input..
Daniel O'Connor написав(ла):
On Wednesday 25 March 2009 13:10:23 Mikhail T. wrote:
Now can one get /real/ support for the most basic functionality of the
most advanced modern Unix in the world? Thanks,
Maybe you should return it to the shop and ask for your money back.
Well
Daniel O'Connor написав(ла):
People ARE helping you, just because they haven't come up with an answer is no
reason to send snarky comments to the list.
No, sorry, people aren't. They are trying, yes, but not even close. The
suggestion to eliminate the -a switch (a no-op, in fact) was
Andrew Snow написав(ла):
I think before this goes any further, you will need to try
rebooting/unmouting it, running fsck on it, and then dump the unmounted
partition and see how that goes.
Rebooted, reran `fsck -y /old' (all clean). Same problem...
-mi
Hello!
I'm trying to migrate a filesystem from one disk to another using:
dump a0hCf 0 32 - /old | restore -rf -
(/old is already mounted read-only). The process runs for a while and
then stops with:
[...]
DUMP: 22.85% done, finished in 3:57 at Tue Mar 24 01:03:21 2009
DUMP:
Hello!
My FreeBSD/amd64 system has two processors, each with 2 out of 4 memory
slots filled. The total RAM is 4Gb.
In the BIOS there are options to enable Software memory hole and
Hardware memory hole.
The only way to have the entire 4Gb of physical RAM enabled is to have
Software memory hole
Hello!
I tried, accidentally, to save a video-file (via firewire) to a
read-only location.
The entire system paniced with the message in subject. Why did it
happen?
Thanks!
-mi
___
freebsd-stable@freebsd.org mailing list
The kernel is from:
FreeBSD 6.3-STABLE #0: Thu Feb 7 ... amd64
The crash:
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0xffe3ffe3e010
fault code = supervisor read data,
Hello!
The machine is running 6.3-PRERELEASE as of Dec 30th. It just paniced in
the middle of web-session as I was browsing for a file to upload via a
web-form... The firefox in use is native (amd64), not a Linux-binary.
The firefox process had over 550Mb of memory to its name -- it was
running
Hello!
I was working remotely, when suddenly the server dropped off the 'net.
Upon reboot it was stuck in unexpected softupdates inconsistency (I
did not have fsck_y_enable set).
Here is the panic:
Unread portion of the kernel message buffer:
Fatal trap 9: general protection fault while in
I'm not 100% certain, this is a legal thing to do. But I think
it is.
I hooked up a brand new hard-drive (Seagate) to the free SATA port,
and then connected the power cable. Before that I had just one SATA
drive (ad8).
The kernel crashed in ata_identify(). I'll keep the core around for
some time
I was ripping one CD (SCSI CD-drive) and inserting another CD
into an ATA CD-DRIVE.
Suddenly the machine paniced... Although I have the crash dump,
it seems corrupted -- kgdb can't print out the stack.
The panic is: vinvalbuf: dirty bufs.
Please, advise. Thanks!
-mi
Hello!
After a couple of huge tarball extracts (`make extract' in jdk14 and jdk15)
I noticed, things are a little slower. During the extracts, the mouse was
moving with visible jerks. Indeed, the system seems VERY busy:
11 usersLoad 1.18 1.52 1.40 Jul 20 00:14
Mem:KB
97 matches
Mail list logo
