Bug#847077: firmware-nonfree: Sid binary packages gone
Source: firmware-nonfree Severity: grave Justification: renders package unusable Hello, The binary packages generated from this source have not been avaiable in Sid for at least one day now. E.g. https://packages.debian.org/unstable/firmware-iwlwifi Thanks, George -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#732279: linux-image-3.2.0-4-686-pae: netback page allocation failure (Xen memory leak?)
0.0.0.0/0tcp dpt:25 4546 263K RETURN tcp -- * * 0.0.0.0/0 0.0.0.0/0tcp dpt:22 28548 1631K NFQUEUEall -- * * 0.0.0.0/0 0.0.0.0/0NFQUEUE num 92 --- Let me know if you need to see anything else. [1] http://sourceforge.net/p/peerguardian/wiki/pgl-Main/ Best regards, George On 16 December 2013 17:52, Ben Hutchings wrote: > On Mon, Dec 16, 2013 at 09:41:56AM +, George B. wrote: > > Package: src:linux > > Version: 3.2.51-1 > > Severity: normal > > > > Hello, > > > > I am seeing the backtrace below in my kernel log after the system has > been running for several weeks. > > > > Looks like it has something to do with Xen - memory leak maybe? > > I'm not sure it's directly connected with Xen - I think that an > interrupt from the physical network interface interrupted a task that > is part of the netback driver. > > This is not necessarily due to a memory leak; more likely this is > memory fragmentation. Some oddity of your networking configuration > results in linearising large packets: > > [...] > > [955212.368551] netback/0: page allocation failure: order:3, mode:0x20 > [...] > > This means: allocating something between 16 and 32K atomically > (no waiting allowed). > > The call trace appears to show that a packet received by the local TCP > via a bridge resulted in an immediate transmission, again going > through the bridge, and that then required this large memory > allocation. > > Please provide details of your networking configuration, > including: > > - Are you using ebtables? > - Are you using VLAN devices? > > Ben. > > -- > Ben Hutchings > Life is like a sewer: > what you get out of it depends on what you put into it. >
Bug#732279: linux-image-3.2.0-4-686-pae: netback page allocation failure (Xen memory leak?)
Package: src:linux Version: 3.2.51-1 Severity: normal Hello, I am seeing the backtrace below in my kernel log after the system has been running for several weeks. Looks like it has something to do with Xen - memory leak maybe? Thanks, George -- Package-specific info: ** Version: Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1 ** Command line: placeholder root=UUID=a1dfd67e-9ada-4ab3-ab6b-d859535e36be ro quiet ** Not tainted ** Kernel log: [955212.368551] netback/0: page allocation failure: order:3, mode:0x20 [955212.368558] Pid: 3346, comm: netback/0 Not tainted 3.2.0-4-686-pae #1 Debian 3.2.51-1 [955212.368561] Call Trace: [955212.368575] [] ? warn_alloc_failed+0xc5/0xd6 [955212.368580] [] ? __alloc_pages_nodemask+0x5c2/0x63e [955212.368586] [] ? arch_local_irq_disable+0x6/0x7 [955212.368600] [] ? __nf_ct_refresh_acct+0x55/0x9f [nf_conntrack] [955212.368607] [] ? cache_alloc+0x253/0x407 [955212.368611] [] ? __kmalloc+0x63/0xab [955212.368616] [] ? pskb_expand_head+0xbc/0x20b [955212.368620] [] ? pskb_expand_head+0xbc/0x20b [955212.368645] [] ? __pskb_pull_tail+0x3d/0x1fb [955212.368650] [] ? dev_hard_start_xmit+0x2f4/0x44f [955212.368655] [] ? sch_direct_xmit+0x49/0xf7 [955212.368659] [] ? dev_queue_xmit+0x244/0x38f [955212.368668] [] ? br_flood+0xb9/0xb9 [bridge] [955212.368675] [] ? br_flood+0xb9/0xb9 [bridge] [955212.368681] [] ? br_dev_queue_push_xmit+0x87/0x8b [bridge] [955212.368688] [] ? NF_HOOK.constprop.10+0x38/0x3b [bridge] [955212.368695] [] ? __br_deliver+0x87/0x87 [bridge] [955212.368702] [] ? br_forward_finish+0x16/0x19 [bridge] [955212.368708] [] ? br_flood+0xb9/0xb9 [bridge] [955212.368715] [] ? NF_HOOK.constprop.10+0x38/0x3b [bridge] [955212.368721] [] ? __br_deliver+0x82/0x87 [bridge] [955212.368728] [] ? __br_deliver+0x87/0x87 [bridge] [955212.368734] [] ? br_dev_xmit+0x10e/0x123 [bridge] [955212.368738] [] ? dev_hard_start_xmit+0x33b/0x44f [955212.368743] [] ? dev_queue_xmit+0x310/0x38f [955212.368747] [] ? nf_hook_thresh.constprop.36+0x2b/0x31 [955212.368751] [] ? ip_finish_output2+0x1a3/0x1d9 [955212.368755] [] ? dst_output+0x9/0xa [955212.368758] [] ? ip_queue_xmit+0x2b8/0x2f9 [955212.368763] [] ? __tcp_v4_send_check+0x21/0x7e [955212.368767] [] ? tcp_transmit_skb+0x63a/0x661 [955212.368771] [] ? tcp_write_xmit+0x642/0x749 [955212.368775] [] ? __tcp_push_pending_frames+0x15/0x42 [955212.368781] [] ? tcp_data_snd_check+0x2c/0xec [955212.368785] [] ? tcp_rcv_established+0xd9/0x4e0 [955212.368789] [] ? __inet_lookup_established+0x89/0x1af [955212.368793] [] ? tcp_v4_do_rcv+0x12e/0x289 [955212.368796] [] ? tcp_v4_rcv+0x206/0x542 [955212.368800] [] ? tcp_v4_rcv+0x375/0x542 [955212.368806] [] ? ip_local_deliver_finish+0x103/0x19f [955212.368810] [] ? xfrm4_policy_check.constprop.11+0x45/0x45 [955212.368814] [] ? NF_HOOK.constprop.10+0x36/0x39 [955212.368818] [] ? ip_local_deliver+0x39/0x3c [955212.368822] [] ? xfrm4_policy_check.constprop.11+0x45/0x45 [955212.368826] [] ? ip_rcv_finish+0x2a0/0x2b2 [955212.368830] [] ? inet_del_protocol+0x24/0x24 [955212.368834] [] ? NF_HOOK.constprop.10+0x36/0x39 [955212.368840] [] ? __netif_receive_skb+0x34f/0x379 [955212.368844] [] ? inet_del_protocol+0x24/0x24 [955212.368847] [] ? enqueue_to_backlog+0xd3/0xd3 [955212.368851] [] ? netif_receive_skb+0x5d/0x62 [955212.368858] [] ? NF_HOOK.constprop.3+0x2a/0x39 [bridge] [955212.368865] [] ? NF_HOOK.constprop.3+0x36/0x39 [bridge] [955212.368873] [] ? br_handle_frame_finish+0x1a4/0x1b5 [bridge] [955212.368876] [] ? enqueue_to_backlog+0xd3/0xd3 [955212.368883] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.368891] [] ? NF_HOOK_THRESH+0x36/0x39 [bridge] [955212.368898] [] ? br_nf_pre_routing_finish+0x182/0x18f [bridge] [955212.368905] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.368913] [] ? br_nf_pre_routing_finish_ipv6+0x87/0x87 [bridge] [955212.368920] [] ? br_nf_pre_routing_finish_ipv6+0x87/0x87 [bridge] [955212.368928] [] ? br_nf_pre_routing_finish_ipv6+0x87/0x87 [bridge] [955212.368935] [] ? NF_HOOK_THRESH+0x36/0x39 [bridge] [955212.368942] [] ? br_nf_pre_routing+0x326/0x334 [bridge] [955212.368950] [] ? br_nf_pre_routing_finish_ipv6+0x87/0x87 [bridge] [955212.368955] [] ? nf_iterate+0x30/0x55 [955212.368962] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.368966] [] ? nf_hook_slow+0x3f/0xcc [955212.368973] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.368980] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.368987] [] ? NF_HOOK.constprop.3+0x2a/0x39 [bridge] [955212.368994] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.369001] [] ? br_handle_frame+0x166/0x17b [bridge] [955212.369008] [] ? NF_HOOK.constprop.3+0x39/0x39 [bridge] [955212.369015] [] ? br_handle_frame_finish+0x1b5/0x1b5 [bridge] [955212.369019] [] ? __netif_receive_skb+0x27b/0x379 [955212.369023] [] ? dev_hard_start_xmit+0x33b/0x44f [955212.36
Bug#604442: linux-image-2.6-686: Kernel Oops after return from hibernation
> 1. Install 2.6.32-27 from http://snapshot.debian.org/, keeping all > other packages the same, and check if it still reproduces the > problem. (It might not, if X was involved.) I ran 2.6.32-27 for a few days and couldn't reproduce the problem any more. FWIW the environment has changed since the time of the issue: I have rebuild the box to run amd64. Up to you on how to go on from here... Thanks, George -- 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/CAD8JW+ivuYxrMajFMjbSiTc1XkdwnfQjXrgsy62=nbzwycm...@mail.gmail.com
Bug#604442: closed by Jonathan Nieder (Re: linux-image-2.6-686: Kernel Oops after return from hibernation)
> From: Jonathan Nieder > > Closing due to lack of response. :/ But please don't hesitate to write > if you have more information, and we can pick this up again. Sorry, I somehow missed the information request e-mail... :-( Anyway the problem has gone away a long time ago after some kernel update, so closing is fine. Laptop was Dell Latitude E6400. Thanks, George -- 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/cad8jw+i5b44haofxc-dghy_pvx40jwpc3f810usg4ory-kt...@mail.gmail.com
Bug#604442: linux-image-2.6-686: Kernel Oops after return from hibernation
Package: linux-image-2.6-686 Version: 2.6.32+28 Severity: important Hello, I am getting regular oopses again from the kernel after returning from hibernation - this used to work without issue for some time before. >From syslog: --- Nov 22 10:03:19 deli kernel: [12670.808315] firewire_core: rediscovered device fw0 Nov 22 10:03:19 deli kernel: [12671.588255] sd 0:0:0:0: [sda] Starting disk Nov 22 10:03:19 deli kernel: [12671.736239] usb 1-6: reset high speed USB device using ehci_hcd and address 4 Nov 22 10:03:19 deli kernel: [12672.024241] usb 3-1: reset full speed USB device using uhci_hcd and address 2 Nov 22 10:03:19 deli kernel: [12672.500053] usb 5-1: reset full speed USB device using uhci_hcd and address 2 Nov 22 10:03:19 deli kernel: [12672.733289] usb 3-1.1: reset full speed USB device using uhci_hcd and address 3 Nov 22 10:03:19 deli kernel: [12672.921290] usb 3-1.2: reset full speed USB device using uhci_hcd and address 4 Nov 22 10:03:19 deli kernel: [12673.072618] Registered led device: iwl-phy0::radio Nov 22 10:03:19 deli kernel: [12673.072639] Registered led device: iwl-phy0::assoc Nov 22 10:03:19 deli kernel: [12673.072659] Registered led device: iwl-phy0::RX Nov 22 10:03:19 deli kernel: [12673.072681] Registered led device: iwl-phy0::TX Nov 22 10:03:19 deli kernel: [12673.095966] Restarting tasks ... Nov 22 10:03:19 deli kernel: [12673.096037] usb 7-1: USB disconnect, address 2 Nov 22 10:03:19 deli kernel: [12673.096146] BUG: unable to handle kernel NULL pointer dereference at (null) Nov 22 10:03:19 deli kernel: [12673.096190] IP: [] strcmp+0x6/0x19 Nov 22 10:03:19 deli kernel: [12673.096225] *pde = Nov 22 10:03:19 deli kernel: [12673.096249] Oops: [#1] SMP Nov 22 10:03:19 deli kernel: [12673.096277] last sysfs file: /sys/devices/virtual/sound/timer/uevent Nov 22 10:03:19 deli kernel: [12673.096315] Modules linked in: vboxnetadp vboxnetflt vboxdrv parport_pc ppdev lp parport i8k fuse ext4 jbd2 crc16 firewire_sbp2 loop btusb bluetooth arc4 joydev ecb snd_hda_codec_intelhdmi iwlagn snd_hda_codec_idt iwlcore i915 uvcvideo snd_hda_intel snd_hda_codec drm_kms_helper videode v mac80211 v4l1_compat snd_hwdep snd_pcm drmdone. Nov 22 10:03:19 deli kernel: [12673.11] pcmcia cfg80211 snd_timer snd i2c_i801 soundcore dell_laptop wmi psmouse snd_page_alloc i2c_algo_bit yenta_socket rsrc_nonstatic button ac dcdbas pcmcia_core serio_raw evdev pcspkr video output rfkill battery processor i2c_core ext3 jbd mbcache sha256_generic aes_i586 aes_ generic cbc dm_crypt dm_mod sg sd_mod crc_t10dif sr_mod cdrom usbhid hid uhci_hcd ata_generic ahci sdhci_pci sdhci thermal libata ricoh_mmc mmc_core led_class firewire_ohci firewire_core crc_itu_t thermal_sys ehci_hcd scsi_mod e1000e usbcore nls_base [last unloaded: scsi_wait_scan] Nov 22 10:03:19 deli kernel: [12673.11] Nov 22 10:03:19 deli kernel: [12673.11] Pid: 293, comm: khubd Not tainted (2.6.32-5-686 #1) Latitude E6400 Nov 22 10:03:19 deli kernel: [12673.11] EIP: 0060:[] EFLAGS: 00010286 CPU: 1 Nov 22 10:03:19 deli kernel: [12673.11] EIP is at strcmp+0x6/0x19 Nov 22 10:03:19 deli kernel: [12673.11] EAX: EBX: f6de7000 ECX: f6a36d20 EDX: f6649ded Nov 22 10:03:19 deli kernel: [12673.11] ESI: EDI: f6649ded EBP: f4e2a018 ESP: f6649da4 Nov 22 10:03:19 deli kernel: [12673.11] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 22 10:03:19 deli kernel: [12673.11] Process khubd (pid: 293, ti=f6648000 task=f66c4000 task.ti=f6648000) Nov 22 10:03:19 deli kernel: [12673.102822] Stack: Nov 22 10:03:19 deli kernel: [12673.102822] f6649ded f4e2a79c c10f2f36 f6c08180 f6649ded c10f1e2c f6c08180 f6a36ca8 Nov 22 10:03:19 deli kernel: [12673.102822] <0> f6649ded f6c01800 f4e2a79c c11b083d f6649ded c12de22a Nov 22 10:03:19 deli kernel: [12673.102822] <0> 000d 0022 3a3331f9 f5003433 f4d45290 f586ec5c 1e193104 f586ec5c Nov 22 10:03:19 deli kernel: [12673.102822] Call Trace: Nov 22 10:03:19 deli kernel: [12673.102822] [] ? sysfs_find_dirent+0x13/0x23 Nov 22 10:03:19 deli kernel: [12673.102822] [] ? sysfs_hash_and_remove+0x20/0x48 Nov 22 10:03:19 deli kernel: [12673.102822] [] ? device_remove_sys_dev_entry+0x57/0x72 Nov 22 10:03:19 deli kernel: [12673.102822] [] ? device_del+0x56/0x152 Nov 22 10:03:19 deli kernel: [12673.102822] [] ? mousedev_destroy+0xe/0x2c Nov 22 10:03:19 deli kernel: [12673.102822] [] ? input_unregister_device+0xe5/0x16f Nov 22 10:03:19 deli kernel: [12673.102822] [] ? hidinput_disconnect+0x32/0x45 [hid] Nov 22 10:03:19 deli kernel: [12673.102822] [] ? hid_disconnect+0x11/0x35 [hid] Nov 22 10:03:19 deli kernel: [12673.102822] [] ? hid_device_remove+0x25/0x3e [hid] Nov 22 10:03:19 deli kernel: [12673.102822] [] ? __device_release_driver+0x74/0xb7 Nov 22 10:03:19 deli kernel: [12673.102822] [] ? device_release_driver+0x15/0x1e Nov 22 10:03:19 deli kernel: [12673.10282
Bug#555360: linux-image-2.6-686: Package uninstallable due to missing dependency
Uwe Kleine-König wrote: I'm sure you intended to write Version: 2.6.31+22 here? Probably. I was lazy and copied and pasted from http://packages.debian.org/sid/linux-image-2.6-686 The problem is that the package hangs in the new queue that isn't handled at the moment. Thanks for the information. George. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555360: linux-image-2.6-686: Package uninstallable due to missing dependency
Package: linux-image-2.6-686 Version: 2.6.30+21 Severity: grave Justification: renders package unusable Hello, Package currently depends on linux-image-2.6.31-1-686 that is not available. Dependency information needs to be updated? This has been broken for at least a week now. Thanks, George. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.30-2-686 2.6.30-8 Linux 2.6.30 image on PPro/Celeron linux-image-2.6-686 recommends no packages. linux-image-2.6-686 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#387460: linux-image-2.6.17-2-686: kernel panic when trying to add vlan to a slave bonded interface
2008/11/29 Moritz Muehlenhoff <[EMAIL PROTECTED]>: > George, did you report that bug upstream? Hi Mortiz, I don't think I submitted a bug upstream (I think I may have had some problems, but I can't remember now). Since then, I've changed jobs twice, so I no longer have access to that hardware. I tried reproducing the problem on a Lenny VirtualBox VM, but could not. Feel free to close this bug - I'll re-open it if I manage to reproduce it (I should have some spare real servers available for that in our lab at some point in future). Thanks. George. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499527: linux-image-2.6.26-1-686: Kernel Oops with Belkin 54g USB wireless network adapter
Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: important Hello, I got an Oops message (see below) when I plugged in a Belkin 54g USB wireless network adapter. Looks like upstream is aware of the problem, but I'm reporting this here so you can track this. http://lkml.org/lkml/2008/8/9/31 Workaround from above link: --- Please note that a workaround is blacklisting rt2500usb and loading rt73usb directly. (The bug is triggered because rt2500usb is loaded for a USB device which does not contain rt 2500usb chipset). --- HTH, George. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-2) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Aug 8 18:51:38 UTC 2008 ** Command line: root=/dev/sda3 ro ** Tainted: G D (128) ** Kernel log: [ 86.265941] usb 5-5: new high speed USB device using ehci_hcd and address 3 [ 86.568746] usb 5-5: configuration #1 chosen from 1 choice [ 86.568746] usb 5-5: New USB device found, idVendor=050d, idProduct=705a [ 86.568746] usb 5-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 86.568746] usb 5-5: Product: Belkin 54g USB Network Adapter [ 86.568746] usb 5-5: Manufacturer: Belkin [ 86.845649] phy1 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected. [ 86.845649] phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device. [ 86.845649] BUG: unable to handle kernel NULL pointer dereference at 0010 [ 86.845649] IP: [] flush_workqueue+0xa/0x3f [ 86.845649] *pde = [ 86.845649] Oops: [#1] SMP [ 86.845649] Modules linked in: rt2500usb(+) rt2x00usb rt2x00lib rfkill input_polldev i915 drm ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables uinput ppdev parport_pc lp parport acpi_cpufreq cpufreq_stats cpufreq_ondemand freq_table cpufreq_powersave cpufreq_userspace cpufreq_conservative nls_utf8 ntfs nls_base fuse sbp2 loop irtty_sir sir_dev snd_hda_intel ipw3945 pcmcia nsc_ircc iTCO_wdt snd_pcm_oss snd_mixer_oss snd_seq_dummy psmouse irda snd_pcm serio_raw crc_ccitt snd_seq_oss rng_core ieee80211 ieee80211_crypt snd_seq_midi i2c_i801 usbhid hid pcspkr battery ac i2c_core arc4 snd_rawmidi snd_seq_midi_event snd_seq ff_memless ecb crypto_blkcipher video output bay snd_timer snd_seq_device iwl3945 firmware_class mac80211 snd thinkpad_acpi yenta_socket rsrc_nonstatic pcmcia_core button cfg80211 soundcore led_class evdev intel_agp agpgart snd_page_alloc nvram ext3 jbd mbcache sd_mod ide_pci_generic ide_core ata_generic ohci1394 ieee1394 sdhci ata_piix libata scsi_mod mmc_core ehci_hcd uhci_hcd usbcore e1000e dock thermal processor fan thermal_sys [ 86.845649] [ 86.845649] Pid: 3890, comm: modprobe Not tainted (2.6.26-1-686 #1) [ 86.845649] EIP: 0060:[] EFLAGS: 00010246 CPU: 0 [ 86.845649] EIP is at flush_workqueue+0xa/0x3f [ 86.845649] EAX: EBX: f69a5020 ECX: 0046 EDX: 0046 [ 86.845649] ESI: c03735ac EDI: EBP: f785f400 ESP: f1833d84 [ 86.845649] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 86.845649] Process modprobe (pid: 3890, ti=f1832000 task=f68b6240 task.ti=f1832000) [ 86.845649] Stack: f69a5020 f69a5020 f69a41a0 f8dea222 ffed f8deac2d f89b5235 f69a40f0 [ 86.845649]f69a41a0 f69a4a5c 0282 f69a5020 f69a5020 f69a5020 f69a41a0 [ 86.845649]f785f400 f8de68c9 f337f400 f785f400 f8dfd970 f8dfd8a0 f88e899a [ 86.845649] Call Trace: [ 86.845649] [] rt2x00lib_remove_dev+0x30/0x51 [rt2x00lib] [ 86.845649] [] rt2x00lib_probe_dev+0x31b/0x337 [rt2x00lib] [ 86.845649] [] wiphy_new+0xdb/0xf4 [cfg80211] [ 86.845649] [] rt2x00usb_probe+0xdd/0x118 [rt2x00usb] [ 86.845649] [] usb_probe_interface+0xad/0xde [usbcore] [ 86.845649] [] __driver_attach+0x0/0x55 [ 86.845649] [] driver_probe_device+0xb5/0x12c [ 86.845649] [] __driver_attach+0x37/0x55 [ 86.845649] [] bus_for_each_dev+0x37/0x59 [ 86.845649] [] driver_attach+0x11/0x13 [ 86.845649] [] __driver_attach+0x0/0x55 [ 86.845649] [] bus_add_driver+0x8a/0x1a6 [ 86.845649] [] kset_find_obj+0x20/0x4b [ 86.845649] [] driver_register+0x6d/0xc1 [ 86.845649] [] usb_register_driver+0x5d/0xb4 [usbcore] [ 86.845649] [] sys_init_module+0x184b/0x19bb [ 86.845649] [] vma_link+0xa3/0xbd [ 86.845649] [] rt2x00mac_bss_info_changed+0x0/0xc0 [rt2x00lib] [ 86.845649] [] do_mmap_pgoff+0x266/0x2b9 [ 86.845649] [] sysenter_past_esp+0x78/0xb1 [ 86.845649] === [ 86.845649] Code: 00 74 14 e8 86 ff ff ff 8b 43 20 e8 22 24 00 00 c7 43 20 00 00 00 00 5b c3 83 c0 10 e9 6d b5 fe ff 57 89 c7 56 be ac 35 37 c0 53 <83> 78 10 00 b8 b0 35 37 c0 0f 44 f0 89 f0 e8 0e d9 0a 00 eb 15 [ 86.845649] EIP: [] flush_workqueue+0xa/0x3f SS:ESP 0068:f1833d84 [ 86.846661] ---[ end trace a57c75844d1bf763 ]--- [ 729.566704] usb 5-5: USB disconnect, address 3 [ 773.116881] ACPI: PCI Interrupt :03:00.0[
Bug#387460: linux-image-2.6.17-2-686: kernel panic when trying to add vlan to a slave bonded interface
On 15/09/06, maximilian attems <[EMAIL PROTECTED]> wrote: On Thu, 14 Sep 2006, George B. wrote: > On 14/09/06, maximilian attems <[EMAIL PROTECTED]> wrote: > > > >blaeh, please try to reproduce with current trunk: > >http://wiki.debian.org/DebianKernel Problem is still there :-( From kern.log: --- Sep 26 16:46:39 dxsfw-dc01 kernel: Linux version 2.6.18-1-686 (Debian 2.6.18-1snapshot.7526) ([EMAIL PROTECTED]) (gcc version 4.1 .2 20060814 (prerelease) (Debian 4.1.1-11-2)) #1 SMP Tue Sep 26 06:46:53 UTC 2006 <-snip-> Sep 26 17:14:19 dxsfw-dc01 kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 0168 Sep 26 17:14:19 dxsfw-dc01 kernel: printing eip: Sep 26 17:14:19 dxsfw-dc01 kernel: f8a7a760 Sep 26 17:14:19 dxsfw-dc01 kernel: *pde = Sep 26 17:14:19 dxsfw-dc01 kernel: Oops: [#1] Sep 26 17:14:19 dxsfw-dc01 kernel: SMP Sep 26 17:14:19 dxsfw-dc01 kernel: Modules linked in: xt_state xt_tcpudp iptable_mangle iptable_nat iptable_filter ip_tables x_t ables ip_nat_ftp ip_nat ip_conntrack_ftp ip_conntrack nfnetlink button ac battery dm_snapshot dm_mirror 8021q bonding ide_disk i de_cd cdrom intel_rng psmouse usbhid serio_raw evdev joydev tsdev pcspkr ehci_hcd uhci_hcd usbcore e1000 tg3 thermal processor f an mptsas mptscsih mptbase scsi_transport_sas dm_mod sd_mod shpchp pci_hotplug piix ata_piix libata scsi_mod ide_generic ide_cor e raid1 raid0 md_mod ext3 jbd mbcache Sep 26 17:14:19 dxsfw-dc01 kernel: CPU:0 Sep 26 17:14:19 dxsfw-dc01 kernel: EIP:0060:[]Not tainted VLI Sep 26 17:14:19 dxsfw-dc01 kernel: EFLAGS: 00010297 (2.6.18-1-686 #1) Sep 26 17:14:19 dxsfw-dc01 kernel: EIP is at bond_netdev_event+0x51/0x74 [bonding] Sep 26 17:14:19 dxsfw-dc01 kernel: eax: ebx: f89732c4 ecx: f7d8ec00 edx: 0005 Sep 26 17:14:19 dxsfw-dc01 kernel: esi: f8a88fc0 edi: f7d8ec00 ebp: 0005 esp: f78f7ec4 Sep 26 17:14:19 dxsfw-dc01 kernel: ds: 007b es: 007b ss: 0068 Sep 26 17:14:19 dxsfw-dc01 kernel: Process vconfig (pid: 3331, ti=f78f6000 task=dff8cab0 task.ti=f78f6000) Sep 26 17:14:19 dxsfw-dc01 kernel: Stack: f89732c4 c012848b f7d8ec00 c037dc18 c037d8e0 c0226f07 0001 Sep 26 17:14:19 dxsfw-dc01 kernel:0001 f7d8ec00 dff100de f7d8ecde dff1 f896f634 002c Sep 26 17:14:19 dxsfw-dc01 kernel:31687465 002c Sep 26 17:14:19 dxsfw-dc01 kernel: Call Trace: Sep 26 17:14:19 dxsfw-dc01 kernel: [] notifier_call_chain+0x19/0x32 Sep 26 17:14:19 dxsfw-dc01 kernel: [] register_netdevice+0x2b4/0x2bd Sep 26 17:14:19 dxsfw-dc01 kernel: [] vlan_ioctl_handler+0x347/0x53f [8021q] Sep 26 17:14:19 dxsfw-dc01 kernel: [] sock_ioctl+0x13f/0x1b5 Sep 26 17:14:19 dxsfw-dc01 kernel: [] sock_ioctl+0x0/0x1b5 Sep 26 17:14:19 dxsfw-dc01 kernel: [] do_ioctl+0x1c/0x5d Sep 26 17:14:19 dxsfw-dc01 kernel: [] vfs_ioctl+0x24a/0x25c Sep 26 17:14:19 dxsfw-dc01 kernel: [] sys_ioctl+0x48/0x5f Sep 26 17:14:19 dxsfw-dc01 kernel: [] sysenter_past_esp+0x56/0x79 Sep 26 17:14:19 dxsfw-dc01 kernel: Code: f8 e8 50 5a 6b c7 89 d8 e8 b2 4c 00 00 89 d8 e8 2e 56 00 00 b8 54 97 a8 f8 e8 6b 5a 6b c7 eb 2a f6 c4 08 74 25 8b 41 70 83 fa 06 <8b> 98 68 01 00 00 74 07 83 fa 0b 75 12 eb 09 89 ca e8 cf fc ff Sep 26 17:14:19 dxsfw-dc01 kernel: EIP: [] bond_netdev_event+0x51/0x74 [bonding] SS:ESP 0068:f78f7ec4 George. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387460: linux-image-2.6.17-2-686: kernel panic when trying to add vlan to a slave bonded interface
On 14/09/06, maximilian attems <[EMAIL PROTECTED]> wrote: blaeh, please try to reproduce with current trunk: http://wiki.debian.org/DebianKernel Any one in particular (2.6.17 or the 2.6.18 RC builds)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387460: linux-image-2.6.17-2-686: kernel panic when trying to add vlan to a slave bonded interface
Package: linux-image-2.6.17-2-686 Version: 2.6.17-8 Severity: important Hello, I managed to get a kernel panic when I tried to add a vlan to one of the slave interfaces in a bond. :-( With hindsight I probably shouldn't have tried it, but crashes are bad, so reporting it now. Snip from /var/log/kern.log --- Sep 14 14:37:20 dxsfw-dc01 kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 0148 Sep 14 14:37:20 dxsfw-dc01 kernel: printing eip: Sep 14 14:37:20 dxsfw-dc01 kernel: f0a6d75d Sep 14 14:37:20 dxsfw-dc01 kernel: *pde = Sep 14 14:37:20 dxsfw-dc01 kernel: Oops: [#1] Sep 14 14:37:20 dxsfw-dc01 kernel: SMP Sep 14 14:37:20 dxsfw-dc01 kernel: Modules linked in: button ac battery dm_snapshot dm_mirror 8021q bonding ide_disk ide_cd cdrom mousedev tsdev evdev psmouse hw_random 8250_pnp serio_raw pcspkr usbhid ehci_hcd uhci_hcd e1000 tg3 usbcore thermal processor fan mptsas mptscsih mptbase scsi_transport_sas dm_mod sd_mod shpchp pci_hotplug piix ata_piix libata scsi_mod ide_generic ide_core raid1 raid0 md_mod ext3 jbd mbcache Sep 14 14:37:20 dxsfw-dc01 kernel: CPU:1 Sep 14 14:37:20 dxsfw-dc01 kernel: EIP:0060:[]Not tainted VLI Sep 14 14:37:20 dxsfw-dc01 kernel: EFLAGS: 00210297 (2.6.17-2-686 #1) Sep 14 14:37:20 dxsfw-dc01 kernel: EIP is at bond_netdev_event+0x67/0x8b [bonding] Sep 14 14:37:20 dxsfw-dc01 kernel: eax: ebx: f0a7bfc0 ecx: b1aa2000 edx: 0005 Sep 14 14:37:20 dxsfw-dc01 kernel: esi: b1aa2000 edi: 0005 ebp: b0369b80 esp: ee997ec0 Sep 14 14:37:20 dxsfw-dc01 kernel: ds: 007b es: 007b ss: 0068 Sep 14 14:37:20 dxsfw-dc01 kernel: Process vconfig (pid: 5201, threadinfo=ee996000 task=dffb6580) Sep 14 14:37:20 dxsfw-dc01 kernel: Stack: f0a7bfc0 b1aa2000 b0126d43 b1aa2000 b0369ebc b021bd52 0001 Sep 14 14:37:20 dxsfw-dc01 kernel:0001 b1aa2000 ef47a0de b1aa20de ef47a000 f09f6636 b013d1b4 002c Sep 14 14:37:20 dxsfw-dc01 kernel: 31687465 002c Sep 14 14:37:20 dxsfw-dc01 kernel: Call Trace: Sep 14 14:37:20 dxsfw-dc01 kernel: notifier_call_chain+0x15/0x2e register_netdevice+0x2a6/0x2af Sep 14 14:37:20 dxsfw-dc01 kernel: vlan_ioctl_handler+0x349/0x553 [8021q] filemap_nopage+0x194/0x2f0 Sep 14 14:37:20 dxsfw-dc01 kernel: sock_ioctl+0x13f/0x1b5 sock_ioctl+0x0/0x1b5 Sep 14 14:37:20 dxsfw-dc01 kernel: do_ioctl+0x1c/0x5d vfs_ioctl+0x24a/0x25c Sep 14 14:37:20 dxsfw-dc01 kernel: sys_ioctl+0x48/0x5f sysenter_past_esp+0x54/0x75 Sep 14 14:37:20 dxsfw-dc01 kernel: Code: f0 e8 ec 4c 00 00 89 f0 e8 16 57 00 00 89 d8 ba ff ff 00 00 f0 0f c1 10 0f 85 d9 14 00 00 eb 2a f6 c4 08 74 25 8b 41 70 83 fa 06 <8b> 98 48 01 00 00 74 07 83 fa 0b 75 12 eb 09 89 ca e8 b9 fc ff Sep 14 14:37:20 dxsfw-dc01 kernel: EIP: [] bond_netdev_event+0x67/0x8b [bonding] SS:ESP 0068:ee997ec0 --- HTH, George B. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.78 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i686 2.3.6.ds1-4 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false lin
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
On 04/09/06, Eito Tamura <[EMAIL PROTECTED]> wrote: Hi George, I am having the same problem as you did. So installing ampd package didn't fix the problem? Just those crappy HDD problem? Upgrading kernel might fix this problem? Hello, The problem is still there, although it does not occur very often (once every few months or so). The few machines that still have those HDDs have the latest Sarge 2.6.8-3 kernel, acpid, DMA disabled, drive power management disabled (through hdparm). To be honest though, we have swapped out the HDDs on most of them for Compact Flash cards and those machines they have been rock solid since. I don't know if the Etch / Sid kernels will fix this, as I never got around trying this out (being firewalls, running Stable is a requirement really). I probably should, since Etch is due in a few months. If you try this, feel free to let me know how it went. HTH, George. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
Just to let you know that the 'fix' did not work. :-( The hard drives will still randomly go to sleep and not wake up. What's more, even a sysrq forced reboot does not wake the drive up - only a cold boot works! The end result is that we are gradually replacing these crappy disks in our firewalls with CompactFlash disks.
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
I think I finally fixed the problem by installing the apmd package. :-\ The problem was, I am guessing, that the hard drive went to sleep at some random time (despite it being explicitly told not to in the BIOS) and regardless of the disk activity (so even my 15 min dd cronjob did not fix it) and nothing was there to detect it and tell the system that the drive was not dead, but just sleeping. I'm not sure what apmd does when the drive goes to sleep, but it seems to do something useful. Anyway, not a kernel bug (unless you think it should have managed without apmd,) so please close this and sorry to have wasted your time. George.
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
P.S. I could try unloading the ide-generic module etc. if you think that's a good idea.
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
On 01/11/05, Horms <[EMAIL PROTECTED]> wrote: > Is there any chance that #336103 is related to this? > > http://bugs.debian.org/336103 Hmm, don't think so. In my case I had no trouble turning DMA on (in fact, I disabled it yesterday with hdparm just to see if it would make any difference - it will take a few weeks before I can draw any conclusions.) George.
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
On 27/10/05, Horms <[EMAIL PROTECTED]> wrote: > > Ok, that does sound like fair resoning, though I should > say that almost always these kind of errors show up faulty hardware. > In this case, its probably a bug. Don't get me wrong, I think may well be faulty hardware, but a general fault rather than with a specific unit. Unfortunately as such this would be way over my head. Just for the record, the hdparm -b 255 hack did not work on at least one of the machines and neither did a 15 min cronjob of dd if=/dev/hdc of=/dev/null bas=1024 count=3000 seek=1000 > /dev/null :-( One of the firewalls I still haven't rebooted, one died last night and the other is still alive for the moment. The only thing that all these boxes have in common (apart from identical HDDs, but one had a different one before) is a VIA chipset. How likely is it that there's a bug either in that, or the driver for it? I am very confused :-(
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
> > Your disks are failing, get new ones if you value your data. I'm afraid I will have to disagree with you on this one. All of the disks were brand new and the problem started showing up after a few days/weeks after assembly. Also, one of the firewalls had a different (3.5") drive in it before, that displayed similar symptoms. Thinking the disk was dying I swapped it, only to have the problem come back. (The 3.5" drive is being happily used by my brother now, with no problems whatsoever.) Also, 3 out of 3 is a bit high failure rate... George B.
Bug#335538: kernel-image-2.6.8-2-386: Hard drive locks up - DMA or Power Management problem?
01:~# mount /dev/hdc1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/hdc3 on /home type ext3 (rw) /dev/hdc5 on /var type ext3 (rw) /dev/hdc6 on /home/adm type ext3 (rw) usbfs on /proc/bus/usb type usbfs (rw) fwbox01:~# dmesg > /home/dmesg.txt -bash: /home/dmesg.txt: Read-only file system fwbox01:~# mount /dev/hdc1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/hdc3 on /home type ext3 (rw) /dev/hdc5 on /var type ext3 (rw) /dev/hdc6 on /home/adm type ext3 (rw) fwbox01:~# hd hd hdparm fwbox01:~# hdparm -bash: /sbin/hdparm: Input/output error fwbox01:/proc/sys/kernel# cat panic 20 fwbox01:/proc/sys/kernel# cat panic_on_oops 0 fwbox01:/proc/sys/kernel# echo 1 > panic_on_oops -r--r--r-- 1 rootroot0 2005-10-21 17:24 version -r--r--r-- 1 rootroot0 2005-10-21 17:24 vmstat fwbox01:/proc# echo diemotherfucker > kcore fwbox01:/proc# fwbox01:/proc# fwbox01:/proc# fwbox01:/proc# cat /dev/hdc > kcore cat: /dev/hdc: Input/output error fwbox01:/proc# cat /dev/random > kcore fwbox01:/dev# ls *mem kmem mem fwbox01:/dev# cat /dev/zero > kmem --- The initial DMA error messages appear now and again, and seem to be harmless (but also PM related) then it all goes wrong after a few weeks running. :-( I will be happy to privide more specific information, if you tell me how to get it. I don't really know much about hardware/kernel debugging. HTH, George B. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.8-2-386 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323570: kernel-source-2.4.27: Build fails with default gcc 4.0
On 8/19/05, Horms <[EMAIL PROTECTED]> wrote: > On Thu, Aug 18, 2005 at 01:05:10PM +0100, George B. wrote: > > On 8/18/05, Horms <[EMAIL PROTECTED]> wrote: > > > > > > > > > Yes, it should do just that. > > > > Sorry, which one? Automatically use gcc-3.3, or default to gcc-4.0? > > Sorry for being unclear. If you build kernel-source-2.4.27 2.4.27-11 > then it should use gcc-3.3 for the build, even if your default > gcc is gcc-4.0. To be more specific, if you inspect the makefile > you will see that it actually sets the compiler to be gcc-3.3, > rather than gcc. > > Of course if you use a different Makefile, say to build > out of tree modules, or force the compiler to something else, > this system breaks down. I'm not sure there is a good solution to > that problem. But unpacking the kernel-source tar ball and doing > a build should work as long as you have gcc-3.3 installed, > which is a recomendation of the package. Well, if it fails when building a module I will just go and bug the maintaner for that module source. ;-) Thanks for your help. George.
Bug#323570: kernel-source-2.4.27: Build fails with default gcc 4.0
On 8/18/05, Horms <[EMAIL PROTECTED]> wrote: > > > Yes, it should do just that. Sorry, which one? Automatically use gcc-3.3, or default to gcc-4.0?
Bug#323570: kernel-source-2.4.27: Build fails with default gcc 4.0
On 8/17/05, Thiemo Seufer <[EMAIL PROTECTED]> wrote: > > The 2.4.27-11 uploaded today depends on gcc-3.3 and should solve that > problem. (It is not yet installed in the archive but available from > http://packages.vergenet.net/pending/ ) :-) Will it automatically use gcc-3.3 when compiling? With me it defaulted to gcc-4.0. George.
Bug#323570: kernel-source-2.4.27: Build fails with default gcc 4.0
Package: kernel-source-2.4.27 Version: 2.4.27-10 Severity: important *** Please type your report below this line *** Hello, Submitting as promised in #31763. The package depends on non-specific gcc. This is now gcc 4.0 by default. As discussed in #317637, build will fail unless gcc 3.2 is used. Possible solutions: 1) Specific dependency on gcc 3.2. The problem is that /usr/bin/gcc may well be linked to /usr/bin/gcc-4.0, as this is now required by quite a few programs. I know that I had to manually re-symlink /usr/bin/gcc to gcc-3 (not sure if it was 3.2, or 3.3 - sorry) in order to get it to compile. I know that there is some sort of variable I could pass when building, but I could not get that to work bor some reason. 2) Get it to build with 4.0 :-p HTH, George B. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27.20050707 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kernel-source-2.4.27 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities Versions of packages kernel-source-2.4.27 recommends: ii gcc 4:4.0.0-2 The GNU C compiler ii libc6-dev [libc-dev] 2.3.5-3GNU C Library: Development Librari ii make 3.80-9 The GNU version of the "make" util -- no debconf information
Bug#317637: kernel-source-2.4.27: kernel compile fails :-(
On 7/10/05, Horms <[EMAIL PROTECTED]> wrote: > > It looks a lot like you are trying to build this kernel with gcc-4.0. > This will not work. Please use gcc-3.2. Perhaps a dependency/conflict entry needs to be assigned to the package, because it broke after a standard package upgrade. I will resubmit a new bug for that. > Also, if you think there are outstanding security issues with this > kernel, pleaese file bugs against kernel-source-2.4.27, and include > any references to CAN numbers, mailing list discusions and best of > all patches, that you have. Oops, I think you misunderstood. It's just that I am running an older version of 2.4.27 kernel that has security issues (which is why I was upgrading.) ;-) HTH, George B.
Bug#317637: kernel-source-2.4.27: kernel compile fails :-(
.4.27/include/asm/processor.h:75: error: array type has incomplete element type In file included from /usr/src/kernel-source-2.4.27/include/linux/unistd.h:9, from init/main.c:17: /usr/src/kernel-source-2.4.27/include/asm/unistd.h:375: warning: conflicting typ es for built-in function '_exit' make[1]: *** [init/main.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.4.27' make: *** [stamp-build] Error 2 --- A attach my kernel .config file. HTH, George B. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kernel-source-2.4.27 depends on: ii binutils 2.15-7 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities Versions of packages kernel-source-2.4.27 recommends: ii gcc 4:4.0.0-2The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the "make" util -- no debconf information # # Automatically generated make config: don't edit # CONFIG_X86=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_X86_HAS_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_F00F_WORKS_OK=y CONFIG_X86_MCE=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_HIGHMEM is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_BIGPHYS_AREA is not set # CONFIG_SMP is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_UP_IOAPIC is not set # CONFIG_X86_TSC_DISABLE is not set CONFIG_X86_TSC=y # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_ISA=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # CONFIG_PCMCIA=m CONFIG_CARDBUS=y # CONFIG_TCIC is not set # CONFIG_I82092 is not set # CONFIG_I82365 is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # CONFIG_HOTPLUG_PCI_COMPAQ is not set # CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set # CONFIG_HOTPLUG_PCI_SHPC is not set # CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set # CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY is not set # CONFIG_HOTPLUG_PCI_PCIE is not set # CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m # CONFIG_OOM_KILLER is not set CONFIG_PM=y CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y CONFIG_APM_CPU_IDLE=y # CONFIG_APM_DISPLAY_BLANK is not set CONFIG_APM_RTC_IS_GMT=y # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # ACPI Support # # CONFIG_ACPI is not set # CONFIG_OPTIMISE_SIZE is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_CML1=m CONFIG_PARPORT_SERIAL=m CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_PC_PCMCIA is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_GSC is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_IP22 is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # # Block devices # CONFI
