As Martin pointed out, it seems that Timm's issue is different than the
one originally reported here. The patch which should resolve the
original bug reported here has already been released as an updated. As
a result, I'm marking the Hardy and Gutsy tasks as Fix Released. Again
Timm, if you can
Thanks, Stefan. Timm, can you please test the current hardy-proposed
kernel and report back in bug 247148, which is most probably the one
that affects you?
** Tags added: verification-needed
** Tags removed: verification-failed
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https
The failed verification IMHO is caused by bug #247148.
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Tags added: hw-specific
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
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
htt
My impression is that this is maybe is a different cause. The original
report was for a standard kernel. The latest updates concern Xen.
Unfortunately I did not have much time for progress but it seems the
driver picks the right DMA size (32bit) but maybe the Xen SWIOMMU is
having problems. I think
One gutsy task is enough. Any progress here? This is marked
verification-failed and thus sounds like a regression?
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Fix Committed => Invalid
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238
I found bug #232017 which sounds very similar to me. Setting swiotlb=128 fixed
the problem in this case. I get an error similar to swiotlb=force. For values
of 64 and 16 I get "BUG: soft lockup - CPU#1 stuck for 11s!", while 16 seems a
bit more stable.
With swiotlb=0, 2 or 8 I am back to the ori
I have the problem even without starting a guest (DomU), i.e. only the
Xen hypervisor and the kernel in Dom0 are running.
With swiotlb=off I get a new kernel bug, but it suggests to use
swiotlb=force. I also tried this option and it makes the system
considerably more stable. I could install and de
It sounds a bit strange, that the sw-iommu is used in first place. IMO
this is only necessary for 64bit. I am not using Xen myself so maybe the
question is dumb, but anyway: the host is running exactly the same
kernel as the guest? Also, have you tried the effect of swiotlb=off?
--
linux-image-2.
I sampled swioltb in the range from 2k to 512k in steps of factor 2 and 4 M as
a very large value. Except for 2k I get the same kernel bug in
/home/smb/hardy-i386/ubuntu-2.6/debian/build/custom-source-xen/mm/bootmem.c:190
For 2k I get "low bootmem alloc... Kernel panic ... Out of low memory".
I c
Sorry for the late response. Ok, the log shows the driver goes in 32bit
DMA mode (which should be right). The question is why the SWIOMMU fails
to provide DMA space. The bitsize of 32 sound valid so the tuneable
would be swiotlb. Be aware that the unit there is a page, so using 64K
there takes away
Here is the result of running the new kernel. 32bit is right for this
machine. Thank you!
** Attachment added: "Console log"
http://launchpadlibrarian.net/16311435/xen_debkrnl1
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received th
I updated the original location with a fresh rebuild. If you could try
that again. http://people.ubuntu.com/~smb/bug238118/linux-
image-2.6.24-20-xen_2.6.24-20.37smb3_i386.deb
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bu
Now that I look at it this does make sense. For some odd reason I put
the wrong package for i386 there (missing the smb extension for the deb
I normally use). So this is some other build and looking at the build
machine it seems I have to run a rebuild. Sorry for that.
--
linux-image-2.6.24-* w/
I deinstalled linux-image-2.6.20-xen with dpkg -r and installed your
kernel with dpkg -i
ls -l /root/linux-image-2.6.24-20-xen_2.6.24-20.37_i386.deb
-rw-r--r-- 1 root root 18747646 2008-07-23 22:21
/root/linux-image-2.6.24-20-xen_2.6.24-20.37_i386.deb
I was a bit confused because the kernel is m
I have put up two -xen kernels at http://people.ubuntu.com/~smb/bug238118/
While they won't fix the problem I'd really like to see what the driver tries
to settle for dma size (the messages should prefix xxx).
Also I saw that the xen iommu implementation seems to support swiotlb=
and dma_bits= wh
marked as 'verification-failed', and rolled back to 'confirmed'. Looks
like more investigation is needed.
** Tags added: verification-failed
** Tags removed: verification-needed
** Changed in: linux (Ubuntu Hardy)
Status: Fix Committed => Confirmed
--
linux-image-2.6.24-* w/ aic79xx cr
I get the same problem with 2.6.24-20.37.
Thanks,
Timm
** Attachment added: "Console log"
http://launchpadlibrarian.net/16211879/xen_fix2
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notification because you are
This patch is included in kernel 2.6.24-20.37 from your log I've seen you are
running 2.6.24-19.x
New kernel is available for testing in proposed but it's not automatically
upgraded by Linux meta package, you have to do it yourself.
You can see bug fix mentioned in changelog.
https://launchpad.
Dear Steve,
thank you for picking up my problem. Unfortunately the new linux-image
does not fix the bug. I attached the console output.
Thank you for your help!
Timm
** Attachment added: "Console log"
http://launchpadlibrarian.net/16133525/xen_fix1
--
linux-image-2.6.24-* w/ aic79xx crash
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https:/
Description: Ubuntu 8.04
Release: 8.04
Affected kernel flavors: 2.6.24-19-xen version 3.2.1-rc1-pre
([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) Fri Apr 11
01:12:53 UTC 2008
Bug remains after patch of Xen kernel!
I installed the kernel from bug #218126
(Ihttp://www.il.is.s.u-t
** Changed in: linux (Ubuntu Hardy)
Status: In Progress => Fix Committed
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Re-setting to "In Progress" for SRU process reasons.
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Re-setting to "In Progress" for SRU process reasons.
** Changed in: linux (Ubuntu Hardy)
Status: Fix Committed => In Progress
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notification because you are a member of
SRU justification (Gutsy + Hardy):
Impact: Hard lockups when doing heavy (IMO just higher) I/O load. The
reason is that dma_get_required_mask returns a wrong value and thus the
memory management will get confused.
Fix: From upstream (in Intrepid) will remove the limit to the current
dma mask when
Commited to ubuntu-gutsy as: 509dc390d293330ff9c1cbdfa0706ea2609ebef1
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Status: In Progress => Fix Committed
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: In Progress => Fix Committed
--
linux-image-2.6.24-* w/ aic79xx crash un
Commited to ubuntu-hardy as: 2595000a54e3c647cf35bb550c3f3a2699237c90
** Changed in: linux (Ubuntu Hardy)
Status: In Progress => Fix Committed
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notification because yo
Just adding a note I've also added Gutsy SRU nominations that Stefan is
working on. Thanks.
** Changed in: linux (Ubuntu Gutsy)
Status: New => Invalid
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
Status: New
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-source-2.6.22 (Ubuntu Hardy)
Importance: Undecided => Medium
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
Status: New => In Progress
--
linux-image-2.6
** Changed in: linux (Ubuntu Hardy)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Stefan Bader
(stefan-bader-canonical)
Status: Triaged => In Progress
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug not
Hi lakostis,
Thanks for the report and the upstream git commit id. It's very
helpful. I'll reassign this to the kernel team and open a nomination
for a Hardy SRU (stable release update). This patch is already in the
upcoming Intrepid Ibex 8.10 kernel. Thanks.
** Changed in: linux (Ubuntu)
** Attachment added: "fixing patch for from upstream"
http://launchpadlibrarian.net/15106795/kernel%20BUG%20at%20drivers_scsi_aic7xxx_aic79xx_osm.c%3A1490%21.eml
--
linux-image-2.6.24-* w/ aic79xx crash under heavy I/O load
https://bugs.launchpad.net/bugs/238118
You received this bug notific
33 matches
Mail list logo
