RE: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C

RE: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C

[Brown, Len]

Martin,
Does this still happen with 2.4.22?
If yes, can I trouble you to drop the info into bugzilla so we can put
it in the queue?

Thanks,
-Len
----
Please file a bug at http://bugzilla.kernel.org/
Category: Power Management
Componenet: ACPI

Please attach the output from dmidecide, available in /usr/sbin/, or
here: 
http://www.nongnu.org/dmidecode/

Please attach the output from acpidmp, available in /usr/sbin/, or in
here
http://www.intel.com/technology/iapc/acpi/downloads/pmtools-20010730.tar
.gz

Please attach /proc/interrupts and the dmesg output showing the failure,
if possible.


> -----Original Message-----
> From: Martin Mokrejs [mailto:mmokrejs-V2lp6ZUObelkZyP8+xg2CQ@public.gmane.org] 
> Sent: Thursday, August 21, 2003 12:15 PM
> To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Subject: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C
> 
> 
> Hi,
>   I observe time to time on cold boot hang of my laptop. I 
> remember to see 
> such hangs at least since 2.4.21-pre3. Here's my latest 
> running kernel:
> 
> # ksymoops --system-map=/boot/System.map-2.4.22-pre7 
> --vmlinux=/usr/src/linux-2.4.22-pre7/vmlinux ./cr
> ksymoops 2.4.9 on i686 2.4.22-pre7.  Options used
>      -v /usr/src/linux-2.4.22-pre7/vmlinux (specified)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.4.22-pre7/ (default)
>      -m /boot/System.map-2.4.22-pre7 (specified)
> 
> EFLAGS: 00010246
> eax: 00000000 ebx: 638a05f0 ecx: 00000000 edx: 00000006
> esi: 638a05f0 edi: f7ebddd0 ebp: f7ebdd78 esp: f7ebdd74
> ds: 0018 es: 0018 ss: 0018
> Process keventd: (pid 2, stackpage=f7ebd000)
> Stack: f7ebdda4 f7ebdd90 c01ede68 638a05f0 f7ebdda4 f7ebddd0 
> 638a05f0 f7ebddc0
>        c01fc0f2 638a05f0 c01fc072 f7ebddd0 00010000 c0337755 
> c033770a 00000050
>        f7ebddd4 f7ebddd4 638a05f0 f7ebddf0 c02037c2 638a05f0 
> f7ebddd0 00000000
> Call Trace:     [<c01ede68>] [<c01fc0f2>] [<c01fc072>] 
> [<c02037c2>] [<c01f8a2a>]
>   [<c0203b8d>] [<c0203ee7>] [<c01fc4c7>] [<c01f8a00>] 
> [<c0207aed>] [<c0207e5e>]
>   [<c0208b60>] [<c01dce5a>] [<c01d4f7d>] [<c011ff0a>] 
> [<c01282e5>] [<c01281b0>]
>   [<c0105000>] [<c01057ee>] [<c01281b0>]
> Code: 80 3b aa 0f 44 c3 5b 5d c3 a1 d4 55 40 c0 eb f6 55 89 e5 8b
> Using defaults from ksymoops -t elf32-i386 -a i386
> 
> 
> >>edi; f7ebddd0 <_end+37a9304c/3a4f02dc>
> >>ebp; f7ebdd78 <_end+37a92ff4/3a4f02dc>
> >>esp; f7ebdd74 <_end+37a92ff0/3a4f02dc>
> 
> Trace; c01ede68 <acpi_get_data+34/60>
> Trace; c01fc0f2 <acpi_bus_get_device+45/a9>
> Trace; c01fc072 <acpi_bus_data_handler+0/3b>
> Trace; c02037c2 <acpi_power_get_context+46/a6>
> Trace; c01f8a2a <acpi_ut_trace+29/2b>
> Trace; c0203b8d <acpi_power_off_device+46/19d>
> Trace; c0203ee7 <acpi_power_transition+111/138>
> Trace; c01fc4c7 <acpi_bus_set_power+15f/273>
> Trace; c01f8a00 <acpi_ut_debug_print_raw+29/2a>
> Trace; c0207aed <acpi_thermal_active+bf/187>
> Trace; c0207e5e <acpi_thermal_check+295/2e2>
> Trace; c0208b60 <acpi_thermal_notify+a6/105>
> Trace; c01dce5a <acpi_ev_notify_dispatch+54/7a>
> Trace; c01d4f7d <acpi_os_execute_deferred+3a/6c>
> Trace; c011ff0a <__run_task_queue+5a/70>
> Trace; c01282e5 <context_thread+135/1d0>
> Trace; c01281b0 <context_thread+0/1d0>
> Trace; c0105000 <_stext+0/0>
> Trace; c01057ee <arch_kernel_thread+2e/40>
> Trace; c01281b0 <context_thread+0/1d0>
> 

