From: Luca Tettamanti <kronos.it@gmail.com>
To: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [acpi:battery?] kernel oops on boot
Date: Wed, 14 Apr 2010 15:13:24 +0200 [thread overview]
Message-ID: <20100414131324.GA6598@nb-core2.darkstar.lan> (raw)
In-Reply-To: <20100414095750.GA3304@swordfish.minsk.epam.com>
Hello,
I'm seeing a similar bug on my notebook (Asus F3Sa) with current git.
-rc4 does not work, while -rc3 does work.
The error (at least in my case) is a division by zero in
acpi_ex_insert_into_field.
Disassembly near the faulty instruction (div %esi) looks like this:
0x000000000001cbee <+205>: 74 09 je 0x1cbf9 <acpi_ex_insert_into_field+216>
0x000000000001cbf0 <+207>: 40 88 f1 mov %sil,%cl
0x000000000001cbf3 <+210>: 49 d3 e5 shl %cl,%r13
0x000000000001cbf6 <+213>: 49 f7 d5 not %r13
0x000000000001cbf9 <+216>: 0f b6 4b 24 movzbl 0x24(%rbx),%ecx
0x000000000001cbfd <+220>: 40 0f b6 f6 movzbl %sil,%esi
0x000000000001cc01 <+224>: 49 83 c9 ff or $0xffffffffffffffff,%r9
0x000000000001cc05 <+228>: 8b 7b 18 mov 0x18(%rbx),%edi
0x000000000001cc08 <+231>: 49 d3 e1 shl %cl,%r9
0x000000000001cc0b <+234>: 8d 7c 3e ff lea -0x1(%rsi,%rdi,1),%edi
0x000000000001cc0f <+238>: 31 d2 xor %edx,%edx
0x000000000001cc11 <+240>: 89 f8 mov %edi,%eax
0x000000000001cc13 <+242>: 4d 21 e9 and %r13,%r9
0x000000000001cc16 <+245>: f7 f6 div %esi
0x000000000001cc18 <+247>: 41 bb 01 00 00 00 mov $0x1,%r11d
0x000000000001cc1e <+253>: 89 45 b4 mov %eax,-0x4c(%rbp)
0x000000000001cc21 <+256>: 31 d2 xor %edx,%edx
0x000000000001cc23 <+258>: 8d 04 0f lea (%rdi,%rcx,1),%eax
0x000000000001cc26 <+261>: 0f b6 4b 0f movzbl 0xf(%rbx),%ecx
Register dump confirms that ESI is 0. The div seems to be generated for
ACPI_ROUND_UP_TO:
865 datum_count = ACPI_ROUND_UP_TO(obj_desc->common_field.bit_length,
0x0000000000000d11 <+220>: movzbl %sil,%esi
0x0000000000000d19 <+228>: mov 0x18(%rbx),%edi
0x0000000000000d1f <+234>: lea -0x1(%rsi,%rdi,1),%edi
0x0000000000000d23 <+238>: xor %edx,%edx
0x0000000000000d25 <+240>: mov %edi,%eax
0x0000000000000d2a <+245>: div %esi
0x0000000000000d32 <+253>: mov %eax,-0x4c(%rbp)
(recompiled with DEBUG_INFO)
Stack trace:
acpi_ex_insert_into_field
acpi_ex_write_data_to_field
acpi_ex_store_object_to_node
acpi_ex_store
acpi_ex_opcode_1A_1T_1R
acpi_ds_exec_end_op
acpi_ps_parse_loop
acpi_ps_parse_aml
acpi_ps_execute_method
acpi_ns_evaluate
acpi_evaluate_object
acpi_battery_update [battery]
acpi_battery_add [battery]
acpi_device_probe
driver_probe_device
bus_for_each_dev
driver_attach
bus_add_driver
driver_register
acpi_bus_register_driver
acpi_battery_init_async [battery]
Compiler is:
$ gcc --version
gcc (Debian 4.4.3-7) 4.4.3
Luca
next prev parent reply other threads:[~2010-04-14 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:57 Sergey Senozhatsky
2010-04-14 13:12 ` Christian Hartmann
2010-04-14 13:13 ` Luca Tettamanti [this message]
2010-04-14 13:50 ` Tero Roponen
2010-04-14 13:58 ` Alexey Starikovskiy
2010-04-14 14:05 ` Tero Roponen
2010-04-14 15:16 ` Justin P. mattock
2010-04-15 10:28 ` Sergey Senozhatsky
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=20100414131324.GA6598@nb-core2.darkstar.lan \
--to=kronos.it@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome