[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bad_page_fault oops

To: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
Subject: Re: bad_page_fault oops
From: "Roberto A. Foglietta" <roberto.foglietta@xxxxxxxxx>
Date: Mon, 5 May 2008 14:19:55 +0200
Cc: "Gaurav Aggarwal" <Gaurav.Aggarwal@xxxxxxxxxx>, "Linux Kernel List" <kernelnewbies@xxxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ZgXPnPYdNnnINH/FLFvsXEn7HfV/y1y0YzQ1doaLlT4=; b=K5vi/TO+d9PIzTmvGCweKR15C2Su0zbfsa1hkfXQRat6qA0VLb98jXYYsF1WMXkBG6q01HUpKBIZx9RCSICpfCICuJhuC1gXhWTcwaWDffGrtznOsRp1Fi+2Z31QoD0xd+lQek5RHRNzKeTgryMxYvNQUhtvPx0TPEQorAWCCEc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jentnvcRG8QVi3Zj8O+/YlFPOiq5lxovcLQc5DYZ8tyCTXDA4Y1MnhttIt6rA5Xs/hnjDAKyX/sbk/vQDPD4EYgu2U2sV+uo9BiTPDYpXKB0KV00JFCe+HfSHD1WHDbW2fWfwHHEB9t/pztOgx0Kswwq4xI7QViRLY4XcEo1v68=
In-reply-to: <f284c33d0804172035j4cf6bc16sb6b6aba85d0b3c47@mail.gmail.com>
List-archive: <http://mail.nl.linux.org/kernelnewbies/>
List-help: <mailto:ecartis@nl.linux.org?Subject=help>
List-id: <kernelnewbies.nl.linux.org>
List-owner: <mailto:ecartis-owner@nl.linux.org>
List-post: <mailto:kernelnewbies@nl.linux.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=unsubscribe>
References: <e4c675870804170103q68dc8713haa4d9f882942307e@mail.gmail.com> <BAC4353025D7FA47A8CD4EFD6A69DA1C042853E9@banpexch01.citrite.net> <f284c33d0804172035j4cf6bc16sb6b6aba85d0b3c47@mail.gmail.com>
Sender: kernelnewbies-bounce@xxxxxxxxxxxx

2008/4/18 Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>:
> Hi alll
>
>
>  On Thu, Apr 17, 2008 at 4:45 PM, Gaurav Aggarwal
>  <Gaurav.Aggarwal@xxxxxxxxxx> wrote:
>  > "BUG: scheduling while atomic: snoopy/0x00000001/1666"
>  >
>  >  From this statement it looks that you are calling blocking/sleeping
>  >  function inside the critical section or code path where it's not
>  >  allowed. This will be really helpful if you just describe about the
>  >  stuff that you are trying to do when you get this error.
>  >  To know more about oops message you can read the oops-tracing.txt doc
>  >  from linux-2.x.y/Documentation folder.
>
>  I try to sharpen the analysis. The stack trace show handle_page_fault,
>  thus it is possible there's blocking memory allocation inside non
>  preemptible code section.
>

 Thank you for your suggestion but... in a way or another I still see
some of these oops.
 The attached text file is reporting some warnings from pcmcia-cs at
boot start and two oopses.
 The first oops happened during the startup and the second one happen
calling hwclock in shutdown.
 Despite the oops message I think could be exist a relation between
pcmcia-cs warnings and these oops.
 Do you agree? If yes: how could I verify a thing like this?

 Thanks in advance,
-- 
/roberto

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ

Follow-Ups:
- Re: bad_page_fault oops
  - From: Roberto A. Foglietta

Prev by Date: Re: Stack at high memory locations
Next by Date: Re: bad_page_fault oops
Previous by thread: Re: EXPORT_SYMBOL Vs extern?
Next by thread: Re: bad_page_fault oops
Index(es):
- Date
- Thread