Re: [ACPI] RE: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C

[Karol Kozimor]

Thus wrote Brown, Len:
> Martin,
> Does this still happen with 2.4.22?
> If yes, can I trouble you to drop the info into bugzilla so we can put
> it in the queue?

FYI, I just had it *after* boot, i.e. some 30 seconds after the swsusp 
resume (trace below), and _again_ _after_ I warm-rebooted the machine using
SysRq+B. The subsequent warm-reboot went OK.

Linux 2.4.21 + ACPI 20030619

ksymoops 2.4.9 on i686 2.4.21-xacs.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.21-xacs/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

c01d7600
Oops: 0000
8139too mii snd-intel8x0 snd-pcm snd-timer snd-ac97-codec snd-page-alloc
snd-mpu401-uart snd-rawmidi snd-seq-device snd soundcore ppp_deflate
zlib_inflate zlib_deflate ppp_async ppp_generic slhc ptserial pctel sr_mod
scsi_mod cdrom radeon agpgart asus_acpi mousedev hid input uhci usbcore ds
yenta_socket pcmcia_core
CPU:    0
EIP:    0010:[<c01d7600>]    Tainted: P Z
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00210293
eax: 00000627   ebx: 872d3184   ecx: cff0fe08   edx: 00000000
esi: 872d3184   edi: cff0fe70   ebp: c01e6bcc   esp: cff0fe10
ds: 0018   es: 0018   ss: 0018
Process keventd (pid: 2, stackpage=cff0f000)
Stack: 00000000 c01d837d 872d3184 cff0fe48 cff0fe70 872d3184 872d3184
c01e6c6f
       872d3184 c01e6bcc cff0fe70 872d3184 cff0fe74 cff0fea0 00010000
c02912cb
       c0291280 c01ee511 872d3184 cff0fe70 872d3184 cff0fea4 cff12e00
00000000
Call Trace: [<c01d837d>]  [<c01e6c6f>]  [<c01e6bcc>]  [<c01ee511>]
[<c01ee964>]  [<c01eed14>]  [<c01e70bc>]  [<c01f2c73>]  [<c01f2f10>]
[<c01bdc09>]  [<c0118d5c>]  [<c011fecd>]  [<c0105668>]
Code: 80 3b aa 75 0b 89 d8 eb 09 8d b4 26 00 00 00 00 31 c0 5b c3


>>EIP; c01d7600 <acpi_ns_map_handle_to_node+1c/30>   <=====

>>ecx; cff0fe08 <_end+fbda4b0/124de708>
>>edi; cff0fe70 <_end+fbda518/124de708>
>>ebp; c01e6bcc <acpi_bus_data_handler+0/44>
>>esp; cff0fe10 <_end+fbda4b8/124de708>

