mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, tiwai@suse.de, alsa-devel@vger.kernel.org
Subject: Re: General protection fault when unloading snd_hda_intel on 2.6.30-rc1+
Date: Sat, 11 Apr 2009 23:03:36 +0200	[thread overview]
Message-ID: <20090411210336.GA15272@Pilar.aei.mpg.de> (raw)
In-Reply-To: <20090411132033.003c581c@infradead.org>

On Sat 11.Apr'09 at 13:20:33 -0700, Arjan van de Ven wrote:
> 
> if you happen to have CONFIG_DEBUG_INFO enabled, then you can run the
> oops through scripts/markup_oops.pl to get the source code of the exact
> line that is oopsing.. makes diagnosing it even easier!

I did not have CONFIG_DEBUG_INFO enabled back then, but now I have.

The script gives me this output:

No vmlinux specified, assuming /lib/modules/2.6.30-rc1-00191-gd848223/build/vmlinux
 		add_input_randomness(type, code, value); 
 		input_handle_event(dev, type, code, value); 
 		spin_unlock_irqrestore(&dev->event_lock, flags); 
 	} 
 } 
 ffffffff8044bf7a:	48 8b 5d d8          	mov    -0x28(%rbp),%rbx |  %ebx => 3 
 ffffffff8044bf7e:	4c 8b 65 e0          	mov    -0x20(%rbp),%r12 |  %r12 => ffffffff805bb97c 
 ffffffff8044bf82:	4c 8b 6d e8          	mov    -0x18(%rbp),%r13 |  %r13 => 5 
 ffffffff8044bf86:	4c 8b 75 f0          	mov    -0x10(%rbp),%r14 |  %r14 => 697665646632785c 
 ffffffff8044bf8a:	4c 8b 7d f8          	mov    -0x8(%rbp),%r15 |  %r15 => 0 
 ffffffff8044bf8e:	c9                   	leaveq  
 ffffffff8044bf8f:	c3                   	retq    
  
 static inline int variable_test_bit(int nr, volatile const unsigned long *addr) 
 { 
 	int oldbit; 
  
 	asm volatile("bt %2,%1\n\t" 
*ffffffff8044bf90:	0f a3 77 20          	bt     %esi,0x20(%rdi) |  %edi = 697665646632785c  %esi = 5 <--- faulting instruction
 ffffffff8044bf94:	19 c0                	sbb    %eax,%eax 
 static struct input_handler *input_table[8]; 
  
 static inline int is_event_supported(unsigned int code, 
 				     unsigned long *bm, unsigned int max) 
 { 
 	return code <= max && test_bit(code, bm); 
 ffffffff8044bf96:	85 c0                	test   %eax,%eax 
 ffffffff8044bf98:	74 e0                	je     ffffffff8044bf7a <input_event+0x2a> 
 { 
 	unsigned long flags; 
  
 	if (is_event_supported(type, dev->evbit, EV_MAX)) { 


  reply	other threads:[~2009-04-11 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 19:36 Carlos R. Mafra
2009-04-11 20:20 ` Arjan van de Ven
2009-04-11 21:03   ` Carlos R. Mafra [this message]
2009-04-11 21:39     ` Arjan van de Ven
2009-04-12  0:33       ` Michal Jaegermann
2009-04-12  1:58         ` General protection fault when unloading snd_hda_intel on 2.6.30-rc1+ (bisected) Carlos R. Mafra
2009-04-14 14:27 ` General protection fault when unloading snd_hda_intel on 2.6.30-rc1+ Takashi Iwai
2009-04-14 16:21   ` Carlos R. Mafra
2009-04-15 11:04     ` [alsa-devel] " Takashi Iwai

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=20090411210336.GA15272@Pilar.aei.mpg.de \
    --to=crmafra2@gmail.com \
    --cc=alsa-devel@vger.kernel.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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

all inboxes | Powered by JetHome®