Bug 123
Summary: | SiL 680 IDE controller has "issues" | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Dave Jones (davej) |
Component: | IDE | Assignee: | Alan (alan) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | blocking | CC: | bunk |
Priority: | P2 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Subsystem: | ||
Regression: | --- | Bisected commit-id: |
Description
Dave Jones
2002-11-27 12:11:22 UTC
Ok I need to understand why it hangs, that is important. If you are seeing spewing crc errors on 2.4 as well then it may be other problems that need looking into as well, or may be hardware can't tell yet According to Andre, rev 0 of this controller has known hardware bugs, so feel free to close this. We need to handle them if so Strange. I moved this card to a different box, and tried it under 2.5 again. This time it spits out.. SiI680: IDE controller at PCI slot 00:09.0 SiI680: chipset revision 1 SiI680: not 100% native mode: will probe irqs later SiI680: BASE CLOCK == 133 ide2: BM-DMA at 0xc000-0xc007, BIOS settings hde:pio, hdf:pio ide3: BM-DMA at 0xc008-0xc00f, BIOS settings hde:pio, hdf:pio Note it was MMIO-DMA in the previous report.. It still hangs solid after printing these two lines. No sysrq, not even capslock LED toggle works.. Just for kicks, I decided to try it as a module. Gets me an oops at the point where it normally prints the ide2: line.. SiI680: IDE controller at PCI slot 00:09.0 SiI680: chipset revision 1 SiI680: not 100% native mode: will probe irqs later SiI680: BASE CLOCK == 133 Unable to handle kernel paging request at virtual address 6f6d657d printing eip: c041a3b2 *pde = 00000000 Oops: 0000 [#1] CPU: 0 EIP: 0060:[<c041a3b2>] Not tainted EFLAGS: 00010202 EIP is at ide_pci_register_host_proc+0x32/0x50 eax: 6f6d656d ebx: c7cdd400 ecx: c89d1958 edx: 6f6d656d esi: c5313e3a edi: c89cea58 ebp: c5313e20 esp: c5313e20 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 7749, threadinfo=c5312000 task=c07f4660) Stack: c5313e4c c89d1374 c89d1958 00000001 c89cea58 c5313e3a 00010001 00000001 0000000b c89cf920 c5313e9c c5313e84 c0416c25 c7cdd400 c89cea58 00000001 c5313e74 00000000 00000001 011b6fb3 0000ffff 00000000 c89cfb00 c89cfa40 Call Trace: [<c89d1374>] +0x374/0x3b0 [siimage] [<c89d1958>] +0x0/0x14 [siimage] [<c89cea58>] +0x8/0xf0 [siimage] [<c89cf920>] +0x0/0xa8 [siimage] [<c0416c25>] do_ide_setup_pci_device+0xb5/0x170 [<c89cea58>] +0x8/0xf0 [siimage] [<c89cfb00>] +0x0/0xe0 [siimage] [<c89cfa40>] driver+0x0/0xc0 [siimage] [<c0416d0a>] ide_setup_pci_device+0x2a/0x90 [<c89cf920>] +0x0/0xa8 [siimage] [<c89cfb00>] +0x0/0xe0 [siimage] [<c89ce8a5>] siimage_init_one+0x45/0xb0 [siimage] [<c89cf920>] +0x0/0xa8 [siimage] [<c02fc49d>] pci_device_probe+0x5d/0x70 [<c89cf9e0>] siimage_pci_tbl+0x0/0x60 [siimage] [<c89cfa68>] driver+0x28/0xc0 [siimage] [<c03dc3d3>] bus_match+0x43/0x80 [<c89cfa68>] driver+0x28/0xc0 [siimage] [<c03dc4ff>] driver_attach+0x5f/0x80 [<c89cfa68>] driver+0x28/0xc0 [siimage] [<c89cfa9c>] driver+0x5c/0xc0 [siimage] [<c03dc859>] bus_add_driver+0xe9/0xf0 [<c89cfa68>] driver+0x28/0xc0 [siimage] [<c89cfa40>] driver+0x0/0xc0 [siimage] [<c89cfb00>] +0x0/0xe0 [siimage] [<c03dcd31>] driver_register+0x91/0xa0 [<c89cfa68>] driver+0x28/0xc0 [siimage] [<c02fc5dd>] pci_register_driver+0x4d/0x60 [<c89cfa68>] driver+0x28/0xc0 [siimage] [<c0416eb8>] ide_pci_register_driver+0x48/0x70 [<c89cfa40>] driver+0x0/0xc0 [siimage] [<c89cfb00>] +0x0/0xe0 [siimage] [<c89ce922>] siimage_ide_init+0x12/0x20 [siimage] [<c89cfa40>] driver+0x0/0xc0 [siimage] [<c0144647>] sys_init_module+0x207/0x370 [<c89cfb00>] +0x0/0xe0 [siimage] [<c016e375>] sys_read+0x45/0x60 [<c010a457>] syscall_call+0x7/0xb Code: 8b 40 10 85 c0 75 f7 89 4a 10 5d c3 89 f6 89 0d 58 7c 66 c0 Hi Dave, is this problem still present in recent 2.6 kernels? I've not tried it in a while, and I'm not sure where I put the card. I'll dig it out and try it sometime. I'm closing this bug. Please reopen it if you are able to reproduce it with a recent 2.6 kernel. |