Trace; c01d837d <acpi_get_data+39/6a>
Trace; c01e6c6f <acpi_bus_get_device+5f/b4>
Trace; c01e6bcc <acpi_bus_data_handler+0/44>
Trace; c01ee511 <acpi_power_get_context+61/cc>
Trace; c01ee964 <acpi_power_off_device+4c/1e0>
Trace; c01eed14 <acpi_power_transition+100/15c>
Trace; c01e70bc <acpi_bus_set_power+1b0/29c>
Trace; c01f2c73 <acpi_thermal_active+d3/1cc>
Trace; c01f2f10 <acpi_thermal_check+18c/2ac>
Trace; c01bdc09 <acpi_os_execute_deferred+5d/7c>
Trace; c0118d5c <__run_task_queue+50/5c>
Trace; c011fecd <context_thread+121/1a0>
Trace; c0105668 <arch_kernel_thread+28/38>

Code;  c01d7600 <acpi_ns_map_handle_to_node+1c/30>
00000000 <_EIP>:
Code;  c01d7600 <acpi_ns_map_handle_to_node+1c/30>   <=====
   0:   80 3b aa                  cmpb   $0xaa,(%ebx)   <=====
Code;  c01d7603 <acpi_ns_map_handle_to_node+1f/30>
   3:   75 0b                     jne    10 <_EIP+0x10>
Code;  c01d7605 <acpi_ns_map_handle_to_node+21/30>
   5:   89 d8                     mov    %ebx,%eax
Code;  c01d7607 <acpi_ns_map_handle_to_node+23/30>
   7:   eb 09                     jmp    12 <_EIP+0x12>
Code;  c01d7609 <acpi_ns_map_handle_to_node+25/30>
   9:   8d b4 26 00 00 00 00      lea    0x0(%esi,1),%esi
Code;  c01d7610 <acpi_ns_map_handle_to_node+2c/30>
  10:   31 c0                     xor    %eax,%eax
Code;  c01d7612 <acpi_ns_map_handle_to_node+2e/30>
  12:   5b                        pop    %ebx
Code;  c01d7613 <acpi_ns_map_handle_to_node+2f/30>
  13:   c3                        ret


1 warning issued.  Results may not be reliable.

[the kernel is tainted by swsusp and pctel module, but it shouldn't really
 matter since this oops happens mainly at boot]

I'll have yet to see if it still happens with 2.4.22.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org

Re: [ACPI] RE: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C

[Nils Faerber]

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

Am Do, 2003-09-04 um 10.53 schrieb Karol Kozimor:
> Thus wrote Brown, Len:
> > Martin,
> > Does this still happen with 2.4.22?
> > If yes, can I trouble you to drop the info into bugzilla so we can put
> > it in the queue?
> FYI, I just had it *after* boot, i.e. some 30 seconds after the swsusp 
> resume (trace below), and _again_ _after_ I warm-rebooted the machine using
> SysRq+B. The subsequent warm-reboot went OK.
> 
> Linux 2.4.21 + ACPI 20030619
[...]

Just FYI...
I have kernel 2.4.22 + swsusp 1.1-rc7 running without problems on the
very same machine (Asus L3800C, BIOS 121a).
I fiddled a little with a home grown suspend script until I got swsusp
reliably working with older versions (0.9-pre and before) and it still
works perfectly for me; the suspend script from the swsusp project was
too generic and complicated for me ;) I have attached my version in case
someone's interested in it.

One point that proofs to be a good idea is to remove any unnecessary
drivers before suspending, like USB, Firewire and ethernet and to
re-insert them afterwards. The attached script does this.

> Best regards,
CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--

