All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Astals Cid <albert@miraveo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_via oops on copying files?
Date: Tue, 19 May 2009 22:35:56 +0200	[thread overview]
Message-ID: <200905192235.56916.albert@miraveo.com> (raw)
In-Reply-To: <20090519211052.55d01236@lxorguk.ukuu.org.uk>

A Dimarts, 19 de maig de 2009, Alan Cox va escriure:
> On Tue, 19 May 2009 09:16:55 -0700
>
> "Albert Astals Cid" <albert@miraveo.com> wrote:
> > Please CC me, i'm not in the list.
> >
> > Not sure if this or bugzilla is preferred, so doing both, shout me if i
> > should wait on bugzilla.
>
> None of this looks IDE related - the first looks like an IRQ routing
> problem which is usually but not always a buggy BIOS. The random crashes
> look like faulty hardware but its always hard to tell hardware and
> software bugs.
>
> Does the system pass memtest86 for 24 hours ?

Hi Alan, 

If i don't use the Compact Flash attached to the miniPCI->IDE->CF adapter it 
works like a charm, it's only when i start writting (reading seems to work 
fine) from the CF card that the kernel oopses, that's why i thought it might 
be IDE/sata_via related.

Is it possible to work around IRQ problems? If so I guess this is not the 
correct mailing list for that question anymore, so can you suggest a better 
one? And if it's not possible i guess all i have left is bugging my hardware 
manufacturer.

Thanks,
  Albert

  reply	other threads:[~2009-05-19 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 16:16 sata_via oops on copying files? Albert Astals Cid
2009-05-19 20:10 ` Alan Cox
2009-05-19 20:35   ` Albert Astals Cid [this message]
2009-05-20  0:04     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2009-05-20 10:00 Albert Astals Cid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200905192235.56916.albert@miraveo.com \
    --to=albert@miraveo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.