All of lore.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Folkert van Heusden <folkert@vanheusden.com>
Subject: Oops / BUG? (2.6.17.2 on VIA Epia CL6000)
Date: Sun, 02 Jul 2006 13:15:39 +0200	[thread overview]
Message-ID: <44A7AADB.8040106@xs4all.nl> (raw)

Hello,

On my otherwise stable Via EPIA CL6000 I experienced an OOPS.
Hardware should be OK. I was unable to reproduce the event, so far.
In what part of the kernel did things go wrong?
What can I do to help fix the bug? (if it is indeed a bug)

Kind regards,
Udo

Jul  2 07:11:23 epia kernel: BUG: unable to handle kernel paging request
at virtual address 52786fdd
Jul  2 07:11:23 epia kernel:  printing eip:
Jul  2 07:11:23 epia kernel: 52786fdd
Jul  2 07:11:23 epia kernel: *pde = 00000000
Jul  2 07:11:23 epia kernel: Oops: 0000 [#1]
Jul  2 07:11:23 epia kernel: PREEMPT
Jul  2 07:11:23 epia kernel: Modules linked in: eeprom sch_tbf xt_string
xt_MARK xt_length xt_tcpmss xt_mac xt_mark vt1211 hwmon_vid i2c_isa
ipt_ttl ipt_owner ip_nat_irc ip_conntrack_irc ipt_REDIRECT ipt_tos
ip_nat_ftp ip_conntrack_ftp ip_nat_h323 ip_conntrack_h323 ipt_MASQUERADE
ipt_LOG ipt_TCPMSS ipt_REJECT xt_limit xt_state ipt_TARPIT
iptable_filter ipt_TOS iptable_mangle xt_NOTRACK iptable_raw binfmt_misc
lp parport_pc parport nvram ehci_hcd uhci_hcd snd_via82xx snd_ac97_codec
snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd_mpu401_uart snd_rawmidi snd_seq_device snd i2c_viapro
Jul  2 07:11:23 epia kernel: CPU:    0
Jul  2 07:11:23 epia kernel: EIP:
0060:[phys_startup_32+1382576093/-1073741824]    Not tainted VLI
Jul  2 07:11:23 epia kernel: EIP:    0060:[<52786fdd>]    Not tainted VLI
Jul  2 07:11:23 epia kernel: EFLAGS: 00010296   (2.6.17.2 #3)
Jul  2 07:11:23 epia kernel: EIP is at 0x52786fdd
Jul  2 07:11:23 epia kernel: eax: 00000000   ebx: 11d3b28e   ecx:
0000000d   edx: 00000001
Jul  2 07:11:23 epia kernel: esi: 5d21e8b6   edi: 9faa859e   ebp:
ca33023d   esp: dd071f38
Jul  2 07:11:23 epia kernel: ds: 007b   es: 007b   ss: 0068
Jul  2 07:11:23 epia kernel: Process named (pid: 1431,
threadinfo=dd070000 task=ddf61a90)
Jul  2 07:11:23 epia kernel: Stack: 2dad9f88 1b77f396 5f57be35 0e045382
fb72cd9d 9ca3ed70 29739bee 90ca7336
Jul  2 07:11:23 epia kernel:        cdb39230 d727e3ff b41a68a9 d1962a09
b9b3a8a9 1109a681 a447b354 fb7969e6
Jul  2 07:11:23 epia kernel:        73a0d873 06446b61 1be5d2eb 16872e4f
c887aede 1fcb7034 7902b644 ac07b40b
Jul  2 07:11:23 epia kernel: Call Trace:
Jul  2 07:11:30 epia kernel: Code:  Bad EIP value.
Jul  2 07:11:30 epia kernel: EIP:
[phys_startup_32+1382576093/-1073741824] 0x52786fdd SS:ESP 0068:dd071f38
Jul  2 07:11:30 epia kernel: EIP: [<52786fdd>] 0x52786fdd SS:ESP
0068:dd071f38



             reply	other threads:[~2006-07-02 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 11:15 Udo van den Heuvel [this message]
2006-07-02 11:21 ` Oops / BUG? (2.6.17.2 on VIA Epia CL6000) Arjan van de Ven
2006-07-02 11:24   ` Udo van den Heuvel
2006-07-02 11:38     ` Arjan van de Ven
2006-07-02 11:46       ` Udo van den Heuvel
2006-07-02 21:15       ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2006-07-02 19:51 Chuck Ebbert

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=44A7AADB.8040106@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=folkert@vanheusden.com \
    --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.