Greetings:
I was fiddling with skype and when i tried to grep my sound card (i
can listen, but i can't speak with skype) instead of the usual dmesg i
just got a whole bunch of these:
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
over and over...
[This message has also been posted to linux.debian.user.]
In article <[EMAIL PROTECTED]>, David Baron wrote:
>
> Can also be the power supply! I had to (temporarily) disconnect one of the CD
> drives to reduce the load. Not a single WD click-clack or DMA timeout since.
Second
ing. ;-)
Can also be the power supply! I had to (temporarily) disconnect one of the CD
drives to reduce the load. Not a single WD click-clack or DMA timeout since.
Guido Heumann wrote:
Shams Fantar schrieb:
I think that the hard disk really has a hardware problem. I'm going to
change it.
Subject closed. ;-)
Thank you for your help.
Regards,
Another thing you could try before replacing the harddrive is replacing
the IDE cable. I once had stran
Shams Fantar schrieb:
> I think that the hard disk really has a hardware problem. I'm going to
> change it.
>
> Subject closed. ;-)
>
> Thank you for your help.
>
> Regards,
>
Another thing you could try before replacing the harddrive is replacing
the IDE cable. I once had strange disk error m
On Sun, 26 Aug 2007 21:50:06 +0200
Shams Fantar <[EMAIL PROTECTED]> wrote:
> I think that the hard disk really has a hardware problem. I'm going to
> change it.
>
Let us know how it goes.
Cheers
Frank
--
Change the world one loan at a time - visit Kiva.org to find out how
I think that the hard disk really has a hardware problem. I'm going to
change it.
Subject closed. ;-)
Thank you for your help.
Regards,
--
Shams Fantar (http://snurf.info)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Frank McCormick wrote:
On Sat, 25 Aug 2007 22:06:34 +0200
Shams Fantar <[EMAIL PROTECTED]> wrote:
Shams Fantar wrote:
Frank McCormick wrote:
As I recall: fsck -n -c -v /dev/hda1
Ok.
After a "fsck", I have still the problem.
What do you think about it
On Sat, 25 Aug 2007 22:06:34 +0200
Shams Fantar <[EMAIL PROTECTED]> wrote:
> Shams Fantar wrote:
> > Frank McCormick wrote:
> >>
> >>As I recall: fsck -n -c -v /dev/hda1
> >
> > Ok.
> >
> >
>
> After a "fsck", I have still the problem.
>
> What do you think about it after some tests ?
Shams Fantar wrote:
Frank McCormick wrote:
As I recall: fsck -n -c -v /dev/hda1
Ok.
After a "fsck", I have still the problem.
What do you think about it after some tests ?
--
Shams Fantar (http://snurf.info)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsu
Frank McCormick wrote:
As I recall: fsck -n -c -v /dev/hda1
Ok.
I guess you know not to run it on a
mounted partition.
Yes, of course. :-)
That way it won't do anything to the file system, I still am not sure whether
the
-c option means it won't add bad blocks to the list, bu
Douglas A. Tutty wrote:
On Sat, Aug 25, 2007 at 03:28:02PM +0200, Shams Fantar wrote:
I also think this is a bug.. but I don't understand why (if it's a bug)
the problem happens suddenly! Maybe after an update ? I am not sure.
I use debian etch and the version of the Linux kernel is : 2.6
On Sat, 25 Aug 2007 15:28:02 +0200
Shams Fantar <[EMAIL PROTECTED]> wrote:
> Frank McCormick wrote:
> >I've been following this thread for quite a while - I have been
> > getting DMA timeout errors on boot for about a year - i am also running
> > SMART and
On Sat, Aug 25, 2007 at 03:28:02PM +0200, Shams Fantar wrote:
> I also think this is a bug.. but I don't understand why (if it's a bug)
> the problem happens suddenly! Maybe after an update ? I am not sure.
>
> I use debian etch and the version of the Linux kernel is : 2.6.18-4-486.
> I still
Frank McCormick wrote:
I've been following this thread for quite a while - I have been
getting DMA timeout errors on boot for about a year - i am also running
SMART and every test I have done shows no problem. Booted with the
install disk and run fschk so many time I have lost track.
D
Douglas A. Tutty wrote:
On Fri, Aug 24, 2007 at 08:12:28PM +0200, Shams Fantar wrote:
Douglas A. Tutty wrote:
Try shutdown, disable DMA in the bios, and reboot into single-user mode
(avoids mounting the drive rw). See if the messages show up in dmesg.
Then reboot into normal mode and
> > http://jumble.snurf.info/desktop/hard-disk
> >
> > So is it dead?
> >
>
> According to SMART, the drive is fine. If the filesystem badblocks
> check was OK then that seems to be OK too.
>
> So I don't know why you're having DMA errors. Hop
On Fri, Aug 24, 2007 at 08:12:28PM +0200, Shams Fantar wrote:
> Douglas A. Tutty wrote:
>
> >Try shutdown, disable DMA in the bios, and reboot into single-user mode
> >(avoids mounting the drive rw). See if the messages show up in dmesg.
> >Then reboot into normal mode and check syslog for that b
Douglas A. Tutty wrote:
Hi Shams,
Hi !
Try shutdown, disable DMA in the bios, and reboot into single-user mode
(avoids mounting the drive rw). See if the messages show up in dmesg.
Then reboot into normal mode and check syslog for that boot (ignore
previous boots).
There are the sa
xpiry: dma status == 0x61
> >>Aug 22 11:03:20 sithare kernel: hda: DMA timeout error
> >>Aug 22 11:03:20 sithare kernel: hda: dma timeout error: status=0x58 {
> >>DriveReady SeekComplete DataRequest Aug 22 11:03:20 sithare kernel: ide:
> >>failed opcode was: unk
if this message is a problem or not :
Aug 22 11:03:20 sithare kernel: hda: dma_timer_expiry: dma status == 0x61
Aug 22 11:03:20 sithare kernel: hda: DMA timeout error
Aug 22 11:03:20 sithare kernel: hda: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest Aug 22 11:03:20 sithare
me if this message is a problem or not :
>
> Aug 22 11:03:20 sithare kernel: hda: dma_timer_expiry: dma status == 0x61
> Aug 22 11:03:20 sithare kernel: hda: DMA timeout error
> Aug 22 11:03:20 sithare kernel: hda: dma timeout error: status=0x58 {
> DriveReady SeekComplete DataR
n I'm starting my desktop and it is starting on the kernel, here are
the logs[1].
I ask me if this message is a problem or not :
Aug 22 11:03:20 sithare kernel: hda: dma_timer_expiry: dma status == 0x61
Aug 22 11:03:20 sithare kernel: hda: DMA timeout error
Aug 22 11:03:20 sithare kernel:
On Sat, Jul 03, 2004 at 02:02:57PM -0400, Owen Mehegan wrote:
> Hello -
>
> The reason I'm submitting this to the Debian list is because this
> issue seems to be related to whatever kernel options Debian gives me,
> or perhaps the specific 2.4 version that Debian installs. In short,
> when I boot
--- Owen Mehegan <[EMAIL PROTECTED]> wrote:
> When the system is warm booting, I get these errors when it tries to
> enable dma (pulled from dmesg so you can see context):
> using_dma= 1 (on)
At your bootprompt, try booting with:
linux nodma
to see if that helps. If not, and the errors
get_event: Interface not connected
hda: 19640880 sectors (10056 MB) w/384KiB Cache, CHS=19485/16/63, UDMA(33)
Partition check:
hda:<4>hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
[PTBL] [1222
hda11 >
> > hdb:<4>hdb: dma_timer_expiry: dma status == 0x61
> > hdb: error waiting for DMA
> > hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete
> > DataRequest }
>
> is hdparm configures hdds on start-up ? perhaps it c
hda9 hda10 hda11 >
> hdb:<4>hdb: dma_timer_expiry: dma status == 0x61
> hdb: error waiting for DMA
> hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete
> DataRequest }
is hdparm configures hdds on start-up ? perhaps it configures yoru hard
dri
On Mon, Jan 12, 2004 at 08:00:40PM +0100, didier gaumet wrote:
> Akira Kitada wrote:
>
> [...]
> > Partition check:
> > hda:<4>hda: dma_timer_expiry: dma status == 0x61
> > hda: error waiting for DMA
> > hda: dma timeout retry: status=0x5
REBALL, bad one)
Partition check:
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 >
hdb:<4>hdb: dma_timer_expiry: dma status == 0x61
hdb: error waiting for DMA
hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
--
On Sun, Jan 11, 2004 at 10:16:02PM +0900, Akira Kitada <[EMAIL PROTECTED]> wrote:
> (please tell me if you feel
> this mail focus on off-topic subject.
> and, if possible, appropriate place, too)
Well, this is a good place I think even if a little off-topic.
> I can use new hdd, Deskstar, with dma
if it helps, there is hdparm to check hd status
--
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
additional information. (sorry for my verbose mail)
(please tell me if you feel
this mail focus on off-topic subject.
and, if possible, appropriate place, too)
I've took another approch to get by.
my plan is ...
1. installing another OSes, such as FreeBSD 4.9 and Windows98,
2. make sure where DMA
status == 0x61
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
blk: queue c04102a0, I/O limit 4095Mb (mask 0x)
hda1 hda2 hda3 <<4>hda: dma_timer_expiry: dma status == 0x61
hda: error waiting for DMA
hda: dma timeout retry: st
On Tue, Mar 02, 1999 at 15:13 -0500, Raymond A. Ingles wrote:
> On Tue, 2 Mar 1999, Dave Swegen wrote:
>
> > I just recently bought an Asus P5A motherboard, and as it has UDMA support,
> > I thought I'd try enabling it using a patch which is available for the
> > 2.2.2 kernel. Now I know that at
On Tue, 2 Mar 1999, Dave Swegen wrote:
> I just recently bought an Asus P5A motherboard, and as it has UDMA support,
> I thought I'd try enabling it using a patch which is available for the
> 2.2.2 kernel. Now I know that at least two other people have successfully
> used this patch (doogie and ak
I just recently bought an Asus P5A motherboard, and as it has UDMA support,
I thought I'd try enabling it using a patch which is available for the
2.2.2 kernel. Now I know that at least two other people have successfully
used this patch (doogie and aklein on #debian). The problem is that a) one
of
37 matches
Mail list logo
