lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9481e140611031506u42e326dbs5c0e97d14c5fb5b3@mail.gmail.com>
Date:	Sat, 4 Nov 2006 00:06:58 +0100
From:	"Nicolas FR" <nicolasfr@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: sc3200 cpu + apm module kernel crash

Hi,

I am currently trying to setup a fully functionnal linux on a Tatung
webpad (shipped with winCE), which has a AMD/NSC SC3200 CPU (more
details on my blog here: http://www.geek-fr.com ). So far everything
goes fine except one thing:

when I try to load the APM module, the kernel crashes. I have tried
different options, but always got the same crash. I have enabled some
verbosing and finally found that the crash is happening in
arch/i386/kernel/apm.c in function static void apm_mainloop(void) when
calling apm_event_handler();

I have thrown a bunch of  "printk(KERN_INFO "apm: I am here\n");" and
noticed the crash is happening just when calling apm_event_handler();
and does not even execute any instruction in this function... This is
the point I don't understand, how can it crash just on calling a
function and not executing the first statement in this function?

Moreover by enabling soft lockup detection I have managed to get those
informations:

==========================
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: entry f000:51c8 cseg16 f000 dseg 40 cseg len ffff, dseg ken ffff
cseg16 len ffff
apm: Connection version 1.2
apm: AC on line, battery statys high, battery life 100%
apm: battery flag 0x01, battery life unknown

BUG: soft lockup detected on CPU#0!
[<c011d102>] update_process_times+0x22/0x60
[<c0106441>] timer_interrupt+0x41/0x80
[<c0134773>] handle_IRQ_event+0x33/0x60
[<c0134813>] __do_IRQ+0x73/0xd0
[<c0105171>] do_IRQ+0x31/0x70
[<c0103b1a>] common_interrupt+0x1a/0x20
[<c0409200>] do_cyrix_devid+0x60/0x90
==========================

Any idea on what can be happening here?

Regards,
Nicolas.

PS: please CC me if answering this message, as I am not subscribed to the list
PPS: I have read the list FAQ before posting, but still if this
message is not appropriate to the list, then sorry.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