[-- Attachment #2: suspend --]
[-- Type: text/x-sh, Size: 1342 bytes --]

#!/bin/sh

#
# swsusp suspend helper script
# for Asus L3800C and maybe other notebooks
# by Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
#
# Comments and suggestions welcome!
#
# It assumes that XFree is running on VT7 and that VT12 is more
# or less unallocated for debugging output.
# It will remove safe-to-remove drivers before suspend and re-insert them
# afterwards (USB, Firewire, Ethernet, etc.) as well as ejecting a built-in
# WLAN card (mini-PCI).
#

# Prepare for suspend
chvt 12
ifdown eth0 > /dev/tty12 2>&1
ifdown eth1 > /dev/tty12 2>&1
cardctl eject 2 > /dev/tty12 2>&1
rmmod 8139too > /dev/tty12 2>&1

#rmmod usb-uhci > /dev/tty12 2>&1
#rmmod usbmouse > /dev/tty12 2>&1
#rmmod usbnet > /dev/tty12 2>&1
#rmmod usb-storage > /dev/tty12 2>&1
/etc/hotplug/usb.rc stop
rmmod ohci1394 > /dev/tty12 2>&1

# Do it
rmmod -a
sync
rmmod -a
sync
echo "waiting a second..." > /dev/tty12 2>&1
sleep 1
#echo "1 0 2" > /proc/sys/kernel/swsusp
#echo "4" > /proc/acpi/sleep
echo > /proc/swsusp/activate

# Come back
sync
echo "waiting a second..." > /dev/tty12 2>&1
sleep 1

#modprobe usb-uhci > /dev/tty12 2>&1
/etc/hotplug/usb.rc start
modprobe 8139too > /dev/tty12 2>&1
hwclock --hctosys
ifup eth0 > /dev/tty12 2>&1

cardctl insert 2 > /dev/tty12 2>&1

chvt 7 > /dev/tty12 2>&1
modprobe ohci1394 > /dev/tty12 2>&1

Re: [ACPI] RE: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C

[Karol Kozimor]

Thus wrote Nils Faerber:
> Just FYI...
> I have kernel 2.4.22 + swsusp 1.1-rc7 running without problems on the
> very same machine (Asus L3800C, BIOS 121a).
[...]
> One point that proofs to be a good idea is to remove any unnecessary
> drivers before suspending, like USB, Firewire and ethernet and to
> re-insert them afterwards. The attached script does this.

Actually, most modules do not need to be unloaded. I don't know about
firewire (I don't use it), but certainly 8139too contains proper
suspend/resume support, I even had no problems suspending with yenta_socket
and orinoco_cs card. As of now: no modules unloading at all. Anyway, the
crash is not swsusp related.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org

Re: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C

[Karol Kozimor]

Thus wrote Martin MOKREJŠ:
>   I cannot say much about 2.4.22. On my laptop I got very slow response, it
> seems because of the very high interrupt rate generated by my network
> card(seen in 2.4.22 in /proc/interrupts).

Strange, I have not observerd such an issue with my (limited so far)
testing of 2.4.22.

>   I attach 3 files from my running instance 2.4.22-pre7. Below is also
> output from /proc/interrupts (2.4.22-pre7). Ithat expected that no IO-APIC
> is found on my laptop? I used to have bios 1.21a but I downgraded to see if

There is no IO-APIC, and moreover, the LAPIC (disabled by BIOS by default)
is buggy and does not interact well with ACPI. Wasn't this particular
laptop blacklisted a while ago?

> the problem with FAN goes off. I've rebooted only once or twice, so cannot
> say if that helped at all. But 1.18 is my original BIOS version and I
> believe I had even with that version FAN problems.

The fan problem occurs at least in 1.18, 1.19 and 1.21. I did not test
others.

> mokrejs@vrapenec$ cat /proc/interrupts
>            CPU0
>   0:    8221410          XT-PIC  timer
>   1:     140910          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   5:     513521          XT-PIC  usb-uhci
>   8:          2          XT-PIC  rtc
>   9:    3588933          XT-PIC  acpi, usb-uhci, eth0
>  11:          0          XT-PIC  Intel ICH3
>  12:      23994          XT-PIC  PS/2 Mouse
>  14:     484418          XT-PIC  ide0
>  15:         24          XT-PIC  ide1
> NMI:          0
> LOC:          0
> ERR:          1
> MIS:          0

Do not compile neither IO-APIC nor UP-APIC. It's useless on this laptop.
BTW: under 2.4.22 (and recent 2.6.0, AFAIR), the above listing is the same,
except that the uhci-hcd goes from IRQ 9 to 11.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf