All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.44 (now 2.5.46-c929): Strange oopses triggered by ...
Date: Wed, 6 Nov 2002 23:09:20 +0200	[thread overview]
Message-ID: <6C5F7CA168B@vcnet.vc.cvut.cz> (raw)

On 25 Oct 02 at 11:19, Petr Vandrovec wrote:
> On 23 Oct 02 at 17:57, Petr Vandrovec wrote:
> 
> > Hi,
> >   I just left my 2.5.44 box unattended for hour and half, and when
> > I came back, I saw very strange things on screen:
> 
> Machine did it again yesterday 7:55 morning, after having ~10 hours
> uptime. All three dumps are same, with minor difference in last one:
> *pde is 024c4067, and Process line is 'cat (pid: 11497, threadinfo=c3960000,
> task=d1c3a780)'... All other values are same.

I'm getting really nervous :-( Is kdb able to track who caused unbalanced
in_atomic() incrementation? 

After more than week of stable system I run simple 
"arp vanicka.vc.cvut.cz" few minutes ago, and after arp output I got 
sleeping function called from illegal context, quickly followed by two
scheduling while atomic, and finally it died because of userspace faults 
when in_atomic() is != 0 are treated as kernel ones...

As I saw nobody else reporting this or simillar problem, I'll start
looking at e100 driver I use. Maybe it did not occured because of I
was running -acX kernels since 25th Oct until yesterday. Anybody knows?
                                                Thanks,
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz

Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Call Trace:
   [..........] __might_sleep+0x43/0x47
   [..........] seq_read
   ...........  vfs_read
   ...........  sys_read
   [..........] syscall_call+0x7/0xb
  
bad: scheduling while atomic!
   [..........] schedule
   ............ sys_read
   [..........] work_resched
   
bad: scheduling while atomic!
   [..........] schedule
   ............ sys_munmap
   [..........] work_resched

Unable to handle kernel paging request...

...
EIP: 0x4004DB65
...
Process: arp



             reply	other threads:[~2002-11-06 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 21:09 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06 21:49 2.5.44 (now 2.5.46-c929): Strange oopses triggered by Petr Vandrovec

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=6C5F7CA168B@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --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 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.