From: tmp <skrald@amossen.dk>
To: linux-kernel@vger.kernel.org
Subject: Kernel oops
Date: Fri, 11 Jun 2004 09:27:57 +0200 [thread overview]
Message-ID: <1086938877.1224.3.camel@debian> (raw)
I got the following oops in my kernel 2.6.6. No modules has been
added/removed ahead of the crash:
Jun 10 00:19:59 debian kernel: Oops: 0002 [#1]
Jun 10 00:19:59 debian kernel: CPU: 0
Jun 10 00:19:59 debian kernel: EIP: 0060:[d_instantiate+44/80] Not
tainted
Jun 10 00:19:59 debian kernel: EFLAGS: 00010286 (2.6.6)
Jun 10 00:19:59 debian kernel: EIP is at d_instantiate+0x2c/0x50
Jun 10 00:19:59 debian kernel: eax: 00814834 ebx: cd814824 ecx:
d8387700 edx: cd814834
Jun 10 00:19:59 debian kernel: esi: d83876dc edi: d7895f2b ebp:
00000022 esp: d7895f08
Jun 10 00:19:59 debian kernel: ds: 007b es: 007b ss: 0068
Jun 10 00:19:59 debian kernel: Process netspeed_applet (pid: 755,
threadinfo=d7894000 task=d91fc8f0)
Jun 10 00:19:59 debian kernel: Stack: d83876dc ddf093c0 c027d19a
d83876dc cd814824 00001a7e cd814824 3837365b
Jun 10 00:19:59 debian kernel: cd005d32 ffffff9f d7894000
c027df17 cd814800 00000000 00000001 d7895f24
Jun 10 00:19:59 debian kernel: 00000006 00001a7e 00000002
00000000 080d76c0 00000005 d7894000 c027e0bd
Jun 10 00:19:59 debian kernel: Call Trace:
Jun 10 00:19:59 debian kernel: [sock_map_fd+170/320]
sock_map_fd+0xaa/0x140
Jun 10 00:19:59 debian kernel: [__sock_create+167/400]
__sock_create+0xa7/0x190
Jun 10 00:19:59 debian kernel: [sys_socket+61/96] sys_socket+0x3d/0x60
Jun 10 00:19:59 debian kernel: [sys_socketcall+104/608]
sys_socketcall+0x68/0x260
Jun 10 00:19:59 debian kernel: [syscall_call+7/11] syscall_call+0x7/0xb
ksymoops 2.4.9 on i686 2.6.6. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.6/ (default)
-m /boot/System.map-2.6.6 (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.
Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Jun 10 00:19:59 debian kernel: Oops: 0002 [#1]
Jun 10 00:19:59 debian kernel: CPU: 0
Jun 10 00:19:59 debian kernel: EIP: 0060:[d_instantiate+44/80] Not
tainted
Jun 10 00:19:59 debian kernel: EFLAGS: 00010286 (2.6.6)
Jun 10 00:19:59 debian kernel: eax: 00814834 ebx: cd814824 ecx:
d8387700 edx: cd814834
Jun 10 00:19:59 debian kernel: esi: d83876dc edi: d7895f2b ebp:
00000022 esp: d7895f08
Jun 10 00:19:59 debian kernel: ds: 007b es: 007b ss: 0068
Jun 10 00:19:59 debian kernel: Stack: d83876dc ddf093c0 c027d19a
d83876dc cd814824 00001a7e cd814824 3837365b
Jun 10 00:19:59 debian kernel: cd005d32 ffffff9f d7894000
c027df17 cd814800 00000000 00000001 d7895f24
Jun 10 00:19:59 debian kernel: 00000006 00001a7e 00000002
00000000 080d76c0 00000005 d7894000 c027e0bd
Jun 10 00:19:59 debian kernel: Call Trace:
Warning (Oops_read): Code line not seen, dumping what data is available
>>ebx; cd814824 <pg0+d423824/3fc0d000>
>>ecx; d8387700 <pg0+17f96700/3fc0d000>
>>edx; cd814834 <pg0+d423834/3fc0d000>
>>esi; d83876dc <pg0+17f966dc/3fc0d000>
>>edi; d7895f2b <pg0+174a4f2b/3fc0d000>
>>esp; d7895f08 <pg0+174a4f08/3fc0d000>
next reply other threads:[~2004-06-11 8:06 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 7:27 tmp [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-23 12:52 kernel oops Andrei Popa
2008-07-23 17:11 ` Vegard Nossum
2008-08-18 16:33 ` Vegard Nossum
2008-08-18 16:39 ` Greg KH
[not found] <e8eb01770803120245x7690e6a9te8ad04296aa3fc4d@mail.gmail.com>
2008-03-12 9:49 ` Zbynek Drlik
2008-03-12 10:33 ` Al Viro
2008-03-12 13:12 ` Zbynek Drlik
2008-02-05 12:57 Andrej Hocevar
2008-02-06 17:55 ` Len Brown
2006-09-12 10:21 Kernel Oops Marcin Prączko
2006-09-13 3:43 ` Andrew Morton
2005-10-15 1:03 Marc Perkel
2005-10-15 1:21 ` Randy.Dunlap
2005-10-15 1:43 ` Marc Perkel
2005-10-15 1:52 ` Randy.Dunlap
2005-01-03 21:10 Kernel oops Marat BN
2005-01-05 10:13 ` Andrew Morton
2004-05-24 20:19 tmp
2004-05-16 12:08 Kernel OOPS tmp
2004-05-16 23:27 ` Andrew Morton
2004-05-17 0:33 ` tmp
2004-03-09 22:13 Kernel oops Philipp Baer
2004-03-09 23:11 ` Andrew Morton
2004-03-12 7:46 ` Philipp Baer
2004-02-08 11:05 Kernel Oops Mathieu LESNIAK
2004-02-08 16:35 ` Greg KH
2004-02-09 7:06 ` Mathieu LESNIAK
2003-11-28 23:15 Kernel oops Ville Jutvik
2003-11-28 5:45 Anderson Levi
2003-08-09 12:39 kernel oops Jean-Yves LENHOF
2003-08-09 20:37 ` Jean-Yves LENHOF
2003-08-09 9:28 Jean-Yves LENHOF
2003-07-18 19:44 Kernel OOPS Robert Scussel
2003-07-18 21:31 ` Alan Cox
2003-07-07 12:53 kernel oops Anders Karlsson
2003-07-07 13:14 ` Alan Cox
2003-07-07 13:32 ` Anders Karlsson
2003-07-07 13:37 ` Alan Cox
2003-07-07 13:56 ` Anders Karlsson
2003-07-08 9:39 ` Marcelo Tosatti
[not found] ` <200307072009.50677.bernd-schubert@web.de>
2003-07-08 5:13 ` Anders Karlsson
2003-05-31 1:32 Nadeem Riaz
2003-03-26 15:52 Steve Terrell
2003-02-03 1:18 Kernel Oops Daniel Espinoza
2003-02-03 3:23 ` vishwas
2002-08-09 5:25 sanket rathi
2002-06-23 19:39 Dirk Schmidt
2002-06-10 8:46 kernel oops Robert Litwiniec
2002-02-26 18:26 Suporte RedeBonja
2002-02-27 13:35 ` Erik Mouw
2001-11-13 13:23 Kernel oops Anthony
2001-11-14 6:02 ` Thiago Rondon
2001-10-08 12:59 kernel oops Terry Kendal
2001-09-27 9:49 kewl
2001-06-01 15:13 Kernel oops David Harris
2001-06-01 15:12 David Harris
2001-04-19 18:32 kernel oops Ronald Bultje
2001-04-19 19:04 ` Alan Cox
2001-04-19 19:08 ` Ronald Bultje
2001-02-19 14:44 Kernel Oops Alberto Bertogli
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=1086938877.1224.3.camel@debian \
--to=skrald@amossen.dk \
--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