FreeBSD 5.x and Bad File Descriptor errors. Why?
Hello What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am considering going back to it but I need to figure out how to prevent this issue from happening again. My system has 2 harddrives, a 16 GB Seagate that I use for backups and mount it under /mnt/backup and a 40 GB Maxtor that I am using for everything else. After the installation of the OS (usually about 8-12 days of running non-stop) I start getting Bad File Descriptor errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get corrupted this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. Now if not for a few things, I'd probably come to the conclusion that my Maxtor HD is dying on me as my Seagate drive isn't causing me any headaches. However this doesn't seem to be the case, as if Linux (EXT3) or Windows (NTFS) are used, no data loss ever occurs even if the system is left running for many weeks in a row. Now what exactly could be causing this bizarre behavior ? If this is of any help, the exact model number of the HD is MAXTOR 4K040H2 and I was using UFS2 on both drives. Thanks in advance. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Kris Kennaway wrote You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris I usually discover that I am having data corruption when trying to update ports. A file that has a Bad File Descriptor refuses to let cvsup overwrite and/or remove itself. I've also had make installworld fail on me for the very same reason. A file in the base system would get corrupted and would prevent anything from overwriting itself. These problems would go away after a full system fsck, but the fsck would remove the damaged files completely, sometimes leaving the system in a severely broken state. And even if it did not, data corruption would happen again in 8-12 days. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Doug White wrote: Maxtor has a diag tool that goes onto a floppy that you could run. I have this exact disk in my sparc64 here and the first time I used it, it kept running over bad sectors and generally causing mayhem. Running the full scan with the tool, it prompted to fix some problems, then the bad sectors went away. I reinstalled the OS to clear out the broken files and I never had any problems afterward. The program is called PowerMax and is available from the downloads section under either diagnostics or utilities. I've tried running PowerMax on the drive with a through scan but no errors were found. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMBus / I2C h/w sensors and FreeBSD 5.1
On Sun, 2003-10-05 at 02:53, Bernd Walter wrote: With a driver for the hardware it's possible of course. You have a VT82C686A/B chip for which you want viapm driver. intpm is for Intel PIIX4 (82371AB, 82443MX) which you don't have. I've replaced intpm with viapm in my kernel config and this is what I am seeing in my dmesg now: viapropm0: SMBus I/O base at 0x5000 viapropm0: VIA VT82C686A Power Management Unit port 0x5000-0x500f at device 7.4 on pci0 viapropm0: failed to enable port mapping! viapropm0: could not allocate bus space device_probe_and_attach: viapropm0 attach returned 6 Obviously, /dev/smb is still nowhere to be seen :( Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
SMBus / I2C h/w sensors and FreeBSD 5.1
Hello (World). I am trying to get my h/w sensors working on my FreeBSD 5.1-RELEASE-p10 system and I am having some trouble. I recall being able to use them in FreeBSD 4.7 on the same box, but things seem to have changed quite a bit. I am using sysutils/consolehm in this case. The manpage for sysutils/consolehm says I need the following in my kernel config: controller smbus0 controller iicbus0 controller iicbb0 controller intpm0 device smb0 at smbus? With those options, a 5.1 kernel does not compile, so after looking through LINT I came up with these options (the kernel builds with them): device smbus device iicbus device iicbb device intpm device smb Unfortunately, running chm results in THIS: Motherboard Temperature: 255 ° C CPU_0 Temperature: 0 ° C CPU_1 Temperature: 0 ° C VCore: 3.98438 V Vit: 3.98438 V Vio: 3.98438 V +5V: 6.65391 V +12V: 15.9375 V -12V: -15.9375 V -5V: -6.65391 V Fan 1: Not Available Fan 2: Not Available Fan 3: Not Available So I figure I should try chm -S to force it to use SMBus (it uses a different method by default), but with -S I get the following error message: Not compiled for use with SMBUS, reverting to ISA Method. Investingating further, I see that I have no /dev/smb on my system even though I have device smb in my kernel config. I've also noticed a line saying pci0: serial bus, SMBus at device 7.4 (no driver attached) in my dmesg. So what's wrong ? Isn't devfs supposed to create /dev/smb by itself ? Does the error of chm -S mean that my kernel is not compiled with smbus support (would be weird) or that sysutils/consolehm is compiled with smbus support disabled (I don't see any appropriate make options in the port Makefile) ? Thank you for your time. Sincerely, Dan Naumov P.S: if the full dmesg output is needed, I can provide it as well. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMBus / I2C h/w sensors and FreeBSD 5.1
On Sun, 2003-10-05 at 00:44, Bernd Walter wrote: You need to have intpm hardware to get this driver working. There are other drivers available depending on your chipset. What is the pciconf -lv output? There you go: [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x700e1022 rev=0x13 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-761 CPU to PCI Bridge' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x700f1022 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-761 CPU to AGP Bridge (AGP 4x)' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:7:0: class=0x060100 card=0x06861106 chip=0x06861106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686/A/B Super South PCI to ISA Bridge' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:7:1: class=0x01018a card=0x05711106 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82 EIDE Controller (All VIA Chipsets)' class= mass storage subclass = ATA [EMAIL PROTECTED]:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x1a hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class= serial bus subclass = USB [EMAIL PROTECTED]:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x1a hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class= serial bus subclass = USB [EMAIL PROTECTED]:7:4: class=0x0c0500 card=0x30571106 chip=0x30571106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686A/B ACPI Power Management Controller' class= serial bus subclass = SMBus [EMAIL PROTECTED]:10:0: class=0x02 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/8130) Fast Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:14:0: class=0x040100 card=0x20001274 chip=0x58801274 rev=0x02 hdr=0x00 vendor = 'Creative (Was: Ensoniq)' device = '5880 AudioPCI' class= multimedia subclass = audio [EMAIL PROTECTED]:5:0: class=0x03 card=0x87001462 chip=0x025310de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce4 Ti 4200 [NV25.4]' class= display subclass = VGA Investingating further, I see that I have no /dev/smb on my system even though I have device smb in my kernel config. I've also noticed a line saying pci0: serial bus, SMBus at device 7.4 (no driver attached) in my dmesg. So it's no intpm hardware. What drivers should I be using then ? I had lm_sensors on Linux work with this hardware... Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange system responsiveness issues with 5.1-CURRENT
Hello (World). I've recently moved from FreeBSD 5.1-RELEASE to 5.1-CURRENT (from September 21) and noticed some strange changes in my system responsiveness (using identical kernel configs). Some applications, like games/fuhquake, Quake3 and SETI seem to run faster (I get better FPS in games and my SETI WU crunching time has slightly decreased). However, in many cases, the results have been less then good: Starting applications (XFree, Evolution, Mozilla, OpenOffice, games) takes a noticably longer time than it used to, I'd say that Mozilla Firebird load times have increased by about 30-40%. I can also now see jerkiness in switching between applications. When Alt-Tabbing between Firebird, OpenOffice and Evolution, the windows appear half-drawn for a second or two. When I play music (MP3 and/or OGG) in XMMS and try to drag the position indicator forward/backward to go to that specific part of the track, it now takes 2-3 seconds until it actually switches to that part of the track and starts playing it, even though with 5.1-RELEASE that was happening instantly. Am I doing something wrong or is this to be expected ? Unfortunately I have no webspace to post my dmesg and kernel config on, but if any of you people want them, I can send them attached to a private mail. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Fixing -pthreads (Re: ports and -current)
On Tue, 2003-09-23 at 23:13, Daniel Eischen wrote: I understand that folks want to wave their hands and say just make -pthread work and do whatever it needs to. I am one of those folks as well. As an end-user, I am not interested in hacking around the source of 3rd-party applications that use -pthread when compiling them from source myself. Not in the slightest. This is BAD BAD BAD for usability. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Fixing -pthreads (Re: ports and -current)
On Tue, 2003-09-23 at 23:25, Dan Naumov wrote: On Tue, 2003-09-23 at 23:13, Daniel Eischen wrote: I understand that folks want to wave their hands and say just make -pthread work and do whatever it needs to. I am one of those folks as well. As an end-user, I am not interested in hacking around the source of 3rd-party applications that use -pthread when compiling them from source myself. Not in the slightest. This is BAD BAD BAD for usability. Sincerely, Dan Naumov I also believe that a question has to be asked, what do the -core and -arch people think of all this ? I think that they should have the final say in the matter. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
:ata1:0:0:0): CAM Status: SCSI Status Error (probe2:ata1:0:0:0): SCSI Status: Check Condition (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): Invalid field in CDB Mounting root from ufs:/dev/ad0s1a cd0 at ata1 bus 0 target 0 lun 0 cd0: LITE-ON COMBO LTC-48161H KH0F Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [818 x 2048 byte records] === Is this something I should worry about ? Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Mon, 2003-09-22 at 00:07, Thomas Quinot wrote: Le 2003-09-21, Bryan Liesner écrivait : Thanks, the hang problems are fixed now. That's great news! I am also very grateful for your fix. I now seem to be able to run -CURRENT on my home desktop without any issues whatsoever :) No one told me that I was barking up the wrong tree... Ah, computers are fragile and playful things that always find creative and unexcepted ways of failing... :) Speaking of failing, should I completely disregard the probe2:ata1 warnings during boot which you saw in the dmesg output I sent you ? Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Mon, 2003-09-22 at 00:42, Daniel Eischen wrote: We've already been over this before. The problem is not as bad as you think, and there are other platforms that don't have -pthread. And those platforms would be? Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
On Sat, 2003-09-20 at 12:32, David R. Colyer wrote: Is atapicam a kernel config option? [14:11]-[jago]-[~]: cat /usr/src/sys/i386/conf/JAGO | grep atapicam #device atapicam# BROKEN in -CURRENT !!! Hope this helps. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Getting -pthread support back into local source tree
Hello Seeing as -pthread support has been removed from -CURRENT breaking _LOTS_ of ports, is it possible to get it back into a local source tree ? If so, how ? Thanks in advance. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports and -current
On Sun, 2003-09-21 at 04:09, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Doug Barton [EMAIL PROTECTED] writes: : I'd really like to see this change backed out, at minimum until the : ports freeze is over. My thoughts exactly. Sincerely, Dan Naumov -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Random lockups and reboots on FreeBSD 5.1-RELEASE
Hello I am having some very annoying problems with a FreeBSD 5.1 install. Every 4-6 hours, it either reboots by itself or locks up hard, with the HD led being constantly lit. I've tried looking into the logs, but nothing is written to them before the lockup/reboot, even if I choose boot FreeBSD with verbose logging from the boot-up menu. I have also tried booting up with ACPI disabled and it didn't help either. As of this moment, I cvsupped my sources to today's -CURRENT and am building world. I hope that since -CURRENT has had many changes since 5.1-RELEASE, chances are my problem could've been fixed. However in case it has not, where should I start to look into in order to find the source of my problem? I have no previous experince in debugging and would appreciate to have some pointers Hardware: AMD T-Bird 1400 Mhz GigaByte GA-7DXR motherboard (AMD761 chipset) Creative NVIDIA GeForce4 Ti4200 (I tried both avaible driver sets) Creative SB128 PCI Lite-On DVD/CDRW Combo Drive LTC-48161H Maxtor 40 GB HD Seagate 16 GB HD Thanks in advance. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random lockups and reboots on FreeBSD 5.1-RELEASE
I forgot to add that excessive heat and faulty ram are ruled out, I've checked system temp and it seems to be OK, memtest has also passed all tests completely without giving any errors. It *COULD* theoretically be the HD going bad, but how could I possibly check this? Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng still problematic
On Fri, 2003-09-19 at 19:21, Marius Strobl wrote: On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote: Anyway, here's backtrace for atapicam panic I've mentioned. It's triggered by: cdrecord dev=1,1,0 /some/track This panic isn't ATAPICAM related. Could you try the patch below? It's against the cdrtools-devel port but should also work with the cdrtools port. Hello. I am sorry for breaking into this conversation, but I thought it's worthy to report that if I have ATAPICAM enabled in my kernel and have my Lite-On DVD/CDRW Combo Drive attached to the system, today's -CURRENT fails to boot (both single- and multiuser). It gets stuck right after: acd0: CDRW LITE-ON COMBO LTC-48161H at ata1-master PIO4 Disabling atapicam in the kernel or detaching the drive from the system works around the problem. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing Sendmail
Terry Lambert wrote: Because syslog is unreliable. See BUGS section of the man page. Don't you think that if syslog is unreliable, then it should be fixed ? If things are as you say, we have 2 problems: Sendmail gettings CERTs every other day and an unreliable system logger. Would you rather just let things be as they are ? Sincerely, -- Dan Naumov [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing Sendmail
On Wed, 02 Apr 2003 10:59:25 -0600 Peter Schultz [EMAIL PROTECTED] wrote: [x] sendmail ... (default) [ ] postfix ... [ ] exim ... [ ] qmail ... [ ] none (caution: desktop users only, insecure use of syslog) AFAIK, sendmail, postfix and none are the options presented to the user during the installation of a NetBSD system. I think it's a good idea. Sincerely, -- Dan Naumov [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing Sendmail
On Wed, 02 Apr 2003 14:29:30 -0500 (EST) John Baldwin [EMAIL PROTECTED] wrote: I find an odd situation here whenever this topic comes up. One the one hand, people are always wanting to split the entire base system up into small packages for each little piece of the base. On the other hand, one of FreeBSD's selling points in real-world environments is that it doesn't have a bunch of little packages for the base system like Linux distros. Do people really prefer something like having rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, etc.? It really depends on where you draw the line. Personally, I'd rather have a very minimal base system that's kept as a whole with additional packages avaible for those who want them. Basically if I was to decide on such things, I'd throw out CVS, BIND, g77, GDB, OpenSSL, SendMail, games and crypto out of base and making them avaible through ports. But that's all IMHO and not very likely to happen to FreeBSD in my lifetime ;) Sincerely, -- Dan Naumov [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing Sendmail
On Wed, 2 Apr 2003 21:56:40 +0200 Wilko Bulte [EMAIL PROTECTED] wrote: On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: I find an odd situation here whenever this topic comes up. One the one hand, people are always wanting to split the entire base system up into small packages for each little piece of the base. On the other hand, one of FreeBSD's selling points in real-world environments is that it doesn't have a bunch of little packages for the base system like Linux distros. Do people really prefer something like having rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, etc.? BarfPuke One of the worst mis-features of Linux in my book. I think being able to update just about ANYTHING, except the kernel without the need for a reboot is one of the best features of Linux and actual advantages it has over FreeBSD. Sincerely, -- Dan Naumov [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
-O2 breaks GCC 3.2.1-compiled code (seems OS specific)
Hello list. Since my issues are related to 5.0, I though I'd rather ask here. I've noticed an interesting problem: I am using FreeBSD 5.0-p4 and GCC 3.2.1 and if I use CPUTYPE=athlon-tbird and CFLAGS= -O2 -mmmx -m3dnow -fomit-frame-pointer -pipe, ezm3 refuses to compile AT ALL and even though AbiWord 1.0.4 does compile, it will always coredump on exit, preventing saving of any changes done to the Preferences. However, going down from -O2 to -O solved both problems. This makes me wonder what exactly is wrong, since I've used exactly the same CPUTYPE and CFLAGS under Gentoo Linux with GCC 3.2.1 for a long time and everything compiled absolutely fine. This leads me to believe that there are not only arch-specific, but also OS-specific GCC issues. Can anyone else confirm this ? Sincerely, -- Dan Naumov [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
