Re: troubles with r8169
Francois Romieu пишет: >> I need help from developers, may be, because I have some troubles with >> r8169 card. >> > > Which kernel do you use ? > This problem appeared with the kernel 2.6.19 - 2.6.22 (since I use this laptop). Now I use the last kernel 2.6.22.2 with Gentoo patches. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: troubles with r8169
Vadim Dyadkin <[EMAIL PROTECTED]> : [...] > I need help from developers, may be, because I have some troubles with > r8169 card. Which kernel do you use ? -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: troubles with r8169
Alistair John Strachan пишет: >> Thank for your answer. This problem never shows up if I use only nvidia >> driver (the work without network), or if I use only r8169 (without >> x.org). If I use both of them I have the hang. Usually the hang appears >> if OpenGL is used or network rate is maximal. I tested this regimes many >> times before. > > If you haven't already, I'd drop [EMAIL PROTECTED] an email to see if they > have any insight. I haven't done it yet. I'm going to do it. > Not that this can't be a kernel bug, just that it's a bit > difficult for kernel developers to debug when you're using a driver for which > we don't have the sources. > > As for changing the IRQ assignments, I don't have any immediate suggestions. > I > notice that this laptop has a dual core processor, so I'm guessing disabling > APIC isn't an option. Have you tried that anyway, just to see if the IRQ > assignment differs? If I've correctly understood your suggestion I should load kernel with 'noapic' option. In that case the situation even worse: ** CPU0 CPU1 0: 106543 11922XT-PIC-XTtimer 1: 53 8XT-PIC-XTi8042 2: 0 0XT-PIC-XTcascade 5: 0 0XT-PIC-XTsdhci:slot0 7: 14250 126092XT-PIC-XTehci_hcd:usb2 8: 2 0XT-PIC-XTrtc 9: 1168190XT-PIC-XTacpi 10:338181XT-PIC-XTHDA Intel 11: 7167 1052XT-PIC-XTohci_hcd:usb1, yenta, eth0, nvidia 12:123 9XT-PIC-XTi8042 14: 19 32XT-PIC-XTide0 15: 10936 1112XT-PIC-XTide1 NMI: 0 0 LOC: 11921 106401 ERR: 41370 MIS: 0 *** Now, pcmcia and usb 1.1 share the same IRQ. Plus, dmesg says: * irq 7: nobody cared (try booting with the "irqpoll" option) [] __report_bad_irq+0x24/0x80 [] note_interrupt+0x226/0x260 [] usb_hcd_irq+0x2b/0x60 [usbcore] [] handle_IRQ_event+0x25/0x50 [] handle_level_irq+0x93/0x100 [] do_IRQ+0x3b/0x70 [] sys_sigreturn+0xce/0xe0 [] common_interrupt+0x23/0x28 === handlers: [] (usb_hcd_irq+0x0/0x60 [usbcore]) Disabling IRQ #7 ** Vadim - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: troubles with r8169
On Sunday 12 August 2007 21:06:43 Vadim Dyadkin wrote: > Robert Hancock пишет: > > This could well be a problem with the nvidia driver as it shares the > > same IRQ. The first step would be to see if the problem still shows up > > without the nvidia binary module loaded. > > Thank for your answer. This problem never shows up if I use only nvidia > driver (the work without network), or if I use only r8169 (without > x.org). If I use both of them I have the hang. Usually the hang appears > if OpenGL is used or network rate is maximal. I tested this regimes many > times before. If you haven't already, I'd drop [EMAIL PROTECTED] an email to see if they have any insight. Not that this can't be a kernel bug, just that it's a bit difficult for kernel developers to debug when you're using a driver for which we don't have the sources. As for changing the IRQ assignments, I don't have any immediate suggestions. I notice that this laptop has a dual core processor, so I'm guessing disabling APIC isn't an option. Have you tried that anyway, just to see if the IRQ assignment differs? -- Cheers, Alistair. 137/1 Warrender Park Road, Edinburgh, UK. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: troubles with r8169
Robert Hancock пишет: > This could well be a problem with the nvidia driver as it shares the > same IRQ. The first step would be to see if the problem still shows up > without the nvidia binary module loaded. Thank for your answer. This problem never shows up if I use only nvidia driver (the work without network), or if I use only r8169 (without x.org). If I use both of them I have the hang. Usually the hang appears if OpenGL is used or network rate is maximal. I tested this regimes many times before. Vadim - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: troubles with r8169
Vadim Dyadkin wrote: Hi! I need help from developers, may be, because I have some troubles with r8169 card. I use laptop ASUS a6tc. The network card in this laptop is r8169. Video is GeForce Go 7300. When I load linux (I use linux almost always), the network and video cards take the same IRQ every time. # cat /proc/interrupts CPU0 CPU1 0:3530622 177152XT-PIC-XTtimer 1: 1910 9 IO-APIC-edge i8042 8: 1 1 IO-APIC-edge rtc 9: 41627115 IO-APIC-fasteoi acpi 12:122 10 IO-APIC-edge i8042 14: 38 12 IO-APIC-edge ide0 15: 53721 8 IO-APIC-edge ide1 16: 0 0 IO-APIC-fasteoi yenta 17: 34909 1 IO-APIC-fasteoi ohci_hcd:usb1 18: 13 1 IO-APIC-fasteoi ehci_hcd:usb2 19: 332826 1 IO-APIC-fasteoi nvidia, eth0 20: 0 0 IO-APIC-fasteoi sdhci:slot0 21: 26981 1 IO-APIC-fasteoi HDA Intel NMI: 0 0 LOC: 1771523530365 ERR: 1 MIS: 0 ** You can see, now it's 19, sometimes it's 17 or 21, but every time it is the same. Often, the computer hangs, only the reboot can help. In /var/log/messages: Jul 14 19:15:29 satah NETDEV WATCHDOG: eth0: transmit timed out Jul 14 19:15:32 satah NVRM: Xid (0002:00): 16, Head Count 00cfda2c Jul 14 19:15:40 satah NVRM: Xid (0002:00): 16, Head Count 00cfda2d Jul 14 19:15:48 satah NVRM: Xid (0002:00): 16, Head Count 00cfda2e Jul 14 19:15:56 satah NVRM: Xid (0002:00): 16, Head Count 00cfda2f Jul 14 19:16:04 satah NVRM: Xid (0002:00): 16, Head Count 00cfda30 Jul 14 19:16:12 satah NVRM: Xid (0002:00): 16, Head Count 00cfda31 Jul 14 19:16:17 satah NETDEV WATCHDOG: eth0: transmit timed out Jul 14 19:16:20 satah NVRM: Xid (0002:00): 16, Head Count 00cfda32 Jul 14 19:16:35 satah NETDEV WATCHDOG: eth0: transmit timed out Jul 14 19:16:53 satah NETDEV WATCHDOG: eth0: transmit timed out There's no such problem in windows. Could you help me with it? This could well be a problem with the nvidia driver as it shares the same IRQ. The first step would be to see if the problem still shows up without the nvidia binary module loaded. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
