Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986654
Title:
disk
The issue is seen on Ubuntu 13.04 also. Although in my case it is not a
real physical machine but a VM running ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986654
Title:
disk I/O race
Thanks a lot for your hard work in investigating this issue, very
appreciated!
I've been fighting with this IRQ problem for almost 2 years now. Same thing as
you reported, those random soft resetting link messages and drive resets out
of the blue.
Unfortunately, no one wants to tackle this
I remain of the opinion that the root issue here is a subtle timing issue.
I spent a tremendous amount of time on this. I have thrashed two old PATA
drives to death. Now, the most recent drive I recovered and am using does not
have the issue (the drive is a little slower than the others I had
I did not realize that I hadn't previously given a link to my related web notes:
http://www.smythies.com/~doug/network/hd_race/index.html
@andi3: you could get this bug report confirmed by clicking that this
effects you also. (although I see that you did not subscribe, and
myself, I don't
From post #22 above: Why? The rule is for sr or removeable devices.
The hard disk is an sd device. Why does the change result in issues
with the hard disk?
The reason is that the single udev rule change that introduced this
issue, actually just created a new, and more probable, way to
demonstrate
Issue persists with up to date 13.04 (devlopment). Reverting the one
line (see post #22) in /lib/udev/rules.d/60-persistent-storage.rules to
the pre revision 2760 state fixes the issue. I went back and forth a few
times. After editing the file run sudo update-initramfs -u then re-
boot(and that is
Issue persists with 13.04 (development), which is not surprising since
the udev version is the same.
doug@test-smy:/$ uname -a
Linux test-smy 3.7.0-2-generic #8-Ubuntu SMP Thu Nov 15 16:21:20 UTC 2012 i686
i686 i686 GNU/Linux
doug@test-smy:/$ cat /proc/version
Linux version 3.7.0-2-generic
Issue persists with 12.10 and udev 175-0ubuntu13.
Workaround: If not being used unplug the CD-ROM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986654
Title:
disk I/O race condition after update
The issue has been isolated to the single line change of launchpad
revision 2760 (while revision 2761 edits the same line again, the
results are the same).
Specifically: in the file rules.d/60-persistent-storage.rules, this line:
ACTION==add, KERNEL==sr*, ATTR{events_poll_msecs}==0,
Posting a few files that may or may not be of interest.
** Attachment added: attribute walk for HD with 175-0ubuntu9 with 2761 put to
2759
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/986654/+attachment/3256970/+files/sda2759.txt
--
You received this bug notification because you
** Attachment added: attribute walk for HD with 175-ubuntu9 with 2761 put to
2760
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/986654/+attachment/3256972/+files/sda2760.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: attribute walk for CD drive with 175-0ubuntu9 with 2761
put to 2760
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/986654/+attachment/3256974/+files/sr02760.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: attribute walk for CD drive with 175-0ubuntu9 with 2761
put to 2759
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/986654/+attachment/3256973/+files/sr02759.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Basically this diff file shows stuff as expected.
These tests were all done with packages built that were basically
175-0ubuntu9 but with Launchpad revision number 2761 taken out and
either 2759 or 2760 put back. (for whatever reason 9.1 was not available
yet).
Summary: the one line change
I wrote a program to help demonstrate the issue. It is now my preferred method
of test.
Finally, I have been able to compile and make the .debs that I was missing.
Now the issue has been isolated as having being introduced in udev 175-0ubuntu7.
It seems most likely to have been introduced with
** Tags removed: bot-comment kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986654
Title:
disk I/O race condition after update
To manage notifications about this bug go
The new udev, 175-0ubuntu9.1, does not fix this problem.
I have not been able to compile udev yet to be able to isolate things further.
I have been using http://developer.ubuntu.com/packaging/html/ as a reference.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This issue has been isolated down to the udev package.
Using udev 175-0ubuntu6 the disk I/O is fine
Using udev 175-0ubuntu9 the intensive disk bashing test fails.
The test has been repeated now a few times of starting from a fesh
installation of the 2012.03.27 ISO, verifying things work
** Package changed: linux (Ubuntu) = udev (Ubuntu)
** Changed in: udev (Ubuntu)
Importance: Medium = Undecided
** Changed in: udev (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As mentioned in the original bug report, everything works fine starting from a
fresh installation of the 2012.03.27 ISO.
This includes with any kernel.
Once sudo apt-get update and sudo apt-get upgrade are done, then any and
every kernel shows this issue.
Starting from a fresh install of the
The error even of posting 11 above was during re-boot and not during the disk
thrashing test as I originally thought.
I have not seen the error during re-boot before.
** Attachment added: part of kern.log for disk issue during re-boot
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested
the upstream kernel, please remove the 'needs-upstream-testing' tag(Only
that
In my original posting, I did not mention that I had also tested a bunnch of
mainline kernels, and always had this issue.
I tested 3.4RC4 this morning, and it has the issue of the bug posting. The
edited kern.log file is attached.
Even if the issue did not appear with kernel 3.4RC4, I would be
My best guess is that this should be package=linux
I do see acticity for ata_piix.c around the right time frame, but I cann't find
the dated change history for the file.
** Package changed: ubuntu = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986654
Title:
disk I/O race condition after update
To manage notifications about this bug
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986654
Title:
disk I/O race condition after update
To manage notifications about this bug go to:
For these two lines in the edited kern.log.txt file:
Apr 20 23:49:33 test-smy kernel: [ 4662.839710] Clocksource tsc unstable (delta
= 303994203 ns)
Apr 20 23:49:33 test-smy kernel: [ 4662.841953] Switching to clocksource pit
I do not think the clock was actually unstable. I think it got out of
** Attachment added: Package differences edited -remove obvious not related
ones.
https://bugs.launchpad.net/ubuntu/+bug/986654/+attachment/3097773/+files/pkg_diff_edit.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Package differences - unedited (in case I removed
something that matters earlier)
https://bugs.launchpad.net/ubuntu/+bug/986654/+attachment/3097774/+files/pkg_diff.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I made a mistake with the version in my orignal posting above. The
listed versions were as the system was running, and tested, at at the
time of writing this bug report. The actual conditions for most of the
testing and attachments were with the original kernel from the
2012.03.27 ISO or:
Linux
** Attachment added: output from sudo lspci -vnvn as suggested in notes
https://bugs.launchpad.net/ubuntu/+bug/986654/+attachment/309/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Believe me, I have been trying to figure out the proper package to
relate this bug to. For two reasons: First, for proper filing of this
bug; Second, so that I can investigate further myself.
I also can not get apport-collect 986654 to work because the computer
is a server only, and it seems to
33 matches
Mail list logo
