On Thu, 30 Oct 2008, Paul Medynski wrote:

> Hi Lou,
>
> I'm experiencing the same problem that you outlined in the email I found
> below. I noticed that we have the same ADMtek ethernet card. Here's my
> dmesg showing the ide and eth0 initialization intermingled:
>
> [ 3.492758] Uniform Multi-Platform E-IDE driver
> [ 3.492837] ide: Assuming 33MHz system bus speed for PIO modes; override
> with idebus=xx
> [ 3.517233] VP_IDE: IDE controller (0x1106:0x0571 rev 0x10) at PCI slot
> 0000:00:07.1
> [ 3.517352] VP_IDE: not 100% native mode: will probe irqs later
> [ 3.517454] VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on
> pci0000:00:07.1
> [ 3.517540] ide0: BM-DMA at 0xd000-0xd007
> [ 3.517608] ide1: BM-DMA at 0xd008-0xd00f
> [ 3.517669] Probing IDE interface ide0...
> [ 3.685949] usbcore: registered new interface driver usbfs
> [ 3.686096] usbcore: registered new interface driver hub
> [ 3.686250] usbcore: registered new device driver usb
> [ 3.707389] USB Universal Host Controller Interface driver v3.0
> [ 3.892502] Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
> [ 3.972184] hda: WDC WD2500JB-00REA0, ATA DISK drive
> [ 4.032028] Marking TSC unstable due to: TSC halts in idle.
> [ 4.255177] hdb: WDC WD3200AAJB-00WGA0, ATA DISK drive
> [ 4.310938] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
> [ 4.311035] hda: UDMA/66 mode selected
> [ 4.311167] hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
> [ 4.311255] hdb: UDMA/66 mode selected
> [ 4.311394] Probing IDE interface ide1...
> [ 4.724888] hdc: WDC WD2500JB-00REA0, ATA DISK drive
> [ 5.004149] hdd: WDC WD2000JB-00GVC0, ATA DISK drive
> [ 5.060137] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
> [ 5.060225] hdc: UDMA/66 mode selected
> [ 5.060356] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
> [ 5.061590] hdd: UDMA/66 mode selected
> [ 5.062912] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> [ 5.063060] ide1 at 0x170-0x177,0x376 on irq 15
> [ 5.064740] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
> [ 5.064811] PCI: setting IRQ 12 as level-triggered
> [ 5.064821] ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 12
> (level, low) -> IRQ 12
> [ 5.064992] uhci_hcd 0000:00:07.2: UHCI Host Controller
> [ 5.065287] uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus
> number 1
> [ 5.065396] uhci_hcd 0000:00:07.2: irq 12, io base 0x0000d400
> [ 5.065708] usb usb1: configuration #1 chosen from 1 choice
> [ 5.065859] hub 1-0:1.0: USB hub found
> [ 5.065936] hub 1-0:1.0: 2 ports detected
> [ 5.168344] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
> [ 5.168423] usb usb1: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [ 5.168496] usb usb1: Product: UHCI Host Controller
> [ 5.168557] usb usb1: Manufacturer: Linux 2.6.26-1-686 uhci_hcd
> [ 5.168620] usb usb1: SerialNumber: 0000:00:07.2
> [ 5.168876] ACPI: PCI Interrupt 0000:00:07.3[D] -> Link [LNKD] -> GSI 12
> (level, low) -> IRQ 12
> [ 5.169052] uhci_hcd 0000:00:07.3: UHCI Host Controller
> [ 5.169178] uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus
> number 2
> [ 5.169286] uhci_hcd 0000:00:07.3: irq 12, io base 0x0000d800
> [ 5.169594] usb usb2: configuration #1 chosen from 1 choice
> [ 5.169735] hub 2-0:1.0: USB hub found
> [ 5.169812] hub 2-0:1.0: 2 ports detected
> [ 5.176864] No dock devices found.
> [ 5.215964] SCSI subsystem initialized
> [ 5.261595] libata version 3.00 loaded.
> [ 5.272409] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
> [ 5.272492] usb usb2: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [ 5.272566] usb usb2: Product: UHCI Host Controller
> [ 5.272625] usb usb2: Manufacturer: Linux 2.6.26-1-686 uhci_hcd
> [ 5.272688] usb usb2: SerialNumber: 0000:00:07.3
> [ 5.274802] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
> [ 5.274879] PCI: setting IRQ 11 as level-triggered
> [ 5.274889] ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 11
> (level, low) -> IRQ 11
> [ 5.275399] tulip0: MII transceiver #1 config 1000 status 7869
> advertising 05e1.
> [ 5.279455] eth0: ADMtek Comet rev 17 at Port 0xe800, 00:04:5a:7c:4e:05,
> IRQ 11.
> [ 5.383698] hda: max request size: 512KiB
> [ 5.399933] hda: 488397168 sectors (250059 MB) w/8192KiB Cache,
> CHS=30401/255/63
> [ 5.400233] hda: cache flushes supported
> [ 5.400416] hda: hda1 hda2 hda3
> [ 5.409031] hdb: max request size: 512KiB
> [ 5.427436] hdb: 625142448 sectors (320072 MB) w/8192KiB Cache,
> CHS=38913/255/63
> [ 5.431315] hdb: cache flushes supported
> [ 5.431490] hdb: hdb1
> [ 5.445991] hdc: max request size: 512KiB
> [ 5.461190] hdc: 488397168 sectors (250059 MB) w/8192KiB Cache,
> CHS=30401/255/63
> [ 5.461458] hdc: cache flushes supported
> [ 5.461649] hdc: hdc1 hdc2 hdc3
> [ 5.470501] hdd: max request size: 512KiB
> [ 5.488660] hdd: 390721968 sectors (200049 MB) w/8192KiB Cache,
> CHS=24321/255/63
> [ 5.490855] hdd: cache flushes supported
> [ 5.491035] hdd: hdd1
>
>
> My hda partition logs aren't split up. eth0 seems to be initialized by then.
> But I'm seeing the following messages from the tulip driver when streaming
> movies off of this box over samba to my Xbox running XBMC:
>
> [92728.562789] 0000:00:0a.0: tulip_stop_rxtx() failed (CSR5 0xfc06c012 CSR6
> 0xff970111)
> [92733.805722] 0000:00:0a.0: tulip_stop_rxtx() failed (CSR5 0xfc664010 CSR6
> 0xff972113)
>
> I'm guessing the initialization weirdness has something to do with our
> ethernet cards and the tulip kernel module. I don't know very much about the
> kernel and stuff, so let me know if you'd like me to run some commands and
> get some more info for you. Here's my kernel version:
>
> paul@media:~$ uname -a
> Linux media 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686 GNU/Linux
>
> I too wasn't having any problems until a reboot yesterday when I accidently
> stepped on the power bar while installing a new KVM switch. Oopsie. Two
> reboots later and I'm still getting the tulip errors. I'll reboot again a
> few times to see what dmesg shows.
>
> -Paul
>


Hi Paul,
I continue to have this problem also. My previous problem update from
6 Apr 2008 turns out not to be quite correct. The problem does NOT
actually correspond 100% to the splitting of the log line about
> hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >.


I am running pure stable etch pre-built kernels, currently version:
Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-23).
The problem does seem somehow initialization-related. Some system boots
result in this problem appearing after a time, but sometimes the system
will boot up OK, and never show the problem. I ran OK for about 45 days
before I finally rebooted after upgrading to this new kernel version.

I am sorry to see you also have the problem in 2.6.26-1-686. It does
sound like the same thing as my problem. I tried many many combinations
of kernel boot params without helping the problem. I have not been able
to spend much time troubleshooting this -- I just resign myself to
the extra reboots until I get lucky with a boot that initializes things
properly, and then try to keep running as long as I can without booting.

I have not opened a proper bug report with the upstream kernel maintainers.
Sorry I'm not very much help. If I can supply any other info about
my situation, I would be happy to help.

I added 419950@bugs.debian.org to the Cc: list, to keep all the info
in one place for others who might have the problem, or even for some
genius who might fix the problem.



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org