Bug#517627: Alteon NIC firmware
Ben Hutchings wrote: Jamie, You appear to be hosting the Alteon NIC firmware source and tools at http://alteon.shareable.org/, but links to those subdirectories yield 'Forbidden' error pages. Is there a reason why these are not available, or is this accidental? A configuration accident as you correctly guessed. Indexing was turned off. They are all readable now. If you build the firmware from the last source version, using the Linux-hosted GCC 2.95 (needing firmware.patch), it even runs a bit faster than the original Acenic binary :-) Somehow I never got around to submitting my version to the kernel. Don't ask me to revisit it now. The tools etc. were originally collected for a custom firmware projects (it was a popular board for that), and I decided to host them because Alteon were shutting down, and as a general principle of keeping source around. I'm not sure if the license would satisfy DFSG. It's pretty open as these things go. Lots of people hacked this chip, Tigon2, in interesting ways because of it's relatively unique openness at the time, and were disappointed when its successor, the Tigon3, wasn't open at all. It is quite a versatile dual-CPU gigE chip. I wrote on the top-level index Look at the source files yourself to understand any licensing restrictions on their use. Alteon's license may be summarised like this: you may share and develop the firmware, but it is only for use with Alteon NIC products. That last bit might refer to just advice, or a DFSG-incompatible restriction, I don't remember which. If it breaks you get to keep both pieces :-) -- Jamie -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100421085337.ga13...@shareable.org
Bug#576274: bug still present in current kernel from Sid
Hi, I tested the current linux-image-2.6.32-4-686 in Sid and the problem is indeed still there. Current workaround: Don't use suspend. I use the laptop while testing and I always lose a little of the stuff I work on when the screen goes dark (the stuff not saved yet). So I really recommend the workaround for now. Cheers, Malte -- Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010042612.156...@gmx.net
Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread
I'm not starting a new thread/bug, as this is probably related... I just discovered that in 2.6.33, if I create a veth inside a namespace and then move one of the halves into the main namespace, when I kill the namespace, I get one of these warnings followed by an oops. This does not happen if the veth is created from the main ns and then moved, nor in 2.6.32. This happens both in Qemu and on real hardware (both amd64) To reproduce: $ sudo ./startns bash # ip l a type veth # ip l s veth0 netns 1 # exit The full log: [ 280.655876] [ cut here ] [ 280.655916] WARNING: at /build/mattems-linux-2.6_2.6.33-1~experimental.4-amd64-ieqSsa/linux-2.6-2.6.33-1~experimental.4/debian/build/source_amd64_none/fs/sysfs/dir.c:487 sysfs_add_one+0xcc/0xe4() [ 280.655920] Hardware name: [ 280.655922] sysfs: cannot create duplicate filename '/devices/virtual/net/veth0/statistics' [ 280.655924] Modules linked in: veth loop parport_pc parport snd_pcm evdev snd_timer tpm_tis button serio_raw snd i2c_piix4 tpm soundcore tpm_bios processor snd_page_alloc psmouse i2c_core pcspkr ext3 jbd mbcache sg sr_mod cdrom sd_mod crc_t10dif ata_generic ata_piix libata thermal floppy thermal_sys 8139cp 8139too mii scsi_mod [last unloaded: scsi_wait_scan] [ 280.655954] Pid: 1276, comm: ip Not tainted 2.6.33-2-amd64 #1 [ 280.655956] Call Trace: [ 280.655961] [8113a399] ? sysfs_add_one+0xcc/0xe4 [ 280.655964] [8113a399] ? sysfs_add_one+0xcc/0xe4 [ 280.655987] [81046b81] ? warn_slowpath_common+0x77/0xa3 [ 280.655991] [81046c09] ? warn_slowpath_fmt+0x51/0x59 [ 280.655994] [8113a2c5] ? sysfs_pathname+0x35/0x3d [ 280.655997] [8113a2c5] ? sysfs_pathname+0x35/0x3d [ 280.656000] [8113a2c5] ? sysfs_pathname+0x35/0x3d [ 280.656007] [8113a2c5] ? sysfs_pathname+0x35/0x3d [ 280.656031] [8113a399] ? sysfs_add_one+0xcc/0xe4 [ 280.656035] [8113aac5] ? create_dir+0x4f/0x7c [ 280.656038] [8113baac] ? internal_create_group+0x51/0x15a [ 280.656062] [8120f3ba] ? device_add_groups+0x22/0x5d [ 280.656066] [8120faba] ? device_add+0x2d1/0x54a [ 280.656085] [81243d22] ? dev_change_net_namespace+0x1a1/0x1fc [ 280.656097] [8124b625] ? do_setlink+0x67/0x356 [ 280.656101] [8124c452] ? rtnl_newlink+0x2f4/0x4f3 [ 280.656104] [8124c203] ? rtnl_newlink+0xa5/0x4f3 [ 280.656107] [8123cdcf] ? __skb_recv_datagram+0x11a/0x24f [ 280.656116] [8123c040] ? memcpy_toiovec+0x3d/0x6d [ 280.656124] [8125d39d] ? netlink_sendmsg+0x15f/0x252 [ 280.656127] [8124bf69] ? rtnetlink_rcv_msg+0x0/0x1f5 [ 280.656130] [8125cf55] ? netlink_rcv_skb+0x34/0x7c [ 280.656133] [8124bf63] ? rtnetlink_rcv+0x1f/0x25 [ 280.656136] [8125cd49] ? netlink_unicast+0xe2/0x148 [ 280.656139] [8125d47d] ? netlink_sendmsg+0x23f/0x252 [ 280.656142] [81232ea3] ? sock_sendmsg+0x83/0x9b [ 280.656162] [810b5122] ? __alloc_pages_nodemask+0x10f/0x5e1 [ 280.656166] [8123bd03] ? copy_from_user+0x13/0x25 [ 280.656169] [8123c0b9] ? verify_iovec+0x49/0x84 [ 280.656172] [81233178] ? sys_sendmsg+0x225/0x2af [ 280.656176] [812343c7] ? sys_recvmsg+0x48/0x56 [ 280.656188] [81008ac2] ? system_call_fastpath+0x16/0x1b [ 280.656191] ---[ end trace f31191528d9325da ]--- [ 280.658197] [ cut here ] [ 280.658202] WARNING: at /build/mattems-linux-2.6_2.6.33-1~experimental.4-amd64-ieqSsa/linux-2.6-2.6.33-1~experimental.4/debian/build/source_amd64_none/net/core/dev.c:5597 dev_change_net_namespace+0x1b6/0x1fc() [ 280.658205] Hardware name: [ 280.658207] Modules linked in: veth loop parport_pc parport snd_pcm evdev snd_timer tpm_tis button serio_raw snd i2c_piix4 tpm soundcore tpm_bios processor snd_page_alloc psmouse i2c_core pcspkr ext3 jbd mbcache sg sr_mod cdrom sd_mod crc_t10dif ata_generic ata_piix libata thermal floppy thermal_sys 8139cp 8139too mii scsi_mod [last unloaded: scsi_wait_scan] [ 280.658229] Pid: 1276, comm: ip Tainted: GW 2.6.33-2-amd64 #1 [ 280.658231] Call Trace: [ 280.658235] [81243d37] ? dev_change_net_namespace+0x1b6/0x1fc [ 280.658238] [81243d37] ? dev_change_net_namespace+0x1b6/0x1fc [ 280.658241] [81046b81] ? warn_slowpath_common+0x77/0xa3 [ 280.658245] [81243d37] ? dev_change_net_namespace+0x1b6/0x1fc [ 280.658248] [8124b625] ? do_setlink+0x67/0x356 [ 280.658251] [8124c452] ? rtnl_newlink+0x2f4/0x4f3 [ 280.658254] [8124c203] ? rtnl_newlink+0xa5/0x4f3 [ 280.658257] [8123cdcf] ? __skb_recv_datagram+0x11a/0x24f [ 280.658261] [8123c040] ? memcpy_toiovec+0x3d/0x6d [ 280.658264] [8125d39d] ? netlink_sendmsg+0x15f/0x252 [ 280.658267] [8124bf69] ? rtnetlink_rcv_msg+0x0/0x1f5 [ 280.658270] [8125cf55] ? netlink_rcv_skb+0x34/0x7c [
Bug#578670: Hibernation while using nouveau restores to video noise
Package: linux-2.6 After restoring from hibernation (uswsusp) while using the nouveau driver, the display is obscured by a pattern of blue noise that persists across all X sessions and VTs. The display remains usable, if you don't mind the constant noise. I'm not sure exactly how to describe it without attaching a picture. I can do this if requested. Attached is my lspci -nn output. -- Chris Howie http://www.chrishowie.com http://en.wikipedia.org/wiki/User:Crazycomputers PGP key: pub 2048R/CF8338F5 2010-04-14 Key fingerprint = 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5 00:00.0 RAM memory [0500]: nVidia Corporation MCP67 Memory Controller [10de:0547] (rev a2) 00:01.0 ISA bridge [0601]: nVidia Corporation MCP67 ISA Bridge [10de:0548] (rev a2) 00:01.1 SMBus [0c05]: nVidia Corporation MCP67 SMBus [10de:0542] (rev a2) 00:01.2 RAM memory [0500]: nVidia Corporation MCP67 Memory Controller [10de:0541] (rev a2) 00:01.3 Co-processor [0b40]: nVidia Corporation MCP67 Co-processor [10de:0543] (rev a2) 00:02.0 USB Controller [0c03]: nVidia Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:02.1 USB Controller [0c03]: nVidia Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:04.0 USB Controller [0c03]: nVidia Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:04.1 USB Controller [0c03]: nVidia Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:06.0 IDE interface [0101]: nVidia Corporation MCP67 IDE Controller [10de:0560] (rev a1) 00:07.0 Audio device [0403]: nVidia Corporation MCP67 High Definition Audio [10de:055c] (rev a1) 00:08.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Bridge [10de:0561] (rev a2) 00:09.0 IDE interface [0101]: nVidia Corporation MCP67 AHCI Controller [10de:0550] (rev a2) 00:0a.0 Ethernet controller [0200]: nVidia Corporation MCP67 Ethernet [10de:054c] (rev a2) 00:0c.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0d.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:12.0 VGA compatible controller [0300]: nVidia Corporation C67 [GeForce 7150M / nForce 630M] [10de:0531] (rev a2) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 02:05.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05) 02:05.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22) 02:05.2 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 12) 02:05.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12) 02:05.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev ff) 03:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5001 Wireless Network Adapter [168c:001c] (rev 01)
Processed: Re: Bug#578670: Hibernation while using nouveau restores to video noise
Processing commands for cont...@bugs.debian.org: tags 578670 moreinfo Bug #578670 [linux-2.6] Hibernation while using nouveau restores to video noise Added tag(s) moreinfo. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12718731804713.transcr...@bugs.debian.org
Bug#578676: linux-image-2.6.32-3-686: KMS fails to load at startup from time to time (macbook 2.1, intel GPU)
Package: linux-2.6 Version: 2.6.32-9 Severity: normal From time to time, when I start my macbook on squeeze, the KMS will just fail to activate, and I get the old big fonts during the boot process (another symptom is the high latency switch from the X server to the console). Usually restarting the computer will re-enable KMS. I *think* the corresponding entries in dmesg might be the following ones: [1.191365] [drm] Initialized drm 1.1.0 20060810 [1.225232] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.225239] i915 :00:02.0: setting latency timer to 64 [1.225257] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module. [1.225318] DRM: Fill_in_dev failed. [1.225371] i915 :00:02.0: PCI INT A disabled [1.225377] i915: probe of :00:02.0 failed with error -22 I guess lspci information will be provided by reportbug If more data is needed to identify correctly the issue, please feel free to ask me. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at 5038 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at 20e0 [size=8] Region 2: Memory at 4000 (32-bit, prefetchable) [size=256M] Region 3: Memory at 5040 (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at 5030 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:07.0 Performance counters [1101]: Intel Corporation Device [8086:27a3] (rev 03) Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: Memory at 50444000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: SigmaTel Device [8384:7680] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 256 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at 5044 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 256 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 1000-1fff Memory behind bridge: 5020-502f Prefetchable memory behind bridge: 5050-506f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied
Bug#578670: Hibernation while using nouveau restores to video noise
tags 578670 moreinfo stop On Wed, Apr 21, 2010 at 01:06:14PM -0400, Chris Howie wrote: Package: linux-2.6 After restoring from hibernation (uswsusp) while using the nouveau driver, the display is obscured by a pattern of blue noise that persists across all X sessions and VTs. The display remains usable, if you don't mind the constant noise. I'm not sure exactly how to describe it without attaching a picture. I can do this if requested. Attached is my lspci -nn output. please use the following, aboves is not enough info: reportbug -N bugnr thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100421175819.gw10...@baikonur.stro.at
Bug#578670: Hibernation while using nouveau restores to video noise
On Wed, Apr 21, 2010 at 1:58 PM, maximilian attems m...@stro.at wrote: please use the following, aboves is not enough info: reportbug -N bugnr Are these the droids you were looking for? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Chris Howie http://www.chrishowie.com http://en.wikipedia.org/wiki/User:Crazycomputers PGP key: pub 2048R/CF8338F5 2010-04-14 Key fingerprint = 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k2m3d2f29dc100422i5b931d8axf0402552ae8f8...@mail.gmail.com
Bug#578676: marked as done (linux-image-2.6.32-3-686: KMS fails to load at startup from time to time (macbook 2.1, intel GPU))
Your message dated Wed, 21 Apr 2010 20:31:15 +0200 with message-id 20100421183115.gn12...@radis.liafa.jussieu.fr and subject line Re: Bug#578676: linux-image-2.6.32-3-686: KMS fails to load at startup from time to time (macbook 2.1, intel GPU) has caused the Debian Bug report #578676, regarding linux-image-2.6.32-3-686: KMS fails to load at startup from time to time (macbook 2.1, intel GPU) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 578676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-9 Severity: normal From time to time, when I start my macbook on squeeze, the KMS will just fail to activate, and I get the old big fonts during the boot process (another symptom is the high latency switch from the X server to the console). Usually restarting the computer will re-enable KMS. I *think* the corresponding entries in dmesg might be the following ones: [1.191365] [drm] Initialized drm 1.1.0 20060810 [1.225232] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.225239] i915 :00:02.0: setting latency timer to 64 [1.225257] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module. [1.225318] DRM: Fill_in_dev failed. [1.225371] i915 :00:02.0: PCI INT A disabled [1.225377] i915: probe of :00:02.0 failed with error -22 I guess lspci information will be provided by reportbug If more data is needed to identify correctly the issue, please feel free to ask me. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at 5038 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at 20e0 [size=8] Region 2: Memory at 4000 (32-bit, prefetchable) [size=256M] Region 3: Memory at 5040 (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at 5030 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:07.0 Performance counters [1101]: Intel Corporation Device [8086:27a3] (rev 03) Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: Memory at 50444000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: SigmaTel Device [8384:7680] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 256 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at 5044 (64-bit, non-prefetchable) [size=16K]
Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread
Martín Ferrari martin.ferr...@gmail.com writes: I'm not starting a new thread/bug, as this is probably related... I just discovered that in 2.6.33, if I create a veth inside a namespace and then move one of the halves into the main namespace, when I kill the namespace, I get one of these warnings followed by an oops. This does not happen if the veth is created from the main ns and then moved, nor in 2.6.32. This happens both in Qemu and on real hardware (both amd64) To reproduce: $ sudo ./startns bash # ip l a type veth # ip l s veth0 netns 1 # exit Nasty weird. I did a quick test here, and I'm not seeing that. Does the 2.6.33 experimental kernel have any patches applied? The sysfs_add_one path looks like someone we hit a duplicate name, which is a bug of an entirely different kind. From there it appears that we later destroy the device not realizing it isn't in sysfs. Which causes everything to explode. The sysctl issues appears to be that somewhere we have the ordering of creates and/or deletes wrong. It is just possible the changes for batch deletion might be exposing a bug under load. The sysctl error appears to be in the class of things that should never happen but that we should handle correctly anyway. Eric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/m1ljcgzjh4@fess.ebiederm.org
Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread
On Wed, 2010-04-21 at 12:36 -0700, Eric W. Biederman wrote: Martín Ferrari martin.ferr...@gmail.com writes: I'm not starting a new thread/bug, as this is probably related... I just discovered that in 2.6.33, if I create a veth inside a namespace and then move one of the halves into the main namespace, when I kill the namespace, I get one of these warnings followed by an oops. This does not happen if the veth is created from the main ns and then moved, nor in 2.6.32. This happens both in Qemu and on real hardware (both amd64) To reproduce: $ sudo ./startns bash # ip l a type veth # ip l s veth0 netns 1 # exit Nasty weird. I did a quick test here, and I'm not seeing that. Does the 2.6.33 experimental kernel have any patches applied? Yes, but not many beyond the stable updates, and nothing in this area. You can see the list at: http://svn.debian.org/wsvn/kernel/dists/trunk/linux-2.6/debian/patches/series/base Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread
Ben Hutchings b...@decadent.org.uk writes: On Wed, 2010-04-21 at 12:36 -0700, Eric W. Biederman wrote: Martín Ferrari martin.ferr...@gmail.com writes: I'm not starting a new thread/bug, as this is probably related... I just discovered that in 2.6.33, if I create a veth inside a namespace and then move one of the halves into the main namespace, when I kill the namespace, I get one of these warnings followed by an oops. This does not happen if the veth is created from the main ns and then moved, nor in 2.6.32. This happens both in Qemu and on real hardware (both amd64) To reproduce: $ sudo ./startns bash # ip l a type veth # ip l s veth0 netns 1 # exit Nasty weird. I did a quick test here, and I'm not seeing that. Does the 2.6.33 experimental kernel have any patches applied? Yes, but not many beyond the stable updates, and nothing in this area. You can see the list at: http://svn.debian.org/wsvn/kernel/dists/trunk/linux-2.6/debian/patches/series/base Then I should ask what is startns? Either that is doing something different from my equivalent program, or I have patches to fix this, that just haven't been merged yet. Eric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/m1sk6oky96@fess.ebiederm.org
