public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: "Arkadiusz Jałowiec" <ajalowiec@interia.pl>
Cc: linux-kernel@vger.kernel.org, linux-usb-users@lists.sourceforge.net
Subject: Re: PROBLEM: Kernel 2.6.x freeze
Date: Fri, 29 Sep 2006 14:38:06 +0200	[thread overview]
Message-ID: <20060929143806.0d6a9162@localhost> (raw)
In-Reply-To: <451B7ACA.1000504@interia.pl>

On Thu, 28 Sep 2006 07:33:30 +0000
Arkadiusz Jalowiec <ajalowiec@interia.pl> wrote:

> OOps:
> 
> ivalid opcode: 0000 [#1]
> Modules linked in ppp_deflate zlib_deflate bsd_comp pppoatm ipv6 
> partport_pc partport snd_pcm_oss snd_mixer oss via_agp agpgart 
> ueagle_atm usbatm uhci_hcd ehci_hcd usbcore i2c_viapro 12c_core 
> snd_via82xx snd_ac97_code snd_mpu401_uart snd_rawmidi opt_LOG 
> snd_seq_device xt limit snd soundcore via_rhine mill xt_tcpudp xt_state 
> iptables_filter nls_iso8859-2 nls_cp852 ip_contract_irc ip_contract_ftp 
> xt_contract ip_contract ip_tables x_tables
> 
> CPU: 0
> EIP: 0060: [<d0d184dc>] Not tainted VLI
> EFLAGS: 00010003 (2.6.18#1)
> EIP is at uhci_giveback_urb+0x59/0x126 [uhci_hcd]
> eax: cefeeed1 ebx: cf3935a0 ecx: ce2a9bc0 edx: cf3935a0
> esi: ce2a9bc0 edi: 00000000 epb: ce4933bc esp: c6b79f00
> ds: 007b es: 007b ss:0068
> 
> Process removepkg (pid: 11084, ti=c6b78000 task=c126e560 task.ti=c6b78000)
> 
> Stack:    00000046 c9936060 cf3935a0 ce4933bc d0d17e17 00000000 cefeeed0 
> cf3935a0
>     ce2a9bc0 00000000 cefeeed0 d0d18627 c6b79fbc c6b79fbc cefeeed0 cf3935a0
>     00000009 c6b79fbc d0d18846 00000246 00000000 00000000 cefeed00 d0d192ad
> 
> Call Trace:
> 
> [<d0d17e17>] uhci_result_common+0xb7/0x146 [uhci_hcd]
> [<d0d18627>] uhci_scan_qh+0x7e/0x174 [uhci_hcd]
> [<d0d18846>] uhci_scan_schedule+0x72/0xec [uhci_hcd]
> [<d0d192ad>] uhci_irq+0xe8/0xf8 [uhci_hcd]
> [<d0d365f8>] udb_hcd_irq+0x27/0x4e [usbcore]
> [<c012c4c4>] handle_IRQ_event+0x21/0x47
> [<c012c545>] do_IRQ+0x5b/0xa2
> [<c0104106>] do_IRQ+0x40/0x4d
> [<c0102c4a>] common_interrupt+0x1a/0x20
> 
> Code:     5c 89 57 2c 8b 40 44 c7 47 40 00 00 00 00 89
>                 47 3c 8b 45 00 8b 55 04 89 02 89 50 04 89
>                 6d 00 8d 47 18 89 6d 04 39 47 18 75
>                 4b 0f <b6> 47 50 a8 02 88 44 24 08 74 3f 0f b6
>                 46 20 8b 4e 20 ba fe ff
> 
> EIP:    [<d0d184dc>] uhci_giveback_urb+0x59/0x126
>     [uhci_hcd] SS: ESP 0068: c6b79f00
> <0> Kernel panic - not syncing: Fatal exception in interrupt


Do you have copied the Oops by hand, right?

Can you send the ".config" for this 2.6.18?


I'm not an expert but...

This is how the code should look like (I've compiled 2.6.18 with gcc
3.3.6 + gentoo patches):

c02dd6a2:       74 5c                   je     c02dd700 <uhci_giveback_urb+0xa0>
c02dd6a4:       0f b6 46 20             movzbl 0x20(%esi),%eax
c02dd6a8:       8b 4e 20                mov    0x20(%esi),%ecx
c02dd6ab:       c7 04 24 fe ff ff ff    movl   $0xfffffffe,(%esp)


But we have:

  500894:       74 3f                   je     5008d5 <_end+0x2d>
  500896:       0f b6 46 20             movzbl 0x20(%rsi),%eax
  50089a:       8b 4e 20                mov    0x20(%rsi),%ecx
  50089d:       ba                      .byte 0xba
  50089e:       fe                      (bad)
  50089f:       ff                      .byte 0xff


So "c7 04 24" turned into
   "ba fe ff"


The funny thing is that "fe ff" comes just after "24" in the original
code...


Questions for LKML:

1) Isn't the kernel code write-protected at page level?
   Or maybe is it only protected when "CONFIG_DEBUG_RODATA=y"?

2) In this case the "corrupted" memory is in a module, is/can also this
code be write-protected?

-- 
	Paolo Ornati
	Linux 2.6.18 on x86_64

  parent reply	other threads:[~2006-09-29 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  7:33 PROBLEM: Kernel 2.6.x freeze Arkadiusz Jałowiec
2006-09-28  9:41 ` Paolo Ornati
2006-09-29 12:38 ` Paolo Ornati [this message]
2006-09-29 21:29   ` [Linux-usb-users] " Alan Stern
2006-09-30  7:56     ` [Linux-usb-users[ " Arkadiusz Jałowiec
2006-09-30 12:14     ` [Linux-usb-users] " Paolo Ornati
2006-09-30 15:49       ` Alan Stern
2006-10-01 14:10         ` Paolo Ornati
2006-10-02 21:47           ` Arkadiusz Jałowiec
2006-10-03 19:52             ` Paolo Ornati
2006-10-03 20:34               ` Alan Stern
2006-10-04  7:14                 ` Paolo Ornati
2006-10-04  7:16                   ` Paolo Ornati

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=20060929143806.0d6a9162@localhost \
    --to=ornati@fastwebnet.it \
    --cc=ajalowiec@interia.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    /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