Dissaster Iminant -=- HELP

[Cuddles]

I have been working, over the past few weeks, creating analog to digital speach files - using ReZound, and ALSA for sound. All was working well, I had gotten all 8 45 to 50 minute tapes digitally recorded as ReZound files on the hard drive. Then went through all the "main" big audio files, making smaller, individual "speach" files as WAV. (all 135 of them) - that too, was going good.

I then went through all 135 individual WAV files cutting pre and post silence from them, that as well went good...

I then went through all 135 WAV files, using K3b, to formulate how many, and what audio files could fit on "n" amount of Audio CD's. (which is 10)

Last step was to actually "burn" the audio cd's - Starting with speach 1, CD#1 - I got all the way up to speach 102, and CD#7 - in which case, K3b locked the complete system up - no nothing. Had to hard reset the system... (this is where I think my problem has started from)

I tried to do a "file" on speach 102 - which, again, locked up the system, and required a hard reset to regain control.

I deleted the speach 102 WAV file, and used my "master" big ReZound file to generate a new speach 102 WAV file - ran "file" across the new file, and was fine. Restarted the system, and upon reboot, tried another "file" on speach 102 - system locked up again - and again, had to do a hard reset to get the system back.

I did this "delete/regenerate/file" thing two more times on speach 102 - and same results happen - the system goes completely frozen - not even the clock is updating, no mouse, no keyboard control - nothing...

I have rebooted so many times, that even fsck had fired off to check both the hda1 and where the speach files are located, hdc2, have been given clean bills of health... Noting only that when I get these locked systems, I usually get hda1 showing recovery and one inode being removed because it no longer points to something...

On the last attempt, I can't even open the "main" speach file used by ReZound that contains my individual speach 102 in it, along with 10 others - ReZound is now causing a complete lock on the system...

Copy/paste of dmesg on my hda1 device - which is where Knoppix is hard drive installed on:

VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
(recovery.c, 256): journal_recover: JBD: recovery, exit status 0, recovered transactions 108429 to 108461
(recovery.c, 258): journal_recover: JBD: Replayed 3017 and revoked 9/30 blocks
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
ext3_orphan_cleanup: deleting unreferenced inode 2883864
EXT3-fs: ide0(3,1): 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

What scares me now is, the "revoked" in the above, and the fact that I think I am watching my whole system eat itself alive... To the point that I am going to not be able to run, or do, anything...

help - Help - HELP

I was starting to make progress on catching up on my business work, this being a VERY important contract for this work I am doing currently, I am not able to get anywhere now with it - worse part is - my system appears to be going into an "implode" mode now. The more I try to get done, the more that seems to be getting the system stuck in this lock mode - nothing has changed on the system, no new installs, no removals, and it was fine last night, this morning I am just doing the same things I was doing last night, what worked before, is now causing catastrophic lock-ups on my system...

Anyone, please help...
Cuddles

[A. Jorge Garcia]

Can you somehow backup your files and reinstall?

Regards,
AJG

[fingers99]

I'm not at all sure what went wrong, but it occurs to me that ReZound is locking up because that one big file has chunks missing (the deleted inodes).

Lessons from this:

1.If at all possible, use alt backspace (it may be that only X is locking up) if that fails, use the magic keys rather than a hard reset. It's a hard lesson, and one someone pointed out to me a while back:

Press:

Alt + SysRq

(with these two held down) next press in order:

r s e i u b

Often (but not always!) one of these two will do the job.

2. Have a seperate /home partition (if you don't already).

I'm not sure why you're using wav files when ReZound will output to ogg. Wavs are huge and are more likely to overstress your system. Of course, you could/should do a quality comparison.

K3b has come on a lot recently, but a command line interface is much less likely to fall over than a GUI one. If you still have the HOWTOs, then

file:/usr/share/doc/HOWTO/en-html/CD-Writing-HOWTO-3.html#ss3.2

is useful although I'd be a bit wary of some of the Perl recipies as they may relate to an earlier version of Perl.

As for your current predicament, I fear that you may just have to find that file (as root do updatedb, then exit and run locate name_of_file) and rm it.

It's usually good practice to either take a rest or to do small bits at a time (maybe one CD's worth). OK, so we all know that, but how many of us do it?

