On Wed, 2009-03-18 at 06:40 +, Iulian Udrea wrote:
> Are these rdepends affected by this upgrade?
>
> Reverse Depends:
> xdebconfigurator
> lm-sensors
>
> It looks like xdebconfigurator is not using read-edid by default. It
> just suggests read-edid now.
That's correct, and it detects t
** Summary changed:
- [jaunty] ata timeout exception with data loss
+ Nvidia MCP67 AHCI ata timeout exception with data loss
--
Nvidia MCP67 AHCI ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 343919 ***
https://bugs.launchpad.net/bugs/343919
Marking as a duplicate of bug #343919 since this appears to affect the
same Nvidia AHCI controller with similar symptoms.
** This bug has been marked a duplicate of bug 343919
[jaunty] ata timeout exceptio
If you are affected by this issue with a Jaunty kernel *and* the Nvidia
MCP67 chip-set, please add your reports to Polygon's new report, bug
#342374 which I've renamed as a master for MCP67-based issues "Nvidia
MCP67 system freezes on boot unless key is held down (continuation of
#272247)".
--
Sy
=> Medium
Assignee: (unassigned) => TJ (intuitivenipple)
Status: New => Confirmed
** Summary changed:
- [jaunty] System freezes on boot unless key is held down (continuation of
#272247)
+ Nvidia MCP67 system freezes on boot unless key is held down (continuation of
#272247)
--
This could be a duplicate of bug #354668 "pausing during boot (several
issues)" for which there is a very new upstream patch:
commit a682604838763981613e42015cd0e39f2989d6bb "rcu: Teach RCU that
idle task is not quiscent state at boot"
--
Nvidia MCP67 system freezes on boot unless key is held do
As a point to note right now - may mean something or nothing.
For each error log, no matter which kernel, it is accompanied by:
ext4_journal_start_sb: Detected aborted journal
And the bug reporter tells us that ext3 file-systems don't suffer the
same issue.
--
Nvidia MCP67 AHCI ata timeout exc
Today I found that an update to the Jaunty packages changed something
subtle and the previously working xorg.conf settings were no longer
effective. The symptom was the intel driver deciding it is possible to
do 1360x768 on the 1024x768 monitor.
The intel driver also ignores monitor options "Prefe
Public bug reported:
Binary package hint: nvidia-180-kernel-source
This can be viewed as an RFC and/or information for others that might
need a work-around for building nvidia DKMS packages on manually
installed kernels.
As a kernel developer I'm building new kernels constantly. Usually I
will n
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Can you try the work-arouns suggested in comment 8 ?
Add "libata.force=nohrst" to the kernel command-line while doing an
'ext4' test?
--
Nvidia MCP67 AHCI ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ub
It looks as if this issue is related to another USB speed issue,
although not caused by or solved by it - bug #296710 "warning: ehci_hcd
loaded AFTER uhci_hcd and ohci_hcd"
However, in this particular case it looks rather that the particular
system hardware is getting confused and may be related t
I'm re-opening this bug since it prevents the user abiding by the local
radio regulations and laws.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Invalid => Confirmed
--
ipw2200: No way to cha
Peter - oops: too many hyphen/switch characters ("--")
It should be a single hyphen switch:
lspci -vvnn >/tmp/reports/lspci-vvnn.log
As to an explanation, we might be able to deduce one once information
from various systems is in. In theory lsusb shouldn't make any different
since it is only sup
Peter, a a side project, I'd be interested to know if lsusb is opening
any files or devices for write access, or otherwise touching a
file/device in a way which changes its status.
If you can get the system into a state where the problem occurs and then
repeatedly run lsusb until it fixes it, usin
The problem here is that ipw2200 doesn't use the (new) the regulatory
domain configuration via cfg80211 and presents as a wired-style
interface.
"Upon the initialization of the wireless core (cfg80211) a world
regulatory domain (highly restrictive) will be set as the central
regulatory domain. If
On Thu, 2009-03-19 at 21:43 +, Jaime Carpenter wrote:
> I have found another solution for me that gives USB2 (480Mbps) every
> time without unloading the ehci_hcd module. This is not optimal, but
> works:
>
> * I plug in the Sansa Clip
> * Sansa powers up and acts like it connects
> * Hardy
Actually I think there's a wider issue here - modprobe failing due to
unsupported module options provided by configuration, kernel or modprobe
command-lines.
I can envisage other scenarios where a change in the kernel build
configuration removes the availability of a module parameter and causes
ot
Something else occured to me about this. When this happens is the USB
device connected to the port whilst the BIOS is POSTing?
For PCs who's BIOS support boot from USB this might/would trigger the
BIOS into initialising at least one USB host controller which would
claim the external port(s). It wo
Public bug reported:
I can reliably reproduce a total system lock-up (no response to SysReq
keys) when-ever the module is removed. It occurs about 3 seconds after
the removal has completed whilst the notification of removal is still
on-screen.
sudo modprobe -r iwl3945
sudo modprobe iwl3945
unam
Can you reproduce the lock-up described in bug #345710 "modprobe -r
iwl3945 causes total system freeze" ?
--
NetworkManager causes system freeze, lock up, kernel panic
https://bugs.launchpad.net/bugs/336001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Can you reproduce the lock-up described in bug #345710 "modprobe -r
iwl3945 causes total system freeze" ?
--
Kernel Panic with iwl3945 ucode
https://bugs.launchpad.net/bugs/314961
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Ahh yes, too many bugs in the bug database... let's try again!
bug #254668 "pausing during boot (several issues)"
--
Nvidia MCP67 system freezes on boot unless key is held down (continuation of
#272247)
https://bugs.launchpad.net/bugs/342374
You received this bug notification because you are a
I've successfully back-ported the upstream commit to Jaunty, built and
booted it. Because my systems don't exhibit this issue I'm going to pass
the hard work of building some test kernels over to Stefan tomorrow.
Once he's built and published them hopefully we can get some test
reports as to wheth
Quentin, any news on this?
--
Hardy 64-bit beta and nightly alternate installation stalls
https://bugs.launchpad.net/bugs/217849
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
ht
3] ipw2200-managed mini-PCI adaptors and neither has a problem
with Jaunty.
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) => TJ
(intuitivenipple)
Status: Triaged => In Progress
--
Wireless (ipw2200) does not work after waking up from sleep(
Tomas. I've looked at the provided logs and the kernel source-code
involved.
The logs show that the PC (I assume this is still the Prestigio 157?)
doesn't provide a radio frequency kill switch using the usual HAL
(hardware abstraction layer) identity. Here's an example of what I'd
expect to see (f
der or locking push-
to-make switch - can you tell me what kind of switch it is?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
--
change 'acerhk' to use 'autowlan=1' by default
https://bugs.launchpad.net/bugs/53953
You received thi
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Triaged => In Progress
--
kernel bug corrupts filesystem on heavy parallel I/O
https://bugs.launchpad.net/bugs/337246
You received this bug notification because you are a member of Ubuntu
Bugs,
David, thank-you for that revelation.
That indicates that the Bluetooth device-driver might not be doing
everything it should when handling the PM suspend event, or it might be
that the hardware is doing something unexpected that is probably handled
as a quirk in Windows drivers (I assume the same
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Incomplete => In Progress
--
NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I found this LKML commentary from 2003. I think the general idea still
applies so I'll add it as reference material:
"One way to cause an intermittent NMI is by having power management enabled
with devices that don't support it. They see the world caving in when power
goes away and sometimes gener
ignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) => TJ
(intuitivenipple)
--
Intrepid: Resume from disk failed
https://bugs.launchpad.net/bugs/317185
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
r
#11159
Status: Invalid => Unknown
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Incomplete => In Progress
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug n
** Attachment added: "Make EHCI retry transaction errors 32 times"
http://launchpadlibrarian.net/24155221/0001-UBUNTU-Make-EHCI-retry-transaction-errors-32-times.patch
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notifica
The acerhk driver should be modified by its maintainer to implement the
rfkill API (see Documentation/rfkill.txt). With that implementation the
power management (PM) system will ensure the device state is set
correctly on resume.
--
change 'acerhk' to use 'autowlan=1' by default
https://bugs.laun
** Changed in: acpi-support (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: New => Invalid
--
Intrepid: Resume from disk failed
https://bugs.launchpad.net/bugs/317185
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: netspeed (Ubuntu)
Importance: Undecided => Low
Assignee: TJ (intuitivenipple) => (unassigned)
Status: New => Confirmed
--
netspeed applet will not measure wired
https://bugs.launchpad.net/bugs/335507
You received this bug notification because you are a
Upstream have applied a patch to fix this.
** Changed in: tracker (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: Confirmed => Fix Committed
** Changed in: tracker (Ubuntu)
Status: Fix Committed => Triaged
--
trackerd ingores SIGINT when scanning
** Changed in: tracker (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
** Changed in: tracker (Ubuntu)
Status: Confirmed => Triaged
--
Options table contains duplicate OptionKey rows
https://bugs.launchpad.net/bugs/324364
You received this bug notification because you
This has been patched upstream.
** Changed in: tracker (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: Confirmed => Fix Committed
** Changed in: tracker (Ubuntu)
Status: Fix Committed => Confirmed
--
Configuration file mis-spells "Divisions
On Fri, 2009-03-20 at 17:41 +, TomasHnyk wrote:
> As for the type of switch, I am not sure what you mean. I think it is
> unfortunately what you describe as momentary push-to-make type.
Yes, that is correct. The key thing about this kind of switch is the
'state' has to be maintained in softwa
Wow! I never expected that! Things are looking promising :)
There now looks to be a work-around we could implement in user-space
when the system suspends and resumes. A simple shell script reads this
value on suspend and writes the same value back on resume.
That would be good since wireless driv
Try installing this power-management script and let me know how it goes.
I'm not completely happy with it since it doesn't try to ensure the
device it is probing and poking is the ipw2200/acerhk combination, but
lets see how it goes.
1. Download the script attachment
2. Copy to /etc/pm/sleep.d/
s
Philipp's original report says:
PM: suspend devices took 5.420 seconds
This means that the arbitrary 5-second boundary set in
TEST_SUSPEND_SECONDS is triggering what looks to be a false positive
report.
We're discussing increasing this value to avoid many of these false
positives.
** Tags added
Quick confirmation I'm still working on this. Not had the time required
to study and re-work the other possible patches to fit this driver.
--
via-rhine network adapater won't work on resume
https://bugs.launchpad.net/bugs/267779
You received this bug notification because you are a member of Ubun
Upstream have applied the patch to fix this.
** Changed in: tracker (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
trackerd uses 100% cpu
https://bugs.launchpad.net/bugs/239391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: test-suspend-seconds
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Your report appears to confirm that the Radio button on the PC is purely
a momentary press-to-make type... the state associated with it is held
by a system I/O device register and therefore lost when power is removed
from all but RAM on S3 suspend.
What a shame... that means we're back to the solu
Updated the debdiff to be based off 7ubuntu4:
cryptsetup (2:1.0.6-7ubuntu5) jaunty; urgency=low
* debian/initramfs/cryptroot-hook: fix support for UUID and LABEL correlation
between fstab and crypttab (LP: #287879).
-- TJ Mon, 16 Feb 2009 23:00:00 +
** Attachment removed: "J
Leann, I think this should re-opened and tagged as affecting Jaunty.
It is (still) not possible to control the back-light on the Vaio VGN-
FE41Z with Nvidia GeForce Go 7600 without my smartdimmer workaround (I
need to build a new package for Jaunty and put it in my PPA).
lspci -nn -s:01:00.0
01:0
Thanks Kees - you have no idea of the frustration each time I had to
recover from a live-CD after the cryptsetup package updated without my
realising and regenerated an initrd image without the keyscript
included!
--
cryptsetup does not understand UUID= in fstab and conf.d/resume
https://bugs.lau
A simplication of the work-around for the right-shift pixels and top-
lines corruption. Just the act of starting nvidia-settings instantly
corrects it here - I don't have to touch the GPU Scaling settings.
However, the issue with the mouse cursor remains. From the upstream
reports it looks like thi
Doing a bit more digging on the nvidia forums I found a related posting
about what is possibly a closely related issue with the 180.29 driver -
complete screen-corruption and system lock-up requiring a forced hard
reset.
It prompted to run an Open GL test with glxgears. Starting from a
'correct' s
The key would appear to be (kern.log):
[ 374.936634] metacity[8085]: segfault at 0 ip 080abab3 sp bfa1c800
error 4 in metacity[8048000+7a000]
and may be related to (Xorg.0.log):
AUDIT: Tue Feb 17 22:55:11 2009: 7857 X: client 4 rejected from local host (
uid=1000 gid=1000 pid=7918 )
which is p
Please attach /var/log/dmesg
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
--
dmraid & attempt to access beyond end of device
https://bugs.launchpad.net/bugs/329880
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
Binary package hint: gtkpod
Jaunty archive contains the binary built on Intrepid.
When the source is built on Jaunty it pulls in libgpod-dev 0.7.0-1
whereas Intrepid uses 0.6.0-5ubuntu1.
There appear to be changes between the two versions, with 0.7.0-1
missing some structur
** Description changed:
Binary package hint: gtkpod
Jaunty archive contains the binary built on Intrepid.
When the source is built on Jaunty it pulls in libgpod-dev 0.7.0-1
whereas Intrepid uses 0.6.0-5ubuntu1.
There appear to be changes between the two versions, with 0.7.0-1
-
** Changed in: linux
Importance: Undecided => Unknown
Bugwatch: None => Linux Kernel Bug Tracker #7912
Status: Fix Released => Unknown
--
Disk Read Errors during boot-time caused by probe of invalid partitions
https://bugs.launchpad.net/bugs/77734
You received this bug notification
*** This bug is a duplicate of bug 77734 ***
https://bugs.launchpad.net/bugs/77734
Yes, that is what I wanted, thank-you.
The issue is not related to udev. This is an issue with how the kernel
scans block devices for partitions during start-up. I've confirmed that
this issue is caused by the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Disk Read Errors during boot-time caused by probe of invalid partitions
https://bugs.launchpad.net/bugs/77734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2/455] filesystem: Disk Errors at boot-time caused
by probe of partitions
Date: Tue, 8 May 2007 09:19:32 -0700 (PDT) (17:19 BST)
On Tue, 8 May 2007, a...@linux-foundation.org wrote:
>
> From: TJ
I don't really like these kinds of addresses. Who is TJ? When I google for
that name, I find a
*** This bug is a duplicate of bug 77734 ***
https://bugs.launchpad.net/bugs/77734
Please post a report the the upstream kernel bug report at:
http://bugzilla.kernel.org/show_bug.cgi?id=7912
--
dmraid & attempt to access beyond end of device
https://bugs.launchpad.net/bugs/329880
You receiv
Jaunty's kvm-83 includes my USB sys-fs patch from upstream QEMU and
therefore no longer requires the /proc/bus/usb/ work-arounds.
I've opened a new report to deal with the permissions issue: bug #331331
"Non-root guest doesn't have permission to access sys-fs USB devices"
--
Could not open /proc
Public bug reported:
Binary package hint: kvm
Since kvm-83 in Jaunty, KVM/QEMU has supported /sys/ file-system access
to USB devices.
There is, however, an issue with insufficient permissions for a non-root
KVM/QEMU guest to access host USB devices.
There was discussion of this issue as part of
Peter, you beat me to it. I was reviewing Stefan Lechner's gnome-mount
log captures and noticed that when it fails it is because the UUID of
the crypto volume isn't yet known:
** (gnome-mount:6982): DEBUG: In crypto_setup_device_added for
/org/freedesktop/Hal/devices/volume_part_1_size_0
Which to
Public bug reported:
On resume from suspend a driver fails to re-load the USB video-camera
firmware. This cause a very long pause (60 seconds according to the log
time-stamps) during suspend before the screen has been restored and
makes it appear the system has locked up.
The driver makes a call
Digging into the source the 60-second pause is the default firmware
loading-timeout in drivers/base/firmware_class.c:
static int loading_timeout = 60;/* In seconds */
which is applied in _request_firmware():
fw_priv = dev_get_drvdata(f_dev);
if (uevent) {
The cause of this issue is that request_firmware() blocks until the
firmware image is available. It makes a request via userspace, but at
the time of resume all userspace tasks are frozen and therefore it waits
and times out.
The solution is for drivers to use the request_firmware_nowait()
functio
** This bug is no longer a duplicate of bug 77734
Disk Read Errors during boot-time caused by probe of invalid partitions
--
dmraid & attempt to access beyond end of device
https://bugs.launchpad.net/bugs/329880
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: New => Confirmed
--
request_firmware() fails on resume from suspend
https://bugs.launchpad.net/bugs/331415
You received this bug notification because you are a member of Ubuntu
Bugs, wh
After some exchanges with Linus on the upstream bug I'm un-duplicating
this from #77734. That bug can deal with the kernel versions that
allowed the disk I/O to be attempted. It appears the current code was
introduced by:
git describe --contains a168ee84c90b39ece357da127ab388f2f64db19c
v2.6.25-rc1
The upstream fix is commit 12d60e28bed3f593aac5385acbdbb089eb8ae21e
The patch is in-line for inclusion into the 2.6.28-stable tree.
--
Jaunty doesn't boot on my DELL Latitude C810 with current kernel
https://bugs.launchpad.net/bugs/314050
You received this bug notification because you are a memb
Thanks for pointing that out Steve. I moved an existing /home/ mount
into the Jaunty environment. Now you've jogged my memory I think I do
recall that with the default Jaunty user profile I saw a bunch of log-
file warnings too. Now I only see one for /var/log/acpid.
The reason for it is that on p
The patch above doesn't deal with the issue that gnome-log-viewer
seemingly doesn't provide for the user deleting a log-file from the
monitored list if that file doesn't exist on-disk.
--
gnome-system-log attempts to open bogus/inexistent logfiles
https://bugs.launchpad.net/bugs/318689
You receiv
Public bug reported:
Binary package hint: xorg
On a secondary X screen (:0.1) which has different (larger) dimensions
than the primary(:0.0), the lower part of the secondary screen is
ignored by the display manager, remaining black and not displaying
windows in that area, although the mouse does
** Attachment added: "Photograph #1 - Overview"
http://launchpadlibrarian.net/22902475/photograph_%231.jpg
--
Outof-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Photograph #1 - Detail"
http://launchpadlibrarian.net/22902519/photograph_%232.jpg
--
Outof-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/22902556/xorg.conf
--
Outof-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "/var/log/Xorg.0.log"
http://launchpadlibrarian.net/22902605/Xorg.0.log
--
Outof-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Also affects: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided
Status: New
--
Outof-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Summary changed:
- Outof-bounds areas for multiple X screens with different dimensions
+ Out-of-bounds areas for multiple X screens with different dimensions
--
Out-of-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug no
On Fri, 2009-02-20 at 10:13 +, Sebastien Bacher wrote:
> thank for your work but I'm not convinced by this approch, it should
> just lists all the available logs listed and not display an error dialog
> which has no use
Hi Sebastien.
I wasn't attempting to fix the fundamental issue, just to m
s to look at to figure out
what changed to cause this.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Triaged => In Progress
--
via-rhine network adapater won't work on resume
https://bugs.launchpad.net/bugs/267779
You received this
I've created a DKMS (Dynamic Kernel Module System) package for Intrepid
and Jaunty with a patch that *may* fix this issue - please install the
package, test, and report your findings and kern.log that covers the
suspend/resume period.
The packages are (currently building) in my PPA at:
https://la
On Sat, 2009-02-28 at 08:45 +, Fridtjof Busse wrote:
> I agree that this is not a critical error, but nonethelesse a kernel
> oops is not exactly a "nice to have".
That was my point in mentioning TEST_SUSPEND_SECONDS. We are discussing
increasing the current 5-second limit to avoid these fals
Please do a shutdown/restart, suspend/resume test. Assuming the resume
fails restart afresh and then attach /var/log/kern.log which should
capture more information than the dmesg logs from the original report.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenip
Thank-you Jacob. I'll mark the bug "Invalid" on the basis of "we'll
never really know". If it recurs please re-open this bug and we'll try
again.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
BUG: scheduling while atomic: notification-da/10006/0x1001
https://bugs.launchpad.n
This should sort that out, allowing a user to manually stop it using:
sudo /etc/init.d/stop-bootchart stop
diff -Nu /etc/init.d/stop-bootchart.orig /etc/init.d/stop-bootchart
--- /etc/init.d/stop-bootchart.orig 2009-02-17 11:26:22.0 +
+++ /etc/init.d/stop-bootchart 2009-02-28 22
On Sun, 2009-03-01 at 17:55 +, chckens wrote:
> Many thanks TJ for looking into this. Unfortunately, I'm still seeing
> this issue after installing via-rhine-dkms 1.4.4-0ubuntu1~ppa2i, having
> removed via-rhine from my SUSPEND_MODULES in /etc/pm/config.d/.
Thanks for testin
On Sun, 2009-03-01 at 13:57 +, Jesse wrote:
> Should I boot into the offending kernel? I mean the 2.6.27-7-generic
kernel works fine for me so far, but the ones upgraded later
(e.g.2.6.27-12) actually will drive up the fan.
No, use the 'good' kernel since the script is going to collect
info
On Sun, 2009-03-01 at 10:50 +, dhenry wrote:
> I tried with Jaunty live-CD (2009-03-01 build), kernel 2.6.28-8, and the
> bug is still present.
Is that the Lenovo 3000 N100 and the psmouse kernel module?
--
Synaptics touchpad ceases functioning after suspend and resume.
https://bugs.launchpa
We've learned long ago never guess or assume when it comes to computers!
With the live-CD you can edit the boot options by pressing F6, pressing
ESCape to close the sub-menu that offers a few common choices, and then
editing the raw kernel command-line as is done from the GRUB menu on
installed sy
)
Assignee: (unassigned) => TJ (intuitivenipple)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a member of Kubuntu
Bugs, whi
Public bug reported:
Affects: Jaunty, GDM
With multiple X screens configured (:0.0 and :0.1) each screen has its
own menu and task-bar.
When launching an application from the menu on an additional X screen it
appears on screen 0. This is a regression since Hardy.
The only work-around is to man
The attached kern.log doesn't reveal any obvious suspend-to-RAM
attempts.
What sleep module is in use?
grep SLEEP_MODULE /etc/pm/config.d/00sleep_module
The log does however contain several hibernation cycles (suspend-to-
disk), such as:
Feb 28 10:46:24 box kernel: [ 229.128539] PM: Creating
This is what a true suspend-to-RAM looks like:
Suspend...
[12964.851509] PM: Preparing system for mem sleep
[12964.851512] Freezing user space processes ... (elapsed 0.00 seconds) done.
[12964.857033] Freezing remaining freezable tasks ... (elapsed 0.01 seconds)
done.
[12964.867857] PM: Entering
The problem appears to be that during suspend the Interrupt for the
Nvidia MCP78S (PCI 00:09.0) isn't being disabled, nor re-enabled on
resume (other AHCI-managed controllers are - see 07.00.0).
Start-up:
[1.364523] ahci :00:09.0: version 3.0
[1.364948] ahci :00:09.0: PCI INT A -
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: Incomplete => Confirmed
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/334644
You received this bug notification because you are a member of Ubunt
** Bug watch added: Linux Kernel Bug Tracker #12542
http://bugzilla.kernel.org/show_bug.cgi?id=12542
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12542
Importance: Unknown
Status: Unknown
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://
301 - 400 of 2922 matches
Mail list logo
