Tony Butt, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1016010/comments/14
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow lin
This seems to have been resolved as of Ubuntu 14.04LTS.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016010
Title:
Adaptec SCSI controller causes modprobe hang
To manage notifications ab
Tony Butt, thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will automatically
gather debugging information, in a terminal:
apport-collect 1016010
When reporting bugs in the future please use apport by using 'ubuntu-bu
Our system was rebooted recently, and came up with the 3.5.0 rc6 kernel.
No attempt was made to access the tape device for a day, as the bacula
storage daemon is currently started manually while we deal with this
issue. When the storage daemon was started, normal tape access was
possible with the r
I checked today against 3.5.0 rc6, the same problem is still there.
I was hopeful the ACPI changes noted in rc5 might have had some effect.
Checking other bug reports (eg
http://bugs.contribs.org/show_bug.cgi?id=373), similar problems have
seemed to occur from time to time over the last 10 years o
Found a similar report as Bug #41061, affecting kernel 2.6.15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016010
Title:
Adaptec SCSI controller causes modprobe hang
To manage notifications about
As another data point for this issue:
The system affected by this issue is a production system performing an
important task for us, so we have been considering our options to work around
this problem.
I tried reverting our kernel revision back to the last Lucid kernel that we
have, 2.6.32, insta
I ran
'ps -ef | grep modprobe'
while my mtx command was stuck (mtx -f /dev/sg4 status)
and had the following output.
root 2233 574 0 12:42 ?00:00:00 /sbin/modprobe -bv scsi:t_0x08
root 2237 1 0 12:42 ?00:00:00 sh -c /sbin/modprobe
--ignore-install st && /etc/i
** Attachment added: "linux-3.5.0-rc3 dmesg output for modprobe hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1016010/+attachment/3199705/+files/linux-3.5.0-030500rc3-generic-dmsg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "linux-3.2.0 dmesg output for modprobe hang"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1016010/+attachment/3199704/+files/linux-3.2.0-24-dmsg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Tested against 3.5-rc3 kernel as suggested. The problem is still present.
Had to remove my modprobe options, as they were rejected.
I have collected output from dmesg showing the available kernel
messages, and output from ps -ef | grep modprobe showing the modprobe
which is hanging. It seems to be
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.5kernel[0] (Not a kernel in the daily directory) and install both the
linux-image and linux-image-extra .deb packages.
Once you've tested the upstream
specifically, seems to be kernel module aic7xx, which I think is part of
the kernel-image package
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016010
Ti
13 matches
Mail list logo