Apart from what's happened to your work, I'd not worry too much about the deleted inodes: they almost certainly don't come as tidings of imminent system meltdown.

[Cuddles]

What in the world :!:

This kind of "just re-install" I would EXPECT in Windows, not Linux - where is the "stability" in an operating system, when the only resolve someone has is to "just re-install" ????

N O

I can not just re-install - this is NOT an option. I did the "just re-install" thing three times now. Once to get my old system over to my new system, Second to get my modem to work, and Third to get ALSA working - now, as I am getting something else on my system going - the solution AGAIN is to re-install - NO - NO WAY...

As for the magic keys - shesh, can you have "invented" anything less complicated ? In windows you have the "three finger salute", whereas in Linux, you have to do the "four finger salute" - now we have this "contorsionistic" set of key presses to do what??? Regain system control ???? The keyboard is locked, the system is locked, nothing is running, its dead when this happens...

How about this as an idea -=- The sound file (speach 102) is on my new 80 gig hard drive, the ReZound "main" 45 to 50 minute file used to generate these "smaller" speach files IS ON THE SAME DRIVE. K3b was trying to burn from files on the SAME DRIVE - when the system locks up, it is when I am doing "something" on the 80gig hard drive - this drive is hdc2 - whereas my system is located on hda1...

Could this be a failing hdc2 device???

How about some routines, or utilities, that can test the device? Or the file system on the device? Or the files on that device?

fsck doesn't seem to think that the "file system" is a problem, does it also test the files? I also noted during one of these "fsck" checks on the hdc2 device (80gig) that 24.5% was non-continueous - the device is not even 20% full - I thought that fsck checked and corrected these "defrag" issues?

Anyone have a disk test utility, something that I can ensure that my new hard drive, which apparently seems to be at the "root" of a common problem (system lock ups) may be causing these problems???

Thanks...
Cuddles

[fingers99]

I'm not talking of a re-install, but of a re-doing of your work. Just the sound files.

Having said that,
Could this be a failing hdc2 device??? well,
I also noted during one of these "fsck" checks on the hdc2 device (80gig) that 24.5% was non-continueous you mean non-contiguous, but this is one alarming figure. I've never seen more than 5%. Something is very screwy here. Can you post your /etc/fstab? Looks to me as though that drive has never been routinely fscked. But I think it's unlikely to be the drive itself, that is, on a hardware level (I'm guessing you have -- can't remember the name of it -- is it SMART? -- anyway, the tests that check the drives in the bios enabled and that no errors have been flagged).

If you have space, you might like to simply drag and drop the files onto your good drive and see what happens.

I know of no way of checking individual files (at least, at this point), only the filesystem.

[Cuddles]

Fingers99, you are MY saviour, you know that, don't you ????

A little background on this hdc device...

I added the 80gig HD after hard drive installing Knoppix v3.3 to the hda1 device - so a fstab entry had to "manually" be setup...

I hardware installed the 80gig hard drive, then booted into Knoppix/Linux, did a mkfs.ext3 (I think this was the command, from root), set up the /gblusr/hdc2 directory with all rights, and then setup the fstab...

Originally, the fstab was the following:

/dev/hdc2 /gblusr/hdc2 ext3 defaults,user,exec,noauto 0 0

With my extensive usage of my "main" system hdc1 device, which is only a 41gig, I began to move, and create these 400meg WAV/REZ files onto the hdc2 device, and I changed the fstab entry to be the following:

/dev/hdc2 /gblusr/hdc2 ext3 defaults,user,exec 0 0

Then I read a little on the mount, and fstab man pages, and changed the fstab file to the following reversion:

/dev/hdc2 /gblusr/hdc2 ext3 defaults,user,exec 0 2

Which, upon first boot with this fstab entry, caused fsck to "force" checking, since it hadn't done so for like 497xx days, or something like that...

