Created attachment 28681 [details]
photo of the T23 laptop screen with the last part of the backtrace
Beware, this might well be a TuxOnIce bug, but the backtrace looks quite general so I am reporting it here. I set Nigel Cunningham on Cc, so he can comment too.
Last kernel and tuxonice-Version that worked: 126.96.36.199-tp23-toi-188.8.131.52-04990-g3a7d1f4 (Nigel's 2.6.34 TuxOnIce tree).
I am testing 184.108.40.206 with TuxOnIce 3.2-rc1 on my ThinkPad T23.
After I few hibernation cycles I now got a backtrace on resume. I tried twice before discarding the image.
I don't know yet, whether it happens regularily. I am attaching a screenshot of the backtrace.
martin@deepdance:~> cat /proc/version
Linux version 220.127.116.11-tp23-toi-3.2-rc1-05026-g59f8a60 (martin@deepdance) (gcc version 4.4.4 (Debian 4.4.4-7) ) #2 PREEMPT Fri Aug 27 08:55:54 CEST 2010
martin@deepdance:~#1> cat /sys/power/tuxonice/debug_info
TuxOnIce debugging info:
- TuxOnIce core : 3.2-rc1
- Kernel Version : 18.104.22.168-tp23-toi-3.2-rc1-05026-g59f8a60
- Compiler vers. : 4.4
- Attempt number : 0
- Parameters : 0 667648 0 0 0 0
- Overall expected compression percentage: 0.
- Checksum method is 'md4'.
0 pages resaved in atomic copy.
- Compressor is 'lzo'.
- Block I/O active.
- Max outstanding reads 1. Max writes 1.
Memory_needed: 1024 x (4096 + 220 + 76) = 4497408 bytes.
Free mem throttle point reached 0.
- Swap Allocator enabled.
Swap available for image: 246902 pages.
- File Allocator active.
Storage available for image: 0 pages.
- No I/O speed stats available.
- Extra pages : 0 used/500.
- Result : No hibernation attempts so far.
Created attachment 28691 [details]
configuration of the kernel that showed the backtrace
Created attachment 28701 [details]
lspci -nnvv of the ThinkPad T23 that showed the backtrace
Unfortunately the trace in the attachment is incomplete, so it is hard to say
what function triggered it and what kind of a message this is (ie. WARN_ON(), BUG_ON() etc.).
Generally, though, there were no hibernate problems reported for 2.6.35.y kernels
I'm sorry to say that the report is of no use to me either.
Martin, if you get it again, would you try adding "toi_debug_setup toi_pause" to the command line? That will get you more verbose debugging and make TuxOnIce pause (assuming you're using a userui) so you can see what's going on.
I didn't see this again. I had another backtrace with a kernel with a slightly newer TuxOnIce 3.2-rc2 (instead of rc1), but this one looks TuxOnIce related so I asked on tuxonice-devel mailing list.
This can be closed as unreproducable. I can always reopen it if need be. I set tty resolution to vga=791, so next time there should be more to see from the backtrace.
Alright, thanks for the update.