From: Christian Hartmann <cornogle@googlemail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Len Brown <lenb@kernel.org>, Lin Ming <ming.m.lin@intel.com>,
Bob Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [acpi:battery?] kernel oops on boot
Date: Wed, 14 Apr 2010 15:12:05 +0200 [thread overview]
Message-ID: <u2gffd8902a1004140612h560dbc9di6377450661c81422@mail.gmail.com> (raw)
In-Reply-To: <20100414095750.GA3304@swordfish.minsk.epam.com>
Hi,
I have the same problem on my thinkpad T30 since this week:
The kernel boots very slowly until the message:
* Loading kernel modules...
there my kernel hangs there forever now.
The first problem is shown after the start of the udev (:
* Waiting for /dev to be fully populated...
[ 18.273664] BUG: unable to handle kernel paging request at 0033393a
[ 18.274036] IP: [<c027d8f5>] acpi_ex_read_data_from_field+0x117/0x14e
[ 18.274249] *pde = 00000000
[ 18.274446] Oops: 0000 [#1]
[ 18.274625] last sysfs file:
/sys/devices/pci0000:00/0000:00:1f.1/ide0/0.0/block/hda/dev
[ 18.274625] Modules linked in : battery ac processor rng_core
button uhci_hcd ehci_hcd thermal usbcore [last unloaded:
scsi_wait_scan]
[ 18.274625]
[ 18.274625] Pid: 1077, comm: async/0 Not tained 2.6.34-rc4 #61
2366DG3/2366DG3
[ 18.274625] EIP: 0060:[<c027d8f5>] EFLAGS: 00010246 CPU:0
[ 18.274625] EIP is at acpi_ex_read_data_from_field+0x117/0x14e
[ 18.274625] EAX: 00000000 EBX: 00333931 ECX: 00000000 EDX: 00000000
[ 18.274625] ESI: 00000000 EDI: efa4dd70 EBP: efa4dd64 ESP: efa4dd50
[ 18.274625] DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068
[ 18.274625] Process async/0 (pid:1077, ti=efa4c000 task= f70a2850
task.ti=efa4c000
[ 18.274625] Stack: <me do not want to type it all...>
[ 18.274625] Call Trace:
[ 18.274625] [<c02823be>] ? acpi_ex_resolve_node_to_value+0x166/0x1dc
[ 18.274625] [<c027e226>] ? acpi_ex_resolve_to_value+0x65/0x6f
[ 18.274625] [<c0279065>] ? acpi_ds_evaluate_name_path+0x71/0xdc
....<me do not want to type it all...>...
[ 18.274625] [<c0102e3e>] ? kernel_thread_helper+0x6/0x10
[ 18.274625] Code: c6 74 4e 0f b6 0d 7d a6 7e c0 8d 50 0c 0f b6 43
09 89 55 f0 89 4d ec e8 93 42 00 00 8b 55 f0 89 d8 8b 4d ec e8 9e 12
00 00 89 c2 <0f> b6 43 09 89 55 f0 e8 44 42 00 00 8b 55 f0 85 d2 74 0f
89 f0
[ 18.274625] EIP: [<c027d8f5>] ?
acpi_ex_read_data_from_field+0x117/0x14e SS: ESP 0068:efa4dd50
[ 18.274625] CR2: 000000000033393a
[ 18.274625] ---[ end trace da97996273142d42 ]---
[ 18.274625] bus: 'pcmcia': registered
...
* Starting early crypto disks...
* Cleaning up ifdown...
* Loading kernel modules...
--- FREEEZE ---
I can boot into the lap with the stable 2.6.32.11 and can give other
infos like the current kernelconfig of this laptop. But I will wait
for the reboot, leaving the message still open, if anybody needs more
info.
sincerelly your
Chris
2010/4/14 Sergey Senozhatsky <sergey.senozhatsky@gmail.com>:
>
> Hello,
> Kernel oops on early stages. The below trace is "copy-paste" from the paper
> since syslog is not runing yet.
>
> kernel: .34-rc4-git1 /* also tested on .34-rc4 .34-rc3-git10 */
> laptop: ASUS f3jc x86
>
>
> ds: 007b es:007b fs:00d8 gs:00e8 ss:0068
> process: async/0
> stack:
> 0000000 c144c708 f66cdd20 c109fc0b f723c1b8 f71fcec0 f71aa208 00000020
> <0> c11c4d40 00001000 000000b6 c12f61e0 c12f61bc f723c1b8 f71aa208
> f71fcec0
> <0> f66cdd54 c11c4d58 00000020 f66cdd64 f73a0f84 f723c1b8 f70cdc70
> f66cdd74
>
> call trace:
> __kmalloc+0xe1
> acpi_ex_read_data_from_field+0x156
> acpi_ex_read_data_from_field+0x16e
> acpi_ex_resolve_node_to_value
> acpi_ex_resolve_to_value
> acpi_ds_evaluate_name_path
> acpi_ds_exec_end_op
> acpi_ps_parse_loop
> trace_hardirqs_on
> acpi_ps_parse_aml
> acpi_ps_execute_method
> acpi_ns_eveluate
> acpi_evaluate_object
> acpi_battery_update
> acpi_battery_add
> acpi_device_probe
> driver_probe_device
> __driver_attach
> bus_for_each_dev
> driver_attach
> __driver_attach
> bus_add_driver
> driver_register
> trace_hardirqs_on_caller
> acpi_bus_register_driver
> acpi_battery_init_async
> async_thread
> default_wake_function
> async_thread
> kthread
> kthread
> kernel_thread_helper
>
> code:
> fb 00 00 b8 0b 00 00 00 83 c4 14 e9 7a 01 00 00 31 c0 8b 7d d4 8b 4d dc 31 d2 f3 aa 6a 00
> 0f b6 4b 1d 8b 43 10 8d 74 01 ff 89 f0 <f7> f1 31 d2 89 45 cc 0f b6 43 1c 8d 04 06 8d 75 ec
> f7 f1 31 d2
>
> eip: <c11c66dd> acpi_ex_extract_from_field+0x5c/0x1c3 ss:esp 0068:f66cdcf8
>
>
> Sergey
--
--
......oooO..............
.....(....).....Oooo...
......)../.....(....)....
.....(_/.......)../.....
...............(_/.......
... I WAS ..............
.......... HERE...... ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-14 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:57 [acpi:battery?] kernel oops on boot Sergey Senozhatsky
2010-04-14 13:12 ` Christian Hartmann [this message]
2010-04-14 13:13 ` Luca Tettamanti
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=u2gffd8902a1004140612h560dbc9di6377450661c81422@mail.gmail.com \
--to=cornogle@googlemail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).