Soft lockup in native_safe_halt on CPU#0

[Ed Hargin]

I am getting these fairly regularly (every few hours perhaps). I have yet to work out exactly what the cause is, but it might be from, for example, viewing flash videos or playing with the wireless network settings. I will gladly give any more information requested, but I am not sure where this should be filed.

Hardware: Acer Aspire 5024
Processor:
AMD Turion 64 ML34, 1.8GHz CPU
Memory:
1024MB RAM
Video Chipset:
ATI Mobility Radeon X700 PCI Express
Wireless Card:
Broadcom BCM4318

[14270.647320] BUG: soft lockup - CPU#0 stuck for 11s! [swapper:0]
[14270.647322]
[14270.647324] Pid: 0, comm: swapper Tainted: P (2.6.24-12-generic #1)
[14270.647327] EIP: 0060:[<c011fc62>] EFLAGS: 00000246 CPU: 0
[14270.647330] EIP is at native_safe_halt+0x2/0x10
[14270.647332] EAX: 00000000 EBX: f7cec000 ECX: 10624dd3 EDX: f7cec02c
[14270.647335] ESI: f7cec278 EDI: c0479300 EBP: 000068a0 ESP: c041bfa0
[14270.647337] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[14270.647340] CR0: 8005003b CR2: 0823de44 CR3: 27264000 CR4: 00000690
[14270.647342] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[14270.647345] DR6: ffff0ff0 DR7: 00000400
[14270.647350] [<f88690c0>] acpi_safe_halt+0x1c/0x29 [processor]
[14270.647366] [<f8869129>] acpi_idle_enter_c1+0x5c/0x64 [processor]
[14270.647385] [<c02918fc>] cpuidle_idle_call+0x7c/0xb0
[14270.647397] [<c0103695>] cpu_idle+0x45/0xd0
[14270.647413] [<c041fa4a>] start_kernel+0x30a/0x3a0
[14270.647420] [<c041f130>] unknown_bootoption+0x0/0x1e0
[14270.647464] =======================

[Alex Lopez (alfitovdkiv)]

Hi, I can confirm this on the same Acer model, also in 2.6.24-19 kernel, using fglrx and b43 driver:

[ 1220.596228] BUG: soft lockup - CPU#0 stuck for 11s! [swapper:0]
[ 1220.596230]
[ 1220.596232] Pid: 0, comm: swapper Tainted: P (2.6.24-19-generic #1)
[ 1220.596235] EIP: 0060:[<c031c46d>] EFLAGS: 00000246 CPU: 0
[ 1220.596238] EIP is at _spin_unlock_irqrestore+0xd/0x20
[ 1220.596240] EAX: 00000246 EBX: 00000000 ECX: 00000246 EDX: 00000000
[ 1220.596242] ESI: 00000246 EDI: 00000001 EBP: 000068a0 ESP: c041df7c
[ 1220.596245] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[ 1220.596247] CR0: 8005003b CR2: b6b5f000 CR3: 35090000 CR4: 00000690
[ 1220.596250] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 1220.596252] DR6: ffff0ff0 DR7: 00000400
[ 1220.596254] [<c0247ed3>] acpi_get_register+0x2a/0x30
[ 1220.596276] [<f88691d5>] acpi_idle_enter_bm+0x51/0x2ce [processor]
[ 1220.596296] [<c0295f34>] menu_select+0x84/0xa0
[ 1220.596321] [<c02952bc>] cpuidle_idle_call+0x7c/0xb0
[ 1220.596333] [<c0102695>] cpu_idle+0x45/0xd0
[ 1220.596349] [<c0421a5f>] start_kernel+0x31f/0x3b0
[ 1220.596357] [<c0421130>] unknown_bootoption+0x0/0x1e0

[Julian Alarcon (julian-alarcon)]

This a duplicated bug from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/204996.

The problem begin in the linux version 2.6.22 and is fixed in the 2.6.25

[Chris Coulson (chrisccoulson)]

Julian - With all due respect Julian - what makes you think that this is a duplicate of bug 204996 other than the fact they share the word 'lockup' in common? The bug you referred to describes a complete freeze, with nothing in the kernel logs. This describes a soft lockup.

Ed - Thank you for taking the time to report this bug and help make Ubuntu better. Could you please try with the latest kernel (2.6.24-19). If you still have the same issue, then please include the following additional information (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[jedioetzi (jedioetzi)]

same problem:

Linux luca-laptop 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

[jedioetzi (jedioetzi)]

here the lspci log

thanks!

[geraldo (geraldo-servus)]

Same bug on Acer Aspire 5021 WLMi, Mobile AMD Turion 64 Processor ML28, ATI Mobility Radeon X600 PCI Express / 64MB VRAM, Broadcom BCM4318 wireless card, kernel 2.6.24-19, not using any proprietary drivers.

uname -a: Linux schleppi 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

[geraldo (geraldo-servus)]

here the dmesg error:

[15191.020042] BUG: soft lockup - CPU#0 stuck for 11s! [swapper:0]
[15191.020046]
[15191.020049] Pid: 0, comm: swapper Not tainted (2.6.24-19-generic #1)
[15191.020054] EIP: 0060:[<c011ec62>] EFLAGS: 00000246 CPU: 0
[15191.020061] EIP is at native_safe_halt+0x2/0x10
[15191.020066] EAX: 00000000 EBX: df9a0000 ECX: 00000286 EDX: 00000000
[15191.020071] ESI: df9a0278 EDI: c047c300 EBP: 000068a0 ESP: c041dfa0
[15191.020076] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[15191.020081] CR0: 8005003b CR2: b6968000 CR3: 37486000 CR4: 00000690
[15191.020086] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[15191.020090] DR6: ffff0ff0 DR7: 00000400
[15191.020098] [<f88670c0>] acpi_safe_halt+0x1c/0x29 [processor]
[15191.020123] [<f8867129>] acpi_idle_enter_c1+0x5c/0x64 [processor]
[15191.020152] [<c02952fc>] cpuidle_idle_call+0x7c/0xb0
[15191.020169] [<c0102695>] cpu_idle+0x45/0xd0
[15191.020191] [<c0421a5f>] start_kernel+0x31f/0x3b0
[15191.020202] [<c0421130>] unknown_bootoption+0x0/0x1e0

[Chris Coulson (chrisccoulson)]

Thanks for the information geraldo

[s|eepy (gregor-pifko)]

Same problem on the same Acer model: Acer Aspire 5024

dmesg start to get filled with this error and eventualy system (hard)locks up. I can only move mouse pointer and thats it. No respons on any running program. Even restarting X doesnt help. It starts to restart X but the proces hangs and only background is visible. Only reboot works.

Is there any workaround becouse this bug is getting on my nerves? Downgrade/upgrade kernel maybe?

Linux misko 2.6.24-21-generic #1 SMP Tue Aug 12 13:37:22 UTC 2008 i686 GNU/Linux

[s|eepy (gregor-pifko)]

lspci log

[Alex Lopez (alfitovdkiv)]

Hi.

I have observed the problem does not reproduce up to now using kernel boot parameter "noapic".
Could you confirm that?

Regards.

[s|eepy (gregor-pifko)]

Confirmed. This solves the problem. Thanks.

[jedioetzi (jedioetzi)]

which are the drawbacks of using noapic options?

[Chris Coulson (chrisccoulson)]

jedioetzi - You might find this useful: https://answers.launchpad.net/ubuntu/+question/4506

[geraldo (geraldo-servus)]

kernel boot parameter "noapic" also seems to solve the problem for me (no freeze since 24 hours). thanks for that tip!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Robert Collins (lifeless)]

This bug occurs for my father, after loading ndiswrapper. Loading the gutsy 2.6.24-15 kernel seems to make things work more smoothly. His hardware is an acer 4315 aspire.

[Robert Collins (lifeless)]

Oh, and noapic had no impact on the problem.

[Robert Collins (lifeless)]

@leanne, 2.6.27-2 causes a hard lockup of the machine, an acer aspire 4315 100508Ci laptop. Seems to be the ath_pci driver.

[Chris Coulson (chrisccoulson)]

Robert - Are you sure that you're seeing exactly the same problem as described by this bug report? Could you please post the call trace from your /var/log/kern.log

[Gianfranco (gianfranco-alongi)]

Hi!

I have ubuntu 8.04 on an LG Laptop.
I have had the same problem for a long long time. Grepping the kern.log outputs the latest "funnies"

Sep 19 16:56:46 zenon-laptop kernel: [ 3101.616162] BUG: soft lockup - CPU#0 stuck for 11s! [xchat:6116]
Sep 19 16:58:01 zenon-laptop kernel: [ 3176.864184] BUG: soft lockup - CPU#0 stuck for 18s! [xchat:6116]
Sep 21 17:11:15 zenon-laptop kernel: [ 1685.664276] BUG: soft lockup - CPU#0 stuck for 22s! [xchat:6254]
Sep 21 17:12:15 zenon-laptop kernel: [ 1745.664943] BUG: soft lockup - CPU#0 stuck for 24s! [swapper:0]
Sep 21 19:01:24 zenon-laptop kernel: [ 8292.681058] BUG: soft lockup - CPU#0 stuck for 11s! [events/0:9]
Sep 21 19:02:20 zenon-laptop kernel: [ 8348.040067] BUG: soft lockup - CPU#0 stuck for 19s! [xchat:6254]
Sep 21 19:40:08 zenon-laptop kernel: [10615.243228] BUG: soft lockup - CPU#0 stuck for 13s! [xchat:6254]
Sep 21 19:40:34 zenon-laptop kernel: [10641.370214] BUG: soft lockup - CPU#0 stuck for 24s! [xchat:6254]
Sep 21 19:42:58 zenon-laptop kernel: [10785.901760] BUG: soft lockup - CPU#0 stuck for 11s! [xchat:6254]

My lspci output

00:00.0 Host bridge: ATI Technologies Inc Unknown device 7930
00:01.0 PCI bridge: ATI Technologies Inc Unknown device 7932
00:04.0 PCI bridge: ATI Technologies Inc Unknown device 7934
00:06.0 PCI bridge: ATI Technologies Inc Unknown device 7936
00:07.0 PCI bridge: ATI Technologies Inc Unknown device 7937
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Xpress 1250
01:05.2 Audio device: ATI Technologies Inc RS600 audio device [Radeon Xpress 12xx Series]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8039 PCI-E Fast Ethernet Controller (rev 15)
08:00.0 Network controller: RaLink Unknown device 0781

I tried the above mentioned "noapic" hack, which for now seems to work.

[Robert Collins (lifeless)]

On Thu, 2008-09-11 at 10:00 +0000, Chris Coulson wrote:
>
> Robert - Are you sure that you're seeing exactly the same problem as
> described by this bug report? Could you please post the call trace
> from
> your /var/log/kern.log

I'm sorry, I can't - I'm in the wrong country to debug this further. Iam
I 100% certain - well it matched all the variables I looked at at the
time.

-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

[Gianfranco (gianfranco-alongi)]

So, I previously posted that i tried the "noapic" kernel option.
However, this has not helped.... I forgot to mention that this bug is only present when one of my cores is NOT disabled.
That is; the bug does not show itself when I disable one of the cores on startup (BIOS desable one core)

This is the latest entry from my logs

/var/log/kern.log:Sep 26 14:20:44 zenon-laptop kernel: [ 6287.130565] BUG: soft lockup - CPU#0 stuck for 31s! [xchat:6246]
/var/log/kern.log:Sep 26 14:20:59 zenon-laptop kernel: [ 6301.633472] BUG: soft lockup - CPU#0 stuck for 12s! [events/0:9]
/var/log/kern.log:Sep 26 16:18:31 zenon-laptop kernel: [13351.886316] BUG: soft lockup - CPU#0 stuck for 20s! [xchat:6246]
/var/log/kern.log:Sep 26 16:19:05 zenon-laptop kernel: [13385.737463] BUG: soft lockup - CPU#0 stuck for 24s! [xchat:6246]
/var/log/kern.log:Sep 26 16:20:18 zenon-laptop kernel: [13458.496987] BUG: soft lockup - CPU#0 stuck for 15s! [pidgin:6166]
/var/log/kern.log:Sep 26 16:54:58 zenon-laptop kernel: [15537.451700] BUG: soft lockup - CPU#0 stuck for 17s! [xchat:6246]
/var/log/kern.log:Sep 26 16:57:37 zenon-laptop kernel: [15696.388054] BUG: soft lockup - CPU#0 stuck for 12s! [xchat:6246]
/var/log/kern.log:Sep 26 16:58:55 zenon-laptop kernel: [15774.384863] BUG: soft lockup - CPU#0 stuck for 20s! [firefox:6155]
/var/log/kern.log:Sep 26 17:24:02 zenon-laptop kernel: [17280.893772] BUG: soft lockup - CPU#0 stuck for 15s! [xchat:6246]
/var/log/kern.log:Sep 26 17:24:32 zenon-laptop kernel: [17310.665437] BUG: soft lockup - CPU#0 stuck for 12s! [xchat:6246]
/var/log/kern.log:Sep 26 17:26:58 zenon-laptop kernel: [17456.874435] BUG: soft lockup - CPU#0 stuck for 11s! [xchat:6246]

[Chris Coulson (chrisccoulson)]

We're getting quite a few people posting in this report that may or may not have the same issue. For the benefit of the reporter, kernel team and the other people that are definately experiencing this bug, I want to try and avoid this report becoming like some other reports have done in the past (where they just become too messy to follow).

I want to try and get this report in to a state where I can set it to triaged, and to do that, I will need to ask for some more information (I need a complete set of data off at least one person really).

Ed Hargin - Could you please include all of the information requested at https://wiki.ubuntu.com/DebuggingACPI separate attachments?

geraldo - It looks like you are seeing the same oops as the original reporter. Could you also please provide any information requested in https://wiki.ubuntu.com/DebuggingACPI which you haven't already provided (I think it is just the output of dmidecode and the contentsof /proc/acpi which is outstanding)

Alex Lopez - After comparing your call trace to Ed's and geraldo's, it seems your oops occurs in a slightly different place. I would encourage you to open another report for your problem.

Gianfranco - There is no evidence from the data you have given that you are experiencing this problem. Please open up another report with the kernel BUG messages from your /var/log/kern.log

Thanks for your co-operation :)

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Roman Littlestork (one-shadow-walker)]

