--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> It should give us a better clue which sysfs file is causing the oops.
This BUG happened during boot-up! The only USB device I have is a pwc webcam:
$ /sbin/lsusb
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002 Device 001:
--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> Please apply this patch to your kernel and try to reproduce:
>
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/gregkh-driver-sysfs-crash-debugging.patch
>
> It should give us a better clue which sysfs file
--- Pekka J Enberg [EMAIL PROTECTED] wrote:
Please apply this patch to your kernel and try to reproduce:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/gregkh-driver-sysfs-crash-debugging.patch
It should give us a better clue which sysfs file is
--- Pekka J Enberg [EMAIL PROTECTED] wrote:
It should give us a better clue which sysfs file is causing the oops.
This BUG happened during boot-up! The only USB device I have is a pwc webcam:
$ /sbin/lsusb
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002 Device 001: ID
Oh yes - I'd better mention what my Ethernet devices are:
$ cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo
colls carrier compressed
lo: 820705
--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> Please apply this patch to your kernel and try to reproduce:
Ta-DA
BUG: unable to handle kernel paging request at virtual address 6b6b6d6b
printing eip:
c0130113
*pde =
Oops: 0002 [#1]
PREEMPT SMP
last sysfs file:
Hi Chris,
On Thu, 1 Mar 2007, Chris Rankin wrote:
> Nope, no difference. Again, this happened while trying to start World of
> Warcraft. However, this time there is no snd-rtctimer module in the
> stack.
Please apply this patch to your kernel and try to reproduce:
--- Pekka Enberg <[EMAIL PROTECTED]> wrote:
> Yeah, but the oops looks more like a reference counting problem with
> sysfs dentries. No harm in trying out the patch or reproducing without
> CONFIG_SCHED_SMT though.
>
Nope, no difference. Again, this happened while trying to start World of
--- Pekka Enberg [EMAIL PROTECTED] wrote:
Yeah, but the oops looks more like a reference counting problem with
sysfs dentries. No harm in trying out the patch or reproducing without
CONFIG_SCHED_SMT though.
Nope, no difference. Again, this happened while trying to start World of
Warcraft.
Hi Chris,
On Thu, 1 Mar 2007, Chris Rankin wrote:
Nope, no difference. Again, this happened while trying to start World of
Warcraft. However, this time there is no snd-rtctimer module in the
stack.
Please apply this patch to your kernel and try to reproduce:
--- Pekka J Enberg [EMAIL PROTECTED] wrote:
Please apply this patch to your kernel and try to reproduce:
Ta-DA
BUG: unable to handle kernel paging request at virtual address 6b6b6d6b
printing eip:
c0130113
*pde =
Oops: 0002 [#1]
PREEMPT SMP
last sysfs file:
Oh yes - I'd better mention what my Ethernet devices are:
$ cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo
colls carrier compressed
lo: 820705
--- Pekka Enberg <[EMAIL PROTECTED]> wrote:
> > Call Trace:
> > [] sysfs_release+0x2d/0x4c
> > [] __fput+0x96/0x13c
>
> So udevd is closing a sysfs attribute file but the pointer passed to
> module_put is bogus. Looks like the sysfs dentry was already taken
> down by release_sysfs_dirent(). Can
On 2/27/07, Chris Rankin <[EMAIL PROTECTED]> wrote:
Hmm, this bug looks interesting:
http://www.ussg.iu.edu/hypermail/linux/kernel/0702.3/0514.html
Yes, my machine *is* a dual P4 with HT enabled...
Yeah, but the oops looks more like a reference counting problem with
sysfs dentries. No harm
Hi,
On 2/26/07, Chris Rankin <[EMAIL PROTECTED]> wrote:
BUG: unable to handle kernel paging request at virtual address 6b6b6ceb
[snip]
EIP is at module_put+0x20/0x52
eax: 6b6b6ceb ebx: 6b6b6b6b ecx: 0001 edx: e5bf
esi: e9040b08 edi: 6b6b6b6b ebp: eae0bb3c esp: e5bf0f58
--- Takashi Iwai <[EMAIL PROTECTED]> wrote:
> snd_timer_global_register() itself doesn't issue any tasklet, so it
> shouldn't be needed.
Hmm, this bug looks interesting:
http://www.ussg.iu.edu/hypermail/linux/kernel/0702.3/0514.html
Yes, my machine *is* a dual P4 with HT enabled...
Cheers,
--- Takashi Iwai [EMAIL PROTECTED] wrote:
snd_timer_global_register() itself doesn't issue any tasklet, so it
shouldn't be needed.
Hmm, this bug looks interesting:
http://www.ussg.iu.edu/hypermail/linux/kernel/0702.3/0514.html
Yes, my machine *is* a dual P4 with HT enabled...
Cheers,
Chris
Hi,
On 2/26/07, Chris Rankin [EMAIL PROTECTED] wrote:
BUG: unable to handle kernel paging request at virtual address 6b6b6ceb
[snip]
EIP is at module_put+0x20/0x52
eax: 6b6b6ceb ebx: 6b6b6b6b ecx: 0001 edx: e5bf
esi: e9040b08 edi: 6b6b6b6b ebp: eae0bb3c esp: e5bf0f58
ds:
On 2/27/07, Chris Rankin [EMAIL PROTECTED] wrote:
Hmm, this bug looks interesting:
http://www.ussg.iu.edu/hypermail/linux/kernel/0702.3/0514.html
Yes, my machine *is* a dual P4 with HT enabled...
Yeah, but the oops looks more like a reference counting problem with
sysfs dentries. No harm in
--- Pekka Enberg [EMAIL PROTECTED] wrote:
Call Trace:
[c01839fe] sysfs_release+0x2d/0x4c
[c015124b] __fput+0x96/0x13c
So udevd is closing a sysfs attribute file but the pointer passed to
module_put is bogus. Looks like the sysfs dentry was already taken
down by release_sysfs_dirent().
--- Randy Dunlap <[EMAIL PROTECTED]> wrote:
> Do you have any of the preceding kernel log messages?
> or can you get them?
Unfortunately, there was none. I posted everything there was. Race condition,
perhaps?
Cheers,
Chris
At Mon, 26 Feb 2007 10:42:38 -0800,
Randy Dunlap wrote:
>
> On Mon, 26 Feb 2007 01:26:06 + (GMT) Chris Rankin wrote:
>
> > Hi,
> >
> > This looks like a memory fault to me; are those 0x6b characters "slab
> > poisoning"? This is the dual
>
> Yes, from include/linux/poison.h:
> #define
On Mon, 26 Feb 2007 01:26:06 + (GMT) Chris Rankin wrote:
> Hi,
>
> This looks like a memory fault to me; are those 0x6b characters "slab
> poisoning"? This is the dual
Yes, from include/linux/poison.h:
#define POISON_FREE 0x6b/* for use-after-free poisoning */
Do you have any of
On Mon, 26 Feb 2007 01:26:06 + (GMT) Chris Rankin wrote:
Hi,
This looks like a memory fault to me; are those 0x6b characters slab
poisoning? This is the dual
Yes, from include/linux/poison.h:
#define POISON_FREE 0x6b/* for use-after-free poisoning */
Do you have any of the
At Mon, 26 Feb 2007 10:42:38 -0800,
Randy Dunlap wrote:
On Mon, 26 Feb 2007 01:26:06 + (GMT) Chris Rankin wrote:
Hi,
This looks like a memory fault to me; are those 0x6b characters slab
poisoning? This is the dual
Yes, from include/linux/poison.h:
#define POISON_FREE 0x6b
--- Randy Dunlap [EMAIL PROTECTED] wrote:
Do you have any of the preceding kernel log messages?
or can you get them?
Unfortunately, there was none. I posted everything there was. Race condition,
perhaps?
Cheers,
Chris
Hi,
This looks like a memory fault to me; are those 0x6b characters "slab
poisoning"? This is the dual
P4 Xeon / 2 GB RAM machine, and I'm guessing that udevd has just loaded
snd_rtctimer (because
that's the module at the top of the list):
BUG: unable to handle kernel paging request at virtual
Hi,
This looks like a memory fault to me; are those 0x6b characters slab
poisoning? This is the dual
P4 Xeon / 2 GB RAM machine, and I'm guessing that udevd has just loaded
snd_rtctimer (because
that's the module at the top of the list):
BUG: unable to handle kernel paging request at virtual
28 matches
Mail list logo
