From: Prasanna P Subash <psubash@turbolinux.com>
To: John Jasen <jjasen1@umbc.edu>
Cc: Matthew Gabeler-Lee <msg2@po.cwru.edu>,
linux-kernel@vger.kernel.org,
AmNet Computers <amnet@amnet-comp.com>
Subject: Re: bttv problems in 2.4.0/2.4.1
Date: Tue, 30 Jan 2001 17:15:28 -0800 [thread overview]
Message-ID: <20010130171528.B25507@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0101301830330.1138-100000@cheetah.STUDENT.cwru.edu> <Pine.SGI.4.31L.02.0101301951040.887333-100000@irix2.gl.umbc.edu>
In-Reply-To: <Pine.SGI.4.31L.02.0101301951040.887333-100000@irix2.gl.umbc.edu>; from John Jasen on Tue, Jan 30, 2001 at 07:53:11PM -0500
[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]
I have experienced similar issues with 2.4.0 and its test. I have a bttv848 chipset.
I even tried compiling in kdb as a part of the kernel to see if it oopses, but no luck.
I will try trying 0.7.47 today.
this works on 2.2.16, last time i tried.
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | "You've got to think about tomorrow!"
of a GNU generation -o) | "TOMORROW! I haven't even prepared for
Kernel 2.4.0-ac4 /\\ | yesterday* yet!"
on a i686 _\\_v |
|
------------------------------------------------------------------------
On Tue, Jan 30, 2001 at 07:53:11PM -0500, John Jasen wrote:
> On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
>
> > These errors all occur in the same way (as near as I can tell) in
> > kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel),
> > 0.7.53, and 0.7.55.
> >
> > I am currently using 2.4.0-test10 with bttv 0.7.47, which works fine.
> >
> > I have sent all this info to Gerd Knorr but, as far as I know, he hasn't
> > been able to track down the bug yet. I thought that by posting here,
> > more eyes might at least make more reports of similar situations that
> > might help track down the problem.
>
> Try flipping the card into a different slot. A lot of the cards
> exceptionally do not like IRQ/DMA sharing, and a lot of the motherboards
> share them between different slots.
>
> --
> -- John E. Jasen (jjasen1@umbc.edu)
> -- In theory, theory and practise are the same. In practise, they aren't.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-01-31 1:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 23:50 bttv problems in 2.4.0/2.4.1 Matthew Gabeler-Lee
2001-01-31 0:53 ` John Jasen
2001-01-31 1:06 ` Matthew Gabeler-Lee
2001-01-31 7:41 ` Gerd Knorr
2001-01-31 16:59 ` Prasanna P Subash
2001-01-31 1:15 ` Prasanna P Subash [this message]
2001-01-31 1:57 ` adrian
2001-01-31 2:05 ` Matthew Gabeler-Lee
2001-01-31 13:06 ` adrian
2001-01-31 21:39 ` Gerd Knorr
2001-02-01 3:23 ` adrian
2001-01-31 8:59 ` bttv problems in 2.4.0/2.4.1 PAL_BG archan
2001-01-31 14:51 ` John Jasen
2001-02-01 4:14 ` archan
2001-02-10 0:02 ` bttv problems in 2.4.0/2.4.1 Dr. Kelsey Hudson
2001-02-10 0:46 ` Matthew Gabeler-Lee
2001-02-10 3:37 ` Matthew Gabeler-Lee
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=20010130171528.B25507@turbolinux.com \
--to=psubash@turbolinux.com \
--cc=amnet@amnet-comp.com \
--cc=jjasen1@umbc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=msg2@po.cwru.edu \
/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.