Bug#270376: Appears fixed in 2.6.14
I just installed 2.6.14 (from backports) and it appears that all the problems are fixed. I would close this bug, but I don't know how to do it properly so the version tracking and such works. -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: Status Update?
I was just wondering what the status of this bug is? Do the current kernels in Sid fix this? Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312279: Error Message on 2.4.27 boot
(Sorry this took so long for me to get. The person I was hoping was going to be able to get it for me was on vacation for a while and then I forgot about it. In any case below is what I get when trying to boot 2.4.27.) hda3: bad access: block=4, count=4 end_request: I/O error, dev 03:03 (hda), sector 4 hda3: bad access: block=6, count=2 end_request: I/O error, dev 03:03 (hda), sector 6 hda3: bad access: block=8, count=8 end_request: I/O error, dev 03:03 (hda), sector 8 hda3: bad access: block=10, count=6 end_request: I/O error, dev 03:03 (hda), sector 10 hda3: bad access: block=12, count=4 end_request: I/O error, dev 03:03 (hda), sector 12 hda3: bad access: block=14, count=2 end_request: I/O error, dev 03:03 (hda), sector 14 hda3: bad access: block=16, count=8 end_request: I/O error, dev 03:03 (hda), sector 16 hda3: bad access: block=18, count=6 end_request: I/O error, dev 03:03 (hda), sector 18 hda3: bad access: block=20, count=4 end_request: I/O error, dev 03:03 (hda), sector 20 hda3: bad access: block=22, count=2 end_request: I/O error, dev 03:03 (hda), sector 22 pivot_root: No such file or directory /sbin/init: 432: cannot open dev/console: No such file Kernel panic: Attempted to kill init! When I scroll back up I see more of the same messages as far as I can scroll. (As I've said before I will probably be using 2.6.8 most of the time, but I would like a second kernel around in case something gets screwed up with 2.6.8.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312279: kernel-image-2.4.27-2-586tsc: System fails to boot with 2.4.27 installed
(Sorry for the duplicate. Forgot to CC the bug before) $ lspci -v :00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 01) Flags: bus master, medium devsel, latency 64 :00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02) Flags: bus master, medium devsel, latency 0 :00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 64 I/O ports at ffa0 [size=16] :00:0d.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (prog-if 00 [VGA]) Flags: medium devsel, IRQ 11 Memory at ff00 (32-bit, non-prefetchable) [size=8M] I'll get you the exact error message hopefully later today. In general I'm planning on using 2.6.8, but I was hoping to get 2.4.27 working so in the event I have some problem when I do an upgrade on 2.6.8 I have some other kernel around to fall back on. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Horms [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 07, 2005 03:09 > To: Jefferson Cowart; [EMAIL PROTECTED] > Subject: Re: Bug#312279: kernel-image-2.4.27-2-586tsc: System > fails to boot with 2.4.27 installed > > On Mon, Jun 06, 2005 at 06:01:47PM -0700, Jefferson Cowart wrote: > > Package: kernel-image-2.4.27-2-586tsc > > Version: 2.4.27-10 > > Severity: important > > > > I installed kernel-image-2.4.27-2-586tsc on my system. > After rebooting > > the system failed to boot with a kernel panic and something about > > killing init. (Sorry I don't remember the exact error, but it is the > > kind of error I get when it fails to mount my drive.) > Directly before > > this I got a bunch of errors about my ide devices. The system does > > however boot 2.6.8 fine so I don't think it is a hardware problem. > > > > I'm sure you will need more info to diagnose this, so please let > > me know what you need. > > Hi, this is a bit vauge, can you provide more information on > what errors you are seeing, and what devices you have > (lspci -v). Also, I would say that if 2.6.8 is working, use that. > > -- > Horms > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312279: Error Message
I am not physically in front of the system at the moment and I just discovered the person I was going to ask to record the exact error message and pass it on to me is away for a few days. As such it might take me a little longer to get you the exact error sorry. Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312279: kernel-image-2.4.27-2-586tsc: System fails to boot with 2.4.27 installed
Package: kernel-image-2.4.27-2-586tsc Version: 2.4.27-10 Severity: important I installed kernel-image-2.4.27-2-586tsc on my system. After rebooting the system failed to boot with a kernel panic and something about killing init. (Sorry I don't remember the exact error, but it is the kind of error I get when it fails to mount my drive.) Directly before this I got a bunch of errors about my ide devices. The system does however boot 2.6.8 fine so I don't think it is a hardware problem. I'm sure you will need more info to diagnose this, so please let me know what you need. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.4.27-2-586tsc depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii modutils 2.4.26-1.2 Linux module utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
I thought the freeze at this point was on ABI changes? I would assume this doesn't change the ABI and thus wouldn't be as big of a problem. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Horms [mailto:[EMAIL PROTECTED] > Sent: Monday, April 11, 2005 23:25 > To: Jefferson Cowart; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Fri, Apr 08, 2005 at 08:02:08PM -0700, Jefferson Cowart wrote: > > Looks like the patch fixed the problem. What are the > chances of getting this > > included in sarge? > > The kernel for sarge is frozen. This makes adding any changes > unlikely. However, buy adding them to the kernel in SVN they > will be considered for inclusion in sarge, and (likely) failing that, > inclusion in any updates to sarge. > > -- > Horms > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
I don't seem to be having any problems with this latest kernel. However as I haven't been able to reproduce that error on the first patched 2.6.11, I can't really be sure. At this point it looks like all these bugs are fixed, so the bug can probably be closed as soon as these are integrated into the Debian kernel packages. Thanks to everyone for their help. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Sunday, April 10, 2005 05:48 > To: Jefferson Cowart > Cc: 'Daniel Ritz'; 'Dominik Brodowski'; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Sun, 10 Apr 2005, Jefferson Cowart wrote: > > > I can send them to you, but as I mentioned in my last > e-mail I can't figure > > out how to reproduce the problem. Additionally it looks > like Daniel Ritz > > already has a patch that he thinks fixes it. Do you still > want me to try to > > get that data or just work with the new patch? > > yes please try the kernel-image with both fixes: > http://charm.itp.tuwien.ac.at/~mattems/kernel-image-2.6.11-ti- > 3c574-fix_01_i386.deb > > thanks for your feedback > maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
I can send them to you, but as I mentioned in my last e-mail I can't figure out how to reproduce the problem. Additionally it looks like Daniel Ritz already has a patch that he thinks fixes it. Do you still want me to try to get that data or just work with the new patch? Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 09, 2005 07:34 > To: Jefferson Cowart > Cc: 'Daniel Ritz'; 'Dominik Brodowski'; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Fri, 08 Apr 2005, Jefferson Cowart wrote: > > > Looks like I may have spoken a bit too soon. The problem is > partially fixed, > > but I'm still having a few problems. After the system was > up I ran cardctl > > eject 0 to stop and let me remove my Ethernet card and I > got the follow > > error: > > > > eth0: no IPv6 routers present > > irq 10: nobody cared! > > [] __report_bad_irq+0x31/0x77 > > can you send the hexdump of the cardbus controller > before and after the cardctl command on this patched 2.6.11 kernel: > /proc/bus/pci/00/07.0 and /proc/bus/pci/00/07.1 > > thanks for your feedback. > maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Looks like I may have spoken a bit too soon. The problem is partially fixed, but I'm still having a few problems. After the system was up I ran cardctl eject 0 to stop and let me remove my Ethernet card and I got the follow error: eth0: no IPv6 routers present irq 10: nobody cared! [] __report_bad_irq+0x31/0x77 [] note_interrupt+0x4c/0x71 [] __do_IRQ+0x93/0xbd [] do_IRQ+0x19/0x24 [] common_interrupt+0x1a/0x20 [] __do_softirq+0x2c/0x7d [] do_softirq+0x22/0x26 [] do_IRQ+0x1e/0x24 [] common_interrupt+0x1a/0x20 [] load_elf_binary+0x236/0xaba [] autoremove_wake_function+0x0/0x3a [] kernel_read+0x38/0x41 [] search_binary_handler+0x71/0x19c [] load_script+0x1c8/0x1d8 [] load_elf_binary+0xa25/0xaba [] __alloc_pages+0x32c/0x338 [] copy_from_user+0x3a/0x60 [] copy_strings+0x178/0x1b7 [] search_binary_handler+0x71/0x19c [] do_execve+0x164/0x1f9 [] sys_execve+0x2b/0x59 [] syscall_call+0x7/0xb handlers: [] (yenta_interrupt+0x0/0x27 [yenta_socket]) [] (yenta_interrupt+0x0/0x27 [yenta_socket]) [] (el3_interrupt+0x0/0x1db [3c574_cs]) Disabling IRQ #10 Subsequent attempts to replicate the error have been unsuccessful, so it doesn't appear to be a big problem. On a related note now my second NIC works so it looks like they were indeed the same bug (or at least a related one). ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Friday, April 08, 2005 12:07 > To: Jefferson Cowart > Cc: 'Daniel Ritz'; 'Dominik Brodowski'; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Thu, 07 Apr 2005, Jefferson Cowart wrote: > > > Thanks for the response. > > > > maximilian attems - Let me know when the kernel is built > and I'll go ahead > > and try that. > > the patch easy applied to 2.6.11 (1 line offset, easy to fix). > you'll find this kernel with the posted patch at > -> http://charm.itp.tuwien.ac.at/~mattems/ > > thanks for your feedback (dmesg appreciated). > a++ maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Looks like the patch fixed the problem. What are the chances of getting this included in sarge? Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Friday, April 08, 2005 12:07 > To: Jefferson Cowart > Cc: 'Daniel Ritz'; 'Dominik Brodowski'; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Thu, 07 Apr 2005, Jefferson Cowart wrote: > > > Thanks for the response. > > > > maximilian attems - Let me know when the kernel is built > and I'll go ahead > > and try that. > > the patch easy applied to 2.6.11 (1 line offset, easy to fix). > you'll find this kernel with the posted patch at > -> http://charm.itp.tuwien.ac.at/~mattems/ > > thanks for your feedback (dmesg appreciated). > a++ maks $ uname -a Linux jcc02003-hawk 2.6.11-ti-fix #1 Fri Apr 8 19:47:44 CEST 2005 i586 GNU/Linux $ dmesg Linux version 2.6.11-ti-fix ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-8)) #1 Fri Apr 8 19:47:44 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000ed800 - 0010 (reserved) BIOS-e820: 0010 - 07d0 (usable) BIOS-e820: fffed800 - 0001 (reserved) 125MB LOWMEM available. On node 0 totalpages: 32000 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 27904 pages, LIFO batch:6 HighMem zone: 0 pages, LIFO batch:1 DMI not present. ACPI: Unable to locate RSDP Allocating PCI resources starting at 07d0 (gap: 07d0:f82ed800) Built 1 zonelists Kernel command line: root=/dev/hda2 ro __iounmap: bad address c00fffd9 No local APIC present or hardware disabled mapped APIC to d000 (010fb000) Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Detected 267.347 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 119284k/128000k available (1387k kernel code, 8168k reserved, 757k data, 220k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 524.28 BogoMIPS (lpj=262144) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: 00808131 01818131 CPU: After vendor identify, caps: 00808131 01818131 Working around Cyrix MediaGX virtual DMA bugs. CPU: After all inits, caps: 00808131 00818131 0001 CPU: Cyrix MediaGXtm MMXtm Enhanced stepping 02 Checking 'hlt' instruction... OK. Checking for popad bug... OK. checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 4352k freed NET: Registered protocol family 16 EISA bus registered PCI: PCI BIOS revision 2.10 entry at 0xfd9b4, last bus=0 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050211 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled PnPBIOS: Scanning system for PnP BIOS support... PnPBIOS: Found PnP BIOS installation structure at 0xc00f7920 PnPBIOS: PnP BIOS version 1.0, entry 0xf:0xaa24, dseg 0x400 PnPBIOS: 17 nodes reported by PnP BIOS; 17 recorded by driver PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) pnp: 00:00: ioport range 0x398-0x399 has been reserved pnp: 00:0a: ioport range 0x480-0x48f has been reserved pnp: 00:0b: ioport range 0x4d0-0x4d1 has been reserved VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 Initializing Cryptographic API PCI: Fixup for MediaGX/Geode Slave Disconnect Boundary (0x41=0x14) isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize input: AT Translated Set 2 keyboard on isa0060/serio0 EISA: Probing bus 0 at eisa0 Cannot allocate resource for EISA slot 3 Cannot allocate resource for EISA slot 4 Cannot allocate resource for EISA slot 5 EISA: Detected 0 cards. NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Thanks for the response. maximilian attems - Let me know when the kernel is built and I'll go ahead and try that. Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 07, 2005 16:26 > To: Daniel Ritz > Cc: Jefferson Cowart; 'Dominik Brodowski'; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Thu, 07 Apr 2005, Daniel Ritz wrote: > > > On Tuesday 05 April 2005 08:56, Jefferson Cowart wrote: > > > Sorry for the delay in sending this. I ended up getting > back later than > > > expected. In any case the hexdumps are below. Please let > me know if you need > > > anything else. > > > > also sorry for the delay :) > > > > > > > > Under 2.6.5-bk1 > > > === > > > (/proc/bus/pci/00/07.0) > > > 000 104c ac17 0007 0210 0002 0607 a820 0082 > > > 010 8000 000c 00a0 0200 0100 b004 1000 > > > 020 f000 103f 1040 f000 107f 4400 > > > 030 44fc 4800 48fc 010a 0540 > > > 040 0001 > > > 050 > > > * > > > 080 7020 2800 3822 0ba4 > > > >^ > > there you go. the intrtie bit is set. this means that both functions > > use INTA to signal the interrupts. but the BIOS is broken > and assigned > > a different irq to function 1 compared to function 0. > > so the reason it broke when the irq-routing patch was merged is that > > irqs are actually probed to see if they work or if the routing needs > > some tuning... > > > > the attached patch should fix it. it's untested 'cos i don't have a > > laptop with TI bridge anymore...but it's simple > > > > rgds > > -daniel > > thanks a lot for your explenations and the provided patch. > i need some sleep right now, but i'll build a kernel > tommorow for jefferson - bug reporter - to test. > > a++ maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Sorry for the delay in sending this. I ended up getting back later than expected. In any case the hexdumps are below. Please let me know if you need anything else. Under 2.6.5-bk1 === (/proc/bus/pci/00/07.0) 000 104c ac17 0007 0210 0002 0607 a820 0082 010 8000 000c 00a0 0200 0100 b004 1000 020 f000 103f 1040 f000 107f 4400 030 44fc 4800 48fc 010a 0540 040 0001 050 * 080 7020 2800 3822 0ba4 090 83c0 6062 0a0 0001 7e21 0080 0809 001f 0b0 * 100 (/proc/bus/pci/00/07.1) 000 104c ac17 0007 0210 0002 0607 a820 0082 010 8000 000d 00a0 0200 0500 b008 1080 020 f000 10bf 10c0 f000 10ff 4c00 030 4cfc 5400 54fc 010b 05c0 040 0001 050 * 080 5020 2844 3822 0ba4 090 82c0 6062 0a0 0001 7e21 0080 0809 001f 0b0 * 100 Under 2.6.12-rc1-mm3 (/proc/bus/pci/00/07.0) 000 104c ac17 0007 0210 0002 0607 a820 0082 010 8000 000c 00a0 0200 0100 b004 0800 020 f000 083f 0840 f000 087f 2000 030 20fc 2400 24fc 010a 0540 040 0001 050 * 080 7020 2800 3822 0ba4 090 83c0 6062 0a0 0001 7e21 0080 0809 001e 0b0 * 100 (/proc/bus/pci/00/07.1) 000 104c ac17 0007 0210 0002 0607 a820 0082 010 8000 000d 00a0 0200 0500 b008 0880 020 f000 08bf 08c0 f000 08ff 2800 030 28fc 2c00 2cfc 010b 0540 040 0001 050 * 080 7020 2844 3822 0ba4 090 82c0 6062 0a0 0001 7e21 0080 0809 001e 0b0 * 100 Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Daniel Ritz [mailto:[EMAIL PROTECTED] > Sent: Friday, April 01, 2005 15:42 > To: Dominik Brodowski; maximilian attems > Cc: Jefferson Cowart; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > On Friday 01 April 2005 19:52, Dominik Brodowski wrote: > > Seems to be the IRQ storm issue again... Daniel, IIRC you > worked on that > > issue before: do you have an idea on how to write a proper > patch for this > > issue? > > > > nope it looks more like something else. looking at the debian > bug report: > - lspci shows function 0 to be on irq 10 while function 1 is on irq 11 > - the irq storm happens on irq 10 when probing the interrupt > of function 1 > > so it looks more like the bios is lying about the actual assignment. > > or it could be really an interrupt routing problem. > > could i get a hexdump of the both functions of the cardbus controller? > (/proc/bus/pci/00/07.0 and /proc/bus/pci/00/07.1 > > thanks, rgds > -daniel > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Daniel Ritz wrote: On Friday 01 April 2005 19:52, Dominik Brodowski wrote: Seems to be the IRQ storm issue again... Daniel, IIRC you worked on that issue before: do you have an idea on how to write a proper patch for this issue? nope it looks more like something else. looking at the debian bug report: - lspci shows function 0 to be on irq 10 while function 1 is on irq 11 - the irq storm happens on irq 10 when probing the interrupt of function 1 so it looks more like the bios is lying about the actual assignment. or it could be really an interrupt routing problem. could i get a hexdump of the both functions of the cardbus controller? (/proc/bus/pci/00/07.0 and /proc/bus/pci/00/07.1 First of all how do I generate those (is hexdump the name of a program)? Secondly, what kernel should I do that under? Third, I will be away from this computer until Sunday afternoon/evening. I'll get you the results then. thanks, rgds -daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
maximilian attems wrote: cc'ing the pcmcia maintainer and the author of the patch for interrupt routing for TI bridges. concerning a bug report about non working irq routing since 2.6.6-rc1 up until 2.6.12-rc1-mm3 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=270376 (lspci, dmesg) hope you can help to resolve that issue. i volountary test build kernels for bug reporter with proposed patches. On Thu, 31 Mar 2005, Jefferson Cowart wrote: (For reference my primary card is a 3C574. My secondary is a 3C589.) .. (I put that card into a Windows XP laptop and it worked fine there so the card itself is fine.) Now I'm trying to see if I have these same problems on 2.5.5 First, Booting with the secondary card plugged in had the same failure as above. Next booting with the primary plugged in. It worked (as expected). Then I was able to pull and re-insert the card without problems. However pulling the primary and inserting the secondary killed the network (as expected). Now I'm going back to 2.4.27 to figure out if my secondary card will work there. It failed. I got a hard lock when I inserted the card. (Reboot button needed.) I'm 99.9% certain that my testing of 2.6.6-2.6.10 was using my primary nic, but I'm booting 2.6.10 now to be sure. (I know the kernels I tested for you yesterday used my primary nic.) As expected no networking. It looks like we may have 2 different bugs here: one in the yenta_socket driver starting somewhere after 2.6.5-bk1 and before 2.6.6-rc1 and one in the 3c589 driver in I don't know what versions. (I seem to remember that 2.4.18 worked, but I'm not sure. If you want me to try that nic under and older kernel let me know, however I think fixing the first bug is more important.) If you need any further log info let me know. indeed there is a change in the irq handling in the yenta code. it went in after 2.6.5-bk2 and is in 2.6.6-rc1. in the context could you send please the ouput of a pre 2.6.6-rc1 kernel on your box: cat /proc/interrupts I will be away from that computer until late in the day Sunday. Once I'm back I'll let you know that. regarding your other pcmcia i don't know if it's supported. thanks for your feedback. Looking up in this bug report it looks like the 3c589 had been previously working on my machine. (The message I sent on Feb 6 2005). However as I said let's deal with that one later. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
> -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > On Wed, 30 Mar 2005, Jefferson Cowart wrote: > > I'm downloading and testing all 3 now. > > > > The short version is none of the 3 worked (same problem as > what I've already > > seen on 2.6.6-10. Further details, dmsg, etc. below. > > ok bad new, but better to check. thanks for feedback. > anyway we are getting closer inbetween of 2.6.5 and 2.6.6-rc1 > there were 2 bk snapshot. i build the bk1 for your testing pleasure, > you'll find it at the same place: > http://charm.itp.tuwien.ac.at/~mattems/ > > it contains the pcmcia patches for 2.6.6, so most probably it > will fail. > please confirm before i hand pick different patches out of it. It actually worked, with a few caveats. (For reference my primary card is a 3C574. My secondary is a 3C589.) I tried swapping to my other nic, by first ejecting the current one and then putting the second one in. When I did that I got an error: Mar 31 01:24:21 jcc02003-hawk kernel: irq 10: nobody cared! Mar 31 01:24:21 jcc02003-hawk kernel: Call Trace: Mar 31 01:24:21 jcc02003-hawk kernel: [__report_bad_irq+49/115] __report_bad_ir q+0x31/0x73 Mar 31 01:24:21 jcc02003-hawk kernel: [note_interrupt+76/111] note_interrupt+0x 4c/0x6f Mar 31 01:24:21 jcc02003-hawk kernel: [do_IRQ+146/249] do_IRQ+0x92/0xf9 Mar 31 01:24:21 jcc02003-hawk kernel: [common_interrupt+24/32] common_interrupt +0x18/0x20 Mar 31 01:24:21 jcc02003-hawk kernel: [__do_softirq+44/115] __do_softirq+0x2c/0 x73 Mar 31 01:24:21 jcc02003-hawk kernel: [do_softirq+34/38] do_softirq+0x22/0x26 Mar 31 01:24:21 jcc02003-hawk kernel: [do_IRQ+229/249] do_IRQ+0xe5/0xf9 Mar 31 01:24:21 jcc02003-hawk kernel: [common_interrupt+24/32] common_interrupt +0x18/0x20 Mar 31 01:24:21 jcc02003-hawk kernel: [default_idle+0/38] default_idle+0x0/0x26 Mar 31 01:24:21 jcc02003-hawk kernel: [default_idle+35/38] default_idle+0x23/0x 26 Mar 31 01:24:21 jcc02003-hawk kernel: [cpu_idle+29/50] cpu_idle+0x1d/0x32 Mar 31 01:24:21 jcc02003-hawk kernel: [start_kernel+389/393] start_kernel+0x185 /0x189 Mar 31 01:24:21 jcc02003-hawk kernel: Mar 31 01:24:21 jcc02003-hawk kernel: handlers: Mar 31 01:24:21 jcc02003-hawk kernel: [__crc_give_up_console+4053730/4336289] (y enta_interrupt+0x0/0x27 [yenta_socket]) Mar 31 01:24:21 jcc02003-hawk kernel: Disabling IRQ #10 After this I pulled that card back out (running cardctl eject told me there was no card) and put the first one back in. The LED indicating that that socket had a card in it came up and linux found it. However at that point I was not able to get my network back. (Rebooting fixed it) Next I tried simply removing the original card and reinserting it without first putting in the other card. That worked fine. Next I tried booting with my secondary card plugged in. That didn't work. The error I got was: Mar 31 01:41:22 jcc02003-hawk kernel: eth0: 3Com 3c589, io 0x310, irq 11, hw_addr 00:60:97:90:E6:51 Mar 31 01:41:22 jcc02003-hawk kernel: 8K FIFO split 5:3 Rx:Tx, auto xcvr Mar 31 01:41:25 jcc02003-hawk kernel: eth0: flipped to 10baseT Mar 31 01:41:26 jcc02003-hawk kernel: irq 10: nobody cared! Mar 31 01:41:26 jcc02003-hawk kernel: Call Trace: Mar 31 01:41:26 jcc02003-hawk kernel: [__report_bad_irq+49/115] __report_bad_irq+0x31/0x73 Mar 31 01:41:26 jcc02003-hawk kernel: [note_interrupt+76/111] note_interrupt+0x4c/0x6f Mar 31 01:41:26 jcc02003-hawk kernel: [do_IRQ+146/249] do_IRQ+0x92/0xf9 Mar 31 01:41:26 jcc02003-hawk kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Mar 31 01:41:26 jcc02003-hawk kernel: [__do_softirq+44/115] __do_softirq+0x2c/0x73 Mar 31 01:41:26 jcc02003-hawk kernel: [do_softirq+34/38] do_softirq+0x22/0x26 Mar 31 01:41:26 jcc02003-hawk kernel: [do_IRQ+229/249] do_IRQ+0xe5/0xf9 Mar 31 01:41:26 jcc02003-hawk kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Mar 31 01:41:26 jcc02003-hawk kernel: Mar 31 01:41:26 jcc02003-hawk kernel: handlers: Mar 31 01:41:26 jcc02003-hawk kernel: [__crc_give_up_console+4053730/4336289] (yenta_interrupt+0x0/0x27 [yenta_socket]) Mar 31 01:41:26 jcc02003-hawk kernel: Disabling IRQ #10 Mar 31 01:41:26 jcc02003-hawk kernel: NET: Registered protocol family 17 Mar 31 01:41:26 jcc02003-hawk kernel: eth0: interrupt(s) dropped! (I put that card into a Windows XP laptop and it worked fine there so the card itself is fine.) Now I'm trying to see if I have these same problems on 2.5.5 First, Booting with the secondary card plugged in had the same failure as above. Next booting with the primary plugged in. It worked (as expected). Then I was able to pull and re-insert the card without problems. However pulling the primary and inserting the secondary killed the network (as expected). Now I'm going back to 2.4.27 to figure out if my secondary card will work there. It failed. I got a hard lo
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
I'm downloading and testing all 3 now. The short version is none of the 3 worked (same problem as what I've already seen on 2.6.6-10. Further details, dmsg, etc. below. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 29, 2005 06:49 > To: Jefferson Cowart; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > [ sorry for late reply, but was quit busy ] > > in the meantime there is a kernel-source-2.6.11 in unstable, > built against it an 386 kernel with debian config to see > if that helps? #dmsg mapped APIC to d000 (010fb000) Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Detected 267.277 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 119284k/128000k available (1387k kernel code, 8168k reserved, 757k data, 220k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 524.28 BogoMIPS (lpj=262144) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: 00808131 01818131 CPU: After vendor identify, caps: 00808131 01818131 Working around Cyrix MediaGX virtual DMA bugs. CPU: After all inits, caps: 00808131 00818131 0001 CPU: Cyrix MediaGXtm MMXtm Enhanced stepping 02 Checking 'hlt' instruction... OK. Checking for popad bug... OK. checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 4352k freed NET: Registered protocol family 16 EISA bus registered PCI: PCI BIOS revision 2.10 entry at 0xfd9b4, last bus=0 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050211 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled PnPBIOS: Scanning system for PnP BIOS support... PnPBIOS: Found PnP BIOS installation structure at 0xc00f7920 PnPBIOS: PnP BIOS version 1.0, entry 0xf:0xaa24, dseg 0x400 PnPBIOS: 17 nodes reported by PnP BIOS; 17 recorded by driver PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) pnp: 00:00: ioport range 0x398-0x399 has been reserved pnp: 00:0a: ioport range 0x480-0x48f has been reserved pnp: 00:0b: ioport range 0x4d0-0x4d1 has been reserved VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 Initializing Cryptographic API PCI: Fixup for MediaGX/Geode Slave Disconnect Boundary (0x41=0x14) isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize input: AT Translated Set 2 keyboard on isa0060/serio0 EISA: Probing bus 0 at eisa0 Cannot allocate resource for EISA slot 3 Cannot allocate resource for EISA slot 4 Cannot allocate resource for EISA slot 5 EISA: Detected 0 cards. NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) NET: Registered protocol family 8 NET: Registered protocol family 20 RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 4352KiB [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/ -\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\ |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/ -\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\ |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/ -\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\ |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/ -\|/-\done. VFS: Mounted root (cramfs filesystem) readonly. Freeing unused kernel memory: 220k freed NET: Registered protocol family 1 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Cyrix 5520: IDE controller at PCI slot :00:12.0 ide0: BM-DMA at 0
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Any update on this? Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 06, 2005 07:04 > To: Jefferson Cowart > Subject: Re: PCMCIA Nic stops working after upgrading to 2.6.6/7/8 > > On Sun, 06 Feb 2005, Jefferson Cowart wrote: > > > One other thing I forgot to mention. That last output I > sent you was after > > the box had been up for about 12:30. If you need output of > one of the > > commands immediately after boot (I would think it would be > the same, but I > > don't know too much about the kernel.) let me know. > > no looks fine, thanks a lot for the info. :) > > will build you a test kernel 2.6.6-rc1 tommorrow. > will be the first out of a test serie to narrow changes down. > (aka binary searching). > > nice sunday. > > -- > maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
The machine I'm running this on is an old Cyrix 233 (or maybe 266). As such I really don't want to compile my own kernel as in my experience that takes a few days. Any chance you could provide an appropriate kernel? ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Michele Baldessari [mailto:[EMAIL PROTECTED] > Sent: Saturday, February 12, 2005 01:07 > To: Jefferson Cowart; [EMAIL PROTECTED] > Subject: Re: Bug#270376: PCMCIA Nic stops working after > upgrading to 2.6.6/7/8 > > Could you try a pristine 2.6.11-rc3 and modprobe yenta_socket, with > "disable_clkrun=1"? > I had very similar issues (albeit my NIC _never_ > worked reliably before the mentioned release, so it might be very well > unrelated, but still worth a try) > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
MII interface. eth0: found link beat eth0: autonegotiation complete: 100baseT-FD selected ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 06, 2005 02:54 > To: Jefferson Cowart > Cc: [EMAIL PROTECTED] > Subject: Re: PCMCIA Nic stops working after upgrading to 2.6.6/7/8 > > On Sat, 05 Feb 2005, Jefferson Cowart wrote: > > > I've been using the stock Debian kernels so a .config from > those should > > work. The last kernel I built for my machine was 2 or 3 > years ago and > > somewhere in the 2.4.15-20 range I think. (I don't still > have it around.) > > ok so please sent me an lspci and lsmod output of a working kernel. > dmesg after boot would also be nice. > > thanks > > -- > maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: 2.6.10 Log
Here is the information that 2.6.10 put into the log file: 1 jcc02003-hawk kernel: Linux Kernel Card Services 1 jcc02003-hawk kernel: options: [pci] [cardbus] [pm] 1 jcc02003-hawk kernel: Yenta: CardBus bridge found at :00:07.0 [:] 1 jcc02003-hawk kernel: Yenta: Enabling burst memory read transactions 2 jcc02003-hawk kernel: Yenta: Using CSCINT to route CSC interrupts to PCI 2 jcc02003-hawk kernel: Yenta: Routing CardBus interrupts to PCI 1 jcc02003-hawk kernel: Yenta TI: socket :00:07.0, mfunc 0x0ba43822, devctl 0x62 1 jcc02003-hawk kernel: Yenta: ISA IRQ mask 0x0010, PCI irq 10 2 jcc02003-hawk kernel: Socket status: 3010 1 jcc02003-hawk kernel: Yenta: CardBus bridge found at :00:07.1 [:] 1 jcc02003-hawk kernel: Yenta TI: socket :00:07.1, mfunc 0x0ba43822, devctl 0x62 1 jcc02003-hawk kernel: irq 10: nobody cared! 1 jcc02003-hawk kernel: [__report_bad_irq+49/119] __report_bad_irq+0x31/0x77 1 jcc02003-hawk kernel: [note_interrupt+76/113] note_interrupt+0x4c/0x71 1 jcc02003-hawk kernel: [__do_IRQ+201/265] __do_IRQ+0xc9/0x109 1 jcc02003-hawk kernel: [do_IRQ+25/36] do_IRQ+0x19/0x24 2 jcc02003-hawk kernel: [common_interrupt+26/32] common_interrupt+0x1a/0x20 1 jcc02003-hawk kernel: [__do_softirq+44/121] __do_softirq+0x2c/0x79 1 jcc02003-hawk kernel: [do_softirq+34/38] do_softirq+0x22/0x26 1 jcc02003-hawk kernel: [irq_exit+41/52] irq_exit+0x29/0x34 1 jcc02003-hawk kernel: [do_IRQ+30/36] do_IRQ+0x1e/0x24 1 jcc02003-hawk kernel: [msleep+33/53] msleep+0x21/0x35 1 jcc02003-hawk kernel: [pg0+140417944/1070044160] yenta_probe_cb_irq+0xa7/0xe3 [yenta_socket] 1 jcc02003-hawk kernel: [pg0+140415792/1070044160] ti12xx_irqroute_func1+0x73/0x1ce [yenta_socket] 1 jcc02003-hawk kernel: [pg0+140416393/1070044160] ti12xx_override+0xfe/0x10c [yenta_socket] 1 jcc02003-hawk kernel: [pg0+140418614/1070044160] yenta_probe+0x125/0x1e5 [yenta_socket] 1 jcc02003-hawk kernel: [pci_device_probe_static+46/65] pci_device_probe_static+0x2e/0x41 1 jcc02003-hawk kernel: [__pci_device_probe+31/50] __pci_device_probe+0x1f/0x32 1 jcc02003-hawk kernel: [pci_device_probe+28/49] pci_device_probe+0x1c/0x31 1 jcc02003-hawk kernel: [driver_probe_device+54/84] driver_probe_device+0x36/0x54 1 jcc02003-hawk kernel: [driver_attach+57/110] driver_attach+0x39/0x6e 1 jcc02003-hawk kernel: [bus_add_driver+94/128] bus_add_driver+0x5e/0x80 1 jcc02003-hawk kernel: [driver_register+45/49] driver_register+0x2d/0x31 1 jcc02003-hawk kernel: [pci_register_driver+87/106] pci_register_driver+0x57/0x6a 1 jcc02003-hawk kernel: [pg0+139866122/1070044160] yenta_socket_init+0xa/0xc [yenta_socket] 1 jcc02003-hawk kernel: [sys_init_module+212/451] sys_init_module+0xd4/0x1c3 1 jcc02003-hawk kernel: [syscall_call+7/11] syscall_call+0x7/0xb 1 jcc02003-hawk kernel: handlers: 1 jcc02003-hawk kernel: [pg0+140412663/1070044160] (yenta_interrupt+0x0/0x27 [yenta_socket]) 1 jcc02003-hawk kernel: Disabling IRQ #10 1 jcc02003-hawk kernel: Yenta TI: socket :00:07.1 no PCI interrupts. Fish. Please report. 1 jcc02003-hawk kernel: Yenta: ISA IRQ mask 0x0010, PCI irq 0 Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
I'm still having the same problem. It says it brings the link up, but it doesn't seem to actually get any packets onto the wire. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Saturday, February 05, 2005 09:49 > To: Jefferson Cowart > Cc: [EMAIL PROTECTED] > Subject: Re: PCMCIA Nic stops working after upgrading to 2.6.6/7/8 > > could you please try latest 2.6.10 kernel-image from unstable. > they had various pcmcia fixes. > > thanks for your feedback. > > > -- > maks > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270376: Still a problem in 2.6.9
reassign 27037 kernel-image-2.6.8-1-386,kernel-image-2.6.9-1-386 Thanks I've upgraded to 2.6.9 to see if the problem still exists and it does. I am still unable to use my PCMCIA cards under any 2.6 kernel. Thanks Jefferson Cowart [EMAIL PROTECTED]
Bug#270376: Still not working
I've upgraded to the current version of this package (2.6.8-10) and I'm still having the same problem. However I've got some more information now that the newer kernel put into the logs. If you need more context on those log files let me know. Dec 8 11:41:00 JeffDebian2 kernel: Linux Kernel Card Services Dec 8 11:41:00 JeffDebian2 kernel: options: [pci] [cardbus] [pm] Dec 8 11:41:00 JeffDebian2 kernel: Yenta: CardBus bridge found at :00:07.0 [:] Dec 8 11:41:00 JeffDebian2 kernel: Yenta: Enabling burst memory read transactions Dec 8 11:41:00 JeffDebian2 kernel: Yenta: Using CSCINT to route CSC interrupts to PCI Dec 8 11:41:00 JeffDebian2 kernel: Yenta: Routing CardBus interrupts to PCI Dec 8 11:41:00 JeffDebian2 kernel: Yenta TI: socket :00:07.0, mfunc 0x0ba43822, devctl 0x62 Dec 8 11:41:00 JeffDebian2 kernel: Yenta: ISA IRQ mask 0x0010, PCI irq 10 Dec 8 11:41:00 JeffDebian2 kernel: Socket status: 3010 Dec 8 11:41:00 JeffDebian2 kernel: Yenta: CardBus bridge found at :00:07.1 [:] Dec 8 11:41:00 JeffDebian2 kernel: Yenta: Using CSCINT to route CSC interrupts to PCI Dec 8 11:41:00 JeffDebian2 kernel: Yenta: Routing CardBus interrupts to PCI Dec 8 11:41:00 JeffDebian2 kernel: Yenta TI: socket :00:07.1, mfunc 0x0ba43822, devctl 0x62 Dec 8 11:41:00 JeffDebian2 kernel: irq 10: nobody cared! Dec 8 11:41:00 JeffDebian2 kernel: [__report_bad_irq+49/115] __report_bad_irq+0x31/0x73 Dec 8 11:41:00 JeffDebian2 kernel: [note_interrupt+76/111] note_interrupt+0x4c/0x6f Dec 8 11:41:00 JeffDebian2 kernel: [do_IRQ+146/249] do_IRQ+0x92/0xf9 Dec 8 11:41:00 JeffDebian2 kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Dec 8 11:41:00 JeffDebian2 kernel: [__do_softirq+44/115] __do_softirq+0x2c/0x73 Dec 8 11:41:00 JeffDebian2 kernel: [do_softirq+34/38] do_softirq+0x22/0x26 Dec 8 11:41:00 JeffDebian2 kernel: [do_IRQ+229/249] do_IRQ+0xe5/0xf9 Dec 8 11:41:00 JeffDebian2 kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Dec 8 11:41:00 JeffDebian2 kernel: [schedule_timeout+0/156] schedule_timeout+0x0/0x9c Dec 8 11:41:00 JeffDebian2 kernel: [__crc_pci_find_class+2631854/4014989] yenta_probe_cb_irq+0xc1/0xfb [yenta_socket] Dec 8 11:41:00 JeffDebian2 kernel: [__crc_pci_find_class+2629814/4014989] ti12xx_irqroute_func1+0x73/0x1ce [yenta_socket] Dec 8 11:41:00 JeffDebian2 kernel: [printk+251/283] printk+0xfb/0x11b Dec 8 11:41:00 JeffDebian2 kernel: [__crc_pci_find_class+2630415/4014989] ti12xx_override+0xfe/0x10c [yenta_socket] Dec 8 11:41:00 JeffDebian2 kernel: [__crc_pci_find_class+2632522/4014989] yenta_probe+0x125/0x1e5 [yenta_socket] Dec 8 11:41:00 JeffDebian2 kernel: [pci_device_probe_static+46/65] pci_device_probe_static+0x2e/0x41 Dec 8 11:41:00 JeffDebian2 kernel: [__pci_device_probe+31/50] __pci_device_probe+0x1f/0x32 Dec 8 11:41:00 JeffDebian2 kernel: [pci_device_probe+28/49] pci_device_probe+0x1c/0x31 Dec 8 11:41:00 JeffDebian2 kernel: [bus_match+46/77] bus_match+0x2e/0x4d Dec 8 11:41:00 JeffDebian2 kernel: [driver_attach+57/110] driver_attach+0x39/0x6e Dec 8 11:41:00 JeffDebian2 kernel: [bus_add_driver+88/112] bus_add_driver+0x58/0x70 Dec 8 11:41:00 JeffDebian2 kernel: [driver_register+45/49] driver_register+0x2d/0x31 Dec 8 11:41:00 JeffDebian2 kernel: [pci_register_driver+78/107] pci_register_driver+0x4e/0x6b Dec 8 11:41:00 JeffDebian2 kernel: [__crc_pci_find_class+2530721/4014989] yenta_socket_init+0xa/0xc [yenta_socket] Dec 8 11:41:00 JeffDebian2 kernel: [sys_init_module+227/468] sys_init_module+0xe3/0x1d4 Dec 8 11:41:00 JeffDebian2 kernel: [syscall_call+7/11] syscall_call+0x7/0xb Dec 8 11:41:00 JeffDebian2 kernel: handlers: Dec 8 11:41:00 JeffDebian2 kernel: [__crc_pci_find_class+2626684/4014989] (yenta_interrupt+0x0/0x27 [yenta_socket]) Dec 8 11:41:00 JeffDebian2 kernel: Disabling IRQ #10 Dec 8 11:41:00 JeffDebian2 kernel: Yenta TI: socket :00:07.1 probing PCI interrupt failed, trying to fix Dec 8 11:41:00 JeffDebian2 kernel: Yenta TI: socket :00:07.1 no PCI interrupts. Fish. Please report. Dec 8 11:41:00 JeffDebian2 kernel: Yenta: ISA IRQ mask 0x0010, PCI irq 0 Dec 8 11:41:00 JeffDebian2 kernel: Socket status: 3006 ---- Thanks Jefferson Cowart [EMAIL PROTECTED]
Bug#270376: LSPCI Output
lspci -vvv under 2.6.5-1-386 :00:00.0 Host bridge: Cyrix Corporation PCI Master Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset+ 16bInt- PostWrite+ 16-bit legacy interface ports at 0001 :00:07.1 CardBus bridge: Texas Instruments PCI1220 (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 :00:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01) Subsystem: Unknown device 0001:0440 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset+ 16bInt- PostWrite+ 16-bit legacy interface ports at 0001 :00:07.1 CardBus bridge: Texas Instruments PCI1220 (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt- PostWrite+ 16-bit legacy interface ports at 0001 :00:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01) Subsystem: Unknown device 0001:0440 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR-
Bug#270376: kernel-image-2.6.8-1-386: PCMCIA Nic stops working after upgradin g to 2.6.6/7/8
Package: kernel-image-2.6.8-1-386 Version: 2.6.8-2 Severity: important I have a 3c589 NIC that does not work in any of 2.6.6/7/8. I have downloaded the most recent versions of these kernels from the debian archive and they don't work. Additionally I downloaded 2.6.0/2/3/4/5 from snapshot.debian.net to determine exactly when the breakage occured. Below are the results I found: Found kernel: /boot/vmlinuz-2.6.8-1-386 -- No DHCP Response Found kernel: /boot/vmlinuz-2.6.7-1-386 -- No DHCP Response Found kernel: /boot/vmlinuz-2.6.6-1-386 -- No DHCP Response Found kernel: /boot/vmlinuz-2.6.5-1-386 -- Works Found kernel: /boot/vmlinuz-2.6.4-1-386 -- Works Found kernel: /boot/vmlinuz-2.6.3-1-386 -- Kernel Panic/Oops Found kernel: /boot/vmlinuz-2.6.2-1-386 -- Kernel Panic/Oops Found kernel: /boot/vmlinuz-2.6.0-1-386 -- Kernel Panic Found kernel: /boot/vmlinuz-2.4.27-1-386 -- Works On the 2.6.6/7/8 kernels the network card appears to be brought up properly however DHCP requests and discovers are unanswered leaving the system in a state without a network. I've marked this severity important as the 3c589 is a rather common nic in my experiance. I have run lspci -vvv under the variout kernels and will send those along to this bugreport once I get a bug number. At present this bug makes the 2.6 kernel in sarge unusable for me as the network just doesn't work. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i586) Kernel: Linux 2.6.5-1-386 Locale: LANG=C, LC_CTYPE=C Versions of packages kernel-image-2.6.8-1-386 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.74 tools to create initrd image for p ii module-init-tools 3.1-pre5-6 tools for managing Linux kernel mo -- no debconf information
