Skip to contentSkip to conversation

2.6.5-mm2 (swsusp not working and acpi problem) (fwd)

DISCUSSION Pavel Machek 2 participants 2 messages Apr 15, 2004 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]

#1 lore raw

Hi!

Quoted 5 lines

I tried updating from 2.6.4-rc1-mm2 to 2.6.5-mm2, and I found two problems:

First, swsusp stopped working, I get a NULL pointer in _poke_blanked_console' after all the other things seem to be fine.

Its not in poke blanked console, its is in memorymanagment. Try latest -aa.

Quoted 3 lines

I made a screenshot available under
http://mh57.de/~martin/oops-part1.png and
http://mh57.de/~martin/oops-part2.png

Hmm, someone should create "OCR for linux-kernel-mailinglist" project.

Quoted 8 lines

This happens regardless of starting X or using the framebuffer. The hardware is an IBM Thinkpad T41p. In the screenshots above, the kernel is tainted from the madwifi module, but not loading it before did not change the oops.

The kernel contains two more patches, linux-iscsi-kernel-4.0.1.3.patch and linux-2.6.3-mppe-mppc-0.99.patch.gz, but these two modules were not loaded before during my tests.

Really? Those taints look scary.
Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
#2 lore raw
Quoted 9 lines · Pavel Machek

Hi!

Quoted 5 lines

I tried updating from 2.6.4-rc1-mm2 to 2.6.5-mm2, and I found two problems:

First, swsusp stopped working, I get a NULL pointer in _poke_blanked_console' after all the other things seem to be fine.

Its not in poke blanked console, its is in memorymanagment. Try latest -aa.

I had tried -mm4 later, there it worked again. I'm sorry I forgot to mention this here.

I'll try the latest -mm on the weekend.

LLAP, Martin