Skip to contentSkip to conversation

Bizzare crashes on IBM Thinkpad A22e

DISCUSSION Tester 4 participants 5 messages Aug 31, 2001 – Sep 1, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Tester

author
#1 lore raw

Another thing,

Linuxcare has certified this laptop as being compatible with Linux 7.1
http://www.linuxcare.com/labs/certs/ibm/thinkpad/A22e/pada22e-2655-rh7-sys.epl

Did they do something that I dont know of? Is there anyone left there?

Tester

Quoted 1 line · Sean Hunter

<Possibly not relevant to your problem>

It is indeed not relevant.. I dont have any pcmcia card as there is an integrated Network adapter... (Intel EEPro100)

Quoted 30 lines

I have a thinkpad and had all sorts of wierd and unpredictable crashes until I removed the old 3com pcmcia network card and replaced it with a new cardbus card. The old card works fine in all sorts of other laptops, but the thinkpad just wasn't having it.

Since replacing the card its worked great.
</>

Sean

Quoted 18 lines · Tester

Hi,

Its a 256 megs machine.. Celeron 800..
I tried using mem=255M or mem=200M and it did not change anything and still crashed. The celeron A22e seems to have the same bios as the A21e...

Btw, I received it as part of a ThinkPad University program (laptop at school) from IBM with the old mandrake installed. And they IS guy of the university told us that they didnt install the latest released because IBM had not approved it... IBM probably already knows of the problem... So a message to IBM and IBMers: Why dont you fix your known bugs?

Also it works correctly in w2k, but win2k uses ACPI and not APM (and it has a IBM pm driver...)

Tester
[email protected]

Signature · 4 lines
Tester
[email protected]

Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer
#2 lore raw

Re: Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related

Hi,

Ok, I've tried removing different parts of the kernel and I have been able to find that the instability (repetable freezes) start to appear when the yenta_socket.o module is loaded. I dont see the link between this module and the events that trigger the freezes... It crashes when I do the following things: use any of the non-keyboard buttons (thinkpad buttons and volume control), brightness control, etc.. These buttons fn-X combination have in common that they do not generate a scancode as shown by showkey.

Signature · 6 lines
Olivier Crete
Tester
[email protected]
[email protected]

Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer
#3 lore raw

Re: Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related

In reply to Tester
Quoted 10 lines · Olivier Crete

Hi,

Ok, I've tried removing different parts of the kernel and I have been able to find that the instability (repetable freezes) start to appear when the yenta_socket.o module is loaded. I dont see the link between this module and the events that trigger the freezes... It crashes when I do the following things: use any of the non-keyboard buttons (thinkpad buttons and volume control), brightness control, etc.. These buttons fn-X combination have in common that they do not generate a scancode as shown by showkey.

Try -ac kernels with PNPBIOS enabled ...

Gerd

Signature · 1 line
Damn lot people confuse usability and eye-candy.
#4 lore raw

Re: Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related

In reply to Tester
Quoted 8 lines · Olivier Crete

Ok, I've tried removing different parts of the kernel and I have been able to find that the instability (repetable freezes) start to appear when the yenta_socket.o module is loaded. I dont see the link between this module and the events that trigger the freezes... It crashes when I do the following things: use any of the non-keyboard buttons (thinkpad buttons and volume control), brightness control, etc.. These buttons fn-X combination have in common that they do not generate a scancode as shown by showkey.

Hmm, I had a similar kind of freeze when using USB hotplug and PCMCIA. I could solve mine by only having CardBus support in the kernel:

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
CONFIG_CARDBUS=y
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set

Erik

Signature · 5 lines
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
Phone: +31-15-2783635  Fax: +31-15-2781843  Email: [email protected]
WWW: http://www-ict.its.tudelft.nl/~erik/
#5 lore raw

Re: Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related

In reply to Tester

In article <[email protected]>,

Quoted 9 lines · Olivier Crete

Ok, I've tried removing different parts of the kernel and I have been able to find that the instability (repetable freezes) start to appear when the yenta_socket.o module is loaded. I dont see the link between this module and the events that trigger the freezes... It crashes when I do the following things: use any of the non-keyboard buttons (thinkpad buttons and volume control), brightness control, etc.. These buttons fn-X combination have in common that they do not generate a scancode as shown by showkey.

What they are doing, however, is to generate a SCI, ie "System Control Interrupt". Which, I bet you five bucks, is routed to the same interrupt that your CardBus controller is on.

So the fact that the system hangs only with the CardBus module loaded really has nothing to do with the yenta code itself - it's just that before the yenta module is loaded, the SCI will be entirely ignored. Once yenta _is_ loaded, however, we have a interrupt handler for the interrupt and will start accepting it.

However, the interrupt handler we have is _not_ aware of system control interrupts. So it won't be able to handle them, and the interrupts will go on forever - locking up the machine.

The problem here is that the SCI really _should_not_ generate a regular interrupt unless the system is ready to accept it. The SCI can be routed to a SMI (system management interrupt, which puts the CPU in SMM mode, at which point the BIOS SMM routines can handle it), _or_ if you have ACPI enabled, ACPI should be (a) enabling the SCI->regular irq routine _and_ (b) actually handling the irq.

Do you have ACPI enabled in your kernel?

What are the bootup messages?

Linus