With all the problems I have been having, only with hdc2 device, I have reverted back to a NON-AUTO mount of the device, so my fstab file looks like this now:

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
# Main HD part1 Linux OS FS
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
# Main HD part3 Linux Swap
/dev/hda3 none swap sw 0 0
# USB hub mount point
none /proc/bus/usb usbfs defaults,user,noexec 0 0
#
proc /proc proc defaults 0 0
# Secondary HD part1 VFAT DOS FS
/dev/hdc1 /gblusr/dosd vfat defaults,user,noauto,exec,umask=000 0 0
# Secondary HD part2 Linux FS
/dev/hdc2 /gblusr/hdc2 ext3 defaults,user,exec,noauto 0 0
# SanDisk USB
/dev/sda1 /gblusr/sda1 vfat noauto,users,exec,noatime,umask=000 0 0
# Remaining devices
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0

If all this comes down to is that my hdc2 device is failing, or needs to be re-formatted, I can re-do all the 135 sound files from scratch, that isn't as much of a problem as my system crashing on me...

Thanks for any assistance,
Cuddles

[fingers99]

Fingers99, you are MY saviour, you know that, don't you ???? :oops:

It's too late at night here for me to think straight, but, FWIW, my entries in /etc/fstab (and the order of my disks is very strange and will be resolved when I get round to it!) are like this:

# root partition
/dev/hdc1 / ext3 defaults,errors=remount-ro 0 1
# seperate /home partition
/dev/hdc3 /home ext3 auto 0 0
#drive where I keep Buffy movies and multi-media stuff
/dev/hda /mnt/mp3 ext3 auto 0 0

Now, check this with Stephen or Eadz, but I think I used to have a 0 2 entry in my /etc/fstab and noticed it wasn't getting fstabed, so I went back to Eadz's suggestion of 0 0 (I think it was Eadz). I'd read the manpages and either the man page is wrong or I'd managed to misinterpret it. Although my system gets a lot less throughput than yours, it's very stable (odd X crash aside, except when my Neuros objected to not having sync in the sda1 /etc/fstab line).

But do check. Those folk are (seriously) good.

the auto should be just fine.

I'd see if I could copy (maybe just the odd "finished" file at a time) onto some kind of media and then reformat. As a temporary measure, you could even comment out the (slightly suspect) HD in /etc/fstab and disconnect it so you could then get on with burning some disks and earning some money!

You'll probably find (but this is something to do later) that the manufacturer of the HD has some kind of diagnostic utility on their site. Often they seem to need a dos boot disk to run, but I think there's one (DOS boot disk, that is) somewhere with Knoppix.

Time for bath and bed!

[windos_no_thanks]

You'll probably find (but this is something to do later) that the manufacturer of the HD has some kind of diagnostic utility on their site. Often they seem to need a dos boot disk to run, but I think there's one (DOS boot disk, that is) somewhere with Knoppix.


A nice collection of most of the available HW diagnostic stuff:
http://www.ultimatebootcd.com/

Boots directly off the CD so it should work regardless of what OS one has installed.

[Dave_Bechtel]

--Fingers, what you really mean to say is use Ctrl-Alt-Backspace to try and kill the X-server. Alt-Bkspc alone won't do it.


1.If at all possible, use alt backspace (it may be that only X is locking up) if that fails, use the magic keys rather than a hard reset. Press:

Alt + SysRq

(with these two held down) next press in order:

r s e i u b

Often (but not always!) one of these two will do the job.

--To me, it sounds maybe like a DMA error on the HD.

--Cuddles, pls post results of (root):
' hdparm /dev/hda ' as well as hdc... DMA usually gets enabled in /etc/init.d/bootmisc.sh.

--As an aside, Cuddles - the Alt-Sysrq sequence is still a 3-finger combo. What the keys do, in order:

Alt-Sysrq-R: unRaw (not needed usually)
Alt-Sysrq-S: SYNC all pending writes to HD's
Alt-Sysrq-E: Send sigTerm to all processes
Alt-Sysrq-I: Send sigKill to all
Alt-Sysrq-U: Umount (remount all partitions R/O)
Alt-Sysrq-B: ReBoot

