Tekram scsi DC-395 card cause Kernel Panic in breezy-rc1 install

Bug #23364 reported by Laurent Coutellier
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Ben Collins

Bug Description

When the Scsi card is turned on. It cause Kernel panic during the breezy
install. It seems during "Hal" packaging configuration

Revision history for this message
Laurent Coutellier (laurent-coutellier) wrote :

(In reply to comment #0)
> When the Scsi card is turned on. It cause Kernel panic during the breezy
> install. It seems during "Hal" packaging configuration

It cause kernel panic too when the scsi card is addeda after install during boot

Revision history for this message
Matt Zimmerman (mdz) wrote :

Please send the text of the panic, including any stack trace.

Revision history for this message
Laurent Coutellier (laurent-coutellier) wrote :

(In reply to comment #2)
> Please send the text of the panic, including any stack trace.

4294739.432000] Stack: e08626cf c131cc80 dfec71fc dfcd4ca0 dfcd6a20 e08629b0
dfec6204 dfec71fc
[4294739.432000] 00000800 dfec6204 dfec71fc dfcd6a20 dfec6204 00009000
e0862451 dfec6204
[4294739.432000] dfcd6a20 dfec71fc dfcd6a20 dfec71fc 00000310 00000387
dfec6204 00000286
[4294739.432000] Call Trace:
[4294739.432000] [<e08626cf>] pci_unmap_srb+0x4a/0x6e [dc395x]
[4294739.432000] [<e08629b0>] srb_done+0x295/0x2b0 [dc395x]
[4294739.432000] [<e0862451>] disconnect+0x195/019d [dc395x]
[4294739.432000] [<e08610ce>] dc395x_handle_interrupt+0x5f/0x11b [dc395x]
[4294739.432000] [<e08611bd>] dc395x_interrupt+0x33/0x61 [dc395x]
[4294739.432000] [<c012d953>] handle_IRQ_event+0x20/0x4c
[4294739.432000] [<c012d9f2>] __do_IRQ+073/0xb1
[4294739.432000] [<c0104ca5>] do_IRQ+0x19/0x24
[4294739.432000] [<c01038b6>] common_interrupt+0x1a/0x20
[4294739.432000] [<e08faa38>] acpi_processor_idle+0x0/0x29b [processor]
[4294739.432000] [<e08fab37>] acpi_processor_idle+0xff/029b [processor]
[4294739.432000] [<c01010a1>] cpu_idle+0x2d/0x42
[4294739.432000] [<c0324665>] start_kernel+0x176/0x178
[4294739.432000] Code: 8b 54 24 04 8b 02 f6 c4 01 75 05 e9 b2 5f 02 00 89
d0 e9 bd 59 02 00 b8 00 e0 ff ff 21 e0 f7 40 14 00 ff ff 0f 8b 54 24 04 74 02
<0f> 0b 8b 02 f6 c4 01 74 07 89 d0 e9 c5 5a 02 00 c3 56 b8 00 e0
[4294739.432000] <0>Kernel panic - not syncing: Fatal exeption in interrupt
[4294739.432000]

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #3)
> (In reply to comment #2)
> > Please send the text of the panic, including any stack trace.
>
> 4294739.432000] Stack: e08626cf c131cc80 dfec71fc dfcd4ca0 dfcd6a20 e08629b0
> dfec6204 dfec71fc

Thanks, but we need the part immediately before this as well. It might say
"oops" or similar.

Revision history for this message
Laurent Coutellier (laurent-coutellier) wrote :

>
> Thanks, but we need the part immediately before this as well. It might say
> "oops" or similar.
>

I've just copied those I see on screen
I've seen on different log in /var/log but perhaps I don't watch in the good path
which log can help you ?

Revision history for this message
Ben Collins (ben-collins) wrote :

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Revision history for this message
Laurent Coutellier (laurent-coutellier) wrote :

the upgrade to 2.15.7-K7 seems well but a repeated message appears when I switch
(Ctrl+Alt+F2) to console : "dc395x: sg_update_list: sg_to_virt failed"

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.