Your message dated Wed, 30 Jan 2008 19:14:31 +0100 with message-id <20080130181431.GG12407@stro.at> and subject line [linux-image-2.6.18-3-686] sky2 crashes on boot or resume has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [linux-image-2.6.18-3-686] sky2 crashes on boot or resume
- From: Florian Lohoff <flo@rfc822.org>
- Date: Thu, 21 Dec 2006 20:09:27 +0100
- Message-id: <20061221190927.GA11951@paradigm.rfc822.org>
Package: linux-image-2.6.18-3-686 Version: 2.6.18-8 Severity: important Hi, on a Fujitsu Siemens LifeBook E8110 the sky2 ethernet driver crashes on bootup about every second try. This also happens on resume or rmmod/modprobe. Here is the output captured via a serial console on a bootup: sky2 eth1: enabling interface sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 0000:02:00.0: pci hw error (0xffff) sky2 0000:02:00.0: pci express error (0xffffffff) sky2 eth1: hw error interrupt status 0xffffffff sky2 eth1: ram data read parity error sky2 eth1: ram data write parity error sky2 eth1: MAC parity error sky2 eth1: RX parity error sky2 eth1: TCP segmentation error sky2 <NULL>: hw error interrupt status 0xffffff sky2 <NULL>: ram data read parity error sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: phy write timeout sky2 eth1: remote fault<1>BUG: unable to handle kernel NULL pointer dereference at virtual address 0000002c printing eip: e024f152 *pde = 00000000 Oops: 0000 [#1] SMP Modules linked in: button ac battery dm_snapshot dm_mirror dm_mod i915 drm sbp2 loop snd_hda_intel snd_hda_codec snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event pcmcia snd_seq ipw3945 joydev snd_timer snd_seq_device hci_usb sdhci tsdev ieee80211 snd ieee80211_crypt i2c_i801 sky2 intel_agp agpgart bluetooth rtc yenta_socket rsrc_nonstatic pcmcia_core serio_raw mmc_core i2c_core parport_pc parport firmware_class soundcore pcspkr eth1394 snd_page_alloc evdev psmouse irda crc_ccitt ext3 jbd mbcache ide_cd cdrom sd_mod generic ata_piix ehci_hcd libata ohci1394 ieee1394 uhci_hcd scsi_mod piix ide_core usbcore thermal processor fan CPU: 0 EIP: 0060:[<e024f152>] Not tainted VLI EFLAGS: 00010296 (2.6.18-3-686 #1) EIP is at sky2_phy_intr+0x10/0x19e [sky2] eax: de15adc0 ebx: 00000001 ecx: 00000046 edx: 00000001 esi: ffffffff edi: c13f5b80 ebp: 00000000 esp: c0313ee8 ds: 007b es: 007b ss: 0068 Process swapper (pid: 0, ti=c0312000 task=c02c76a0 task.ti=c0312000) Stack: de15adc0 e024eefd 00042010 ffffffff c13f5b80 fffef9d2 e024fe35 c0313f50 de977400 de15adc0 00000040 c0215ff3 ffffffff c0215e47 00000000 00000000 c0361b14 00000286 c01254c5 00000000 00000286 00000000 de977400 c13f5b80 Call Trace: [<e024eefd>] sky2_hw_error+0xe5/0x110 [sky2] [<e024fe35>] sky2_poll+0x181/0x8e8 [sky2] [<c0215ff3>] i8042_timer_func+0x0/0xb [<c0215e47>] i8042_interrupt+0x4c/0x1f8 [<c01254c5>] __mod_timer+0x99/0xa3 [<c022a4c3>] net_rx_action+0x92/0x17f [<c012186c>] __do_softirq+0x5a/0xbb [<c0121903>] do_softirq+0x36/0x3a [<c0103747>] apic_timer_interrupt+0x1f/0x24 [<e003f5ac>] acpi_processor_idle+0x1ec/0x380 [processor] [<c0101b52>] cpu_idle+0x9f/0xb9 [<c03186fd>] start_kernel+0x379/0x380 Code: 68 51 50 52 ff 73 04 68 81 22 25 e0 e8 32 e8 ec df 83 c4 14 59 5b 5b 5e 5f 5d c3 55 57 56 53 89 d3 83 ec 08 89 04 24 8b 6c 90 08 <8b> 45 2c a8 02 0f 84 7c 01 00 00 8d 85 d0 02 00 00 e8 11 1e 03 EIP: [<e024f152>] sky2_phy_intr+0x10/0x19e [sky2] SS:ESP 0068:c0313ee8 <0>Kernel panic - not syncing: Fatal exception in interrupt Here is an lspci -vvv output of the chip: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12) Subsystem: Fujitsu Limited. Unknown device 139a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 66 Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at 2000 [size=256] [virtual] Expansion ROM at 34000000 [disabled] [size=128K] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000fee00000 Data: 4042 Capabilities: [e0] Express Legacy Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0 Link: Latency L0s <256ns, L1 unlimited Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x1 Capabilities: [100] Advanced Error Reporting -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii initramfs-tools [linux-initra 0.85c tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: * linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: -- Florian Lohoff flo@rfc822.org +49-171-2280134 Heisenberg may have been here.Attachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 404107-done@bugs.debian.org
- Subject: [linux-image-2.6.18-3-686] sky2 crashes on boot or resume
- From: maximilian attems <max@stro.at>
- Date: Wed, 30 Jan 2008 19:14:31 +0100
- Message-id: <20080130181431.GG12407@stro.at>
Version: 2.6.23-1 should be fixed in newer as no newer update. -- maks
--- End Message ---