--Note: You should wait a few (2-5) seconds between each sysrq request, so all the writes can commit and things have a chance to settle down. To get help on Sysrq, get to a text console and hit Alt-Sysrq-H. (Make sure to use the LEFT Alt key.)

--AFA testing the HD: Boot knoppix cd into runlevel 2:
boot: ' knoppix 2 vga=normal ' (and whatever other codes you normally use)

' badblocks -c 128 -s -v /dev/hda ' == Equivalent to "surface scan"; tests R/O for bad sectors on entire disk.

--Also run badblocks for /dev/hdc. (There is additionally a non-destructive R/W mode; see ' man badblocks '.)

--1st thing I did after ordering a new 80GB Hitachi drive about a month ago, even before partitioning, was run badblocks R/W on the entire drive - and sure enough it went bad on me during the test. I sent it back and exchanged it for a Seagate 80GB. The Seagate tested OK and is doing fine. Remember to put a HD fan on the drive if it's 7200rpm or greater - they will help the drive last longer.

--Finally, if you have to replace the HD I would recommend the following:

o Test the entire new HD with badblocks in "destructive R/W mode" before partitioning it, to see if it fails.

o If it passes, consider formatting it with Reiserfs instead of ext3 (yes, I'm just a little biased) with the "noatime" mount option:



/dev/hdb11 /mnt/bkps2 reiserfs defaults,noatime,notail,rw 0 0


--If you will likely have more Large files than small on the partition, (or if you value speed over space-savings) "notail" makes sense as well. But I basically put that "noatime" option on *all* my Linux mounts, and 99% of my partitions are Reiserfs; and I haven't had a significant problem with that setup for YEARS.



I can not just re-install - this is NOT an option. I did the "just re-install" thing three times now. Once to get my old system over to my new system, Second to get my modem to work, and Third to get ALSA working - now, as I am getting something else on my system going - the solution AGAIN is to re-install - NO - NO WAY...

As for the magic keys - shesh, can you have "invented" anything less complicated ? In windows you have the "three finger salute", whereas in Linux, you have to do the "four finger salute" - now we have this "contorsionistic" set of key presses to do what??? Regain system control ???? The keyboard is locked, the system is locked, nothing is running, its dead when this happens...

How about this as an idea -=- The sound file (speach 102) is on my new 80 gig hard drive, the ReZound "main" 45 to 50 minute file used to generate these "smaller" speach files IS ON THE SAME DRIVE. K3b was trying to burn from files on the SAME DRIVE - when the system locks up, it is when I am doing "something" on the 80gig hard drive - this drive is hdc2 - whereas my system is located on hda1...

Could this be a failing hdc2 device???

How about some routines, or utilities, that can test the device? Or the file system on the device? Or the files on that device?

fsck doesn't seem to think that the "file system" is a problem, does it also test the files? I also noted during one of these "fsck" checks on the hdc2 device (80gig) that 24.5% was non-continueous - the device is not even 20% full - I thought that fsck checked and corrected these "defrag" issues?

Anyone have a disk test utility, something that I can ensure that my new hard drive, which apparently seems to be at the "root" of a common problem (system lock ups) may be causing these problems???

Thanks...
Cuddles

[Cuddles]

O K - this doesn't make any sense, someone explain why this works

Attempt was made to copy needed files off the hdc device (this includes, from my fstab file above, my Win98 install, and files, and my Linux "storage" area partitions) - the Win98 partition wasn't having problems, but when attempting to copy off stuff, my system hung - as it has before... The backspace trick did nothing, and the magic keys did nothing as well - a hard reset was the only way to get the system back.

As a try, I disabled the DMA on hdc device, all my other devices, including hda, have had DMA enambed from day one - rebooted and checked hdparm to ensure DMA is disabled on hdc, and it was...

I then tried to copy off my Win98 files, and it worked. On a roll, I went after the Linux storage (hdc2) - more than 15gig of files, started the copy, and it completed in around 1.5 hours of "constant" running - w/o a hitch... WHAT GIVES?????????

Why did DMA cause (assumption) this problem, especially when it was ALWAYS on all this time, and NOW, disabling it resolves the problem??? The same fstab file was unchanged, only DMA was disabled on this device... Could DMA have been the ONLY culprit on this issue all along??? How??? Why??? And why, now, without anything changing, is it not working, when all along it was working, without problems???

I was able to copy all my files (sound files, taking approximatelly 14gig) off the drive, after DMA was disabled, and when viewing and playing these "copied" files on to the hda device, I can play them, ReZound was able to load them, XMMS was able to play them, even speach 102, without problems, and I was able to "burn" the Cdrom#7, with this troublesome speach102 w/o problems....

Someone explain to me what was going on, and why DMA (could) be the problem, when all along it wasn't a problem????

Thanks for any information on this, I can't fathom why,
Cuddles
PS -=- "smart" was disabled on BIOS from day one, and Knoppix is not enabling it, from what I can tell.

[Dave_Bechtel]

--Could be either a kernel bug, motherboard IDE bug, or the HD's fault.

--Please post results of ' dmesg '. (You can edit-out anything that's not related to the IDE and HD stuff.) I'd like to know what kind of HD hdc is (manufacturer, model, and RPM), as well as what chipset is on the mobo IDE.

My edited dmesg looks like this:


Kernel command line: auto BOOT_IMAGE=Linux ro root=341 hda=scsi hdb=scsi hdc=scs
i hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce idebus=66

ide: Assuming 66MHz system bus speed for PIO modes
SIS5513: IDE controller at PCI slot 00:00.1
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS730 ATA 100 (1st gen) controller
ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 4D080H4, ATA DISK drive
hdb: ST380011A, ATA DISK drive
blk: queue c02f8600, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c02f8748, I/O limit 4095Mb (mask 0xffffffff)
hdc: GENERIC DVD DUAL 4XMax, ATAPI CD/DVD-ROM drive
hdd: DVD-ROM DVD-16X3H, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 160045200 sectors (81943 MB) w/2048KiB Cache, CHS=9962/255/63, UDMA(100)
hdb: attached ide-disk driver.
hdb: host protected area => 1
hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
ide-cd: passing drive hdc to ide-scsi emulation.
ide-cd: passing drive hdd to ide-scsi emulation.
hdc: attached ide-scsi driver.
hdd: attached ide-scsi driver.
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >
hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11 >


--Also, you might want to put "idebus=66" as a kernel parm in lilo, and see if it makes a difference. (the "append=" line.)

--Finally, check with your motherboard mfr and see if there's a flash update available for your chipset; sometimes those can fix things like DMA errors.

(As far as HD mfrs go, I've had Good luck with:

Maxtor, Seagate;

and Bad luck with:

Western Digital, Hitachi)

--Just so you know, SMART is enabled on my box; and all my HD's that are over 5400RPM have fans on them.

--Also, all my IDE cables are 80-pin and rated for (at least) ATA-100, or ATA-133. If you have a 40-pin cable on hdc (common for 2ndary controllers that are usually only connected to cdrom drives), that could be the problem right there.


O K - this doesn't make any sense, someone explain why this works

Attempt was made to copy needed files off the hdc device (this includes, from my fstab file above, my Win98 install, and files, and my Linux "storage" area partitions) - the Win98 partition wasn't having problems, but when attempting to copy off stuff, my system hung - as it has before... The backspace trick did nothing, and the magic keys did nothing as well - a hard reset was the only way to get the system back.

As a try, I disabled the DMA on hdc device, all my other devices, including hda, have had DMA enambed from day one - rebooted and checked hdparm to ensure DMA is disabled on hdc, and it was...

I then tried to copy off my Win98 files, and it worked. On a roll, I went after the Linux storage (hdc2) - more than 15gig of files, started the copy, and it completed in around 1.5 hours of "constant" running - w/o a hitch... WHAT GIVES?????????

Why did DMA cause (assumption) this problem, especially when it was ALWAYS on all this time, and NOW, disabling it resolves the problem??? The same fstab file was unchanged, only DMA was disabled on this device... Could DMA have been the ONLY culprit on this issue all along??? How??? Why??? And why, now, without anything changing, is it not working, when all along it was working, without problems???

I was able to copy all my files (sound files, taking approximatelly 14gig) off the drive, after DMA was disabled, and when viewing and playing these "copied" files on to the hda device, I can play them, ReZound was able to load them, XMMS was able to play them, even speach 102, without problems, and I was able to "burn" the Cdrom#7, with this troublesome speach102 w/o problems....

Someone explain to me what was going on, and why DMA (could) be the problem, when all along it wasn't a problem????

Thanks for any information on this, I can't fathom why,
Cuddles
PS -=- "smart" was disabled on BIOS from day one, and Knoppix is not enabling it, from what I can tell.

[Cuddles]

output from dmesg: (complete)

root@Polaris:/home/cuddles# dmesg
Linux version 2.4.22-xfs (root@Knoppix) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 SMP Fr Okt 3 20:36:25 CEST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
512MB LOWMEM available.
On node 0 totalpages: 131072
zone(0): 4096 pages.
zone(1): 126976 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=Linux ro root=301 hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce
ide_setup: hda=scsi
ide_setup: hdb=scsi
ide_setup: hdc=scsi
ide_setup: hdd=scsi
ide_setup: hde=scsi
ide_setup: hdf=scsi
ide_setup: hdg=scsi
ide_setup: hdh=scsi
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 1466.305 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 2922.90 BogoMIPS
Memory: 515168k/524288k available (1262k kernel code, 8732k reserved, 534k data, 132k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch ([email protected])
mtrr: detected mtrr type: Intel
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000
CPU0: AMD Athlon(tm) XP 1700+ stepping 00
per-CPU timeslice cutoff: 731.10 usecs.
SMP motherboard not detected.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1466.2929 MHz.
..... host bus clock speed is 266.5987 MHz.
cpu: 0, clocks: 2665987, slice: 1332993
CPU0<T0:2665984,T1:1332976,D:15,S:1332993,C:2665987>
Waiting on wait_init_idle (map = 0x0)
All processors have done init_idle
PCI: PCI BIOS revision 2.10 entry at 0xfb470, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/0686] at 00:07.0
Applying VIA southbridge workaround.
PCI: Disabling Via external APIC routing
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
vesafb: framebuffer at 0xd0000000, mapped to 0xe080d000, size 3072k
vesafb: mode is 1024x768x16, linelength=2048, pages=1
vesafb: protected mode interface info at c000:f910
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
pty: 256 Unix98 ptys configured
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
hda: HDS722540VLAT20, ATA DISK drive
hdb: SONY DVD-ROM DDU1611, ATAPI CD/DVD-ROM drive
hdc: SAMSUNG SP0802N, ATA DISK drive
hdd: OPTORITECD-RW CW5201, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 80418240 sectors (41174 MB) w/1794KiB Cache, CHS=5005/255/63
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 156368016 sectors (80060 MB) w/2048KiB Cache, CHS=9733/255/63
ide-cd: passing drive hdb to ide-scsi emulation.
ide-cd: passing drive hdd to ide-scsi emulation.
hdb: attached ide-scsi driver.
hdd: attached ide-scsi driver.
Partition check:
hda: hda1 hda3
hdc: hdc1 hdc2
ide: late registration of driver.
Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found
Highpoint HPT370 Softwareraid driver for linux version 0.02
Guestimating sector 80389004 for superblock
Guestimating sector 156344324 for superblock
driver for Silicon Image(tm) Medley(tm) hardware version 0.0.1: No raid array found
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: SONY Model: DVD-ROM DDU1611 Rev: GYS1
Type: CD-ROM ANSI SCSI revision: 02
Vendor: OPTORITE Model: CD-RW CW5201 Rev: 160E
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
sr0: scsi3-mmc drive: 0x/40x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
sr1: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 131072 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 144k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 132k freed
Adding Swap: 489972k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
spurious 8259A interrupt: IRQ7.
Real Time Clock Driver v1.10e
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 20:50:29 Oct 3 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 5 for device 00:07.2
PCI: Sharing IRQ 5 with 00:07.3
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 5 for device 00:07.3
PCI: Sharing IRQ 5 with 00:07.2
usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
hub.c: new USB device 00:07.2-2, assigned address 2
parport0: PC-style at 0x378 [PCSPP,EPP]
usb-uhci.c: interrupt, status 2, frame# 635
parport0: Printer, HEWLETT-PACKARD DESKJET 940C
parport_pc: Via 686A parallel port: io=0x378
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 440M
agpgart: Detected Via Apollo Pro KT133 chipset
agpgart: AGP aperture is 64M @ 0xe0000000
PCI: Found IRQ 10 for device 00:07.5
PCI: Setting latency timer of device 00:07.5 to 64
usb_control/bulk_msg: timeout
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: SanDisk Model: ImageMate II Rev: 1.30
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 15681 512-byte hdwr sectors (8 MB)
sda: Write Protect is off
sda: sda1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (4096 buckets, 32768 max) - 292 bytes per conntrack
blk: queue c0334b60, I/O limit 4095Mb (mask 0xffffffff)
NET4: Linux IPX 0.47 for NET4.0
IPX Portions Copyright (c) 1995 Caldera, Inc.
IPX Portions Copyright (c) 2000, 2001 Conectiva, Inc.
lp0: using parport0 (polling).
lp0: console ready
0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004

I "know" the new hard drive (the 80gig, connected as hdc) is a Samsung - can't recall what the 41 gig is, the one as hda, and the main system device...


Hope this helps,
Cuddles

[Dave_Bechtel]

Cuddles - any word on the HD / DMA issue? How are things running?

[Cuddles]

Dave,

Where things are at currently (update)

I disabled DMA on the Samsung (80gig) hdc device, and was able to copy off more than 15gig of data, and sound files, from the device, onto my "home" or hda device, the files copied without a hitch, and the copied files were "intact" and usable, completely able to be loaded into ReZound, and I also was able to burn more than 18 CD Audio discs (all without any problems)...

Since "stripping off" the files on the hdc device, the 80gig Samsung, I have not used it any further... I am not sure if the problem is resolved, nor do I "trust" the drive at this point, to place "important" files onto the device...

So, I guess I have a 80 gig device, that is running on my system, but don't dare use it, unless I can run something on my booted system, as it is at the moment, and feel a little more confident about it.

Cuddles

[fingers99]

I'd try copying redundant stuff over to it and interacting with it: maybe try (using CDRW media!) to recreate the original issue.

[Dave_Bechtel]

--Per my previous post, I recommend the following:

o Check with your motherboard mfr and see if there's a flash update available for your chipset; sometimes those can fix things like DMA errors.

o Enable SMART; and put a fan on the HD if it's more than 5400 RPM (likely.)

--Check to make sure that an 80-pin cable is connected to the drive, and rated for (at least) ATA-100, or ATA-133. If you have a 40-pin cable on hdc (common for 2ndary IDE controllers that are usually only connected to cdrom drives), that could be the problem right there.

--If none of this solves the DMA problem, return the drive and get another brand; this is what I had to do. (Hitachi Deathstar replaced with Seagate.) It's never good to have "known / suspected unreliable" devices on the system - computers are unstable enough as it is these days. ;-)


Dave,

Where things are at currently (update)

I disabled DMA on the Samsung (80gig) hdc device, and was able to copy off more than 15gig of data, and sound files, from the device, onto my "home" or hda device, the files copied without a hitch, and the copied files were "intact" and usable, completely able to be loaded into ReZound, and I also was able to burn more than 18 CD Audio discs (all without any problems)...

Since "stripping off" the files on the hdc device, the 80gig Samsung, I have not used it any further... I am not sure if the problem is resolved, nor do I "trust" the drive at this point, to place "important" files onto the device...

So, I guess I have a 80 gig device, that is running on my system, but don't dare use it, unless I can run something on my booted system, as it is at the moment, and feel a little more confident about it.

Cuddles