I had not had any problems of this nature until I tried updating some
packages this morning. Then this bug hit me. I was seeing 100% CPU
utilization and strace showed a continued access to a futex. Sorry I
don't have a package update list since I had to revert the system
immediately (it is a
Below is the contents of my network interfaces file. As you suspected,
it is empty and I am using network manager to provide network interface
setup for the user, and so I guess the network isn't being brought up
early enough to satisfy autofs.
The network manager has long bothered me. I REALLY
Below is the contents of my network interfaces file. As you suspected,
it is empty and I am using network manager to provide network interface
setup for the user, and so I guess the network isn't being brought up
early enough to satisfy autofs.
The network manager has long bothered me. I REALLY
I'm wondering if more information is needed. If someone can point me to
some detailed instructions on how to compile the offending driver with
symbols for Ubuntu, to provide a more meaningful stack trace I'd be
happy to try. This bug is causing me grief one out every two boots.
Also, although I
Public bug reported:
This bug is very similar in nature to Bug #958704. In a nutshell,
autofs is unable to initialize correctly on boot due to upstart not
starting things in proper sequence. In my case, network drives are
described in LDAP maps and autofs is most likely starting before the
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/994212
Title:
ubuntu 12.04 automounts (autofs) not working with ldap maps on boot
To manage notifications about this bug go to:
Public bug reported:
This bug is very similar in nature to Bug #958704. In a nutshell,
autofs is unable to initialize correctly on boot due to upstart not
starting things in proper sequence. In my case, network drives are
described in LDAP maps and autofs is most likely starting before the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994212
Title:
ubuntu 12.04 automounts (autofs) not working with ldap maps on boot
To manage notifications about this bug go to:
Public bug reported:
On my fresh install of Precise Ubuntu, I am suffering an lircd crash on
boot. This occurs most boots and apport has sent a few error reports
in, but I didn't see an official bug open yet. I am using a usbuirt
receiver. Judging by the SegvAnalysis, it looks like a null
** Attachment added: crash report
https://bugs.launchpad.net/bugs/993202/+attachment/3124952/+files/_usr_sbin_lircd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993202
Title:
lircd
** Attachment added: button definition file referenced in lircd.conf
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/993202/+attachment/3124954/+files/lircd.conf.hauppauge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I too have experienced disk corruption following suspend to ram, which I
use on my NAS storage server in conjunction with PowerNap. I have
observed this working in both Lucid and Natty over the last year. In my
experience, this problem is not limited to external drives. I have
observed
I put back the problem configuration and ran again and the error logs
were empty.
I installed the latest 2.17 PPA for Natty and enabled disk monitoring in
its normal position in the config file (below the InputMonitor).
Everything seems to work fine.
FYI, one thing I did notice, however is that
Public bug reported:
I noticed that my system was going into standby at odd times, when it
should have been staying on. I make use of the DiskMonitor plugin that
I authored some time back.
I investigated and found that the InputMonitor doesn't seem to be
loading/parsing correctly at init time
** Attachment added: powernap.config.diff
https://bugs.launchpad.net/bugs/899927/+attachment/2619118/+files/powernap.config.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899927
Title:
The broken log file
** Attachment added: powernap.log.broke
https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/899927/+attachment/2619119/+files/powernap.log.broke
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The working log file
** Attachment added: powernap.log.works
https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/899927/+attachment/2619121/+files/powernap.log.works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Steps:
1. Install powernap and configure (in my case see above config file)
2. Enable powernap debugging by setting
DEBUG=1
in /etc/powernap/config
3. Reboot system (using 'shutdown -r now')
4. Disable powernap debugging by setting
DEBUG=0
in /etc/powernap/config
5. Reboot system (using 'shutdown
Public bug reported:
With the move to grub2 I recently discovered that my headless Natty
server running as a NAS device will not reboot following a power
failure. I was able to track this down to the behavior of the
'recordfail' logic in grub2. This logic prevents grub from booting
following an
Here is a better diff of the change I made to /etc/grub.d/00_header to
work around the problem
jheck@twilightzone:/etc/grub.d$ diff -Naur 00_header.orig 00_header
--- 00_header.orig 2011-10-10 19:23:44.0 -0400
+++ 00_header 2011-10-10 19:24:43.0 -0400
@@ -229,11 +229,11 @@
Public bug reported:
I have determined that powernap is causing my system to be unable to
unmount root (/) on shutdown or reboot. I noticed that my system was
doing an fsck check of root on every boot following installation of
powernap. I found that the system was failing to unmount '/' due to
** Attachment added: Powernap config file
https://bugs.launchpad.net/bugs/872109/+attachment/2535792/+files/config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872109
Title:
powernap
Thanks, I'll check it out! I'm just finishing building my NAS box, so the
timing is good.
-Jim
On Tue, Apr 19, 2011 at 2:55 PM, Andres Rodriguez
andres...@ubuntu-pe.orgwrote:
Hi Jim,
Just commited your branch. Will be released in the next upstream release
of testdrive
** Changed in:
I have done more testing with the patch released in hdparm
(9.32-1ubuntu2) and found that there are some problems with the approach
taken. I think this bug should be marked FIXED-FAILED and revisited.
By adding the hdparm -S parameter handling to the power.d script for
'true' and 'false' power.d
I have created a branch with the DiskMonitor changes here
https://code.launchpad.net/~jinfo/powernap/trunk. This was my first
time using the bzr source control system, but I think I did it
correctly. Let me know if not.
--
You received this bug notification because you are a member of Ubuntu
Andres,
Yes your understanding of my script is correct and your example is spot
on.
Explained another way, there are three computers involved in the
process. There is the requester who is ARPing for the sleeping machine,
there is the sleeping machine, which will not wake to ARP requests, and
Andres,
No I have not tested it with the pm-powersave ACTION_METHOD. I will
have to take a look at this and see how it works to comment. The
hardware I have been working with is too old to do much with the
powersave mode, so I really hadn't looked at it much.
The way the plugin works, it
I will also see what I can do about posting a step by step with
hdparm.conf example.
-Jim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738764
Title:
powernap enhancement, DiskMonitor plugin to
Public bug reported:
Binary package hint: hdparm
Upon wakeup from pm-suspend, all spindown settings on drives as set in
hdparm.conf are lost and drives will not spindown until reboot.
This will affect the performance of such useful packages such as
powernap, since drives will not enter spindown
** Patch added: /usr/lib/pm-utils/sleep.d/95hdparm-spindown to restore
spindown parameters after pm-suspend
https://bugs.launchpad.net/bugs/738757/+attachment/1923484/+files/95hdparm-spindown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: powernap
I have coded a powernap plugin module that leverages hdparm to monitor
disks that enter standby or sleeping state. This plugin should be
useful in scenarios such as building a NAS box, where the primary
objective is to have the server powered
** Patch added: DiskMonitor plugin for powernap
https://bugs.launchpad.net/bugs/738764/+attachment/1923503/+files/powernap-2.5.disk.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738764
Public bug reported:
Binary package hint: powernap
Here is a suggestion for an enhancement that could be made to the
powerwake utility. I am posting this suggestion as an enhancement bug
here since it seems very in line with the functionality of
powernap/powerwake, and I thought you might find
** Attachment added: scapy script to wake on ARP to specific IPs
https://bugs.launchpad.net/bugs/737479/+attachment/1917148/+files/sniffwake.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737479
Could I please bother you to block out the MAC addresses in the script I
just posted, or to delete the attachment and let me upload it again.
Best Regards,
-Jim Heck
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am uploading a version of the script with MACs removed.
Best Regards,
-Jim Heck
** Attachment added: sniffwake.py Monitor for ARP from IPs and send Magic
Packets
https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/737479/+attachment/1917178/+files/sniffwake.py
** Attachment removed:
Public bug reported:
Binary package hint: powernap
I have been looking at the forthcoming changes to powernap in natty and
noticed something I think can be a significant enhancement for the
IOMonitor Plugin.
The IOManager Plugin currently uses a regex search of '/proc/%s/cmdline'
to find the
One more piece of useful information. Processes without a
/proc/PID/cmdline can be easily identified in the ps list, in that they
have their process names placed inside square brackets. From the ps man
page:
args COMMANDcommand with all its arguments as a string.
Modifications to
It occurred to me just after writing this bug report, that some people
may be using the current functionality of the regex search of the
cmdline to find a particular instance of a process based on its args.
So a better enhancement idea may be to keep the current functionality of
scanning the
Public bug reported:
Binary package hint: network-manager
Release Lucid
$ apt-cache policy network-manager
network-manager:
Installed: 0.8-0ubuntu3
Candidate: 0.8-0ubuntu3
Version table:
*** 0.8-0ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
100
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/623502/+attachment/1515925/+files/Dependencies.txt
** Attachment added: IfupdownConfig.txt
https://bugs.launchpad.net/bugs/623502/+attachment/1515926/+files/IfupdownConfig.txt
** Attachment added: IpAddr.txt
I can confirm that a kernel BUG involving memory allocation happens on
every boot of my Inspiron 5000e when booting from the Jaunty LiveCD. I
can install Intrepid fine, and found that if I update to Jaunty, the
kernel BUGs on reboot after the update. It seems to occur right around
the time the
An update to this bug states that the uploads to proposed have been
accepted, yet I have not yet found that the new version is available
when I update my apt cache. There are only three days of guide data
left from Zap2It, is there any hope that it will be possible to update
from the normal
zimgao,
Thanks! You were correct, the nvidia driver was not getting loaded due
to its name. I am compiling a custom kernel using the nvidia-new-
kernel-source package along with the linux-source-2.6.20 package. It
appears as you suggest that nvidia-glx-new causes the modprobe to look
for
Public bug reported:
Binary package hint: nvidia-new-kernel-source
The name of the NVIDIA driver created when compiling a custom kernel and
compiling the module code from nvidia-new-kernel-source is nvidia.ko.
The nvidia-glx-new package depends on linux-restricted-modules-common
(so that is
Public bug reported:
Binary package hint: linux-source-2.6.20
I build a custom kernel using the linux-source, mainly to get LIRC
module support built in for my MythTV box. On the latest update of the
linux-source-2.6.20 package (2.6.20-15.25), the kernel that I have built
is causing a machine
** Attachment added: dmesg-crash
http://librarian.launchpad.net/7330141/dmesg-crash
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you are a member
** Attachment added: lspci-vv-nn-crash
http://librarian.launchpad.net/7330144/lspci-vv-nn-crash
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you
** Attachment added: lsmod-crash
http://librarian.launchpad.net/7330142/lsmod-crash
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you are a member
** Attachment added: uname-a-crash
http://librarian.launchpad.net/7330154/uname-a-crash
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you are a
** Attachment added: proc_version-crash
http://librarian.launchpad.net/7330151/proc_version-crash
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you
** Attachment added: lspci-vv-crash
http://librarian.launchpad.net/7330143/lspci-vv-crash
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you are a
** Attachment added: IMG_0358_1.JPG
http://librarian.launchpad.net/7330180/IMG_0358_1.JPG
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification because you are a
Of note is that this system includes one PATA drive and two SATA drives.
The PATA drive is the boot drive.
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification
Another note. This problem also occurs with linux-
source-2.6.20_2.6.20-14.23.
Also unfortunately I no longer have 2.6.20-14.22 deb in my
/var/cache/apt/archive directory and has disappeared off the mirrors.
Since this is the only version currently working on my machine is there
a way I can get
The kernel command line option did not help (same kind of machine
check), but I did check my aptitude log and it was indeed 15.24 and not
15.25. I will install the latest 15.25 source package and rebuild and
retest.
[UPGRADE] linux-source-2.6.20 2.6.20-14.23 - 2.6.20-15.24
Two questions.
1.
Recompiling with 2.6.20-15.25 has resolved the panic issue. It booted
cleanly. Thank you VERY much.
-Jim
--
Machine Check on AMD64 with 2.6.20-15.25 (built from source) during (S)ATA disk
discovery - bus timeout
https://bugs.launchpad.net/bugs/106543
You received this bug notification
Public bug reported:
I have found that when I tried switching back from the new nvidia-glx-
new package to the nvidia-glx package, a hidden file
.nvidia_new_installed gets left behind and X won't start because /sbin
/lrm-video continues to load the nvidia-new driver due to the hidden
file.
Adding another note. I have found that for some reason, on my system,
the missing wfb driver causes X to not start with my custom kernel and
compiled nvidia-kernel-source module, while X will start with the
generic 2.6.20-14 kernel and the nvidia module from the linux-
restricted-modules package
Log of successful X start with generic kernel and linux-restricted-
modules nvidia drivers
** Attachment added: Xorg.0.log.generic
http://librarian.launchpad.net/7300014/Xorg.0.log.generic
--
NVidia driver missing libwfb
https://bugs.launchpad.net/bugs/98641
You received this bug
Log of failing X start with custom kernel and module compiled from
nvidia-kernel-source.
** Attachment added: Xorg.0.log.custom
http://librarian.launchpad.net/7300017/Xorg.0.log.custom
--
NVidia driver missing libwfb
https://bugs.launchpad.net/bugs/98641
You received this bug notification
I agree that by using UUIDs the system is stable. Perhaps this should
be classified a documentation bug. A comment at the top of the
/etc/fstab file would suffice to warn the user that unexpected results
could occur when using the more traditional /dev/sdX designations.
While the installer puts
Public bug reported:
Binary package hint: linux-restricted-modules-common
The /sbin/lrm-manager script is allowing the new nvidia_new.ko driver to
be loaded when DISABLED_MODULES=nv in /etc/default/linux-restricted-
modules-common. The case statement for 'nv' in this script needs to
have the
Public bug reported:
Binary package hint: udev
Since updating my Fiesty installation a few days ago, my parallel IDE
drive is no longer described by udev as /dev/hdc, but instead is being
designated as /dev/sda or /dev/sdc depending on the boot. I also have
two SATA drives in the box, and these
** Attachment added: lspci_vvnn.log
http://librarian.launchpad.net/7237372/lspci_vvnn.log
--
Udev is swapping hard disk /dev/sdX designations for PATA drive
https://bugs.launchpad.net/bugs/105148
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: uname-a.log
http://librarian.launchpad.net/7237375/uname-a.log
--
Udev is swapping hard disk /dev/sdX designations for PATA drive
https://bugs.launchpad.net/bugs/105148
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: dpkg_udev.log
http://librarian.launchpad.net/7237371/dpkg_udev.log
--
Udev is swapping hard disk /dev/sdX designations for PATA drive
https://bugs.launchpad.net/bugs/105148
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: dmesg.log
http://librarian.launchpad.net/7237369/dmesg.log
--
Udev is swapping hard disk /dev/sdX designations for PATA drive
https://bugs.launchpad.net/bugs/105148
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: proc_version.log
http://librarian.launchpad.net/7237373/proc_version.log
--
Udev is swapping hard disk /dev/sdX designations for PATA drive
https://bugs.launchpad.net/bugs/105148
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
In the dmesg.log on this particular boot, /dev/sdc is the PATA drive
with 4 partitions (/dev/sdc1 /dev/sdc2 and /dev/sdc3 are EXT3 /dev/sdc4
is SWAP). Also, /dev/sda is a SATA drive with EXT3 partition on top of
LVM, /dev/sdb is SATA drive with simple EXT3 partition.
--
Udev is swapping hard
Just another note, I had had 9755 working on my system, with a custom
built kernel, but lost it with a set of upgrades today. I was doing
some cleanup and removed some old built kernels at the same time.
Between that and changing from the nvidia-glx package to the nvidia-glx-
new package, the
** Attachment added: lspci-vv-2.6.20.3-ubuntu1.070326.log
http://librarian.launchpad.net/7056224/lspci-vv-2.6.20.3-ubuntu1.070326.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
** Attachment added: dmesg-2.6.20.3-ubuntu1.070326.log
http://librarian.launchpad.net/7056218/dmesg-2.6.20.3-ubuntu1.070326.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
Public bug reported:
In order to properly setup my myth box under Fiesty, I have recompiled
the 2.6.20-13 kernel in order to build module support for LIRC. I am
also setting up a PCHDTV 5500 card, which has drivers for both DVB
(cx88-dvb) and video4linux (cx8800). The DVB drivers are not
** Attachment added: lsmod-2.6.20-13-generic.log
http://librarian.launchpad.net/7056221/lsmod-2.6.20-13-generic.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci-vv-2.6.20-13-generic.log
http://librarian.launchpad.net/7056228/lspci-vv-2.6.20-13-generic.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci-vvnn-2.6.20.3-ubuntu1.070326.log
http://librarian.launchpad.net/7056229/lspci-vvnn-2.6.20.3-ubuntu1.070326.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
** Attachment added: dmesg-2.6.20-13-generic.log
http://librarian.launchpad.net/7056219/dmesg-2.6.20-13-generic.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: proc_version-2.6.20.3-ubuntu1.070326.log
http://librarian.launchpad.net/7056235/proc_version-2.6.20.3-ubuntu1.070326.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
** Attachment added: proc_version-2.6.20-13-generic.log
http://librarian.launchpad.net/7056236/proc_version-2.6.20-13-generic.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
** Attachment added: uname-a-2.6.20.3-ubuntu1.070326.log
http://librarian.launchpad.net/7056239/uname-a-2.6.20.3-ubuntu1.070326.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
** Attachment added: uname-a-2.6.20-13-generic.log
http://librarian.launchpad.net/7056249/uname-a-2.6.20-13-generic.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci-vvnn-2.6.20-13-generic.log
http://librarian.launchpad.net/7056232/lspci-vvnn-2.6.20-13-generic.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
** Attachment added: /etc/modprobe.d/blacklist-cx8800
http://librarian.launchpad.net/7056251/blacklist-cx8800
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lsmod-2.6.20.3-ubuntu1.070326.log
http://librarian.launchpad.net/7056258/lsmod-2.6.20.3-ubuntu1.070326.log
--
modprobe.d blacklist of cx8800 driver does not work for recompiled kernel
https://launchpad.net/bugs/98982
--
ubuntu-bugs mailing list
Also, I should note that the cx8800 driver unloads and loads properly
when I use modprobe. So for example, once the machine is booted with
the recompiled kernel, if I execute
modprobe -r cx8800
the module unloads properly as checked with a subsequent lsmod.
Also, the cx88-dvb driver loads
Well it doesn't seem quite as simple as that. I now have blacklisted
all of the following drivers
---
$ cat /etc/modprobe.d/blacklist-cx8800
# 2.6.20.3 kernel seems to find the analog driver
# for the PCHDTV 5500 card and fail to load
# the dvb driver, so blacklist it
87 matches
Mail list logo
