All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: paulmck@us.ibm.com, dipankar@in.ibm.com, rusty@au1.ibm.com,
	ak@suse.de, gareth@valinux.com, davidm@hpl.hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] Strange code in cpu_idle()
Date: Mon, 6 Dec 2004 11:01:01 +0100	[thread overview]
Message-ID: <200412061101.07264.mbuesch@freenet.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0412060250410.1036@montezuma.fsmlabs.com>

[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]

Quoting Zwane Mwaikambo <zwane@arm.linux.org.uk>:
> On Mon, 6 Dec 2004, Michael Buesch wrote:
> 
> > Hi Paul,
> > 
> > Well, your mail is _very_ interresting for me.
> > 
> > I get this oops for weeks with several kernel versions now:
> 
> There shouldn't be any oopses with the changes in question, the original 
> bugfix was for crashes whilst unloading ACPI processor or APM module.
> 
> > Unable to handle kernel paging request at virtual address 00099108
> >  printing eip:
> > b01010c0
> > *pde = 00000000
> > Oops: 0000 [#1]
> > SMP 
> > Modules linked in: nfs lockd sunrpc nvidia ipv6 ohci_hcd tuner tvaudio msp3400 bttv video_buf firmware_class btcx_risc ehci_hcd uhci_hcd usbcore intel_agp agpgart evdev
> > CPU:    0
> > EIP:    0060:[<b01010c0>]    Tainted: P      VLI
> > EFLAGS: 00010286   (2.6.10-rc2-ck2-nozeroram-findvmastat)
> 
> It would be a lot easier to debug with a vanilla kernel and no nvidia 
> loaded.
> 
> > The above oops shows a crash when we try to access the
> > thread_info->flags field. This is done by need_resched()
> > to check the TIF_NEED_RESCHED flag.
> > I don't know how to interpret the oops correctly to find
> > the source of the crash.
> 
> Looks like thread_info was. Wow i think you're in a different world of 
> hurt. If you can reproduce with less patches and no nvidia please send 
> over the bugreport.

Yes. That's the problem.
It's impossible to reproduce and it's pure luck when it's triggered.
I'll look what I can do. nvidia already received this bugreport.

> Thanks,
>  Zwane
> 
> 
> 

-- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-12-06 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 23:11 [RFC] Strange code in cpu_idle() Paul E. McKenney
2004-12-06  0:32 ` Michael Buesch
2004-12-06  9:54   ` Zwane Mwaikambo
2004-12-06 10:01     ` Michael Buesch [this message]
2004-12-06  9:47 ` Zwane Mwaikambo
2004-12-06 11:02   ` Dipankar Sarma
2004-12-06 14:33     ` Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2004-12-06  9:13 Li, Shaohua

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=200412061101.07264.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=ak@suse.de \
    --cc=davidm@hpl.hp.com \
    --cc=dipankar@in.ibm.com \
    --cc=gareth@valinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=rusty@au1.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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.