From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Arjan van de Ven <arjan@infradead.org>
Subject: Re: Oops / BUG? (2.6.17.2 on VIA Epia CL6000)
Date: Sun, 02 Jul 2006 13:46:15 +0200 [thread overview]
Message-ID: <44A7B207.4040901@xs4all.nl> (raw)
In-Reply-To: <1151840308.3111.14.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sun, 2006-07-02 at 13:24 +0200, Udo van den Heuvel wrote:
>
>> CONFIG_KALLSYMS=y
>
> hmmmmm then something really bad happened, so bad that even the
> backtrace is corrupted ;(
>
> I'm sorry to say but unless you already have a suspect, those are really
> really hard to diagnose or fix. One thing you can do is remove all
> modules you don't actually use (just from a statistical pov that reduces
> the risk of it repeating)... and hope maybe a next backtrace does
> provide more information.
Later another one happened with less info. Maybe the `different`
location helps?
Jul 2 09:07:30 epia kernel: BUG: unable to handle kernel paging request
at virtual address fec9bd89
Jul 2 09:07:30 epia kernel: printing eip:
Jul 2 09:07:30 epia kernel: fec9bd89
Jul 2 09:07:30 epia kernel: *pde = 00000000
Jul 2 09:07:30 epia kernel: Oops: 0000 [#1]
Jul 2 09:07:30 epia kernel: PREEMPT
Jul 2 09:07:36 epia kernel: Modules linked in: 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 snd_via82xx snd_ac97_codec
snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
uhci_hcd 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 09:07:42 epia kernel: CPU: 0
Jul 2 09:07:42 epia kernel: EIP: 0060:[pg0+1049402761/1069728768]
Not tainted VLI
Jul 2 09:07:42 epia kernel: EIP: 0060:[<fec9bd89>] Not tainted VLI
Jul 2 09:07:42 epia kernel: EFLAGS: 00010296 (2.6.17.2 #3)
Jul 2 09:07:42 epia kernel: EIP is at 0xfec9bd89
Kind regards,
Udo
next prev parent reply other threads:[~2006-07-02 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 11:15 Oops / BUG? (2.6.17.2 on VIA Epia CL6000) Udo van den Heuvel
2006-07-02 11:21 ` 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 [this message]
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=44A7B207.4040901@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=arjan@infradead.org \
--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