All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaco Kroon <jkroon@cs.up.ac.za>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Kernel OOPS (what looks like memory or interrupt handling issues to me)
Date: Tue, 01 Jun 2004 14:09:23 +0200	[thread overview]
Message-ID: <40BC71F3.7090408@cs.up.ac.za> (raw)

[-- Attachment #1: Type: text/plain, Size: 3575 bytes --]

Hello,

This is what I could get.

==========================
Process cc1plus (pid: 29992, threadinfo=c173a000 task=c1d74a10

Stack:      0000bba8 c00bb9c0 c124742c c03083fc 00000000 c0308380 
c030849c c173bbc4
               c013725b c0308380 00000000 00000000 00000083 c0308380 
c0308380 c030848c
               c173bbf0 c0137623 c0308380 00000000 00ff00ff c030849c 
00000000 00000046

Call Trace:
  [<c013725b>] rmqueue_bulk+0xdb/0x140
  [<c0137624>] buffered_rmqueue+0x253/0x270
  [<c01376ec>] __alloc_pages+0xac/0x320
  [<c0137982>] __get_free_pages+0x22/0x50
  [<c013c694>] cache_grow+0x114/0x450
  [<c013cd51>] cache_alloc_refill+0x381/0x4d0
  [<c013d54b>] kmem_cache_alloc+0x19b/0x1c0
  [<c0253fdc>] alloc_skb+0x1c/0xe0
  [<c022dbe1>] tulip_refill_rx+0x91/0x100
  [<c0105d33>] handle_IRQ_event+0x33/0x60
  [<c0106239>] do_IRQ+0x119/0x2f0
  [<c0104688>] common_interrupt+0x18/0x20
  [<c01159b3>] panic+0xc3/e0
  [<c0104d94>] die+0x154/0x1e0
  [<c010f320>] do_page_fault+0x260/0x574
  [<c0241d82>] ide_build_sglist+0x32/0xb0
  [<c011e5f7>] __mod_timer+0x247/0x670
  [<c0110526>] recalc_task_prio+0xab/0x200
  [<c0241d82>] ide_build_sglist+0x32/0xb0
  [<c010f0c0>] do_page_fault+0x0/0x574
  [<c01046cd>] error_code+0x2d/0x40
  [<c0132c35>] unlock_page+0x25/0x50
  [<c0151186>] end_swap_bio_read+0x36/0x50
  [<c015ded5>] bio_endio+0x45/0x70
  [<c021d6a7>] __end_that_request_first+0x1d7/0x230
  [<c0238be8>] ide_end_request+0xb8/0x220
  [<c0241d2d>] ide_dma_intr+0x6d/0x90
  [<c023a935>] ide_intr+0x245/0x4c0
  [<c0241cc0>] ide_dma_intr+0x0/0x90
  [<c0105d33>] handle_IRQ_event+0x33/0x60
  [<c0106239>] do_IRQ+0x119/0x2f0
  [<c0104688>] common_interrupt+0x18/0x20

Code: 89 02 89 50 04 c7 01 00 01 10 00 c7 41 04 00 02 20 00 8b 55

 <0>Kernel Panic:  Fatal exception in interrupt
In interrupt handler - not synching
==========================

Getting this in your logs looks rather - hmm - amusing, to say the least:

Jun  1 02:27:01 slowcoach CRON[29951]: (root) CMD (test -x 
/usr/sbin/run-crons && /usr/sbin/run-crons )
Jun  1 02:28:01 slowcoach CRON[29967]: (root) CMD (test -x 
/usr/sbin/run-crons && /usr/sbin/run-crons )
Jun  1 02:29:01 slowcoach CRON[29978]: (root) CMD (test -x 
/usr/sbin/run-crons && /usr/sbin/run-crons )
Jun  1 02:30:00 slowcoach CRON[29995]: (root) CMD (test -x 
/usr/sbin/run-crons && /usr/sbin/run-crons )
Jun  1 08:00:52 slowcoach syslog-ng[5253]: syslog-ng version 1.6.0rc3 
starting

Anyway, I also attach my .config file.

# uname -a
Linux slowcoach 2.6.6 #2 Sat May 22 16:17:30 SAST 2004 i586 Pentium 75 - 
200 GenuineIntel GNU/Linux
# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 5
model           : 2
model name      : Pentium 75 - 200
stepping        : 4
cpu MHz         : 90.088
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : yes
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de tsc msr mce cx8
bogomips        : 174.59
# cat /proc/interrupts
           CPU0      
  0:   21316411          XT-PIC  timer
  1:        984          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  4:         50          XT-PIC  serial
  8:          2          XT-PIC  rtc
 11:      63961          XT-PIC  eth0
 14:      17038          XT-PIC  ide0
 15:      17317          XT-PIC  ide1
NMI:          0
ERR:          0

I also have vm.min_free_kbytes = 1024 in /etc/sysctl.conf, which is 
already 4 times the default value for my 64MB ram.

This info was gathered on a clean boot - obviously.

Jaco

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 4980 bytes --]

                 reply	other threads:[~2004-06-01 12:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40BC71F3.7090408@cs.up.ac.za \
    --to=jkroon@cs.up.ac.za \
    --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.