From: Michael Buesch <mbuesch@freenet.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] fix address passing of unknown_bootoption
Date: Mon, 8 Nov 2004 09:43:43 +0100 [thread overview]
Message-ID: <200411080943.43734.mbuesch@freenet.de> (raw)
In-Reply-To: <418EC395.3070002@osdl.org>
Quoting "Randy.Dunlap" <rddunlap@osdl.org>:
> > hm, I don't know what happened there. Maybe the value of pm_idle in
> > cpu_idle() is garbage. Or maybe not.
>
> Zwane and someone else had patches for that happening IIRC
> a month or 2 back.
> I can dig them out if wanted... Michael, want to try?
Yes, sure. Please.
oh, one second before pressing the send button for this mail I had
another panic. 8-}
Unable to handle kernel paging request at virtual address 00020800
printing eip:
00020800
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in: ipv6 ohci_hcd tuner tvaudio msp3400 bttv video_buf btcx_risc nvidia ehci_hcd uhci_hcd usbcore intel_agp agpgart evdev
CPU: 0
EIP: 0060:[<00020800>] Tainted: P VLI
EFLAGS: 00010296 (2.6.9-ck3-ac6-nozeroram)
EIP is at 0x20800
eax: 00000001 ebx: b03e8000 ecx: 00000001 edx: 00000001
esi: 00099100 edi: b01020a7 ebp: 0045c007 esp: b03e9fec
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=b03e8000 task=b034cac0)
Stack: b03ea81c 000000db b03ea310 b04162a0 b0100211
Call Trace:
[<b03ea81c>] start_kernel+0x139/0x152
[<b03ea310>] unknown_bootoption+0x0/0x171
Code: Bad EIP value.
<0>Kernel panic - not syncing: Attempted to kill the idle task!
next prev parent reply other threads:[~2004-11-08 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 21:47 [PATCH 2.6] fix address passing of unknown_bootoption Michael Buesch
2004-11-08 0:42 ` Andrew Morton
2004-11-08 0:53 ` Randy.Dunlap
2004-11-08 8:43 ` Michael Buesch [this message]
2004-11-08 17:42 ` Randy.Dunlap
2004-11-08 21:40 ` Michael Buesch
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=200411080943.43734.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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.