From: Dave Airlie <airlied@gmail.com>
To: nboyle@tampabay.rr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Oops: EIP is at sysfs_release+0x34/0x80
Date: Sat, 9 Jul 2005 12:35:42 +1000 [thread overview]
Message-ID: <21d7e9970507081935268a2651@mail.gmail.com> (raw)
In-Reply-To: <42CEB851.1000004@tampabay.rr.com>
> Unable to handle kernel paging request at virtual address 762f7473
> printing eip:
> c0183c14
> *pde = 00000000
> Oops: 0002 [#1]
> PREEMPT
> Modules linked in: rtc nls_utf8 snd_emu10k1_synth snd_emu10k1
> snd_emux_synth snd_seq_virmidi snd_rawmidi snd_pcm_oss snd_ac97_codec
> snd_seq_midi_event snd_seq_midi_emul snd_seq snd_pcm ehci_hcd ide_cd
> usbhid snd_mixer_oss snd_timer uhci_hcd af_packet ohci_hcd cdrom
> snd_seq_device snd_page_alloc floppy isofs usbcore snd_hwdep ntfs snd
> tulip snd_util_mem soundcore evdev crc32 smbfs ext2 nls_base unix
> CPU: 0
> EIP: 0060:[<c0183c14>] Not tainted VLI
> EFLAGS: 00010202 (2.6.13-rc2-GIT-08-7-2005-0)
> EIP is at sysfs_release+0x34/0x80
> eax: 00000001 ebx: dc7c2000 ecx: d1979860 edx: 00000001
> esi: 762f7373 edi: d5ba26a0 ebp: d9368544 esp: dc7c3f80
> ds: 007b es: 007b ss: 0068
> Process udev (pid: 31802, threadinfo=dc7c2000 task=c7c19040)
> Stack: df468c40 df798140 dffe4140 c0153c08 d5a9edbc df468c40 df798140
> 00000000
> dc7c2000 c01523d3 00000000 00000003 080ac568 00000003 c0103101
> 00000003
> 080ac568 00000004 080ac568 00000003 08057198 00000006 0000007b
> 0000007b
> Call Trace:
> [<c0153c08>] __fput+0xf8/0x110
> [<c01523d3>] filp_close+0x43/0x70
> [<c0103101>] syscall_call+0x7/0xb
> Code: 8b 41 0c 8b 40 48 8b 58 14 8b 41 48 8b 40 14 85 db 8b 70 04 74 07
> 89 d8 e8 9a 11 02 00 85 f6 74 1f bb 00 e0 ff ff 21 e3 ff 43 14 <ff> 8e
> 00 01 00 00 83 3e 02 74 32 8b 43 08 ff 4b 14 a8 08 75 21
> <6>note: udev[31802] exited with preempt_count 1
>
> I was still able to log in afterwards (I still haven't rebooted the
> machine and I'm typing this on it) but hotplug processes are reproducing
> like rodents and I think the kernel is starting them (I kill everything
> related and they all come back). This was around 5-10 minutes after my
> first boot with this kernel.
>
Can you send my your .config, lspci and /var/log/Xorg.0.log?
Dave.
next prev parent reply other threads:[~2005-07-09 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 17:30 [BUG] Oops: EIP is at sysfs_release+0x34/0x80 Nathan Boyle
2005-07-08 21:50 ` Andrew Morton
2005-07-08 21:55 ` Greg KH
2005-07-09 17:59 ` Nathan Boyle
2005-07-10 3:20 ` Dave Airlie
2005-07-10 20:47 ` Nathan Boyle
2005-07-09 2:35 ` Dave Airlie [this message]
2005-07-09 17:55 ` Nathan Boyle
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=21d7e9970507081935268a2651@mail.gmail.com \
--to=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nboyle@tampabay.rr.com \
/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.