From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops with 2.6.1-rc1 and rc-3
Date: Mon, 02 Feb 2004 21:54:18 +0100 [thread overview]
Message-ID: <401EB8FA.2060108@gmx.de> (raw)
In-Reply-To: <401EB859.9090200@gmx.de>
Prakash K. Cheemplavam wrote:
> Len Brown wrote:
>
>>>> handlers:
>>>> [<c02a6b50>] (ide_intr+0x0/0x190)
>>>> [<c03248c0>] (snd_intel8x0_interrupt+0x0/0x210)
>>>> Disabling IRQ #11
>>>> irq 11: nobody cared!
>>
>>
>>
>> dmesg -s40000 output (or serial console log if dmesg unavailable)
>> /proc/interrupts
>
>
> This is starting to get stupid: I tried recreating the oops with rc2 and
> rc2-mm2, but this time they started up normal. Currently I am even using
> a mm2 based kernel. But 2.6.2-rc3 still oopses. The problem is it
BTW, the only maybe affecting thing I change in the meanwhileis using
the newest nvidia binary driver 53.36. Could something of it survive to
the next boot (without powering the machin down)? Or might above oops
just be a timing issue?
Prakash
next prev parent reply other threads:[~2004-02-02 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB18@hdsmsx402.hd.intel.com>
2004-02-01 19:49 ` oops with 2.6.1-rc1 and rc-3 Len Brown
2004-02-02 8:45 ` Prakash K. Cheemplavam
2004-02-02 18:59 ` Len Brown
2004-02-02 20:51 ` Prakash K. Cheemplavam
2004-02-02 20:54 ` Prakash K. Cheemplavam [this message]
2004-01-31 7:28 [Swsusp-devel] Software Suspend 2.0 Nigel Cunningham
2004-01-31 7:38 ` Joseph Pingenot
2004-01-31 8:32 ` Nigel Cunningham
2004-01-31 9:03 ` Prakash K. Cheemplavam
2004-01-31 9:08 ` Nigel Cunningham
2004-01-31 9:19 ` Prakash K. Cheemplavam
2004-01-31 9:51 ` Nigel Cunningham
2004-01-31 10:43 ` Prakash K. Cheemplavam
2004-01-31 13:25 ` Måns Rullgård
2004-01-31 23:11 ` Joseph Pingenot
2004-02-01 0:26 ` Micha Feigin
2004-02-01 1:48 ` oops with 2.6.1-rc1 and rc-3 Prakash K. Cheemplavam
2004-02-01 2:54 ` Micha Feigin
2004-02-01 10:36 ` Prakash K. Cheemplavam
2004-02-01 11:37 ` Prakash K. Cheemplavam
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=401EB8FA.2060108@gmx.de \
--to=prakashkc@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox