From: "rui.p.m.sousa@clix.pt" <rui.p.m.sousa@clix.pt>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: manuel@mclure.org (Manuel McLure),
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up
Date: Mon, 13 Aug 2001 11:08:54 GMT [thread overview]
Message-ID: <20010813110855.9358.qmail@webmail.clix.pt> (raw)
In-Reply-To: <E15W1eR-000691-00@the-village.bc.nu>
In-Reply-To: <E15W1eR-000691-00@the-village.bc.nu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1011 bytes --]
Alan Cox writes:
Did you have any lockups with non Athlon
motherboards?
>> On 2001.08.12 05:04 Alan Cox wrote:
>> > The in kernel one seemed fine. The 2.4.8 update one is definitely broken
>> > on
>> > SMP boxes
>>
>> I'm getting 2.4.8 Oopsen that seem to be in emu10k1 code on UP - see my
>> message "2.4.8 oops in ksoftirqd_CPU0"...
>
> Yep. So far the new driver that Linus took from a non maintaier breaks
>
> SMP
> Some mixers
> Uniprocessor with some cards
> Surround sound (spews noise on cards)
>
> so I think Linus should do the only sane thing - back it out. I'm backing
> it out of -ac. Of my three boxes, one spews noise, one locks up smp and
> one works.
>
> Alan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Crie o seu Email Grátis no Clix em
http://registo.clix.pt/
next prev parent reply other threads:[~2001-08-13 11:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 2:52 Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up Eric S. Raymond
[not found] ` <997611708.29909.22.camel@DESK-2>
2001-08-12 10:23 ` Jeffrey Ingber
2001-08-12 12:04 ` Alan Cox
2001-08-12 18:31 ` Manuel McLure
2001-08-12 20:15 ` Alan Cox
2001-08-12 20:30 ` Nerijus Baliunas
2001-08-13 3:27 ` Robert Love
2001-08-12 20:35 ` Manuel McLure
2001-08-12 21:59 ` Manuel McLure
2001-08-12 22:24 ` Linus Torvalds
2001-08-12 22:55 ` Manuel McLure
2001-08-12 22:59 ` Linus Torvalds
2001-08-12 23:15 ` Manuel McLure
2001-08-13 0:36 ` Paul G. Allen
2001-08-13 1:39 ` Justin A
2001-08-13 3:08 ` Mike Frisch
2001-08-13 1:00 ` Linus Torvalds
2001-08-13 1:33 ` Paul G. Allen
2001-08-13 1:50 ` Nicholas Knight
2001-08-12 22:10 ` Linus Torvalds
2001-08-12 22:18 ` Alan Cox
2001-08-12 22:21 ` Dax Kelson
2001-08-12 22:31 ` Linus Torvalds
2001-08-16 23:28 ` Pavel Machek
2001-08-17 20:33 ` Alan Cox
2001-08-13 11:08 ` rui.p.m.sousa [this message]
[not found] <no.id>
2001-08-12 22:30 ` Alan Cox
2001-08-13 12:16 ` Alan Cox
2001-08-13 12:19 ` rui.p.m.sousa
2001-08-13 12:19 ` Alan Cox
2001-08-13 12:35 ` Alan Cox
2001-08-13 12:43 ` Tobias Ringstrom
2001-08-13 12:47 ` Anton Altaparmakov
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 18:53 Ryan C. Bonham
2001-08-13 18:58 ` Daniel T. Chen
2001-08-13 18:54 Anton Altaparmakov
2001-08-13 19:11 Ryan C. Bonham
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=20010813110855.9358.qmail@webmail.clix.pt \
--to=rui.p.m.sousa@clix.pt \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel@mclure.org \
--cc=torvalds@transmeta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox