public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: 2.5.1-pre5 not easy to boot with devfs
Date: Sat, 01 Dec 2001 10:59:33 +0100	[thread overview]
Message-ID: <3C08AA05.C3218C82@wanadoo.fr> (raw)
In-Reply-To: <3C085FF3.813BAA57@wanadoo.fr> <9u9qas$1eo$1@penguin.transmeta.com> <200112010701.fB171N824084@vindaloo.ras.ucalgary.ca>

This Oops comes after starting devfsd by hand, it is possibly more
reliable than the previous one :

Unable to handle kernel paging request at virtual address 5a5a5a5e 
 printing eip: 
c01516f9 
*pde = 00000000 
Oops: 0002 
CPU:    0 
EIP:    0010:[devfs_put+13/188]    Tainted: P  
EFLAGS: 00013206 
eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 00000016   edx: 5a5a5a5a 
esi: 00000000   edi: 00000026   ebp: 00000000   esp: cf631f40 
ds: 0018   es: 0018   ss: 0018 
Process devfsd (pid: 144, stackpage=cf631000) 
Stack: 00000026 c015419c 5a5a5a5a cf96ba34 ffffffea 00000000 00000420
cfb80800  
c01e7200 cf4f2240 5a5a5a5a 000003fa 00000000 00000000 00000001 00000000  
cf630000 00000000 00000000 00000000 cf630000 c01e722c c01e722c c012f5e6  
Call Trace: [devfsd_read+852/972] [sys_read+150/204]
[system_call+51/56]  
 
Code: ff 4b 04 0f 94 c0 84 c0 0f 84 9e 00 00 00 3b 1d 00 15 21 c0  

ksymoops 2.4.3 on i686 2.5.1-pre5.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.1-pre5/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Unable to handle kernel paging request at virtual address 5a5a5a5e 
c01516f9 
*pde = 00000000 
Oops: 0002 
CPU:    0 
EIP:    0010:[devfs_put+13/188]    Tainted: P  
EFLAGS: 00013206 
eax: 5a5a5a5a   ebx: 5a5a5a5a   ecx: 00000016   edx: 5a5a5a5a 
esi: 00000000   edi: 00000026   ebp: 00000000   esp: cf631f40 
ds: 0018   es: 0018   ss: 0018 
Process devfsd (pid: 144, stackpage=cf631000) 
Stack: 00000026 c015419c 5a5a5a5a cf96ba34 ffffffea 00000000 00000420
cfb80800  
c01e7200 cf4f2240 5a5a5a5a 000003fa 00000000 00000000 00000001 00000000  
cf630000 00000000 00000000 00000000 cf630000 c01e722c c01e722c c012f5e6  
Call Trace: [devfsd_read+852/972] [sys_read+150/204]
[system_call+51/56]  
Code: ff 4b 04 0f 94 c0 84 c0 0f 84 9e 00 00 00 3b 1d 00 15 21 c0  
Using defaults from ksymoops -t elf32-i386 -a i386

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   ff 4b 04                  decl   0x4(%ebx)
Code;  00000002 Before first symbol
   3:   0f 94 c0                  sete   %al
Code;  00000006 Before first symbol
   6:   84 c0                     test   %al,%al
Code;  00000008 Before first symbol
   8:   0f 84 9e 00 00 00         je     ac <_EIP+0xac> 000000ac Before
first symbol
Code;  0000000e Before first symbol
   e:   3b 1d 00 15 21 c0         cmp    0xc0211500,%ebx


1 warning issued.  Results may not be reliable.

Pierre
-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

  parent reply	other threads:[~2001-12-01 10:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  4:43 2.5.1-pre5 not easy to boot with devfs Pierre Rousselet
2001-12-01  5:01 ` Alexander Viro
2001-12-01  5:37 ` Linus Torvalds
2001-12-01  7:01   ` Richard Gooch
2001-12-01  8:45     ` Pierre Rousselet
2001-12-01 18:36       ` Richard Gooch
2001-12-01 20:37         ` Pierre Rousselet
2001-12-01 23:20           ` Richard Gooch
2001-12-02  1:11             ` Pierre Rousselet
2001-12-02 10:28               ` Pierre Rousselet
2001-12-02 16:59                 ` Alexander Viro
2001-12-02 17:14                   ` Alan Cox
2001-12-02 18:02                     ` Richard Gooch
2001-12-03 12:58                       ` Jens Axboe
2001-12-03 19:06                         ` Richard Gooch
2001-12-03 20:52                           ` Jens Axboe
2001-12-02 17:55                   ` Richard Gooch
2001-12-03 19:54                     ` Alexander Viro
2001-12-02 22:57                   ` Keith Owens
2001-12-03  4:50                     ` Pierre Rousselet
2001-12-02  8:05             ` Pierre Rousselet
2001-12-01 23:47           ` Richard Gooch
2001-12-02  7:11             ` Pierre Rousselet
2001-12-02 21:22               ` Richard Gooch
2001-12-02  9:27         ` Pierre Rousselet
2001-12-02 19:40       ` Bongani Hlope
2001-12-01  9:59     ` Pierre Rousselet [this message]
2001-12-03  6:33 ` Richard Gooch
2001-12-03  5:57   ` Pierre ROUSSELET
2001-12-03 12:16   ` Pierre Rousselet

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=3C08AA05.C3218C82@wanadoo.fr \
    --to=pierre.rousselet@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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