I am running Ubuntu 10.10 Studio, Kernel Linux 2.6.35-26 Generic, GNOME 2.32.01Gb memory with 128 Mb shared video on an NVIDIA card leaving me 874.2 Mb of memory on an AMD Sempron Processor 3100+. I have installed all the latest updates, sans what was affected by a hard freeze. The same BUD affects me as well. I am willing to help by submitting any and all necessasary information in order to resolve this BUG as it affects me every day! It often happens when I am updating and installing via the Synoptic kage Installer. This also happens when I am surfing the net, I may have only 2-3 tabs open or I may have 10 or more tabs open without freezing up. It happens shortly after startup, or I can be on the net for hours w/out freezing up. Any good info there? Need more? Let me know if you have any ideas.

[Andy Whitcroft (apw)]

@Roman -- could you run an "apport-collect 206316" to get current system information, and please confirm here that this issue still remains. Thanks!

[Roman Littlestork (one-shadow-walker)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: indio54 3034 F.... pulseaudio
 /dev/snd/controlC0: indio54 3034 F.... pulseaudio
 /dev/snd/pcmC0D0p: indio54 3034 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH'/'Intel ICH with ALC655 at irq 23'
   Mixer name : 'Realtek ALC655 rev 0'
   Components : 'AC97a:414c4760'
   Controls : 41
   Simple ctrls : 26
Card1.Amixer.info:
 Card hw:1 'U0x46d0x824'/'USB Device 0x46d:0x824 at usb-0000:00:0b.1-1, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0824'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 6144
   Mono: Capture 0 [0%] [6.00dB] [off]
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=2d9b41cb-1786-4128-b4aa-39602a75ca2c
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gateway W3107
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=806303bd-b16c-414f-b21f-800579c8660a ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-27.47-generic 2.6.35.11
Regression: No
RelatedPackageVersions: linux-firmware 1.38.4
Reproducible: No
RfKill:

Tags: maverick kernel-fs needs-upstream-testing
Uname: Linux 2.6.35-27-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev root sambashare scanner tape users video
WpaSupplicantLog:

dmi.bios.date: 11/25/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: K8MC51G
dmi.board.vendor: First International Computer, Inc.
dmi.board.version: PCB 1.x
dmi.chassis.asset.tag: Asset Tag Number xxxxxx
dmi.chassis.type: 3
dmi.chassis.vendor: Manufactory Name
dmi.chassis.version: Version xx
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/25/2005:svnGateway:pnW3107:pvrSYS-xxxxxx:rvnFirstInternationalComputer,Inc.:rnK8MC51G:rvrPCB1.x:cvnManufactoryName:ct3:cvrVersionxx:
dmi.product.name: W3107
dmi.product.version: SYS-xxxxxx
dmi.sys.vendor: Gateway

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

apport information

[Roman Littlestork (one-shadow-walker)]

What startted out as a soft lockup has long ago turned into a complete freeze! The soft lockup part is experienced in reboot messages displayed in the onscreen process being executed, they state BUG SOFT LOCKUP 61 secs; however, while I am using the system, I am experiencing the complete freeze of the entire system. I ultimately have to execute a cold-kill with the on/off switch on the machine and follow that with an F10 & selecting BOOT from HARD-DRIVE, then in the next screen, I will select recovery mode followed by selecting from the menu-> Repair Packages. This will recover the system from the freeze, however if I was using the synoptic package installer, I then have to open a terminal, enter: "sudo dpkg --configure -a" to recover functionality of the synoptic package installer. This "freeze" can occur with only one workspace open and no Internet Browsers open or I can have 2-4 workspaces open with multiple downloads going and browsing the internet with anywhere from 8-12 tabs open and 2 browsers online on the same time. It also happens when downloading updates, installing updates, or not until it is doing a cleanup after updaqting. BTW, the version is likely not the issue as I have been running Ubuntu 10.10 Studio edition for nearly 2 monthe using Kernal Linux 2.6.35-27 running GNOME 2.32-0. YES, this IS Release 10.10 (maverick) and it is currently completely up to date. Soooo, what would you have me do? I am willing to run whatever diagnostics you may need and am willing to give a complete report of all system diagnostics your team may require. just send me info on the command line diologues I need to enter and I will fullfill oyur every wish as this is the most completely updated system I see in the reports of this nature. ShaDDoWWalkeR

[Roman Littlestork (one-shadow-walker)]

Soooooo, I am now considering starting a BLOG as this matter has become so entailing! LOL Just kidding. SO, it has happened again, this time to the extent that I was unable to recover in the usual manner because after I selected - repair - the whole system completely froze in recovery mode as well and upon reboot, I completely lost video so ouy of frustration, I resorted to using my Windows system on my laptop. Now THAT IS BAD! I also was able to determine as the very start of the boot dialog that this BUG is loaded even before the BOOT SECTOR is loaded. This reminds me of the archaic viruses which plagued Windows 3.11 running DOS 6.11 of which the worst were of a genere known as TSR, "Terminate and Stay Resident", thus called TSR as they became more common. These also were pre-loaded before the BOOT SECTOR was loaded causing them to be much more resilient than regular virus'.
The only way to cure most of these was to boot into DOS and load the back-up copy of the original MBR, or Master Boot Record. Yhis was always found at the very end of the hard drive, no matter how litle data was on the drive, so as to separate it and therefore protect it from the rest of the data on the drive. It was also contained in its own separate sector of which didn't even show up on normal scans of the drive. Sort of like NTFS now does, but before the time when NTFS came to exist. I originaly installed the OS as UBUNTU 8.10d Desktop i386 Live CD burned on 11/16/08 on a University of Texas Library computer so I am certain it contained no BUGS. I didn't experience the problem until I upgraded to UBUNTU STUDIO 10.10.I hooe this last bit of info along with the history lesson may help in "killing" the BUG". Until then, I am outta here. Roman Littlestork

[Roman Littlestork (one-shadow-walker)]

And YES! I HAVE been into computers that long. I first started programming in BINARY and was also an IBM Keypunch instructor. Go ahead, figure it out. (1970/1971 fiscal year)