Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

My ubuntu 10.10 is freezing during downloading from my other computer on sftp. I thought it might be some nautilus issues so I tried it via command line and I got the same thing - after few minutes the whole computer freezes.

Mostly the numlock led is blinking (I've heard somewhere that this means a kernel panic), but not in 100% cases.

I dunno if that helps but here is a log from /var/log/message in the time that this happened. At least I hope so - it wasn't that big, when it happened before. But this looks quite "errorish", right? (isn't complete - see bottom)

Jan  5 17:57:49 tomas-ntb kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jan  5 17:57:49 tomas-ntb rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="953" x-info="http://www.rsyslog.com"] (re)start
Jan  5 17:57:49 tomas-ntb rsyslogd: rsyslogd's groupid changed to 103
Jan  5 17:57:49 tomas-ntb rsyslogd: rsyslogd's userid changed to 101
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] Initializing cgroup subsys cpuset
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] Initializing cgroup subsys cpu
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] Linux version 2.6.35-24-generic (buildd@vernadsky) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 (Ubuntu 2.6.35-24.42-generic 2.6.35.8)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] BIOS-provided physical RAM map:
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 0000000000100000 - 00000000dffa8000 (usable)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000dffa8000 - 00000000dffb0000 (ACPI NVS)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000dffb0000 - 00000000dffbff00 (ACPI data)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000dffbff00 - 00000000dfff0000 (ACPI NVS)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000dfff0000 - 00000000e0000000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 00000000ff700000 - 0000000100000000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  BIOS-e820: 0000000120000000 - 0000000140000000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] DMI 2.5 present.
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] last_pfn = 0xdffa8 max_arch_pfn = 0x100000
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] Scanning 0 areas for low memory corruption
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000] modified physical RAM map:
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  modified: 0000000000010000 - 000000000009e800 (usable)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  modified: 000000000009e800 - 00000000000a0000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  modified: 00000000000e0000 - 0000000000100000 (reserved)
Jan  5 17:57:49 tomas-ntb kernel: [    0.000000]  modified: 0000000000100000 - 00000000dffa8000 (usable)

... to long - for whole and better view click here

share|improve this question

closed as off topic by Marco Ceppi Feb 3 '12 at 0:19

Questions on Ask Ubuntu are expected to relate to Ubuntu within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
Please file a bug report and debug the problem per help.ubuntu.com/community/DebuggingSystemCrash . –  João Pinto Jan 5 '11 at 19:16
    
Well so I followed this, memory test gave zero results than I tried to reproduce the crash in a text console, which was successful but I wasn't able to print the desired output. So I tried the remote version of this, but I am not able to reproduce the crash again. I copied like 3G of files successfully. I just don't get it... I'll try it further and I'll see. But it's strange. –  tsusanka Jan 5 '11 at 22:29
    
Well so reproduced the crash again - already twice, but in neither of those cases i didnt get any output from /proc/kmsg (using ssh on second computer).. What shall I do then? –  tsusanka Jan 20 '11 at 18:08
    
This question should instead be filed as a bug report, and as such is off-topic, thanks! Instructions here. –  jrg Feb 3 '12 at 0:07

1 Answer 1

Maybe, for the time being, you can download using a different utility, such as PSFTP (installed from Synaptic Package Manager) ?

share|improve this answer
1  
-1 since it crashes both from nautilus and command line sftp it is very unlikely that using a different utility will help. It seems to be a kernel bug during the transfer. –  João Pinto Jan 5 '11 at 19:59
    
ok, so I get a -1 just for a suggestion that was reasonable? –  djangofan Jan 6 '11 at 21:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.