Description of problem: I have encountered this bug once and has not recurred but, everytime the tape is mounted on the tape drive by the backup software, the server hangs (no network connection, no console access) Version-Release number of selected component (if applicable): kernel-2.4.21-32.EL How reproducible: 3 x Dell Servers connected to SAN and sharing one Dell PowerVault 132T LTO3 tape library. Steps to Reproduce: 1. Configure Netbackup with shared storage option 2. Have one media server mount the tape drive 3. Actual results: Server hangs (mostly), Kernel bug encountered once (please see the attached messages file Expected results: Additional info: I have already check with our backup provider, however, they could not interpret the bug encountered. Apologies in advance if this issue should does not belog to bug report criteria. Our backup provider wanted to know what the kernel bug messages mean. Thank you in advance.
Created attachment 125990 [details] messages file which contains the Kernel BUG at pci_dma:43 info
Correcting "hardware" field. This looks related to bug 171473, but I'll let Chip decide if this should be closed as a dup.
(In reply to comment #3) > Correcting "hardware" field. This looks related to bug 171473, > but I'll let Chip decide if this should be closed as a dup. I don't think this is a dup of 171473 -- but I do think this bug (bug 185183), bug 185399, bug 182996, and bug 162212 are all duplicates of each other and therefore all fixed in RHEL3 U8. Would it be possible to have the customer upgrade to U8 and retest? Thanks, Chip
(In reply to comment #4) > I don't think this is a dup of 171473 -- but I do think this bug (bug 185183), > bug 185399, Scratch that. bug 185399 is totally unrelated. Chip
Chip, customers can't yet "upgrade to U8" because it's still in development. We can provide an RPM of an interim build to verify whether this bug has been addressed, but a customer has no way to obtain such an RPM directly (without the help of you or someone in Customer Support).
(In reply to comment #6) > Chip, customers can't yet "upgrade to U8" because it's still in > development. My mistake; I thought it was out in the beta channels. Your comment on bug 182996 indicates that the fix for that bug went into kernel 2.4.21-40.5 -- so if we can get that build to the customer to test, that would be very helpful. Chip
We have a kernel build that includes a patch that we believe fixes this bug. If the customer can send me the output of "uname -a" on the affected system, I can identify the apropriate rpm to send to him. Thanks, Chip
*** This bug has been marked as a duplicate of 182996 ***
A fix for this problem was committed to the RHEL3 U8 patch pool on 27-Mar-2006 (in kernel version 2.4.21-40.5.EL).
Adding a couple dozen bugs to CanFix list so I can complete the stupid advisory.
(In reply to comment #9) > We have a kernel build that includes a patch that we believe fixes this bug. If > the customer can send me the output of "uname -a" on the affected system, I can > identify the apropriate rpm to send to him. > > Thanks, > > Chip > Hi Chip, Here is the "uname -a" output. Linux ssmpora02 2.4.21-32.EL #1 SMP Fri Apr 15 21:02:58 EDT x86_64 x86_64 x86_64 GNU/Linux Is it possible to send the right rpm to address this bug so that we could already test it? If I may ask, when will the Update8 most likely to be released? Thanks. -Alan
Alan, I'm not allowed to provide an official statement about the U8 schedule. Please ask Customer Support. But I suggest checking the RHN beta channels in a couple of weeks if you'd like to participate in beta testing.
(In reply to comment #14) > Alan, I'm not allowed to provide an official statement about the U8 > schedule. Please ask Customer Support. > > But I suggest checking the RHN beta channels in a couple of weeks if > you'd like to participate in beta testing. > Hi Ernie, Will check RHN beta channels as per your advise. Thanks. -Alan