Also seeing through sensors-applet in Ubuntu 10.04.
With no disks in sensors-applet monitoring, works.
When disks present, spins up within minutes.
** Also affects: sensors-applet (Ubuntu)
Importance: Undecided
Status: New
--
running hddtemp causes unnecessary disk activity
I found this behaviour extremely annoying, but I cannot ever remember
this bug on 80/90's HP, or Sun workstations.
Maybe that's because those companies, or the sysadmins mapped the arrow
keys to something else.
If vim_tiny has to be kept, can I suggest doing 2 things
1. Mapping arrow keys
Public bug reported:
Binary package hint: checkbox
the system testing utility attempts to test virtual terminals using chvt.
but I can switch virtual terminals fine using ctrl+alt+fn, and sudo chvt 1.
ProblemType: Bug
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v',
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32996099/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/32996100/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/32996101/ArecordDevices.txt
Still happening today, with all updates applied.
--
nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
https://bugs.launchpad.net/bugs/406788
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is happening to me in apha6, with updates applied
ubuntuone-clientversion:0.95.1-0ubuntu1
--
nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
https://bugs.launchpad.net/bugs/406788
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Your power issues are interesting.
The motherboard I have done most testing on, has in the past had power issues,
which were mainly cured by getting a high quality PSU.
So, turning off power management, (the fix that worked best for me) probably
avoids stressing an under-powered USB controller.
I have now tested with RAID1 on Hardy.
Is still failing.
For the machine with this controller, I have built a custom kernel, with the
changes suggested by Walter.
This is working well.
Q: Do we need a new bug for ITE8212 RAID1 config?
I agree with Watler, for the moment, Ubuntu should disable
robinl:
Can you provide a reference for only fixing IDE controller (JBOD mode)?
I've been doing a little investigation, and it looks like there are fixes
towards both RAID and JBOD...
Infact my recollection from the changelog is that if applied fixes for both.
--
Unable to detect ITE8212 RAID0
Ric:
Try the procedure described in my comment here, to put autosuspend in the boot
procedure:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/209
Sometimes not all devices seem to recover properly after turning off
autosuspend.
I suspect we could divide this
P.s. Ric:
Can you try to find out more about why the bug is marked Won't fix?
I'm tempted to open a bug for case A, so at least the case I'm seeing
can progress towards a fix.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug
I've tested with alpha 5 live CD, and still get the same errors.
So either John's bug is different from mine, or the kernel he used
isn't in alpha 5.
John:
Could you try alpha 5 live CD and see if it works?
--
ehci_hcd module causes I/O errors in USB 2.0 devices
John:
It's quite possible was just checking what has changed in the kernel
this weekend and found the following:
[PATCH] EHCI: add a short delay to the bus_suspend routine
Here it's released as a patch (10th Jan)
http://thread.gmane.org/gmane.linux.usb.general/547
And here it goes into the
I think the fix Pedro's found should resolve this bug.
But this is only released on the 2.6.25 kernel.
Any chance of getting this patch on Hardy's 2.6.24 kernel??
--
Unable to detect ITE8212 RAID0 array
https://bugs.launchpad.net/bugs/106931
You received this bug notification because you
Why is this flagged wontfix?
Still a show stopper for people like me.
Has discouraged at least one potential Linux user I know.
Has certainly discouraged me from promoting Linux commercially.
This bug does need to be divided up into a number of distinct bugs,
depending on symptoms, and which
Still failing in hardy a4.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
A fall back to 1.1 speeds when ehci fails sounds good.
Probably should warn users when this is happening, if in desktop mode, via
dialog, or notification in toolbar.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification
I have just had a look through the lspci logs attached to this bug and a
significant number are nvidia nforce2 motherboards.
So, can I ask all users with nforce2 to try my auto suspend suggestion.
(https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/209)
Ok, I'm going to clarify what I said above:
For some DVB cards, the windows firmware works on Linux.
For others it does not.
So, if your symtoms are:
1. run windows(DVB works)
2. restart into linux (DVB fails)
3. power-down re-start linux (DVB succeeds)
.Then your
Well, I have to agree with Elias and NoWhereMan.
USB autosuspend needs to be disabled in Hardy.
Probably best to do it by config in the initrd so that brave users can
modify it without a re-compile.
(I've looked into the git repository for ubuntu and if I'm looking at the
correct stuff,
Charles:
I gave the commands to test disabling autosuspend above.
Details are in the following comment
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/188
*Note* you must be logged on as root at the console to do this.
Please try it, and report back.
I
I've now tried putting the autosuspend into the boot procedure
After power-on this works succesfully.
There may still be problems after a restart.
My procedure was as follows:
1. Type the following in a terminal window:
sudo gedit /etc/modprobe.d/usb-core-options
2. Add the
It it works after restart from Windows, this suggests that you don't have the
correct firmware for this card.
Windows leaves the firmware in the DVB-t decoder after reboot, enabling some
people's cards to work.
--
dvb-t driver troubles with an intuix s800 usb stick
Update to last report:
My problems on restart are not related to this bug.
But I definitely need a full restart before everything is working fully.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a
I have just tried the Hardy alpha2 live CD, and still get this problem.
Changing the autosuspend option at the command line doesn't work.
I would like to try changing this in the Hardy live CD initframfs, but don't
know how.
Any ideas?
--
ehci_hcd module causes I/O errors in USB 2.0 devices
The following link contains important documentation for users developers
regarding this bug
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/usb/power-management.txt;h=b2fc4d4a99177be7bd48dce560d1f28417c60aa9;hb=HEAD
This decsribes issues in the 2.6.24
Leann, I tested with Gutsy not Hardy.
I would have tested with Hardy but couldn't find the live cd.
...When Alpha2 comes out, where will I find the live CD?
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because
Another thing to note is that my devices were working with Gutsy
And then mysteriously stopped working.
Maybe a kernel update caused this?
I believe Elias also reported this above.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this
I've got my system working after doing the following:
[EMAIL PROTECTED]:~# modprobe -r ehci-hcd
[EMAIL PROTECTED]:~# echo -n -1 /sys/module/usbcore/parameters/autosuspend
[EMAIL PROTECTED]:~# modprobe ehci-hcd
Everything now seems to be working.
From past experience, I'll keep testing, because
Ok, and here's the kernel log for the above session.
Note that the system start wth failing ehci.
At around 14:11:10 I execute the commands above, and everything seems to start
working.
** Attachment added: kern.log
http://launchpadlibrarian.net/10914443/kern.log
--
ehci_hcd module causes
I think everyone using Gutsy should try the autosuspend workaround, and report
on bug# 85488 as directed here:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/102
NOTE: I could only get this working by removing ehci, and re-installing.
Simply setting the
Ok, I've reported success using the autosuspend workaround in bug #88746.
(See following comment:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/188)
Now, should some of my hardware be blacklisted?
Is this now being done in kernel, or in udev rules?
I have also
Ok, here's the kernel log from my current failing USB setup.
Not that this setup was previously succeeding.
** Attachment added: Ubuntu 7.10 kernlog--usb errors
http://launchpadlibrarian.net/10819214/Ubuntu%207.10%20kernlog--usb%20errors
--
ehci_hcd module causes I/O errors in USB 2.0
In previous e-mail second line should read:
Note that this setup was previously succeeding.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
And here's the lspci output to go with the kernel log.
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/10819223/lspci-vvnn.log
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a
Update on my last report.
It seems I may be experiencing intermittent failure of usb system on boot.
Will investigate when I have time.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of
This could be important for debugging Xorg crashes with compiz.
There are a number of bugs I have had in Xorg that I cannot find logs for, as I
believe one crash was almost immediately followed by another.
Maybe it would be good to bump this importance to improve compiz debugging?
--
X Should
The 'dynamic' option didn't work for me.
Appears not to manage lack of DNS.
It is the lack of a valid DNS that causes NTP to fail
And NTP isn't yet designed to cope with DNS changes/missing DNS.
Apparently there has been some discussion of making DNS queries dynamic on one
of the mailing
I'm having this problem in gutsy.
But...I've noticed an option to pass to the server entries in ntp.conf that
might work.
From the ntp documentation it's describe as follows.
dynamic
Allows a server/peer to be configured even if it is not reachable at
configuration time. It is
I saw similar on upgrade from feisty to gutsy...
I was placed immediately on the nvidia-glx package.
No suggestion that an upgrade was possible, or worthwhile.
After some fiddling I installed nvidia-glx-new package.
My config is as follows:
lspci | grep -i nv
00:00.0 Host bridge: nVidia
Public bug reported:
Boot into X, and into user.
When doing a ctrl-alt-fN where N is not 7,
then on returning to X by ctrl-alt-F7, most of the time succeeds, but
occasionally, I'm left with a black screen with only a cursor visible.
I'd say that this can be repeated one time in 5, and may
output from lspci -n -vv accached.
** Attachment added: lspci-gutsy2
http://launchpadlibrarian.net/10343780/lspci-gutsy2
--
ctrl-alt-f7 doesn't always return to valid X session
https://bugs.launchpad.net/bugs/162252
You received this bug notification because you are a member of Ubuntu
Bugs,
Note: This dooes *not* hang the system.
Can always to a ctrl-alt-f1 and log into the console.
Can also do a ctrl-alt-delete at console to restart.
--
ctrl-alt-f7 doesn't always return to valid X session
https://bugs.launchpad.net/bugs/162252
You received this bug notification because you are a
I have recently upgraded to nvdida-glx-new in an attempt to fix this
problem, and still see black windows after ~ 5-6 apps open.
My graphics card is identified as:
03:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600
GT] (rev a2)
--
[nvidia-glx] Window content is black
With Ubuntu 7.10 (gutsy) I'm having some success.
NOTE: I have made no changes to the kernel at all.
I can successfully see all my devices.
In addition I have added a Cannon lpb5000 printer and and Epson perfection 3200
scanner, which are working correctly.
But I'm having minor problems with
If you're still having trouble...
Looks like there are 2 things to try.
1. Working without ACPI
Q: would disabling acpi as kernel parameter suffice?
2. Disabling usb autosuspend.
(See my last post for the method)
Q: What info do the developers to start repeating this bug, and
Correction: *Everything* is working fine.
In my Success with 7.10 comment applying the autosuspend off, and the flash
drive working were a coincidence.
Further testing revealed that 9 times out of 10 the flash drive would pause and
reset.
I have since switched to using a powered USB hub, and
Sitsofe:
Could you clarify when you want us to report in Bug #85488?
Do you want us to report in that bug if our USB devices work after
trying the gutsy live cd, and *only* the live CD?
Do you want us to to report in the bug when the only combination that
fixes the bug is the Gutsy live CD
I too have been hit by this bug, in feisty.
I have a whole page of gparted bugs, which I saw during attempts to manage my
partitions.
I believe the root cause of most (possibly all) of these bugs is the partition
re-mounts.
I believe this bug can cause data loss when mounts occur between
Here's the diff for the kernel config of the failing kernel.
Only changes from generic kernel are debug messages.
** Attachment added: config-2.6.60-rob-dbg.diff
http://launchpadlibrarian.net/8190257/config-2.6.60-rob-dbg.diff
--
USB devices are not recognized when having ehci_hcd modprobed
Here's the kernel log of the failing kernel with usb and other debugging
enabled (see last message for what was enabled)
Things start going wrong after this line:
Jun 25 23:40:12 rob-desktop kernel: [ 37.446489] usb 3-4: usb
auto-suspend.
And that's about all I can do.
** Attachment
I can finally confirm that my USB devices are working.
The devices that are working are 3 usb ports, printer, keyboard , mouse and
wacom tablet.
I have also compiled the restricted modules package agianst my modified kernel.
I've attached a diff of the kernel config between non-functioning, and
Here's the kernel log for my new successful kernel.
(Will follow soon with kernel log for standard failing kernel, with
debugging msgs enabled.)
** Attachment added: kernel-log-2.6.20-16-rob-dbg-nosuspendusb
http://launchpadlibrarian.net/8179716/kernel-log-2.6.20-16-rob-dbg-nosuspendusb
--
CONFIG_USB_SUSPEND does indeed work (Or appears to so far)
Will now try to build the extra modules I have installed and do a proper boot.
I'll be putting up kernel logs with some debug messages turned on soon, so
demonstrate the differences in the boot process.
--
USB devices are not recognized
Tadzik, I'm intending to *disable* it.
The fact that your kernel had it disabled ans still fails doesn't bode well.
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug suggests a possible soloution.
http://bugzilla.kernel.org/show_bug.cgi?id=7932
It suggests that some of these problems may be due to suspend operations
occuring.
I'm building a kernel without power management, as a first test.
Will try one with CONFIG_USB_SUSPEND unset, and rest of
Initial tests suggest that turning off power management works.
Have not yet booted into X, and modules outside kernel package not
installed.
but looking good.
Tomorrow I'll try full power management, but without CONFIG_USB_SUSPEND
. unless someone wants to beat me to it ;)
--
USB
Ok thanks for tyring Tadzik.
I've also tried to compile the 2.6.22 kernel that's slated for next
version of ubuntu, and still had USB problems.
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you
Usbfs trick on my system doesn't work.
On my system the usbfs appears properly mounted.
Tried adding the exact line into fstab, with no change.
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you
tried adding acpi=off and noapic (but not both at the same time)
No change, still failing
Tadzik:
Could you look at what the changes between the basic 2.6.21 kernel, from
gentoo, and the genkernel version.
Maybe there's a conifgure option change?
--
USB devices are not recognized when having
ingo, 2.6.20-15 is the version that doesn't work for me.
What was the latest non-functioning version for you?
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs, which
I wasn't sure if the earlier reports of the old_before_new usbcore
property not working were due to the property not being set early enough
in the boot process.
I thought I'd try adding the old_before_new to my intramdisk image.
Successfully applied the property via file in /etc/modprobe.d, but
Correction:
I should say old_scheme_first when is said old_before_new in my last post.
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Ok, here's my kernel logs.
Initially it shows the hubs failing.
At time [ 6758.049237] I unplug/plug the hub, and all attached deices
wok properly.
** Attachment added: kernel-logs showingusb issue
http://librarian.launchpad.net/7572917/kernel-logs%20showingusb%20issue
--
USB devices are
Here are the PCI logs.
No change before/after plug/unplug of USB devices.
** Attachment added: pcipostusb
http://librarian.launchpad.net/7572929/pcipostusb
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug
Here are the lsusb just after boot.
Hubs are missing, and connected devices missing.
** Attachment added: usbpreusb
http://librarian.launchpad.net/7572968/usbpreusb
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug
Here is the lsusb with the devices now working.
** Attachment added: usbpostusb
http://librarian.launchpad.net/7572994/usbpostusb
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member
I too am having this problem in feisty, since install.
Current kernel: 2.6.20-15-generic.
Will attach log file, and hardware info later.
--
USB devices are not recognized when having ehci_hcd modprobed
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a
It might be worth noting that I only have this problem at boot, and only with
USB hubs.
Other devices connected directly to PC work fine.
If I plug/unplug the hub, all attached devices are seen correctly, and
work fine.
Also hardware submission id for this machine is (without working USB
69 matches
Mail list logo
