The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jurriaan on adsl-gate <thunder7@xs4all.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3-mm1: scheduling while atomic (ext3?)
Date: Wed, 13 Aug 2003 11:19:58 +0200	[thread overview]
Message-ID: <20030813091958.GA30746@gates.of.nowhere> (raw)
In-Reply-To: <20030813014746.412660ae.akpm@osdl.org>

On Wed, Aug 13, 2003 at 01:47:46AM -0700, Andrew Morton wrote:
> Jurriaan <thunder7@xs4all.nl> wrote:
> >
> > Aug 13 06:47:48 middle -- MARK --
> >  Aug 13 06:53:03 middle kernel:  printing eip:
> >  Aug 13 06:53:03 middle kernel: c016c14a
> >  Aug 13 06:53:03 middle kernel: Oops: 0000 [#1]
> >  Aug 13 06:53:03 middle kernel: PREEMPT 
> >  Aug 13 06:53:03 middle kernel: CPU:    0
> >  Aug 13 06:53:03 middle kernel: EIP:    0060:[<c016c14a>]    Not tainted VLI
> >  Aug 13 06:53:03 middle kernel: EFLAGS: 00010286
> >  Aug 13 06:53:03 middle kernel: EIP is at find_inode_fast+0x1a/0x60
> 
> And indeed, your %edx is zero.
> 
> But if a prefetch of zero oopses then we should be oopsing in there all the
> time.
> 
> hlist_for_each() is completely assuming that prefetch(0) is safe, and you
> undoubtedly oopsed doing it.
> 
> 
> Colour me confused, and let me Cc lots of x86 guys ;)
> 
> Exactly what sort of CPU are you using?
> -
AMD Athlon XP2400+ on a VIA KT400 chipset, single CPU-system.

Kind regards,
Jurriaan

  reply	other threads:[~2003-08-13  9:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  4:56 2.6.0-test3-mm1: scheduling while atomic (ext3?) Jurriaan
2003-08-13  8:47 ` Andrew Morton
2003-08-13  9:19   ` Jurriaan on adsl-gate [this message]
2003-08-13  9:55     ` Andrew Morton
2003-08-13 11:06       ` Alan Cox
2003-08-13 11:25         ` Andrew Morton
2003-08-13 11:40           ` Alan Cox
2003-08-18 12:08           ` Pavel Machek
2003-08-13 11:06   ` Andi Kleen
     [not found] <20030813045638.GA9713@middle.of.nowhere.suse.lists.linux.kernel>
     [not found] ` <20030813014746.412660ae.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]   ` <20030813091958.GA30746@gates.of.nowhere.suse.lists.linux.kernel>
     [not found]     ` <20030813025542.32429718.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]       ` <1060772769.8009.4.camel@localhost.localdomain.suse.lists.linux.kernel>
2003-08-13 11:17         ` Andi Kleen
     [not found]         ` <20030813042544.5064b3f4.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]           ` <1060774803.8008.24.camel@localhost.localdomain.suse.lists.linux.kernel>
2003-08-13 12:10             ` Andi Kleen
2003-08-13 12:48               ` Alan Cox
2003-08-13 13:14                 ` Andi Kleen
2003-08-13 14:09                   ` Alan Cox
2003-08-13 14:20                     ` Andi Kleen
2003-08-13 15:20                       ` Alan Cox
2003-08-13 15:32                         ` Andi Kleen
2003-08-13 18:44                           ` Alan Cox
2003-08-13 18:53                             ` Andi Kleen
2003-08-13 16:39                         ` Dave Jones
2003-08-13 18:34                           ` Alan Cox
2003-08-13 20:12                             ` Dave Jones
2003-08-13 18:37                           ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 18:59 richard.brunner

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=20030813091958.GA30746@gates.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=akpm@osdl.org \
    --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