Regression: Ubuntu 9.04 Beta goes to BusyBox (like in 8.10) [ATI Chipset]

[jusko]

Goes to busybox on 9.04 Beta
Like on 8.10 i have BusyBox when i trying to run Ubuntu LiveCd.

Info about my hardware:

- Processor: AMD64 4200+
- Video Card : ATi Radeon X1200 Series
- Disk: ATA Hitachi HDS72161
- 1024 MB RAM

BusyBox message (one per second):

"EXT3-fs: mounted filesystem with ordered data mode
kjournal starting. Commit interval 5 seconds"

[Jon Charge (seropith)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Jon Charge (seropith)]

I see you added more to the description just before I requested more information. Please disregard my above message.

Best,
Jon

[Jon Charge (seropith)]

Is this message repeated for the entire time the system is up, or just a few times?

[jusko (jusko)]

All the time when I try to boot system from LiveCd. This message fill the screen (about 30 seconds). Next thing i see is BusyBox.

p.s : Sorry for bad english - im from Poland.

[Paul Dufresne (paulduf)]

Note: Symptoms similar with https://bugs.launchpad.net/bugs/350531

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (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!

[Dan Dart (dandart)]

uname -a:
Linux dominator 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

Note: These attachments are from a working system, not the one that broke, just one I had to do "hpet=disable" on

[Dan Dart (dandart)]

Whoop. Wrong bug..

[Paul Dufresne (paulduf)]

Sorry Jusko, asking you to give these infos is probably meaningless if you can't boot a working Linux.

But you could try the tricks that have worked for Dan:
On the Live CD boot screen, press F6, erase "quiet splash" and replace it by "acpi=off".
If it won't help, you could try to replace it by "hpet=disable".

[jusko (jusko)]

hpet=disable and acpi=off won't work - still this same message and BusyBox. It's second version of Ubuntu that I can't use (8.10 and 9.04) :-( Im using 8.04 - good it's LTS. Well... I must wait to 9.10. Maybe this version will be working on my PC.

[Paul Dufresne (paulduf)]

Thanks for these new information Jusko.

Which CD image were you using? (mostly wanting to know if using 32 or 64 bits version)

I note that your dmesg.log have the following:
[ 35.170685] Clocksource tsc unstable (delta = -90900229 ns)
...
[ 41.773114] hda-intel: Invalid position buffer, using LPIB read method instead.

Well, I have no clue about the second.

I don't really understand the first, but it might be an idea to try to boot with:
clocksource=jiffies

also I guess adding 'debug' to kernel parameters may help to have more precise messages.

And in fact, if you have fast access to the Internet, you really should try 9.04 Beta Live CD:
http://www.ubuntu.com/testing/jaunty/beta

[Paul Dufresne (paulduf)]

Also, since it seems to be an ATI chipset (not even sure what I say here) you could try:
enable_timer_pin_1
kernel parameter.

[jusko (jusko)]

Even with enable_timer_pin_1, clocksource=jiffies or debug, still I have BusyBox and that messages. All Ubuntu versions works fine (even 4.10). I have problem only with 8.10 and 9.04. I fear about next version of Ubuntu on my PC. It seems my machine is now incompatible with Intrepid Ibex and Jaunty Jackalope. I think I must wait to 9.10, but I fear BusyBox even on Karmic.

p.s : Again - Im sorry for my bad english

[jusko (jusko)]

Oh - I have 64bit processor, but preffer 32bit - more applications and no complications with 32bit depends. BusyBox appears on 32 and 64bit version.

[Paul Dufresne (paulduf)]

Sorry, I somehow did miss the title bug that says that it is on 9.04 Beta... and 8.10.

Well I guess as a bug triager I did my part.
Confirming the bug to let a kernel team member to look at it.

[Paul Dufresne (paulduf)]

Oh well, maybe I am forgetting something:

When in busybox, you could try to:
cat /var/log/syslog and looks for errors.

If you know a bit about command line, you could probably copy the file to an USB key, then attach it to this bug.

[jusko (jusko)]

Booting 9.04 Beta (or 8.10). BusyBox appears. Typing "cat /var/log/syslog".

Message appears:

"cat: can't open 'var/log/syslog' : No such file or directory"

In /var I have only one, empty folder - lock.

Any ideas ? :-(