You are not logged in.
- Topics: Active | Unanswered
#1 2010-02-23 18:08:29
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi. I have problems with latest kernels. After suspend (to ram), wired connection doesn't work (eth0 doesn't connect). It occurs with those kernels in ArchLinux 32 bits and with 2.6.31 in Ubuntu Karmik.
The card is:
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller (rev 10)and the sys log is:
Feb 23 18:50:01 eduardo crond[3083]: FILE /var/spool/cron/eduardo USER eduardo PID 4029 /usr/share/prey/prey.sh > /dev/null
Feb 23 18:50:01 eduardo crond[3083]: FILE /var/spool/cron/root USER root PID 4030 /usr/share/prey/prey.sh > /dev/null
Feb 23 18:50:57 eduardo NetworkManager: <info> Sleeping...
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): now unmanaged
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): device state change: 8 -> 1 (reason 37)
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): deactivating device (reason: 37).
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Withdrawing address record for 192.168.1.11 on eth0.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.11.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo dhcpcd: received SIGTERM, stopping
Feb 23 18:50:57 eduardo dhcpcd: eth0: removing interface
Feb 23 18:50:57 eduardo kernel: sky2 eth0: disabling interface
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 3516
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): cleaning up...
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): taking down device.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Withdrawing address record for fe80::2a0:d1ff:fe2d:57b5 on eth0.
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth1): now unmanaged
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth1): device state change: 2 -> 1 (reason 37)
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): carrier now OFF (device state 1)
Feb 23 18:50:57 eduardo NetworkManager: <WARN> nm_dhcp_manager_handle_event(): Received DHCP event from unexpected PID 3516 (expected 0)
Feb 23 18:50:57 eduardo kernel: [drm] Num pipes: 1
Feb 23 18:51:07 eduardo kernel: PM: Syncing filesystems ... done.
Feb 23 18:51:07 eduardo kernel: PM: Preparing system for mem sleep
Feb 23 18:51:07 eduardo kernel: Freezing user space processes ... (elapsed 0.00 seconds) done.
Feb 23 18:51:07 eduardo kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Feb 23 18:51:07 eduardo kernel: PM: Entering mem sleep
Feb 23 18:51:07 eduardo kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 23 18:51:07 eduardo kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 23 18:51:07 eduardo kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: PCI INT D disabled
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: eth1: Going into suspend...
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ata_piix 0000:00:1f.2: PCI INT B disabled
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: PCI INT B disabled
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: PCI INT D disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: PCI INT C disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: PCI INT B disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ACPI: Preparing to enter system sleep state S3
Feb 23 18:51:07 eduardo kernel: Disabling non-boot CPUs ...
Feb 23 18:51:07 eduardo kernel: Back to C!
Feb 23 18:51:07 eduardo kernel: Force enabled HPET at resume
Feb 23 18:51:07 eduardo kernel: ACPI: Waking up from system sleep state S3
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:01.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x2010b, writing 0x2010a)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x8ff18c01)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0xbff0bc00)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0xb0a0)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x20200)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810004)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
Feb 23 18:51:07 eduardo kernel: pci 0000:00:1e.0: restoring config space at offset 0x6 (was 0x20060600, writing 0x200a0600)
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: restoring config space at offset 0x1 (was 0x2900007, writing 0x2900003)
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x6 (was 0x0, writing 0xc0000000)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x5 (was 0x1, writing 0xc001)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x4 (was 0x8, writing 0x90000008)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x4)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x6 (was 0x1, writing 0xa001)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xbc000004)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x4)
Feb 23 18:51:07 eduardo acpid: client 3452[0:0] has disconnected
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0xf (was 0x18030100, writing 0x1803010b)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0x4 (was 0x0, writing 0xb000b000)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0x3 (was 0x0, writing 0x8000)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900006)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xf (was 0x34001ff, writing 0x5c001ff)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xe (was 0x0, writing 0x64fc)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xd (was 0x0, writing 0x6400)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xc (was 0x0, writing 0x60fc)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xb (was 0x0, writing 0x6000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xa (was 0x0, writing 0xb7fff000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x9 (was 0x0, writing 0xb4000000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x8 (was 0x0, writing 0x83fff000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x7 (was 0x0, writing 0x80000000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x6 (was 0x40000000, writing 0xb00a0706)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x4 (was 0x0, writing 0xb0001000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x3 (was 0x820000, writing 0x82a808)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100007)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0xf (was 0x4020300, writing 0x402030b)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x5 (was 0x0, writing 0xb0004000)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x4 (was 0x0, writing 0xb0000000)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x3 (was 0x800000, writing 0x808004)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0xf (was 0x40704ff, writing 0x4070405)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0x4 (was 0x0, writing 0xb0008000)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0x3 (was 0x800000, writing 0x808004)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0xf (was 0x40701ff, writing 0x407010b)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x6 (was 0x0, writing 0xb000a200)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x5 (was 0x0, writing 0xb000a100)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x4 (was 0x0, writing 0xb000a000)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x3 (was 0x800000, writing 0x808004)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: PCI INT A -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb2: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: PCI INT B -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb3: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: PCI INT C -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb4: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: PCI INT D -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb5: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: PCI INT A -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: pci 0000:00:1e.0: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: PCI INT B -> Link[LNKE] -> GSI 5 (level, low) -> IRQ 5
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: ata_piix 0000:00:1f.2: PCI INT B -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: ignoring stuck error report bit
Feb 23 18:51:07 eduardo kernel: eth1: Coming out of suspend...
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: ipw2200: Radio Frequency Kill Switch is On:
Feb 23 18:51:07 eduardo kernel: Kill switch must be turned off for wireless networking to work.
Feb 23 18:51:07 eduardo kernel: ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata2.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata1.00: configured for UDMA/100
Feb 23 18:51:07 eduardo kernel: ata2.00: configured for UDMA/33
Feb 23 18:51:07 eduardo kernel: firewire_core: skipped bus generations, destroying all nodes
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: PCI INT D -> Link[LNKE] -> GSI 5 (level, low) -> IRQ 5
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: sd 0:0:0:0: [sda] Starting disk
Feb 23 18:51:07 eduardo kernel: firewire_core: rediscovered device fw0
Feb 23 18:51:07 eduardo kernel: usb 2-1: reset low speed USB device using uhci_hcd and address 2
Feb 23 18:51:07 eduardo kernel: PM: Finishing wakeup.
Feb 23 18:51:07 eduardo kernel: Restarting tasks ... done.
Feb 23 18:51:07 eduardo logger: ACPI action undefined: BAT1
Feb 23 18:51:08 eduardo acpid: client connected from 3452[0:0]
Feb 23 18:51:08 eduardo acpid: 1 client rule loaded
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo NetworkManager: <info> Waking up...
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): now managed
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): bringing up device.
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): preparing device.
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): deactivating device (reason: 2).
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): now managed
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): device state change: 1 -> 2 (reason 2)
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): bringing up device.
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): deactivating device (reason: 2).
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 eth0: enabling interface
Feb 23 18:51:08 eduardo kernel: ADDRCONF(NETDEV_UP): eth0: link is not readyDue to this problem affects ubuntu and arch I suppose that there is a problem in kernel (or in my laptop, but with 2.6.30 works fine). I would report this to kernel bugs but I don't know how. Thanks
Offline
#2 2010-02-23 19:19:28
- eldragon
- Member
- From: Buenos Aires
- Registered: 2008-11-18
- Posts: 1,029
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
create an account at bugzilla.kernel.org
search for similar bugs related to your hardware. and if you find a similar bug report. post what youve posted here. otherwise, create a new bug report, with what you posted here, since its related to your marvel ethernet card, post the bug under drivers/networking.
since you got a working kernel and a non working one, be prepared to be asked to bisect this. if you got the time. start bisecting...
in order to bisect. you will need to know how to build a custom kernel, and use git to search the commit that introduced the bug between 2.6.30 and 2.6.31
Offline
#3 2010-02-23 22:44:20
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Thanks. I'm going to report this bug.
Offline
#4 2010-02-26 01:16:17
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Here is the bug report:
http://bugzilla.kernel.org/show_bug.cgi?id=15388
Offline
#6 2010-02-26 15:36:52
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
I think so. All older kernels I have tried (my first linux was ubuntu festy) have worked fine. I found this page, http://www.kernel.org/pub/software/scm/ … isect.html, I'm going to try solve the problem.
Thanks.
Last edited by aberkoke (2010-02-26 15:48:15)
Offline
#7 2010-02-26 20:21:22
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi. I have a problem. bisected kernel between 2.6.30 and 2.6.31 boot sucesfully, but It doesn't restart after suspend. Display is black, and fans go to 100%. After reboot computer, I have seen dmesg command and :
------------[ cut here ]------------
WARNING: at arch/x86/kernel/apic/apic.c:249 ret_point+0x1bbb5/0x2f79f9()
Hardware name: Satellite M40
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.30-ARCH-05856-g925d74a #1
Call Trace:
[<c104275a>] ? ret_point+0x41684/0x2f79f9
[<c101cc8b>] ? ret_point+0x1bbb5/0x2f79f9
[<c10427c0>] ? ret_point+0x416ea/0x2f79f9
[<c101cc8b>] ? ret_point+0x1bbb5/0x2f79f9
[<c10139b1>] ? ret_point+0x128db/0x2f79f9
[<c1012313>] ? ret_point+0x1123d/0x2f79f9
[<c10e23f3>] ? ret_point+0xe131d/0x2f79f9
[<c1013805>] ? ret_point+0x1272f/0x2f79f9
[<c12f0314>] ? ret_point+0x2ef23e/0x2f79f9
[<c12ee422>] ? ret_point+0x2ed34c/0x2f79f9
[<c1418d66>] ? __smp_locks_end+0x843e/0x34c98
[<c1418f65>] ? __smp_locks_end+0x863d/0x34c98
[<c1095dd0>] ? ret_point+0x94cfa/0x2f79f9
[<c1411a18>] ? __smp_locks_end+0x10f0/0x34c98
[<c14114dc>] ? __smp_locks_end+0xbb4/0x34c98
---[ end trace a7919e7f17c0a725 ]---What do in this case??
Also this:
Pid: 25, comm: udevd Tainted: G W 2.6.30-ARCH-05856-g925d74a #1
Call Trace:
[<c11891f1>] ? ret_point+0x18811b/0x2f79f9
[<c111acac>] ? ret_point+0x119bd6/0x2f79f9
[<c111e0b0>] ? ret_point+0x11cfda/0x2f79f9
[<c111b8ed>] ? ret_point+0x11a817/0x2f79f9
[<c111e163>] ? ret_point+0x11d08d/0x2f79f9
[<c1003c73>] ? ret_point+0x2b9d/0x2f79f9Last edited by aberkoke (2010-02-26 20:25:40)
Offline
#8 2010-02-27 02:35:54
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi. I have found that error is between 2.6.31-rc7 and 2.6.31-rc8, without above problem. I am 81 pending revisions
Offline
#9 2010-02-27 15:12:33
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hello. I made git bisect and have come to this commit as responsible for the problem. Do you think that is well done? Or am I wrong in some way?
eduardo@eduardo-laptop:~/linux-git$ git bisect bad
523d2f6982136d332c9b7dd00e9e16da1091f060 is first bad commit
commit 523d2f6982136d332c9b7dd00e9e16da1091f060
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Wed Jul 1 21:26:43 2009 +0200
mac80211: fix todo lock
The key todo lock can be taken from different locks
that require it to be _bh to avoid lock inversion
due to (soft)irqs.
This should fix the two problems reported by Bob and
Gabor:
http://mid.gmane.org/20090619113049.GB18956@hash.localnet
http://mid.gmane.org/4A3FA376.8020307@openwrt.org
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: Bob Copeland <me@bobcopeland.com>
Cc: Gabor Juhos <juhosg@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
:040000 040000 2803e553716a71541dd9be2cf1beba8d78b176bc 1bd14aad91d5ee67620e0bea5f70cea8a86bc653 M netand
eduardo@eduardo-laptop:~/linux-git$ git bisect log
git bisect start
# bad: [326ba5010a5429a5a528b268b36a5900d4ab0eba] Linux 2.6.31-rc8
git bisect bad 326ba5010a5429a5a528b268b36a5900d4ab0eba
# good: [422bef879e84104fee6dc68ded0e371dbeb5f88e] Linux 2.6.31-rc7
git bisect good 422bef879e84104fee6dc68ded0e371dbeb5f88e
# bad: [9f459fadbb38abe68aa342f533ca17d8d90d6f2e] Merge branch 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
git bisect bad 9f459fadbb38abe68aa342f533ca17d8d90d6f2e
# bad: [1cac6ec9b7f9c48a26309380656f399a0587b860] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6
git bisect bad 1cac6ec9b7f9c48a26309380656f399a0587b860
# bad: [d2f3ad4cedc00c8ee848e7abe9b2bbc93b9a8c2d] pxaficp-ir: remove incorrect net_device_ops
git bisect bad d2f3ad4cedc00c8ee848e7abe9b2bbc93b9a8c2d
# bad: [649bf17829d087f83754e2a8161e094a167ce3d3] Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6
git bisect bad 649bf17829d087f83754e2a8161e094a167ce3d3
# bad: [e7a5965a81a29a13cd4994fa23a6a7a1488bcdb6] yellowfin: Fix buffer underrun after dev_alloc_skb() failure
git bisect bad e7a5965a81a29a13cd4994fa23a6a7a1488bcdb6
# bad: [518ff04fd84290a7ad9042e8a46d78d29cb443d3] orinoco: correct key bounds check in orinoco_hw_get_tkip_iv
git bisect bad 518ff04fd84290a7ad9042e8a46d78d29cb443d3
# bad: [523d2f6982136d332c9b7dd00e9e16da1091f060] mac80211: fix todo lock
git bisect bad 523d2f6982136d332c9b7dd00e9e16da1091f060Offline
#10 2010-03-01 02:00:57
- eldragon
- Member
- From: Buenos Aires
- Registered: 2008-11-18
- Posts: 1,029
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
you got to a commit that touches ethernet code. you most likely did it right. but the kernel guys will know better
Offline
#12 2010-03-01 23:37:19
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi. Thanks for the response. I don't know why, but my last post was wrong. I tested that bisect and 2.6.31-rc7 didn't work (it should work). I think something was wrong in the process. Today I have repeated kernel bisect and i have found another commit. I think, this is the good because i have tested that with 2.6.31-rc7 it works (and it should work).
eduardo@eduardo-laptop:~/linux-git$ git bisect bad
c82f63e411f1b58427c103bd95af2863b1c96dd1 is first bad commit
commit c82f63e411f1b58427c103bd95af2863b1c96dd1
Author: Alek Du <alek.du@intel.com>
Date: Sat Aug 8 08:46:19 2009 +0800
PCI: check saved state before restore
Without the check, the config space may be filled with zeros. Though
the driver should try to avoid call restoring before saving, but the
pci layer also should check this.
Also removes the existing check in pci_restore_standard_config, since
it's superfluous with the new check in restore_state.
Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Alek Du <alek.du@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
:040000 040000 b363995a162a427fdf907059d38882036d68109d
6aca235abde6bf4545e479a87b7f7171e934a988 M driversand
git bisect start
# bad: [326ba5010a5429a5a528b268b36a5900d4ab0eba] Linux 2.6.31-rc8
git bisect bad 326ba5010a5429a5a528b268b36a5900d4ab0eba
# good: [422bef879e84104fee6dc68ded0e371dbeb5f88e] Linux 2.6.31-rc7
git bisect good 422bef879e84104fee6dc68ded0e371dbeb5f88e
# bad: [9f459fadbb38abe68aa342f533ca17d8d90d6f2e] Merge branch 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
git bisect bad 9f459fadbb38abe68aa342f533ca17d8d90d6f2e
# bad: [1cac6ec9b7f9c48a26309380656f399a0587b860] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6
git bisect bad 1cac6ec9b7f9c48a26309380656f399a0587b860
# good: [d2f3ad4cedc00c8ee848e7abe9b2bbc93b9a8c2d] pxaficp-ir: remove incorrect net_device_ops
git bisect good d2f3ad4cedc00c8ee848e7abe9b2bbc93b9a8c2d
# good: [e3054ea7f79db2c694a4f74febead2d4f8de5a98] Merge git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6
git bisect good e3054ea7f79db2c694a4f74febead2d4f8de5a98
# bad: [637952ca689013339b977558061fa4ca8e07e1c1] [S390] set preferred console based on conmode
git bisect bad 637952ca689013339b977558061fa4ca8e07e1c1
# bad: [3edf2fb9d80a46d6c32ba12547a42419845b4b76] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6
git bisect bad 3edf2fb9d80a46d6c32ba12547a42419845b4b76
# bad: [c82f63e411f1b58427c103bd95af2863b1c96dd1] PCI: check saved state before restore
git bisect bad c82f63e411f1b58427c103bd95af2863b1c96dd1I have posted this at kernel's bugzilla, http://bugzilla.kernel.org/show_bug.cgi?id=15388#c8. I hope my effort has not been in vain. Thanks!!
Last edited by aberkoke (2010-03-02 00:41:13)
Offline
#13 2010-03-02 16:53:02
- pyther
- Member
- Registered: 2008-01-21
- Posts: 1,395
- Website
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hopefully someone should be able to help you. By doing the git bisect you did most of the dirty work and tracked down which commit broke it. So hopefully it'll be fairly easy for a dev to fix the problem.
Offline
#14 2010-05-04 20:35:26
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi everyone. Today someone has responded me, today!!. He say me that
Did you try to revert the commit you found via 'git bisect' from 2.6.33.3, for
example?I undestand that i have to compile a 2.6.33.3 kernel without bad commit, but how??
I have downloaded kernel tree again, and I think I have to set kernel versión to 2.6.33.3 and after, eject the commit (how??).
Thanks
Eduardo
Offline
#15 2010-05-04 23:22:41
- eldragon
- Member
- From: Buenos Aires
- Registered: 2008-11-18
- Posts: 1,029
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
aberkoke wrote:
Hi everyone. Today someone has responded me, today!!. He say me that
Did you try to revert the commit you found via 'git bisect' from 2.6.33.3, for example?I undestand that i have to compile a 2.6.33.3 kernel without bad commit, but how??
I have downloaded kernel tree again, and I think I have to set kernel versión to 2.6.33.3 and after, eject the commit (how??).
Thanks
Eduardo
im almost sure git has a command to revert a commit from a tree..
man git 
Offline
#16 2010-05-05 15:08:33
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi. I have found git-revert. I have searched about its usage, and I think I have problems.
[arch@chakra-laptop linux-2.6.33.y]$ git revert c82f63e411f1b58427c103bd95af2863b1c96dd1
warning: too many files (created: 3331 deleted: 937), skipping inexact rename detection
Automatic revert failed. After resolving the conflicts,
mark the corrected paths with 'git add <paths>' or 'git rm <paths>'
and commit the result.I have removed the patches manually and in this moment I am compiling the kernel. I hope all go fine.
Greetings
Offline
#17 2010-05-09 20:15:50
- aberkoke
- Member
- From: Murcia - España
- Registered: 2010-01-13
- Posts: 25
Re: Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)
Hi. Finally, i had to remove patch manually (only was 2 lines of code) and i could see that without this lines, problem was solved. So, this files are the responsable of the problem. I have submited this information to kernel bugzilla.
Greetings
Offline