Your message dated Fri, 3 Dec 2010 06:49:41 +0100 with message-id <20101203054941.gr1...@mykerinos.kheops.frmug.org> and subject line Re: Bug#605689: installation-reports - kernel module crash when configuring bridge has caused the Debian Bug report #605689, regarding installation-reports - kernel module crash when configuring bridge 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.) -- 605689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: installation-reports Boot method: CD Image version: debian-squeeze-di-beta1-amd64-netinst Date: 01/12/2010 Machine: Dell OptiPlex 330 Processor: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz Memory: 3GB Partitions: /dev/mapper/bridge-root ext4 234130312 1014996 221222172 1% / tmpfs tmpfs 1542012 0 1542012 0% /lib/init/rw udev tmpfs 1536836 140 1536696 1% /dev tmpfs tmpfs 1542012 0 1542012 0% /dev/shm /dev/sda1 ext2 233191 15614 205136 8% /boot Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Dell Device [1028:0220] Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) Subsystem: Dell Device [1028:0220] 00:02.1 Display controller [0380]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c3] (rev 02) Subsystem: Dell Device [1028:0220] 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01) Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: uhci_hcd 00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: uhci_hcd 00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: uhci_hcd 00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: uhci_hcd 00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: ata_piix 00:1f.2 IDE interface [0101]: Intel Corporation N10/ICH7 Family SATA IDE Controller [8086:27c0] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 01) Subsystem: Dell Device [1028:0220] Kernel driver in use: i801_smbus 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5787 Gigabit Ethernet PCI Express [14e4:169b] (rev 02) Subsystem: Dell Device [1028:0220] Kernel driver in use: tg3 03:01.0 Ethernet controller [0200]: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) [1186:4b01] (rev 11) Subsystem: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) [1186:4b01] Kernel driver in use: skge 03:02.0 Ethernet controller [0200]: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) [1186:4b01] (rev 11) Subsystem: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) [1186:4b01] Kernel driver in use: skge Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system: [O] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install: [O] Comments/Problems: I've tried to configure a bridge between the devices 03:01.0 and 03:02.0, but I get an kernel module erro in dmesg: /etc/network/interfaces # The loopback network interface auto lo br0 iface lo inet loopback # The primary network interface #allow-hotplug eth0 iface br0 inet static address 10.10.10.10 netmask 255.255.252.0 gateway 10.0.10.2 bridge_ports eth0 eth1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers x.x.x.x y.y.y.y dns-search domain.local [ 39.816081] ------------[ cut here ]------------ [ 39.816095] WARNING: at /build/buildd-linux-2.6_2.6.32-28-amd64-EUJiNq/linux-2.6-2.6.32/debian/build/source_amd64_none/net/sched/sch_generic.c:261 dev_watchdog+0xe2/0x194() [ 39.816101] Hardware name: OptiPlex 330 [ 39.816104] NETDEV WATCHDOG: eth1 (skge): transmit queue 0 timed out [ 39.816108] Modules linked in: bridge stp ext2 loop i915 drm_kms_helper drm i2c_algo_bit video output snd_pcm snd_timer i2c_i801 snd soundcore i2c_core rng_core snd_page_alloc parport_pc processor parport button dcdbas evdev joydev pcspkr psmouse serio_raw ext4 mbcache jbd2 crc16 usbhid hid dm_mod sg sd_mod crc_t10dif sr_mod cdrom ata_generic uhci_hcd tg3 ata_piix libphy skge thermal ehci_hcd thermal_sys libata scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] [ 39.816177] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 [ 39.816180] Call Trace: [ 39.816183] <IRQ> [<ffffffff81261c12>] ? dev_watchdog+0xe2/0x194 [ 39.816193] [<ffffffff81261c12>] ? dev_watchdog+0xe2/0x194 [ 39.816200] [<ffffffff8104dd6c>] ? warn_slowpath_common+0x77/0xa3 [ 39.816206] [<ffffffff81261b30>] ? dev_watchdog+0x0/0x194 [ 39.816211] [<ffffffff8104ddf4>] ? warn_slowpath_fmt+0x51/0x59 [ 39.816219] [<ffffffff8105a588>] ? lock_timer_base+0x26/0x4b [ 39.816225] [<ffffffff8105ab06>] ? __mod_timer+0x141/0x153 [ 39.816230] [<ffffffff81261b04>] ? netif_tx_lock+0x3d/0x69 [ 39.816240] [<ffffffff8124c97c>] ? netdev_drivername+0x3b/0x40 [ 39.816243] [<ffffffff81261c12>] ? dev_watchdog+0xe2/0x194 [ 39.816246] [<ffffffff8103f9bb>] ? __wake_up+0x30/0x44 [ 39.816249] [<ffffffff8105a337>] ? run_timer_softirq+0x1c9/0x268 [ 39.816253] [<ffffffff81053aaf>] ? __do_softirq+0xdd/0x1a2 [ 39.816257] [<ffffffff8102419a>] ? lapic_next_event+0x18/0x1d [ 39.816262] [<ffffffff81011cac>] ? call_softirq+0x1c/0x30 [ 39.816264] [<ffffffff8101322b>] ? do_softirq+0x3f/0x7c [ 39.816267] [<ffffffff8105391e>] ? irq_exit+0x36/0x76 [ 39.816270] [<ffffffff81024c68>] ? smp_apic_timer_interrupt+0x87/0x95 [ 39.816273] [<ffffffff81011673>] ? apic_timer_interrupt+0x13/0x20 [ 39.816275] <EOI> [<ffffffff8101731c>] ? mwait_idle+0x72/0x7d [ 39.816280] [<ffffffff810172cc>] ? mwait_idle+0x22/0x7d [ 39.816284] [<ffffffff8100feb1>] ? cpu_idle+0xa2/0xda [ 39.816288] [<ffffffff814f3140>] ? early_idt_handler+0x0/0x71 [ 39.816291] [<ffffffff814f3cd1>] ? start_kernel+0x3dc/0x3e8 [ 39.816295] [<ffffffff814f33b7>] ? x86_64_start_kernel+0xf9/0x106 [ 39.816297] ---[ end trace d74831a900d9556f ]---
--- End Message ---
--- Begin Message ---Quoting Diego Morato (diego.mor...@hotmail.com): > > Yes, It was on the installed system, on the initial configuration of the > network. What I suggest, then, is to try to get a good reproducible case, then report a bug against the kernel (linux-2.6 package). In the meantime, I prefer closing this installation report because, as an installation report, this is a successful one..:-) Thanks for your care reporting your experience.signature.asc
Description: Digital signature
--- End Message ---