[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#487670: Nvidia GeForce 8200 chipset not recognised



On Tuesday 24 June 2008, Rob Quin wrote:
> I downloaded 	debian-LennyBeta2-amd64-netinst.iso
> When I booted with that it hung for several minutes before the familiar
> ncurses menus appeared. Then it did the same as before.
>
> Here are the hardware-summary and syslog from that install attempt.

Thanks. The syslog clearly shows your NIC and IDE controller being
recognized. It also clearly shows a problem with your SATA controller.
This looks to be a kernel problem. Here's the relevant part:

kernel: ahci 0000:00:09.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl IDE mode
kernel: ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio 
kernel: PCI: Setting latency timer of device 0000:00:09.0 to 64
kernel: scsi0 : ahci
kernel: scsi1 : ahci
kernel: scsi2 : ahci
kernel: scsi3 : ahci
kernel: scsi4 : ahci
kernel: scsi5 : ahci
kernel: ata1: SATA max UDMA/133 abar m8192@0xfe02a000 port 0xfe02a100 irq 1275
kernel: ata2: SATA max UDMA/133 abar m8192@0xfe02a000 port 0xfe02a180 irq 1275
kernel: ata3: SATA max UDMA/133 abar m8192@0xfe02a000 port 0xfe02a200 irq 1275
kernel: ata4: SATA max UDMA/133 abar m8192@0xfe02a000 port 0xfe02a280 irq 1275
kernel: ata5: SATA max UDMA/133 abar m8192@0xfe02a000 port 0xfe02a300 irq 1275
kernel: ata6: SATA max UDMA/133 abar m8192@0xfe02a000 port 0xfe02a380 irq 1275

Good, the controller is recognized.

kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ata1.00: qc timeout (cmd 0xec)
kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata1: failed to recover some devices, retrying in 5 secs
kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ata1.00: qc timeout (cmd 0xec)
kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata1: failed to recover some devices, retrying in 5 secs
kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ata1.00: qc timeout (cmd 0xec)
kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata1: failed to recover some devices, retrying in 5 secs
kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

These lines seem to indicate that a disk (or DVD) is connected to link 1,
but actually talking to it fails.

kernel: ata2: SATA link down (SStatus 0 SControl 300)
kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ata3.00: qc timeout (cmd 0xec)
kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata3: failed to recover some devices, retrying in 5 secs
kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ata3.00: qc timeout (cmd 0xec)
kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata3: failed to recover some devices, retrying in 5 secs
kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ata3.00: qc timeout (cmd 0xec)
kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata3: failed to recover some devices, retrying in 5 secs
kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Same for link 3 as for link 1.

kernel: ata4: SATA link down (SStatus 0 SControl 300)
kernel: ata5: SATA link down (SStatus 0 SControl 300)
kernel: ata6: SATA link down (SStatus 0 SControl 300)


Googling leads me to this thread on the kernel mailing list:
http://lkml.org/lkml/2008/2/14/467

There are two people there reporting the same problem, though possibly
with other chipsets. In both cases a BIOS upgrade solved the problem.

However, as you can see the kernel developer would be interested to
find out the actual cause of the problem and there are two kernel boot
options that could be tried first.

Can you try booting the installer [1] with (separately):
- pci=nomsi
- irqpoll

And see if that makes a difference? Please check the syslog or output of
dmesg for changes in the above.

Also, please check if a BIOS update is available but, unless you're in a
hurry, don't apply it yet as this may still be of interest to the upstream
kernel people, although it's also possible that the problem has been solved
in the mean time in 2.6.25.

Cheers,
FJP

[1] http://www.debian.org/releases/testing/i386/ch05s01.html.en#boot-screen



Reply to: