Related topics

Virus.Win9x.SK
The virus does not manifest itself in any way and does not cause any system error messages when running under Windows95. It seems to me that VxD infection routine has a bug (the virus does not parse correctly LE Object Table), and the virus will corrupt "non-standard" VxD drivers, but all VxDs from virus' list are

freebsd-questions Digest, Vol 202, Issue 18
__FreeBSD_version wasn't bumped specifically for it, but 700044 should be fine (first bump after the last significant bug fix to ar support, as far as I can tell) DES ...... It is very likely that many other things you created on this system (eg compiled binaries, modified files, etc) are also corrupted.

freebsd-stable Digest, Vol 238, Issue 7
The alternative is to disable the disk write cache. But that isn't modern practice or recommendation, since I/O write barriers were implemented and they are much Not only can it lose data on power loss, it can corrupt the guest filesystem too, due to reordering. This is contrary to what people expect, I think.

Virus.DOS.Eddie.651.a
I have a MP3 player that says it is 2GB, but really is only 128MB. any data placed beyond 128MB gives instantly corrupted results... Warner ------------------------------ Message: 9 Date: Wed, 20 Feb 2008 06:39:07 GMT From: Alan Sanders <alan_1...@yahoo.com> Subject: usb/120873: if_zyd and if_rum panic in

freebsd-current Digest, Vol 230, Issue 11
To install itself memory resident, the virus scans the Windows kernel, obtains the necessary Windows-functions addresses and installs itself "memory resident" as a system driver (VxD). It allocates a block of Windows VxD memory, copies itself to there and hooks IFS API (disk file access functions).

Virus.DOS.Yosha.745
Sorry for the inconvenience caused by the driver's update. ------------------------------ Message: 2 Date: Thu, 21 Feb 2008 09:26:16 +0900 From: Alexander .... Note that some packets are being corrupted on the way out, too. Just to make troubleshooting difficult, this problem only shows up after the system has been

freebsd-stable Digest, Vol 241, Issue 4
Is it possible that the problem lies in the ATA drivers in FreeBSD or even in ZFS and just looks like HW issues? I do not have enough info/expertise to know. ..... Message: 21 Date: Tue, 12 Feb 2008 02:06:31 +0100 From: Kris Kennaway <k...@FreeBSD.org> Subject: Re: mount of ext2fs volume stuck in "D+" state (disk

freebsd-usb Digest, Vol 173, Issue 3
Message: 3 Date: Mon, 18 Feb 2008 11:07:19 GMT From: FreeBSD bugmaster <bugmas...@FreeBSD.org> Subject: Current problem reports assigned to Firewire drive not properly supported o usb/89954 usb [umass] [panic] USB Disk driver race condition? o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas

freebsd-bugs Digest, Vol 256, Issue 1
A known issue, or bug, maybe? Or is VMware support not yet enabled? Help would be greatly appreciated. Thanks. Dimitri -- This message has been scanned for ..... To be honest, if I'm not using an install CD (which will do the job) I may as well look at making a custom recovery disk which just needs to be booted

freebsd-current Digest, Vol 231, Issue 9
We need to identify why the reset failed but it's likely a hardware/expresscard issue and not in the driver. Unfortunately I don't have an SRX card (just ...... 2) Turn off the disks with the corrupted pool. (Fortunately, mine was on an external Firewire disk pair.) 3) Reboot the system, study where the panic was,

freebsd-current Digest, Vol 230, Issue 8
Skybuck Flying s...@hotmail.com alt comp lang borland-delphi microsoft public development device drivers microsoft public windows 64bit general HOLYFUCK. long folder which should have so many characters that it at least exceeds 255 characters hopefully my fucking file disk image wont get corrupted by this

freebsd-bugs Digest, Vol 255, Issue 7
Dovecot logs that index files are corrupt, and marked broken. Recovery involves re-selecting the IMAP mailbox. In response to your post, ...... cpufreq # Bus support. device eisa device pci # Floppy drives device fdc device crypto # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid

Virus.DOS.MAD.1288
kern/sched_4bsd.c:905 Previous frame inner to this frame (corrupt stack?) On http://dummynetcrash.matthew.sk you can also find the kernel.debug and tha crash files, for more debugging. ..... I guess a DVD release would more than help: all the packages would be on a single disc (plus, we might add some more).

freebsd-current Digest, Vol 229, Issue 11
Christian Perrier bubu...@debian.org linux debian bugs dist # french translation of python-apt # Copyright (C) 2007 Hugues NAULET <hnau...@gmail.com> ..... Please free at least %s of disk space on %s. " #~ "Empty your trash and remove temporary packages of former installations " #~ "using 'sudo apt-get clean'.

Filepath/Filename beyond 255 characters ?
The corrupted sync message scared the heck out of me: Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiti Synncgi n(gm adxi sk6s0, .... I would try upgrading to 6.3R (there are several em driver bug fixes) and then try the box with % cat /boot/loader.conf hw.pci.enable_msi=1 ...if the cards

freebsd-stable Digest, Vol 239, Issue 2
One of the issues that came out of this was it seemed that the ports database (/var/db/pkg/pkgdb.db) was corrupt. So I tried to rebuild it by deleting it and ..... Could be your /var/db/pkg is damaged as well, if it's the same disk. -- Mel Problem with today's modular software: they start with the modules and never

Proposal for "proper" durable fsync() and fdatasync()
Uriel From January, 15th it formats disk sectors. It has the bugs which can halt the system. It contains the internal text strings: Uriel 1.00Eur<FoG> Eddie.Alexander It's not a dangerous virus. It hooks INT 08h, 21h, 27h vectors and infects COM and EXE files. Sometimes it decrypts and displays the message:

freebsd-current Digest, Vol 230, Issue 13
First the screen is bit corrupted and only then it gets back properly. During this corrupt screen phase most of the stuff freeze for a moment. But this bug was not fixed in HEAD. -- WBR, Anton Yuzhaninov ------------------------------ Message: 21 Date: Tue, 19 Feb 2008 23:58:22 +0100 From: Miroslav Lachman

freebsd-current Digest, Vol 230, Issue 10
This is not a driver issue. It's just what your drive supports. ------------------------------ Message: 12 Date: Sat, 9 Feb 2008 07:41:08 +1100 From: Peter .... It's not as if one bit on the disk flipped - it affects the whole (1/2) block. Does this seem like a disk error, controller error/bug, cable problem (I

freebsd-usb Digest, Vol 173, Issue 1
The corrupted sync message scared the heck out of me: Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiti Synncgi n(gm adxi sk6s0, ..... Error 2 occurred at disk power-on lifetime: 5171 hours (215 days + 11 hours) When the command that caused the error occurred, the device was in an unknown