From: Prasanna P Subash <psubash@turbolinux.com>
To: Gerd Knorr <kraxel@goldbach.in-berlin.de>
Cc: msg2@po.cwru.edu, John Jasen <jjasen1@umbc.edu>,
linux-kernel@vger.kernel.org,
AmNet Computers <amnet@amnet-comp.com>
Subject: Re: bttv problems in 2.4.0/2.4.1
Date: Wed, 31 Jan 2001 08:59:48 -0800 [thread overview]
Message-ID: <20010131085948.A26240@turbolinux.com> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0101301951040.887333-100000@irix2.gl.umbc.edu> <Pine.LNX.4.32.0101302004420.1138-100000@cheetah.STUDENT.cwru.edu> <200101310741.f0V7fj600833@bogomips.masq.in-berlin.de>
In-Reply-To: <200101310741.f0V7fj600833@bogomips.masq.in-berlin.de>; from Gerd Knorr on Wed, Jan 31, 2001 at 08:41:45AM +0100
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
My bttv is at IRQ 3 and it still hangs the machine :(
I dont even have acpi built in.
btw I am testing with 2.4.1-pre9
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | When the sun shineth, make hay. -- John
of a GNU generation -o) | Heywood
Kernel 2.4.0-ac4 /\\ |
on a i686 _\\_v |
|
------------------------------------------------------------------------
On Wed, Jan 31, 2001 at 08:41:45AM +0100, Gerd Knorr wrote:
> > > > 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.
> >
> > I will try this, but my card has (and does) worked with irq sharing for
> > a long time. Its entry in /proc/interrupts:
> > 9: 164935 165896 IO-APIC-level acpi, bttv
> ^^^^
> What happens with acpi disabled? The power-down at boot could be caused by
> the acpi power management maybe ...
>
> Gerd
>
> --
> Get back there in front of the computer NOW. Christmas can wait.
> -- Linus "the Grinch" Torvalds, 24 Dec 2000 on linux-kernel
> -
> 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 17:00 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 [this message]
2001-01-31 1:15 ` Prasanna P Subash
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=20010131085948.A26240@turbolinux.com \
--to=psubash@turbolinux.com \
--cc=amnet@amnet-comp.com \
--cc=jjasen1@umbc.edu \
--cc=kraxel@goldbach.in-berlin.de \
--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.