Interesting that a re-install fixed it in your case. I currently run a
1GB md mirrored root filesystem (without a separate /home) and re-
installing is a big project - I'll need an extra drive before I can
attempt it.
I tried to boot Kubuntu live from a USB stick and see if I could trigger
a
Toal,
I don't believe my bug has anything to do with xorg I can trigger
it by using handbrake (CLI) to rip a DVD with no X server running.
Just testing it again (using linux 2.6.35-22)...
1) booted without nolapic kernel parameter
2) switched to tty1
3) login and sudo stop kdm
4) begin
Toal,
linux-image-2.6.35-22-generic does not correct it. Nor does any
upstream kernel I've tested up to 2.6.36-020636rc7-generic correct it.
Thanks,
Phil
--
[maverick] intermittent full system freeze
https://bugs.launchpad.net/bugs/586901
You received this bug notification because you are a
** Summary changed:
- [lucid] intermittent full system freeze
+ [maverick] intermittent full system freeze
--
[maverick] intermittent full system freeze
https://bugs.launchpad.net/bugs/586901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** This bug is no longer a duplicate of bug 585765
Ubuntu 10.04 random freezes
--
[lucid] intermittent full system freeze
https://bugs.launchpad.net/bugs/586901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I've removed the duplicate status of this report (previously marked
duplicate of #585765.) I've been living with bug for over six months
now (running with only 1 core enabled out of two) , and believe that it
is quite specific and distinct from the range of issues in #58575.
My system was stable
*** This bug is a duplicate of bug 549756 ***
https://bugs.launchpad.net/bugs/549756
Omer. Yes, 549756 is a duplicate of this bug, which as you can see from
David's post is still an issue in Maverick.
I agree, this is more likely to be a ubiquity issue than grub2, as it
has to do with the
*** This bug is a duplicate of bug 549756 ***
https://bugs.launchpad.net/bugs/549756
** This bug has been marked a duplicate of bug 549756
[Regression] Installing to USB drive, proposes MBR to be written to internal
disk
--
[karmic] grub re-writes boot sector on wrong drive on fresh
I believe this is actually a duplicate of the earlier bug #414996,
marked critical against grub2 (do to it's potential for data loss or
making a system unable to boot.) However, I've marked the earlier bug
as duplicate as this likely correctly identifies ubiquity as the
project.
--
[Regression]
Hi Ignor. acpi_skip_timer_override does not work for me. So far the
only thing that stabilizes my system is nolapic, which has the side-
effect of disabling my second core.
--
Ubuntu 10.04 random freezes
https://bugs.launchpad.net/bugs/585765
You received this bug notification because you are a
Hi Steve,
I'm not sure which kernel, specifically, you want tested from
proposed. but I tested 2.6.32-24.38 (amd64) and I'm still seeing
freezes. (I find ripping a DVD in handbrake is the easiest way to force
a freeze in only a few minutes, but I still get freezes randomly without
it).
** This bug is no longer a duplicate of bug 585765
Ubuntu 10.04 random freezes
--
Regular freezes experienced in Ubuntu Lucid
https://bugs.launchpad.net/bugs/569011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
All, please note from the earlier posts florianr, myself, and
others confirmed that the freezing we were seeing could still happen
without X and the desktop running, and on very different video hardware.
If your bug seems to be graphics related, you should probably report it
separately.
I
*** This bug is a duplicate of bug 585765 ***
https://bugs.launchpad.net/bugs/585765
I am able to avoid hangs if I boot with kernel parameters noapic
nolapic. This is different from the reporter of bug #585765, and that
reporter is moving to a different distribution.
Please remove the
The suggestion of using 2.6.31-10-rt prompted me to give
2.6.32-22-preempt a try. While I was impressed with how responsive the
desktop seemed with a mix of high CPU load tasks going on in the
background, it still failed the torture test and locked up this
time with the return of both the
Just so we don't get too many unrelated freezes being tracked in this thread...
the symptoms characterized by florianr were:
- issue was NOT present prior to 10.04
- intermittent system-wide freezes
- frozen image on screen, showing the desktop image without any change and not
taking
I had 3 freezes yesterday. In each case the last entry in kern.log was:
do_IRQ: 0.189 No irq handler for vector (irq -1)
(Sometimes the number is 0.175, 0.177).
(Interestingly, there have been no instances of the BUG: CPU soft
lockup messages in the last two days.
I ran a memory test overnight
I had a freeze during the night, with the last message that was written
kern.log:
Jun 3 01:21:47 family kernel: [13403.676449] do_IRQ: 0.177 No irq
handler for vector (irq -1)
Examining the log more closely, I've had four freezes in the last 24
hours... in each case, there are between 1 and 4
Priority should be at least high. I experienced over a dozen crashes
last night, as I tried various kernels. Finally my system wouldn't boot
anymore - just a grub prompt, and no menu. (I think, because the
system froze while I was installing an old kernel/headers.) Took me
about 3 hours to
I've had the same behaviour while playing audio... a few seconds of
audio playing over and over again, and no other response from the system
(except possibly ping...didn't check that when it happened.)
If it's related to disk I/O... I boot from a RAID-1 EXT4 root file
system, assembled from 2 x
Okay, some progress. I was on a screen showing the System Monitor and
some processor load widgets when I experienced my most recent freeze.
The System Monitor window went blank, but I could still move the mouse,
and I could the processor load widgets kept running I could see that
both cores
Me again. ;-) Checking my old logs further, I found 92 incidents of
BUG: soft lockup from a variety of processes (kswapd, soffice.bin,
mythbackend, firefox-bin, soffice.bin). In each case, the CPU
(sometimes CPU#0, sometimes CPU#1... I only have two cores) is stuck for
a reported 61s.
Well...so much for that theory. nomodeset did not stop the lock-ups for
me. Did not get a soft lockup message this time, but I may have
rebooted before it was written to the log.
--
Ubuntu 10.04 random freezes
https://bugs.launchpad.net/bugs/585765
You received this bug notification because
I removed virtualbox-3.2 just to eliminate outside code from the kernel,
and because I saw a higher frequency of freezes with virtualbox running.
System still froze with virtualbox removed.
Also tried going back to 2.6.32-21-generic, and still had the freezes.
Three freezes so far today, with the
Hi Florian,
I agree, my bug (586901) is a duplicate of yours - thanks for catching
it. However, I would say kai's problem in the above comments is
different, as I've never been able to ssh in after a freeze, and I
gather you haven't either.
I see the exact same behaviour as you under the
Public bug reported:
This bug may be a duplicate of #569011 (which inexplicably now has a
status of fix-released), however there are minor differences.
I have been experiencing occasional (2 or 3 times a day) system hangs
under Lucid/10.04 for at least a couple of weeks, with the following
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/49268269/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/49268270/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49268271/BootDmesg.txt
**
** Tags removed: needs-upstream-testing
--
[lucid] intermittent full system freeze
https://bugs.launchpad.net/bugs/586901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As mentioned, I've tested using upstream kernel 2.6.34-020634-generic,
from May 17. However, for good measure I'll test with the latest
nightly, linux-image-2.6.34-999-generic_2.6.34-999.201005261208 (May 26)
and verify that it hasn't been fixed in the last week.
--
[lucid] intermittent full
BTW, I've also tried booting with noacpi on grub kernel command line, and
separately pegging the CPU speed via:
echo 300 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
--
[lucid] intermittent full system freeze
https://bugs.launchpad.net/bugs/586901
You received this bug
Well, that was interesting. Using last night's kernel I got slightly
different behaviour.
System locked up within minutes of logging in, and before I could
even start to put a significant load on it. Slight different symptoms,
however the mouse never locked. I was able to mouse
Under ubuntu 10.04/Lucid I'm getting the same skipping messages in
syslog as the original reporter, and the same glitching of audio over
A2DP. I've tried two different A2DP headsets (Motorola S9 and Jabra
BT320s) in combination with two different Bluetooth dongles. I also use
a Bluetooth mouse
Public bug reported:
I have a Dell Latitude C400 laptop with Intel 82830M graphics hardware
running Lucid 10.04 beta , kernel 2.6.32-21-generic.
The laptop suspends, and on occasion resumes fine. However, more often-
than-not, on resume the display will turn on (an improvement over
karmic) but
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/44972955/AlsaDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/44972956/ArecordDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/44972957/BootDmesg.txt
**
I did some further testing of using pm_suspend from tty1. I noted that
the same behaviour occurred... that is that on the first, or second
attempt resuming worked... but then on subsequent attempts it did not
work, with the whole display going white, and then bleeding to black.
Noting this, I
I can confirm that the bug was resolved in later karmic alpha's and is
not present in the karmic release.
Thanks for following up.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
wireless networking fails with PCI FATAL interrupt on kernel 2.6.30-7-generic
My printer still isn't working. I reported this in
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/443981 but was
directed here.
The following is a snippet from dmesg where I turn the printer off, and
then on...
[71725.855070] usb 1-2: usbfs: interface 0 claimed by usb-storage while 'usb'
*** This bug is a duplicate of bug 420015 ***
https://bugs.launchpad.net/bugs/420015
My system was already updated when reported the bug, and while I've done
an apt-get update ; apt-get dist-upgrade since, I haven't seen
anything cups/udev/etc. related come in.
I'd previously tried most of
Public bug reported:
Binary package hint: kdebase-workspace
I have an Epson Stylus Photo R300 inkjet printer that worked find under
Jaunty and early alphas of Karmic. Around alpha 4 or 5 printing stopped
work, and is no longer recognized as a local printer. This is still the
case under Karmic
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33058737/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/33058738/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/33058741/ProcStatus.txt
--
Local
** Attachment added: lsusb -v
http://launchpadlibrarian.net/33058783/lsusb_v.txt
--
Local printer does not show in Printer Configuration
https://bugs.launchpad.net/bugs/443981
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
** Attachment added: dmesg output
http://launchpadlibrarian.net/33058799/dmesg.txt
--
Local printer does not show in Printer Configuration
https://bugs.launchpad.net/bugs/443981
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: pulseaudio
Have have two Bluetooth Headsets - one supporting HSP, and other supporting
both A2DP and HSP. Both worked on early Karmic alphas. The following is the
situation under karmic beta.
If I have a either headset connected using HSP,
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33059790/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33059791/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/33059792/ArecordDevices.txt
Log files from /var/log/installer on USB drive
** Attachment added: casper.log
http://launchpadlibrarian.net/30429572/casper.log
--
[karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu install
https://bugs.launchpad.net/bugs/414996
You received this bug notification
Log files from /var/log/installer on USB drive
** Attachment added: partman
http://launchpadlibrarian.net/30429579/partman
--
[karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because
Log files from /var/log/installer on USB drive
** Attachment added: version
http://launchpadlibrarian.net/30429587/version
--
[karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because
Log files from /var/log/installer on USB drive
** Attachment added: syslog
http://launchpadlibrarian.net/30429584/syslog
--
[karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because
Log files from /var/log/installer on USB drive
** Attachment added: initial-status
http://launchpadlibrarian.net/30429598/initial-status
--
[karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu install
https://bugs.launchpad.net/bugs/414996
You received this bug
The grub menu appeared when the USB drive was connected to the laptop.
Just in case someone else runs into this I was able to fix my the
main boot record on my laptop (following suggestions on the IRC) as
follows:
Insert the USB stick I made to get the grub menu,
boot Windows
Followed this
There is indeed an option in the Advanced menu available from the
summary screen which allows you to specify the drive for the boot
loader. Pointing this to the USB stick resolves the install problem
the laptop hard drive was left alone and bootable, and the USB stick now
boots with mythbuntu
I was wondering why my system was starting to swap and discovered that I
have 112 of these processes running,
each consuming between 1MB and 25MB of memory (over 2GB in total.) No on
screen notifications, and nothing in the task bar.
Also running Karmic alpha 3. Not sure what bugs is
Actually, it seems to have resolved itself within the last week. I
waited a few mornings to be sure, but I've had a least 4 days in a row
now without XOrg hogging a core in the morning.
No change to kernel (I've stayed on 2.6.30-9) or video driver. There
were updates to both XOrg, and the
Public bug reported:
After resuming from screen saver ccometen4 from repositories left
running over-night (and monitor sleep after 1/2 hr), Xorg consumes 100%
of a single CPU core (amd64 dual-core).
Happens every morning... but not when the screen saver is used for only
short periods.
I suspect
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/28413701/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28413702/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28413703/Dependencies.txt
**
Public bug reported:
Previously working under Karmic alpha 1 with ALSA 1.0.19 - now unable to get a
peep out of HDMI after the alsa 1.0.20 binary and pulse audio 0.9.15 updates.
aplay -L
front:CARD=NVidia,DEV=0
HDA NVidia, VT1708B Analog
Front speakers
surround40:CARD=NVidia,DEV=0
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/27683359/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/27683360/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/27683361/ArecordDevices.txt
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/27461136/dmesg.txt
--
wireless networking fails with PCI FATAL interrupt on kernel 2.6.30-7-generic
https://bugs.launchpad.net/bugs/383241
You received this bug notification because you are a member of Ubuntu
Bugs, which is
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# wireless lan
auto wlan0
iface wlan0 inet static
address
output from lspci -vvnn
** Attachment added: lspci-vvnn.txt
http://launchpadlibrarian.net/27461142/lspci-vvnn.txt
--
wireless networking fails with PCI FATAL interrupt on kernel 2.6.30-7-generic
https://bugs.launchpad.net/bugs/383241
You received this bug notification because you are a
Public bug reported:
This is a regression found in both kernel 2.6.30-6 and 2.6.30-7, over
kernel 2.6.29 (I have not tested earlier releases of 2.6.30)
Wireless networking in karmic alpha1 will fail to associate with the
access point, frequently on boot, or occasionally may initially
associate
Just to add to the discussion, I did an upgrade from 9.04 to 9.10/karmic alpha
1 and encountered this same problem.
Re-installing with sudo apt-get install --reinstall python-qt4-dbus
does not resolve it.
The sym-link does exist:
# ls -l /var/lib/python-support/python2.6/dbus/mainloop/qt.so
ksg,
The freezes I was experiencing have been resolved in the 2.6.29 kernel.
These changes are being back-ported to 2.6.28 and 2.6.27 as I understand
it, but I don't believe they've been released yet.
I suggest trying 2.6.29.
--
gutsy amd64 freeze crash lockup
There is a huge number of people that seem to be having different
problems with intrepid, and multi-core amd64.
I have an Asus M3N78-VM motherboard with 4GB RAM and integrated NVIDIA
8200 GPU and dual-core AMD 6000.
I get the following message when booting with Intrepid with every kernel
I've
Able to reliably reproduce freeze on 8.10 (Intrepid) 2.6.27-7 with dual-
core AMD64, and multiple versions of NVIDIA drivers.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
gutsy amd64 freeze crash lockup
https://bugs.launchpad.net/bugs/15
You received this bug
Please see the following kernel bug report which includes some details
of my system configuration and steps to reproduce.
http://bugzilla.kernel.org/show_bug.cgi?id=11527...
The problem appears to be related to interrupt handling (and possibly
CPU frequency power management) on multi-core AMD64
I also get the same error:
ACPI Warning (tbutils-0217): Incorrect checksum in table [OEMB] - AE,
should be A6 [20080609]
This is an Asus M3N78-VA, 2.6.27-7-generic (kubuntu 8.10).I don't
think I'm experiencing any ill effects due to this, (although I do
experienced system freezes with
B. Nossum, are you able to turn of Wiress Multi-Media (WMM) / Wireless
Quality of Service (Wireless QoS) on your router? This should get rid
of thee Wireless Event too big message.
If you still experience freeze-ups, you might want to try booting with
the second CPU core disables (kernel boot
uuklanger, yes I have broadcast enabled I'd noticed elsewhere that
this was recommended for 8.10, and while I was trying to diagnose my
issue I turned on broadcast and left it that way. I think I saw a
different bug report related to this.
All I can say is that the new NetworkManager (and
I now have my DWA-552 PCI card working reliably using the ath9k driver
and 802.11n. Performance seems quite good. I´m using WPA, and kubuntu
8.10 rc1 (2.6.27-7-generic) with all updates.
There were two issues:
1) I had to turn off WMM (Wireless QoS) on my router, otherwise I would
get
On the Linksys 300N, WMM is called Wireless QoS. It can be fond under
Applications Gaming - QoS - Wireless QoS. It is enabled by
default.
I have been getting the sale Wireless Event too big. Disabling
Wireless QoS on my Linksys 300N seemed to get rid of the message... but
perversely my
Public bug reported:
Applies to: Ubuntu intrepid (development branch) Release 8.10
(2.6.27-7-generic)
By hangs, I mean that the screen goes all one colour (blue or black
normally), and I can’t switch to a pseudo tty, and can’t toggle num/caps
lock keys on keyboard. Requires reboot, and
** Attachment added: C:\Documents and
Settings\phil.lintell\Desktop\sysinfo.txt
http://launchpadlibrarian.net/18655702/C%3A%5CDocuments%20and%20Settings%5Cphil.lintell%5CDesktop%5Csysinfo.txt
--
802.11n (ath9k) intermittently hangs system
https://bugs.launchpad.net/bugs/285327
You received
73 matches
Mail list logo
