in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = TJ
Status: New = In Progress
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = TJ
Status: New = In Progress
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: TJ = Ubuntu Kernel ACPI Team
This could be a knock-on effect of other problems with Gutsy. Your other
report ought to be solved first since if Gnome config is broken it is
likely gnome-power-manager isn't operating correctly.
--
[Gutsy] suspend and hibernate don't work with kernel 2.6.22-8.18
Fix applied to Andrew Morton's -mm tree in January 2007
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: In Progress = Fix Released
** Changed in: linux (upstream)
Status: In Progress = Fix Released
--
Disk Read Errors during boot-time caused by probe of invalid partitions
Public bug reported:
Binary package hint: nvidia-glx-180
This issue could affect all versions of the Nvidia proprietary drivers.
The symptoms are that users report that systems with Nvidia-based
graphics cards won't start the X server successfully. There are a wide
range of symptoms that don't
** Summary changed:
- failed to load the nvidia kernel module
+ No PCI IOMEM space available below 4GB
** Description changed:
Binary package hint: nvidia-glx-180
+
+ failed to load the nvidia kernel module
This issue could affect all versions of the Nvidia proprietary drivers.
The
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = TJ (intuitivenipple)
Status: New = Confirmed
--
No PCI IOMEM space available below 4GB
https://bugs.launchpad.net/bugs/342926
You received this bug notification because you are a member of Ubuntu
** Description changed:
Binary package hint: nvidia-glx-180
This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10, 9.04+)
It usually only shows up dramatically with video cards that have large
memory (e.g. 256MB) and on systems that
a) have 3GB or more RAM and/or
-
** Description changed:
Binary package hint: nvidia-glx-180
This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10, 9.04+)
It usually only shows up dramatically with video cards that have large
memory (e.g. 256MB) and on systems that
a) have 3GB or more RAM and/or
** Description changed:
Binary package hint: nvidia-glx-180
This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10, 9.04+)
It usually only shows up dramatically with video cards that have large
memory (e.g. 256MB) and on systems that
a) have 3GB or more RAM and/or
** Description changed:
Binary package hint: nvidia-glx-180
This can affect almost all releases (6.10 7.04, 7.10, 8.04, 8.10, 9.04+)
It usually only shows up dramatically with video cards that have large
memory (e.g. 256MB) and on systems that
a) have 3GB or more RAM and/or
*** This bug is a duplicate of bug 342926 ***
https://bugs.launchpad.net/bugs/342926
Marking this as a duplicate of my master bug report for all PCI IOMEM
allocation issues.
This is a mainline kernel issue that will be resolved upstream soon and
be inherited by all distributions.
** This
*** This bug is a duplicate of bug 342926 ***
https://bugs.launchpad.net/bugs/342926
Marking this as a duplicate of my master bug report for all PCI IOMEM
allocation issues.
This is a mainline kernel issue that will be resolved upstream soon and
be inherited by all distributions.
** This
Public bug reported:
In Jaunty, up to and including 2.6.28-7, if the Wireless network
regulatory domain needed setting manually for non USA regions such as
the European Union (EU) or Japan, an option was added for the cfg80211
module in /etc/modprobe.d/options.conf:
options cfg80211
** Attachment added: Terminal window decoration corruption
http://launchpadlibrarian.net/23872416/Xubuntu-Terminal-window-decoration-corruption.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23872417/Dependencies.txt
--
Xubuntu Terminal window-decoration
Public bug reported:
Testing the Jaunty Xubutu live-CD i386 2009-03-14 I found that one
application, the Terminal, displayed consistently corrupted window
decorations. I couldn't find other applications affected in the same
way.
I'm attaching a screenshot that shows the issue.
The contents of
Has anyone been able to test this on an IPv6 network so we could
determine the scope of the cause to help hunting it down?
It does look like an IPv4 issue. Could you boot the kernel with debug
mode, provoke the error, and then check the end of /var/log/kern.log for
any relevant kernel errors
In reply to dcam, the patch in
http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-06/msg02958.html
from Björn Steinbrink to __inet_del_ifa() is included in Hardy, Intrepid
and Jaunty.
commit 6363097cc4d182f93788131b5d8f72aa91d950a0
Author: Herbert Xu herb...@gondor.apana.org.au
Date: Thu
Based on Dustin's report of manually using ifconfig (probably the
simplest scenario that can cause -ENOBUFS), I've looked at the source-
code for ifconfig in the net-tools package.
Would it be possible for one or more of you to single-step through a
simple ifconfig scenario using gdb to pin-point
) the Wireless access point is
operating with, including the encryption method. (E.g. 802.11g WPA2
AES+TKIP).
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = TJ (intuitivenipple)
--
No NET with 2.6.27: No buffer space available
https://bugs.launchpad.net
A *temporary* workaround to help stop /var/log/syslog and
/var/log/user.log (and rotated copies) from consuming all disk space on
the /var/ mount.
src/modules/alsa-util.c:1160:pa_log(snd_pcm_avail_update() returned a
value that is exceptionally large: %lu bytes (%lu ms)
with ACPI_FUTURE_USAGE and
specific additional checks, there is no way to know the reason a system
resumed.
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = TJ (intuitivenipple)
Status: New = Confirmed
--
Resume immediately after Suspend due to some WAKE event
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) = (unassigned)
Status: In Progress = Won't Fix
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee:
The 'greyed out' Network device combo-box is due to:
gtk_widget_set_sensitive(applet-network_device_combo,
!applet-auto_change_device);
The setting is controlled by the Always monitor a connected device, if
possible. Un-ticking this option will enable the Network device combo-
box.
--
netspeed
300543358
get_device_info() calling glibtop_get_netload(netload, eth0)
up 1, running 1, bytes_out 7426926470, bytes_in 300545617
To stop the applet use the interrupt (Ctrl+C).
** Changed in: netspeed (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
Status: New = Incomplete
From our additional discussion on IRC #ubuntu+1 here's some further
information.
When src/netspeed.c::update_applet() is called (controlled by the gconf
refresh_time setting) it calls src/backend.c::get_device_info(). This in
turn calls:
glibtop_get_netload(netload, device);
to obtain the
This issue may be related to upstream libgtop re-working the struct
glibtop_netload
http://bugzilla.gnome.org/show_bug.cgi?id=565096
and netspeed applet not using the latest upstream source (see bug
#268727).
--
netspeed applet will not measure wired
https://bugs.launchpad.net/bugs/335507
You
On Mon, 2009-03-16 at 16:38 +, Scott James Remnant wrote:
Are you affected by this bug?
At some point a few weeks/months ago I believed I was but then the issue
went away and afterwards I pretty much convinced myself I'd been
imagining a problem since USB transfers were above the USB1
On Mon, 2009-03-16 at 10:04 +, BUGabundo wrote:
I upgraded, and once i added a new one, it didnt detect my wired connection
(the only one I'm using right now).
I force to manually use wired and still it failed to measure traffic
I suspect your description may be confusing the issue here,
Adding information here for the ongoing debug session with Keybuk and
rtg on IRC, for the following system:
Sony Viao VGN-FE41Z
lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
00:01.0 PCI bridge
dmesg log exhibiting warning message.
for hci in /sys/bus/pci/drivers/?hci_hcd; do echo $hci; cat $hci/*/modalias;
done
/sys/bus/pci/drivers/ehci_hcd
pci:v8086d27CCsv104Dsd81EFbc0Csc03i20
/sys/bus/pci/drivers/uhci_hcd
pci:v8086d27C8sv104Dsd81EFbc0Csc03i00
The laptop has three external-facing USB ports on the right side; number
them from back to front 1 2 3. Attached an external USB hard drive to
port 1:
kernel: [ 393.808054] usb 5-3: new high speed USB device using ehci_hcd and
address 6
kernel: [ 393.941436] usb 5-3: configuration #1 chosen
Test without ehci_hcd. ehci_hcd was blacklisted and didn't load:
lsmod | grep hci
ohci1394 42036 0
ieee1394 108416 1 ohci1394
uhci_hcd 34464 0
/var/log/kern.log:
kernel: [ 365.076048] usb 2-1: new full speed USB device using uhci_hcd and
address 3
Without ehci_hcd
** Attachment added: dmesg
http://launchpadlibrarian.net/23951849/dmesg
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Without rebooting I disconnected the external USB device, unloaded the
USB modules then loaded ehci_hcd first:
sudo modprobe -r uhci_hcd
sudo modprobe -r ohci_hcd
sudo modprobe ehci_hcd
sudo modprobe uhci_hcd
sudo modprobe ohci_hcd
readlink /sys/block/sdb
So, as described on IRC #ubuntu-kernel by mjg59, the issue is USB host
controllers sharing physical ports.
In this test-case the PC has 4x USB 1.1 host controllers and 1x USB2
host controller.
The three physical external USB ports are connected such that the USB2
host controller and one of the
Something to be aware of: It looks as if once a port has been claimed
after power-up it will always be associated with the host controller
that claimed it until the system does a cold boot.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You
I want to test the flags being returned by the IOCTL call to the socket.
I've written a minimal C program to do that. You can either compile the
attached source or, if you'd prefer, I can provide a binary. Try it on
all your network interfaces.
gcc -o socket-flags socket-flags.c
for dev in
:00.0 VGA compatible controller [0300]: nVidia Corporation G70 [GeForce 7600
GT] [10de:0391] (rev a1)
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = TJ (intuitivenipple)
Status: New = In Progress
--
[jaunty] ata timeout exception with data loss
Stefan, is this a candidate for back-porting to Hardy/Intrepid?
--
hardy / ibex - raid5 - ata#: hard resetting link
https://bugs.launchpad.net/bugs/263160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The patch from Mark Lord is included in Jaunty as commit
c42fae333255b08b8d4bc03e5853023145208d45 sata_mv: fix 8-port timeouts on
508x/6081 chips
Other non-marvel chipsets may be affected by similar bugs in other
drivers.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
This issue is likely to be caused by the same root issue in bug #254668.
A potential fix in the boot-time RCU code is just making its way
upstream and may well land in a Jaunty kernel soonish. Please review the
other bug to confirm the symptoms are similar. If you think so, we'll
mark this as a
Can this bug be closed now - it looks as if the issue has gone away and
was related to SATA AHCI NCQ?
--
alert! /dev/disk/by-uuid/be80cf42-e6f2-466c-bb73-7d664956a334 does not exist
https://bugs.launchpad.net/bugs/315572
You received this bug notification because you are a member of Ubuntu
Bugs,
It looks like there may be a fix upstream in the form of commit
a682604838763981613e42015cd0e39f2989d6bb rcu: Teach RCU that idle task
is not quiscent state at boot.
--
[2.6.27] pausing during boot (several issues)
https://bugs.launchpad.net/bugs/254668
You received this bug notification because
It is very likely this is a duplicate of bug #254668 pausing during
boot (several issues) for which an upstream patch has just become
available and will make its way into mainline and Ubuntu soon.
Please look at the other bug report and if you feel that represents this
issue comment here and
There was a similar issue affecting the sata_mv driver for Marvell SATA
chip-sets where an iport address for interrupt handling was incorrectly
set. Although in this case a different driver is used (sata_nv) it is
possible something similar to that issue might cause this one.
For reference, that
The issue appears to occur when the primary monitor doesn't provide EDID but
the secondary does, and the secondary monitor specifications exceed what the
primary can support.
It seems the xserver then tries to apply the secondary EDID values to the
primary, and the screen is blanked since it
Please test the package in my PPA and report back.
https://launchpad.net/~intuitivenipple/+archive/ppa/
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well there is the evidence that there's something unusual on that system
unrelated to netspeed.
You can clearly see that according to the network IOCTL flags, etho
isn't running (IFF_RUNNING).
So, what's the PCI [vendor:product] of the network device, which driver
is managing it (lspci -vvnn -d
For reference, I've discovered a linux-netdev mailing-list article
describing this and an underlying change to the way the IFF_RUNNING flag
is used from March 2006.
http://marc.info/?l=linux-netdevm=12292253463w=2
commit b00055aacdb172c05067612278ba27265fcd05ce
Author: Stefan Rompf
I suspect the solution here would be to get the newer upstream version
of netspeed packaged and into the archives.
See bug #268727 new upstream version of netspeed applet 0.15
--
netspeed applet will not measure wired
https://bugs.launchpad.net/bugs/335507
You received this bug
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
--
Kernel panic on boot if SMP (ASUS M3A-H/HDMI)
https://bugs.launchpad.net/bugs/292619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Feature Freeze Exception request
* Upstream added support for amd64 architecture (using libx86) and has
a new maintainer
** Attachment added: FFE ChangeLog
http://launchpadlibrarian.net/24017626/ffe-ChangeLog.patch
--
[needs-packaging} read-edid-2.0.0 for amd64
** Attachment added: pbuilder jaunty amd64 build log
http://launchpadlibrarian.net/24017675/read-edid-2.0.0-0ubuntu1%7Etj%7Eppa1j-jaunty-amd64-2009-03-13_21-00-50.log
--
[needs-packaging} read-edid-2.0.0 for amd64
https://bugs.launchpad.net/bugs/242043
You received this bug notification
.
After this operation, 77.8kB of additional disk space will be used.
Selecting previously deselected package read-edid.
(Reading database ... 205161 files and directories currently installed.)
Unpacking read-edid (from .../read-edid_2.0.0-0ubuntu1~tj~ppa1j_amd64.deb) ...
Processing triggers for man
Here's the promised log-files and photographs to make the issue easier
to understand.
Note: the xserver doesn't fallback into fail-safe mode in this scenario,
it is only a case that monitors show no output.
Here's the tests I did, after which I took a photograph and copied the
current
Boot with external monitor.
Shows both monitors active at GRUB stage.
There is no splash screen during boot which is, I think, an unreated
issue with the framebuffer driver since it is the same when booting
without external monitor.
** Attachment added: dual screen BRUB boot menu
default-external-monitor.tar.gz (blank screens)
dual-screen-default.jpg
xorg.conf-default.conf
Xorg.0.log-default-with-external.log
** Attachment added: Default with external monitor attached
http://launchpadlibrarian.net/24022780/default-external-monitor.tar.gz
--
Multiple monitors can
default-single-screen.tar.gz
single-screen-default.jpg
xorg.conf-default.conf
Xorg.0.log-default-no-external.log
** Attachment added: Default with single screen
http://launchpadlibrarian.net/24022663/default-single-screen.tar.gz
--
Multiple monitors can cause xserver to show blank screens
defined-monitor-external-monitor.tar.gz
dual-screen-defined-monitor.jpg
xorg.conf-default-defined-monitor.conf
Xorg.0.log-defined-monitor-with-external.log
** Attachment added: Defined with external monitor
http://launchpadlibrarian.net/24022969/defined-monitor-external-monitor.tar.gz
--
if the status is 0x7f
to make polling IDENTIFY presence detection work for these machines.
Signed-off-by: Tejun Heo t...@kernel.org
Signed-off-by: Jeff Garzik jgar...@redhat.com
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
libata causes boot
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
libata causes boot timeout on Asus Pundit-R
https://bugs.launchpad.net/bugs/293218
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ernst, thanks for pointing that out. I think I must have gained tunnel-
vision after chasing that sata_mv similarity!
For reference, lsmod will no longer be so reliable for checking modules
in Jaunty and later since we're now building a lot of modules into the
kernel. sata_nv is one of those
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 the
** 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
*** 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
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).
--
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)
--
Nvidia MCP67 system freezes
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 down
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
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
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
Could both of you attach the details of the disk drive that is slow to
respond? There are several potential scenarios I'm exploring:
1. Specific issues with some disk drives. Some drives take a *long* time to
clear the status register after a reset.
2. Issues with the particular
This looks to be related to a known issue with some combinations of
controller and disk. The warning link is slow to respond, please be
patient is issued in drivers/ata/libata-core.c::ata_wait_ready().
It waits for the link status to change from 0xff (no device) for up to
ATA_TMOUT_FF_WAIT.
Forgot to mention my primary concern here!
Although the change in the arbitrary time-out will remove the 'link is
slow to respond' message it won't of itself remove the kernel oops.
The ideal solution would be parallel processing for multiple devices
maybe combined with some intelligence in the
Fridtjof, we're looking at this issue in more detail and thinking about
back-porting the Jaunty patch from bug #318978 to test kernels for
Intrepid. However we noticed that in one of your dmesg reports in
comment #16
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/286672/comments/16
It
Felipe, I've spent about an hour examining the log-files and reports.
Everything points to a (intermittent) hardware problem. I'm inclined to
think it could be something causing a memory-mapping issue right now,
but that is just a guess with no evidence to point to.
Here's some things you can do
On Thu, 2009-02-26 at 20:18 +, Felipe Figueiredo wrote:
Should I post any other tests? Should this report be closed as Fix
Released, or Invalid?
I'm glad to hear you've apparently solved the issue. I would recommend
you keep the bug open for a couple of weeks whilst you test the system
Jacob, your problem looks unrelated to this bug and more serious.
Please create a new bug report BUG: scheduling while atomic:
notification-da/10006/0x1001 against the linux package, attach
the same logs you've attached here (maybe delete the attachments from
this report to save confusion)
Tested Aaron's patch with Jaunty and it appears to be working fine. I've
repackaged the patch in a debdiff and am nominating for Jaunty.
** Attachment added: Watch all X screens for activity
http://launchpadlibrarian.net/23174124/gnome-screensaver_2.24.0-0ubuntu5.debdiff
--
Screensaver just
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
BUG: scheduling while atomic: notification-da/10006/0x1001
https://bugs.launchpad.net/bugs/335429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment removed: lspci.txt
http://launchpadlibrarian.net/23161853/lspci.txt
** Attachment removed: cpuinfo.txt
http://launchpadlibrarian.net/23161849/cpuinfo.txt
** Attachment removed: kern.log
http://launchpadlibrarian.net/23161811/kern.log
--
kernel warning while suspending
If you are experiencing this issue (kernel reporting a slow resume -
more than 5 seconds) there are several potential causes, at least two of
which are expected (1 2) and the warning is something of a false
positive.
1. Several devices pushing the resume time slightly beyond the arbitrary
The only thing of note in the disk reports is that both disks are on the
first PCI SATA controller and, probably more significant, both devices
are Western Digital. Anecdotal reports suggest some WD drives in
particular have this characteristic slow reset.
Please try the Intrepid kernel Stefan
This is a small shell-script that can help identify whether a system is
affected by this bug.
for log in /var/log/kern.log*; do CMD=cat ; echo $log; [ !
${log##*.gz} ] CMD=zcat ; $CMD $log | grep -n 'PM:
\(suspend\|resume\) devices took'; done
Example output:
var/log/kern.log
Trust me to provide an incorrect shell script! I omitted to test for the
resume as well as suspend action!
Please use this shell script instead:
for log in /var/log/kern.log*; do CMD=cat ; echo $log; [ !
${log##*.gz} ] CMD=zcat ; $CMD $log | grep -n 'PM:
\(suspend\|resume\) devices took'; done
in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
--
BUG: scheduling while atomic: notification-da/10006/0x1001
https://bugs.launchpad.net/bugs/335429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: xorg-server (Ubuntu Hardy)
Assignee: TJ (intuitivenipple) = (unassigned)
Status: In Progress = Confirmed
--
Xdmx packages missing in hardy
https://bugs.launchpad.net/bugs/242191
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've just taken a look at the original dmesg and noticed something which
could be significant:
[0.004000] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[0.004000] Placing software IO TLB between 0x2000 - 0x2400
Quentin, when you get the opportunity could you attach a
Are any users still suffering the symptoms described in the original bug
report?
Resume from suspend fails and triggers a normal boot. The suspend works
and causes spin down and blinking suspend light.
If not I propose we close this report as Fix Released
--
[intrepid] Resume from suspend does
The irqfixup solution is intended for working around broken device
firmware and therefore it could be argued there isn't a bug in the
kernel. Andrey also reports interesting scenarios in his Gentoo bug
comments:
If module is loaded and interface is down via ifconfig, then after resuming
network
If this is still happening on Hardy, Intrepid, or Jaunty could you
please report/attach the following information:
Q. Does this happen for hibernation (a.k.a. suspend to disk) ?
Q. Does this happen for suspend/resume (suspend to RAM) ?
If you answered Yes to either of these questions please
For those that can reproduce this could you provide the following
reports/attachments?
For both hibernate (to disk) and suspend (to RAM) gather the kern.log
files from the current start-up and the previous after a suspend/resume
and hibernate cycle. By providing the previous kern.log file we
*** This bug is a duplicate of bug 267779 ***
https://bugs.launchpad.net/bugs/267779
This looks like a duplicate of Bug #267779 via-rhine network adapter
won't work on resume. Please take a look at that.
In both big reports lspci shows:
Ethernet controller [0200]: VIA Technologies, Inc.
Fridtjof, thank-you.
As already mentioned there is no real problem here.
[ 110.100086] sd 0:0:0:0: [sda] Starting disk
[ 114.984030] ata1: link is slow to respond, please be patient (ready=0)
[ 116.216086] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 116.232336] ata1.00:
If you're still experiencing this issue with Hardy, Intrepid or Jaunty
please report/attach the following after enabling kernel debug logging.
To enable kernel debug enter the GRUB menu at start-up by pressing
ESCape. Highlight the kernel to boot, press E to edit it. Highlight
the kernel line and
This bug is related to the Intel ipw2200 kernel module which manages the
2200BG adapter.
Tomas Hynk's PC has:
Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
Alex Fraser's PC has the 3945 which uses the iwl3945 module:
Intel Corporation PRO/Wireless 3945ABG [Golan] Network
*** This bug is a duplicate of bug 34389 ***
https://bugs.launchpad.net/bugs/34389
I'm marking this as a duplicate of #34389 Lid state is incorrect on
Dell Inspiron 700m since the problem appears to affect several makes
and models in the same way. The symptom being that after resuming the
** Summary changed:
- Lid state is incorrect on Dell Inspiron 700m
+ Lid state is incorrect (closed) after resume with lid open
--
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
The key to this issue may be given by the following clue from
/var/log/kern.log:
ACPI Error (evxfevnt-0383): Could not disable RealTimeClock events [20080609]
ACPI: RTC can wake from S4
Which, if it is indicating the root cause, indicates a 'bad' ACPI DSDT.
If you're experiencing this issue
Is anyone who experiences this issue able to test it with a Jaunty live-
CD and suspend/resume?
--
Synaptics touchpad ceases functioning after suspend and resume.
https://bugs.launchpad.net/bugs/59867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
701 - 800 of 2963 matches
Mail list logo
