Bug#623808: Please activate RT33XX options
Package: linux-2.6 Version: 2.6.38-3 Severity: wishlist Tags: sid Hi, As there was not follow-up on my email to the list, I'm sending this bug report, in the hope that it will bring attention to the kernel team. I have an old laptop with a bad internal WiFi board, so I bought a newer RaLink driver. To make it work, I had to add the option rt2800usb - Include support for rt33xx devices (EXPERIMENTAL) and rt2800usb - Include support for rt35xx devices (EXPERIMENTAL). These are not activated in your build (I've just checked). I believe that one of the most important point of running a backported kernel is to have such drivers for newer hardware. Could you please include the option above? The options to activate are as below: CONFIG_RT2800PCI_RT33XX CONFIG_RT2800PCI_RT35XX CONFIG_RT2800USB_RT33XX CONFIG_RT2800USB_RT35XX If you include the above options, I'll be able to test your backport instead of the quick and dirty one that I did myself. Thanks, and keep-up the good work, Thomas Goirand (zigo) -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110423073521.4668.34214.report...@buzig.gplhost.com
Re: building 2.6.26 kernel source fails on squeeze
On Tue, 19 Apr 2011, Ben Hutchings wrote: On Tue, 2011-04-19 at 02:41 +0530, Faheem Mitha wrote: [...] If I understand this correctly, altering the config changes the kernel ABI. Sometimes. If an exported function is conditional on CONFIG_FOO, or it uses a type whose definition depends on CONFIG_FOO, then turning CONFIG_FOO on or off changes the ABI of that function, and thus of the kernel as a whole. Enabling or changing the configuration of a single driver usually doesn't change the ABI, because most drivers don't export anything. Question: wouldn't patching the kernel also change the ABI? Sometimes, yes. Therefore it is required to also change the ABI name, otherwise this is detected by the build process (Question: how does it do this?) which aborts. The kernel build process generates a 'symbol version' for each exported function or variable. This is a hash of the definitions that it depends on, and should change whenever the function's ABI changes. The kernel module loader detects incompatible modules by comparing symbol versions. The whole set of symbol versions represents the kernel ABI. We collect the symbol versions for previously uploaded packages under the directory debian/abi and then compare the new kernel with those. If the ABI name is unchanged but the ABI itself is changed - except for additions, or changes that we have marked as acceptable - then the build is aborted, as you saw. I see. I advocate having something like this in the kernel documenation. Currently it is just a list of commands to type, and some background explanation would be helpful. So I set 'abiname: custom1.0' and ran fakeroot debian/rules debian/control-real and then fakeroot debian/rules source fakeroot make -f debian/rules.gen binary-arch_i386_none_686 BTW, what does fakeroot debian/rules source do? Copies and patches the upstream source. Mention this too. The resulting kernel package looks like linux-image-2.6.26-custom1.0-686-bigmem_2.6.26-26lenny1_i386.deb. I get warnings of the form Compatibility levels before 5 are deprecated. See extract from build log below. Does this mean it expected the abiname to start with 5, for some reason? No, this is a warning from debhelper. Ah, Ok. debhelper wants debian/compat to be 5? I've attempted to document this, since it currently does not appear to be. See patch to kernel handbook below. I'm sure I'm made errors, so corrections, please. [...] Thanks. I'll apply something like that, but change 'is necessary' to 'may be necessary. I'll review your patch. Addendum: I get this error when trying to install dpkg: dependency problems prevent configuration of linux-headers-2.6.26-custom1.0-686-bigmem: linux-headers-2.6.26-custom1.0-686-bigmem depends on linux-headers-2.6.26-custom1.0-common (= 2.6.26-26lenny1); however: Package linux-headers-2.6.26-custom1.0-common is not installed. dpkg: error processing linux-headers-2.6.26-custom1.0-686-bigmem (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-2.6.26-custom1.0-686-bigmem The debian packaging does not generate this linux-header common package. It does, just not with the rule you used. You'll have to use: make -f debian/rules.gen binary-arch_i386_none_real I tried this, and it produces linux-headers-2.6.26-custom1.0-common_2.6.26-26lenny1_i386.deb in contrast with the original command fakeroot make -f debian/rules.gen binary-arch_i386_none_686 which produces the header and linux-image packages. Is the general syntax target_arch_featureset_real ? Why 'real'? Is this produced by a separate command because it doesn't need to be regenerated every time? It would be simpler if it was produced along with the header and linux image packages with fakeroot make -f debian/rules.gen binary-arch_i386_none_686 imo. In any case, this should also be added to the documentation. I'll attempt updates to your patch. Regards, Faheem -- 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/alpine.deb.2.00.1104231345330.16...@orwell.homelinux.org
Bug#600656: linux-image-2.6.32-5-amd64: Crash after nullpointer dereference during gparted reading a disk
Hi Moritz, I just tried using the following kernel: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 This time, the reading stage of gparted was completed successfully, but during the actual right-shift of the partition, the following oops occurred. The system is yet running, but the gparted process is hanging (so, now I must do what probably would have been the easiest solution anyway, re-creating the partition from scratch). But of course it would be interesting to have an indication if e.g. the hard disc is broken, or the PATA controller? Best regards, Andreas. Apr 23 03:04:47 myserver kernel: [ 7637.393410] PGD af0f9067 PUD b1e6d067 PMD 0 Apr 23 03:04:47 myserver kernel: [ 7637.393434] CPU 1 Apr 23 03:04:47 myserver kernel: [ 7637.393437] Modules linked in: tcp_diag inet_diag ppdev lp cpufreq_conservative cpufreq_stats capifs snd_hrtimer uinput binfmt_misc fuse ext4 jbd2 crc16 it87 hwmon_vid eeprom cpufreq_userspace cpufreq_powersave powernow_k8 mperf psmouse ide_generic ide_gd_mod ide_cd_mod ide_core dm_crypt dm_mod nvidia(P) joydev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm em28xx v4l2_common videodev ir_lirc_codec lirc_dev ir_sony_decoder snd_seq_midi ir_jvc_decoder snd_rawmidi ir_rc6_decoder ir_rc5_decoder snd_seq_midi_event snd_seq edac_core ir_nec_decoder snd_timer snd_seq_device snd v4l2_compat_ioctl32 videobuf_vmalloc videobuf_core rc_core tveeprom soundcore evdev pcspkr k8temp edac_mce_amd serio_raw tpm_tis tpm tpm_bios snd_page_alloc i2c_nforce2 parport_pc parport i2c_core processor button thermal_sys ext3 jbd mbcache hid_cherry usbhid hid sg sr_mod cdrom sd_mod crc_t10dif ata_generic ohci_hcd pata_amd sata_nv libata ehci_hcd usbcore firewire_ohci scsi_mod floppy Apr 23 03:04:47 myserver kernel: firewire_core forcedeth crc_itu_t nls_base [last unloaded: scsi_wait_scan] Apr 23 03:04:47 myserver kernel: [ 7637.393577] Apr 23 03:04:47 myserver kernel: [ 7637.393584] Pid: 1276, comm: flush-8:0 Tainted: P O 2.6.38-2-amd64 #1/GA-K8NF-9-RH Apr 23 03:04:47 myserver kernel: [ 7637.393595] RIP: 0010:[8111b18b] [8111b18b] __block_write_full_page+0xc7/0x2b5 Apr 23 03:04:47 myserver kernel: [ 7637.393607] RSP: 0018:8800b11c1ab0 EFLAGS: 00010293 Apr 23 03:04:47 myserver kernel: [ 7637.393612] RAX: 7470656e RBX: ea2a36b0 RCX: 0003 Apr 23 03:04:47 myserver kernel: [ 7637.393618] RDX: 0009 RSI: ea2a36b0 RDI: 8800bc3200e0 Apr 23 03:04:47 myserver kernel: [ 7637.393624] RBP: 8800bc3200e0 R08: 8111a0b1 R09: 000167d0 Apr 23 03:04:47 myserver kernel: [ 7637.393630] R10: R11: 0018 R12: 8800b11c1d30 Apr 23 03:04:47 myserver kernel: [ 7637.393635] R13: 002b R14: 88002bcd8410 R15: 8111a0b1 Apr 23 03:04:47 myserver kernel: [ 7637.393643] FS: 7f808980() GS:8800bfd0() knlGS: Apr 23 03:04:47 myserver kernel: [ 7637.393649] CS: 0010 DS: ES: CR0: 8005003b Apr 23 03:04:47 myserver kernel: [ 7637.393654] CR2: 002b CR3: b17e CR4: 06e0 Apr 23 03:04:47 myserver kernel: [ 7637.393660] DR0: DR1: DR2: Apr 23 03:04:47 myserver kernel: [ 7637.393666] DR3: DR6: 0ff0 DR7: 0400 Apr 23 03:04:47 myserver kernel: [ 7637.393673] Process flush-8:0 (pid: 1276, threadinfo 8800b11c, task 8800b91e5e80) Apr 23 03:04:47 myserver kernel: [ 7637.393681] 0200 3ea1e3f8 7470656e 0001b11c1bf8 Apr 23 03:04:47 myserver kernel: [ 7637.393691] 8111d2c4 0200 8800bc320228 8800bc320228 Apr 23 03:04:47 myserver kernel: [ 7637.393701] 8800b11c1d30 8800bc320228 Apr 23 03:04:47 myserver kernel: [ 7637.393721] [8111d2c4] ? blkdev_get_block+0x0/0x5b Apr 23 03:04:47 myserver kernel: [ 7637.393730] [810bbfee] ? __writepage+0xa/0x21 Apr 23 03:04:47 myserver kernel: [ 7637.393738] [810bd1a4] ? write_cache_pages+0x221/0x321 Apr 23 03:04:47 myserver kernel: [ 7637.393745] [810bbfe4] ? __writepage+0x0/0x21 Apr 23 03:04:47 myserver kernel: [ 7637.393754] [8100a30e] ? apic_timer_interrupt+0xe/0x20 Apr 23 03:04:47 myserver kernel: [ 7637.393764] [81113875] ? writeback_single_inode+0x91/0x18c Apr 23 03:04:47 myserver kernel: [ 7637.393773] [81113cc3] ? writeback_sb_inodes+0x91/0x104 Apr 23 03:04:47 myserver kernel: [ 7637.393781] [81114526] ? writeback_inodes_wb+0xfd/0x10f Apr 23 03:04:47 myserver kernel: [ 7637.393789] [8111474a] ? wb_writeback+0x212/0x316 Apr 23 03:04:47 myserver kernel: [ 7637.393797] [81114a29] ? wb_do_writeback+0x1db/0x1fb Apr 23
Processed: severity of 619877 is important
Processing commands for cont...@bugs.debian.org: severity 619877 important Bug #619877 [nfs-common] rpc.mountd: svc_tli_create: could not bind to requested address Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 619877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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.130354922831109.transcr...@bugs.debian.org
Bug#622337: More info
I just noticed an interesting aspect of this bug. I was running kernel 2.6.38-2-amd64 for a couple of hours while connected to mains power and the mouse was working perfectly. I then unplugged the power and moved to the couch. With a couple of minutes the mouse problem recurred. There is obviously a connection between the mouse problem and running on laptop battery power. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- 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/20110423190952.ae7212d5.er...@mega-nerd.com
Bug#581525: rt2860: rt2860 doesn't connect to WPA2 networks
It seems it was due to a conflict between the rt2870sta and the rt2800pci modules. Blacklisting rt2870sta solved the problem (both in Debian an Ubuntu). Sorry for not asking to close the bug report before. Thanks! 2011/4/22 Moritz Mühlenhoff j...@inutil.org tags 581525 moreinfo thanks On Thu, May 13, 2010 at 02:31:34PM +0200, Miguel Angel Fraile wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: important File: rt2860 It seems it's not possible to connect to WPA2 wireless networks with the squeezix version of the rt2860 module. I've tested it with both network-manager and wicd. Both of them are unable to authenticate with the correct password. Both have NO problems to connect to WPA-PSK networks. Tested with a Buffalo WZR-HP-G300NH router. No problem connecting to that WPA2 network with other devices. The router encryption is set to WPA/WPA2-Mixed TKIP+AES, using a preshared key. Tested also after updating the rt2860 firmware-ralink to the Debian SID version (v0.24). No luck, either. Does this still occur with the final Squeeze kernel or more recent kernels? Cheers, Moritz
Bug#607416: Device table incorrect for drivers/s390/block/dasd_eckd.c: 3880/3390 should be 3880/3380
On Fri, 22 Apr 2011 23:09:50 -0400 (EDT), Jonathan Nieder wrote: If you run git log dd30ac3 --grep='dasd: correct device table', then the fix will show up: commit 5da24b7627ff821e154a3aaecd5d60e1d8e228a5 Author: Stefan Haberland stefan.haberl...@de.ibm.com Date: Thu Feb 17 13:13:55 2011 +0100 [S390] dasd: correct device table The 3880 storage control unit supports a 3380 device type, but not a 3390 device type. Reported-by: Stephen Powell zlinux...@wowway.com Signed-off-by: Stefan Haberland stefan.haberl...@de.ibm.com Signed-off-by: Martin Schwidefsky schwidef...@de.ibm.com ... Presumably that (5da24b76) is the commit to backport; I am not sure which kernels it applies to. Thanks for the information, Jonathan. I'm afraid I don't know much about git, and my ignorance is showing. What I do know how to use is the Linux cross reference at http://lxr.linux.no/+trees, and by using that it appears that this bug, in some form, goes all the way back to day 1. All supported stable kernels will no doubt contain the bug, though the line numbers in the patch may need to be adjusted from one release to the next. It is a very simple one-line change. So, stable, I hereby respectfully request that the above-mentioned bug fix be backported to the supported stable kernel releases. Personally, I am most interested in the 2.6.32 kernel, as that is the basis for Debian Squeeze. -- .''`. Stephen Powell : :' : `. `'` `- -- 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/2113607793.121790.1303564219125.javamail.r...@md01.wow.synacor.com
Bug#623840: linux-image-2.6.38-2-amd64: no sound via headphones
Package: linux-2.6 Version: 2.6.38-2 Severity: normal Afer upgrading to 2.6.38, no sound comes out of headphones plugged into my headphones jack. It worked with 2.6.32-5-amd64. I'm using a Satellite T115D Here's the relevent lspci output: 0 jamie@chicken:~$ sudo lspci -vv -s 00:14.2 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: Toshiba America Info Systems Device ffe2 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin ? routed to IRQ 16 Region 0: Memory at f060 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: HDA Intel 0 jamie@chicken:~$ sudo lspci -vv -s 01:05.1 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller Subsystem: ATI Technologies Inc Device 9612 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: 32 bytes Interrupt: pin B routed to IRQ 19 Region 0: Memory at cfdec000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Kernel driver in use: HDA Intel 0 jamie@chicken:~$ amixer shows no controls for the headphone jack: Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined penum Playback channels: Front Left - Front Right Limits: Playback 0 - 74 Mono: Front Left: Playback 74 [100%] [0.00dB] [on] Front Right: Playback 74 [100%] [0.00dB] [on] Simple mixer control 'PCM',0 Capabilities: pvolume penum Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 255 [100%] [0.00dB] Front Right: Playback 255 [100%] [0.00dB] Simple mixer control 'Mic B',0 Capabilities: cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] Simple mixer control 'Mic C',0 Capabilities: cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] Simple mixer control 'Mic E',0 Capabilities: cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] Simple mixer control 'Mic F',0 Capabilities: cswitch cswitch-joined cswitch-exclusive penum Capture exclusive group: 0 Capture channels: Mono Mono: Capture [on] Simple mixer control 'Beep',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 7 Mono: Playback 6 [86%] [-4.00dB] [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 80 Front Left: Capture 80 [100%] [6.00dB] [on] Front Right: Capture 80 [100%] [6.00dB] [on] Simple mixer control 'Analog Mic Boost',0 Capabilities: cenum Items: '0dB' '10dB' '20dB' '30dB' '40dB' Item0: '40dB' Simple mixer control 'Digital',0 Capabilities: cvolume penum Capture channels: Front Left - Front Right Limits: Capture 0 - 120 Front Left: Capture 79 [66%] [9.50dB] Front Right: Capture 79 [66%] [9.50dB] -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-2) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-14) ) #1 SMP Tue Mar 29 16:45:36 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=/dev/mapper/vg_chicken0-root ro quiet ** Tainted: WC (1536) * Taint on warning. * Module from drivers/staging has been loaded. ** Kernel log: [770848.178002] sd 0:0:0:0: [sda] Stopping disk [770848.184943] HDA Intel :00:14.2: PCI INT A disabled [770848.757487] ahci :00:11.0: PCI INT A disabled [770849.079793] [drm] Disabling audio support [770849.199512] radeon :01:05.0: PCI INT A disabled [770849.212089] PM: suspend of devices complete after 1211.711 msecs [770849.212252] atl1c :08:00.0: PME# enabled [770849.212443] pcieport :00:05.0: wake-up capability enabled by ACPI [770849.260295] PM: late suspend of devices complete after 48.200 msecs [770849.260406] ACPI: Preparing to enter system sleep state S3 [770849.348151] PM: Saving platform NVS memory [770849.348200] Disabling non-boot CPUs ... [770849.348200] Back to C! [770849.348200] PM: Restoring platform NVS memory [770849.348200] ACPI: Waking up from
Bug#579858: marked as done (xserver-xorg-video-nouveau: X fails to find nouveau device)
Your message dated Sat, 23 Apr 2011 21:46:49 +0530 with message-id 4db2fb71.4060...@debian.org and subject line Re: xserver-xorg-video-nouveau: X fails to find nouveau device has caused the Debian Bug report #579858, regarding xserver-xorg-video-nouveau: X fails to find nouveau device 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.) -- 579858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-nouveau Version: 1:0.0.15+git20100329+7858345-3 Severity: important Hi, I have been trying to configure nouveau for my nvidia card but looks like I have a very preliminary problem for which I did not find a solution yet. X fails complaining that it could not find any of the device in /dev/dri/cardN On my box, even with nvidia.ko loaded, I do not have the /dev/dri/ folder at all. Any ideas on where I should start investigating ? I did manually load the nouveau.ko driver as it does not autoload. Is it because of a missing udev rule ? Regards, Ritesh -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Nov 2 19:06 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1725368 Apr 19 23:47 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: nVidia Corporation G72M [GeForce Go 7400] (rev a1) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 126 May 1 23:17 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # Minimal xorg.conf for the Nouveau driver Section Device Identifier Default screen Driver nouveau EndSection Kernel version (/proc/version): Linux version 2.6.32-4-686 (Debian 2.6.32-11) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Tue Apr 6 07:02:27 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 8119 May 1 23:30 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.7.6.901 (1.7.7 RC 1) Release Date: 2010-04-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 i686 Debian Current Operating System: Linux learner 2.6.32-4-686 #1 SMP Tue Apr 6 07:02:27 UTC 2010 i686 Kernel command line: root=/dev/mapper/VgSD3-ROOT ro Build Date: 19 April 2010 06:12:31PM xorg-server 2:1.7.6.901-3 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat May 1 23:30:20 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No device specified for screen Default Screen Section. Using the first device section listed. (**) | |--Device Default screen (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi does not exist. Entry deleted from font path.
Re: building 2.6.26 kernel source fails on squeeze
Hi Ben, On Tue, 19 Apr 2011, Ben Hutchings wrote: On Tue, 2011-04-19 at 05:00 +0100, Ben Hutchings wrote: [...] I've attempted to document this, since it currently does not appear to be. See patch to kernel handbook below. I'm sure I'm made errors, so corrections, please. [...] Thanks. I'll apply something like that, but change 'is necessary' to 'may be necessary. I ended up making some more changes and included the new text in the 'applying patches' section. Do you think this covers it? Ben. I've made some more changes - mostly additions - to your patch. I've included your ABI comments almost verbatim, because I think they are interesting and it is useful for people to have an idea of what is going on. If you disagree, of course please feel free to remove them, or indeed make any suitable changes or clarifications you think are necessary. Thank you for your assistance with this. It has been most helpful. Regards, Faheem diff -r 657cba972ce9 -r 0959d26b78d1 chapter-common-tasks.sgml --- a/chapter-common-tasks.sgml Mon Apr 18 11:54:22 2011 +0530 +++ b/chapter-common-tasks.sgml Sat Apr 23 22:08:17 2011 +0530 @@ -45,7 +45,7 @@ The version ttemversion/em-emN/em/tt (like 2.6.18-8) of the ttlinux-patch-debian-emversion/em/tt - package contains all the individual patches applied to the + package contains all the individual patches applied to the source to achieve any patchlevel up to ttemN/em/tt. They are stored in the directory tt/usr/src/kernel-patches/all/emversion/em/debian//tt. @@ -90,7 +90,7 @@ /p /sect1 sect1 - headingApplying patches/heading + headingApplying patches or configuration changes/heading p It is possible to apply extra patches to the source before starting the build. First, you should apply the existing @@ -104,6 +104,60 @@ (featuresets added). You should apply the extra patches in the appropriate subdirectory. /p + p + To change the configuration before building, for example + for the 686-bigmem flavour on i386, run the commands: + example +$ fakeroot make -f debian/rules.gen setup_i386_none_686-bigmem +$ make -C debian/build/build_i386_none_686-bigmem menuconfig + /example + /p + p + Patches or configuration changes to the kernel may alter + the kernel Application Binary Interface (ABI). + /p + p +If an exported function is conditional on CONFIG_FOO, or +it uses a type whose definition depends on CONFIG_FOO, +then turning CONFIG_FOO on or off changes the ABI of that +function, and thus of the kernel as a whole. + /p + p + Enabling or changing the configuration of a single driver + usually doesn't change the ABI, because most drivers don't + export anything. + /p + p + The kernel build process generates a 'symbol version' for + each exported function or variable. This is a hash of the + definitions that it depends on, and should change whenever + the function's ABI changes. The kernel module loader + detects incompatible modules by comparing symbol versions. + The whole set of symbol versions represents the kernel + ABI. + /p + p + We collect the symbol versions for previously uploaded + packages under the directory debian/abi and then compare + the new kernel with those. If the ABI name is unchanged + but the ABI itself is changed - except for additions, or + changes that we have marked as acceptable - then the build + is aborted. + /p + p + If the kernel ABI has changed you must then change the ABI + name. This is the part after the upstream version in + package names and in the output of + ttuname -r/tt. For example, in the package name + ttlinux-image-2.6.38-2-686-bigmem/tt it is + the tt2/tt. It is defined by the ttabiname/tt + in ttdebian/config/defines/tt. For example, + ttabiname: custom1.0/tt. Then run the command + example +$ fakeroot debian/rules debian/control-real + /example + to regenerate the package definitions for this ABI name. + /p /sect1 sect1 headingBuilding many packages/heading @@ -125,17 +179,45 @@ sect1 headingBuilding packages for one flavour/heading p - For example, to build only the binary packages for 686 - flavour on i386 architecture, use the following commands: + For example, to build only the ttlinux-image-emversion/em/tt and +
Bug#621072: marked as done (linux-image-2.6.32-5-amd64: 2.6.32-33 failes to boot as PV domU on Xen)
Your message dated Sat, 23 Apr 2011 17:37:00 + with message-id e1qdglq-00033e...@franck.debian.org and subject line Bug#621072: fixed in linux-2.6 2.6.38-4 has caused the Debian Bug report #621072, regarding linux-image-2.6.32-5-amd64: 2.6.32-33 failes to boot as PV domU on Xen 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.) -- 621072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-33 Severity: critical Justification: breaks the whole system I'm currently investigation why my Debian squeeze systems don't live migrate on an XenSever pool. By chance I stumbled upon the (as it seems to me) soon to be released 2.6.32-33 kernel version and as my live migration issues are kernel related I decided to try that kernel. But this kernel doesn't boot as a PV domU neither on my Citrix XenServer 5.6 FP1 nor on a Debian system with Xen 3.4.3 at all. It doesn't even get so far as to provide a hvc console but crashes with a page fault on domain creation: (XEN) d16:v0: unhandled page fault (ec=) (XEN) Pagetable walk from 82df2000: (XEN) L4[0x1ff] = 00023dd49067 1003 (XEN) L3[0x1fe] = 00023dd45067 1007 (XEN) L2[0x016] = (XEN) domain_crash_sync called from entry.S (XEN) Domain 16 (vcpu#0) crashed on cpu#1: (XEN) [ Xen-3.4.3 x86_64 debug=n Not tainted ] (XEN) CPU:1 (XEN) RIP:e033:[8100c2af] (XEN) RFLAGS: 0216 EM: 1 CONTEXT: pv guest (XEN) rax: 82df2000 rbx: 8063 rcx: 8163 (XEN) rdx: 4000 rsi: rdi: (XEN) rbp: rsp: 8142db90 r8: 01ff (XEN) r9: 0003 r10: 00302000 r11: 0010 (XEN) r12: 8163 r13: r14: 4000 (XEN) r15: 4000 cr0: 8005003b cr4: 06f0 (XEN) cr3: 00023dd4b000 cr2: 82df2000 (XEN) ds: es: fs: gs: ss: e02b cs: e033 (XEN) Guest stack trace from rsp=8142db90: (XEN)8163 0010 8100c2af (XEN)0001e030 00010016 8142dbd8 e02b (XEN) 8100c2c2 8100c33c 03c0 (XEN)8100c3da 8100c1c9 0010 00302000 (XEN)0003 01ff 83c00063 (XEN)4000 8163 812f8981 ff40 (XEN)000100302000 ff40 0001049d 0010 (XEN)0001 8100dbe3 0010 8800010060f0 (XEN)8142dd38 03c0 ff40 8800010060f0 (XEN)8163 03c0 4000 (XEN)812f8bc7 00370009 00010008 81e3 (XEN) 2020205b 4000 880001006000 (XEN)8100dbe3 8142decc 8163 001e (XEN)0010 0010 4000 880001002000 (XEN) 8163 4000 (XEN)812f8d8f 00300020 (XEN)4000 880001002000 (XEN)0010 00302000 4000 81001880 (XEN) 8800 4000 88004000 (XEN)812f8feb ff40 88004000 Apart from addresses this is the same with domU kernel 2.6.32-32 and 2.6.32-33 as well as with either the hypervisor from XenServer or vanilla Xen. The current release 2.6.32-31 does boot without problems. System Information below is from a Debian lenny, where I tested this kernel (I don't have any other VM to hand for quick testing currently) but as this is a kernel problem this shouldn't matter. Regards Florian Wagner -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf-2.0]
Bug#622306: marked as done (2.6.32-33 Xen amd64 kernel fails to boot as Xen guest)
Your message dated Sat, 23 Apr 2011 17:37:00 + with message-id e1qdglq-00033e...@franck.debian.org and subject line Bug#621072: fixed in linux-2.6 2.6.38-4 has caused the Debian Bug report #621072, regarding 2.6.32-33 Xen amd64 kernel fails to boot as Xen guest 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.) -- 621072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-xen-amd64 Version: 2.6.32-33 We were unable to boot the Xen amd64 flavor of the 2.6.32-32 or 2.6.32-33 proposed kernels as a Xen guest. The failure occurs very early, before the kernel prints any messages to the console; the guest machine shows up in xm list as crashed. git bisect indicated that the commit x86: Cleanup highmap after brk is concluded is the probable culprit. It seems this patch has caused problems for others as well, see for example https://bugs.launchpad.net/system76/+bug/752870. We haven't yet tested whether the x86, hibernate: Initialize mmu_cr4_features during boot commit mentioned in that thread fixes the boot as a Xen guest. Regards, Reid Barton ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.38-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.38-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.38-4.diff.gz linux-2.6_2.6.38-4.dsc to main/l/linux-2.6/linux-2.6_2.6.38-4.dsc linux-doc-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-doc-2.6.38_2.6.38-4_all.deb linux-manual-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-manual-2.6.38_2.6.38-4_all.deb linux-patch-debian-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.38_2.6.38-4_all.deb linux-source-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-source-2.6.38_2.6.38-4_all.deb linux-support-2.6.38-2_2.6.38-4_all.deb to main/l/linux-2.6/linux-support-2.6.38-2_2.6.38-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 621...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 23 Apr 2011 03:17:53 +0100 Source: linux-2.6 Binary: linux-tools-2.6.38 linux-source-2.6.38 linux-doc-2.6.38 linux-manual-2.6.38 linux-patch-debian-2.6.38 linux-support-2.6.38-2 linux-libc-dev linux-headers-2.6.38-2-all linux-headers-2.6.38-2-all-alpha linux-headers-2.6.38-2-common linux-image-2.6.38-2-alpha-generic linux-headers-2.6.38-2-alpha-generic linux-image-2.6.38-2-alpha-smp linux-headers-2.6.38-2-alpha-smp linux-image-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-all-amd64 linux-image-2.6.38-2-amd64 linux-headers-2.6.38-2-amd64 linux-image-2.6.38-2-amd64-dbg linux-headers-2.6.38-2-all-armel linux-image-2.6.38-2-iop32x linux-headers-2.6.38-2-iop32x linux-image-2.6.38-2-ixp4xx linux-headers-2.6.38-2-ixp4xx linux-image-2.6.38-2-kirkwood linux-headers-2.6.38-2-kirkwood linux-image-2.6.38-2-orion5x linux-headers-2.6.38-2-orion5x linux-image-2.6.38-2-versatile linux-headers-2.6.38-2-versatile linux-headers-2.6.38-2-all-hppa linux-image-2.6.38-2-parisc linux-headers-2.6.38-2-parisc linux-image-2.6.38-2-parisc-smp linux-headers-2.6.38-2-parisc-smp linux-image-2.6.38-2-parisc64 linux-headers-2.6.38-2-parisc64 linux-image-2.6.38-2-parisc64-smp linux-headers-2.6.38-2-parisc64-smp linux-headers-2.6.38-2-all-i386 linux-image-2.6.38-2-486 linux-headers-2.6.38-2-486 linux-image-2.6.38-2-686 linux-headers-2.6.38-2-686 linux-image-2.6.38-2-686-bigmem linux-headers-2.6.38-2-686-bigmem linux-image-2.6.38-2-686-bigmem-dbg linux-headers-2.6.38-2-all-ia64 linux-image-2.6.38-2-itanium linux-headers-2.6.38-2-itanium linux-image-2.6.38-2-mckinley linux-headers-2.6.38-2-mckinley linux-headers-2.6.38-2-all-m68k linux-image-2.6.38-2-amiga linux-headers-2.6.38-2-amiga linux-image-2.6.38-2-atari linux-headers-2.6.38-2-atari linux-image-2.6.38-2-bvme6000 linux-headers-2.6.38-2-bvme6000 linux-image-2.6.38-2-mac linux-headers-2.6.38-2-mac
Bug#622361: marked as done (linux-base: Please enable option BATMAN_ADV)
Your message dated Sat, 23 Apr 2011 17:37:00 + with message-id e1qdglq-00033k...@franck.debian.org and subject line Bug#622361: fixed in linux-2.6 2.6.38-4 has caused the Debian Bug report #622361, regarding linux-base: Please enable option BATMAN_ADV 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.) -- 622361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-base Version: 3.2 Severity: wishlist Hi, please add OPTION_BATMAN_ADV as a kernel module in linux-image-* Thanks! bye, Roland -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii libuuid-perl 0.02-4 Perl extension for using UUID inte ii udev 167-1 /dev/ and hotplug management daemo ii util-linux2.17.2-9.1 Miscellaneous system utilities linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual-boot-loader: linux-base/disk-id-update-failed: * linux-base/disk-id-manual: * linux-base/disk-id-convert-plan-no-relabel: true linux-base/do-bootloader-default-changed: * linux-base/disk-id-convert-plan: true * linux-base/disk-id-convert-auto: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.38-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.38-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.38-4.diff.gz linux-2.6_2.6.38-4.dsc to main/l/linux-2.6/linux-2.6_2.6.38-4.dsc linux-doc-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-doc-2.6.38_2.6.38-4_all.deb linux-manual-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-manual-2.6.38_2.6.38-4_all.deb linux-patch-debian-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.38_2.6.38-4_all.deb linux-source-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-source-2.6.38_2.6.38-4_all.deb linux-support-2.6.38-2_2.6.38-4_all.deb to main/l/linux-2.6/linux-support-2.6.38-2_2.6.38-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 622...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 23 Apr 2011 03:17:53 +0100 Source: linux-2.6 Binary: linux-tools-2.6.38 linux-source-2.6.38 linux-doc-2.6.38 linux-manual-2.6.38 linux-patch-debian-2.6.38 linux-support-2.6.38-2 linux-libc-dev linux-headers-2.6.38-2-all linux-headers-2.6.38-2-all-alpha linux-headers-2.6.38-2-common linux-image-2.6.38-2-alpha-generic linux-headers-2.6.38-2-alpha-generic linux-image-2.6.38-2-alpha-smp linux-headers-2.6.38-2-alpha-smp linux-image-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-all-amd64 linux-image-2.6.38-2-amd64 linux-headers-2.6.38-2-amd64 linux-image-2.6.38-2-amd64-dbg linux-headers-2.6.38-2-all-armel linux-image-2.6.38-2-iop32x linux-headers-2.6.38-2-iop32x linux-image-2.6.38-2-ixp4xx linux-headers-2.6.38-2-ixp4xx linux-image-2.6.38-2-kirkwood linux-headers-2.6.38-2-kirkwood linux-image-2.6.38-2-orion5x linux-headers-2.6.38-2-orion5x linux-image-2.6.38-2-versatile linux-headers-2.6.38-2-versatile linux-headers-2.6.38-2-all-hppa linux-image-2.6.38-2-parisc linux-headers-2.6.38-2-parisc linux-image-2.6.38-2-parisc-smp linux-headers-2.6.38-2-parisc-smp linux-image-2.6.38-2-parisc64 linux-headers-2.6.38-2-parisc64 linux-image-2.6.38-2-parisc64-smp linux-headers-2.6.38-2-parisc64-smp linux-headers-2.6.38-2-all-i386 linux-image-2.6.38-2-486 linux-headers-2.6.38-2-486 linux-image-2.6.38-2-686 linux-headers-2.6.38-2-686 linux-image-2.6.38-2-686-bigmem
Bug#622570: marked as done (linux-image-2.6.38-2-s390x: Unable to handle kernel pointer dereference at virtual kernel address (null).)
Your message dated Sat, 23 Apr 2011 17:37:00 + with message-id e1qdglq-00033p...@franck.debian.org and subject line Bug#622570: fixed in linux-2.6 2.6.38-4 has caused the Debian Bug report #622570, regarding linux-image-2.6.38-2-s390x: Unable to handle kernel pointer dereference at virtual kernel address (null). 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.) -- 622570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-3 Severity: important I installed linux-image-2.6.38-2-s390x version 2.6.38-3 on my up-to-date Wheezy system today. It runs in a virtual machine under z/VM 5.4.0 running in an LPAR on an IBM z/890. It IPLed just fine. After the IPL, the system fell idle for a while. Then a CRON job kicked off, which caused a page fault, which caused a kernel oops. Here is the log: [ 2697.934752] Unable to handle kernel pointer dereference at virtual kernel address (null) [ 2697.982153] Oops: 0004 [#1] SMP [ 2698.001730] Modules linked in: nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc loop qeth_l3 qeth vmur ccwgroup ext3 jbd mbcache dm_mod dasd_eckd_mod dasd_diag_mod dasd_mod [ 2698.003407] CPU: 0 Not tainted 2.6.38-2-s390x #1 [ 2698.003430] Process cron (pid: 1106, task: 1f962f78, ksp: 1fa0f9d0) [ 2698.003455] Krnl PSW : 040420018000 0002c03e (pfault_interrupt+0xa2/0x138) [ 2698.021870]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:0 CC:2 PM:0 EA:3 [ 2698.021902] Krnl GPRS: 0001 0001 [ 2698.021943]1f962f78 00518968 9002 1ff03280 [ 2698.021979] 0064f000 1f962f78 2603 [ 2698.022016]06002603 1ff7fe68 1ff7fe48 [ 2698.022096] Krnl Code: 0002c036: 5820d010l %r2,16(%r13) [ 2698.051390]0002c03a: 1832lr %r3,%r2 [ 2698.051407]0002c03c: 1a31ar %r3,%r1 [ 2698.051430] 0002c03e: ba23d010cs %r2,%r3,16(%r13) [ 2698.051448]0002c042: a744fffcbrc 4,2c03a [ 2698.051466]0002c046: a7290002lghi%r2,2 [ 2698.051486]0002c04a: e320d024stg %r2,0(%r13) [ 2698.051502]0002c050: 07f0bcr 15,%r0 [ 2698.051514] Call Trace: [ 2698.051521] ([1f962f78] 0x1f962f78) [ 2698.051537] [0001acda] do_extint+0xf6/0x138 [ 2698.051555] [0039b6ca] ext_no_vtime+0x30/0x34 [ 2698.052373] [7d706e04] 0x7d706e04 [ 2698.052387] Last Breaking-Event-Address: [ 2698.052395] [] 0x0 [ 2698.052406] [ 2698.053263] Kernel panic - not syncing: Fatal exception in interrupt [ 2698.053316] CPU: 0 Tainted: G D 2.6.38-2-s390x #1 [ 2698.053502] Process cron (pid: 1106, task: 1f962f78, ksp: 1fa0f9d0) [ 2698.053516] 1ff7fa70 0002 [ 2698.053539]1ff7fb10 1ff7fa88 1ff7fa88 00397b9e [ 2698.053576]0001 1ff03280 [ 2698.053623]0008 000e 0078 [ 2698.053674]1ff7faf0 00011b36 1ff7fa70 1ff7fab8 [ 2698.053740] Call Trace: [ 2698.053762] ([00011a60] show_trace+0x5c/0xa4) [ 2698.053801] [003979de] panic+0x9e/0x214 [ 2698.054443] [00012046] die+0x15e/0x170 [ 2698.054485] [0002c5d6] do_no_context+0xd6/0xe0 [ 2698.054529] [0002cd52] do_protection_exception+0x46/0x2a0 [ 2698.054577] [0039b208] pgm_exit+0x0/0x4 [ 2698.054627] [0002c03e] pfault_interrupt+0xa2/0x138 [ 2698.054679] ([1f962f78] 0x1f962f78) [ 2698.056408] [0001acda] do_extint+0xf6/0x138 [ 2698.056424] [0039b6ca] ext_no_vtime+0x30/0x34 [ 2698.056439] [7d706e04] 0x7d706e04 HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0001DE26 I have backed out to a 2.6.32 kernel until the problem is resolved. The 2.6.38 kernel is obviously unusable for me. -- .''`. Stephen Powell : :' : `. `'` `- ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version:
Processed: tagging 617743
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 617743 + pending
Bug #617743 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image: found another USB midi cable with a 4 byte limit
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
617743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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.130358039928619.transcr...@bugs.debian.org
Processed: tagging 622361
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 622361 + pending
Bug #622361 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-base: Please enable option BATMAN_ADV
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
622361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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.130358040328859.transcr...@bugs.debian.org
Processed: tagging 621072
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 621072 + pending
Bug #621072 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-5-amd64: 2.6.32-33 failes to boot as PV domU on Xen
Bug #622306 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] 2.6.32-33
Xen amd64 kernel fails to boot as Xen guest
Added tag(s) pending.
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
621072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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.130358040828882.transcr...@bugs.debian.org
Processed: tagging 622570
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 622570 + pending
Bug #622570 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.38-2-s390x: Unable to handle kernel pointer dereference at
virtual kernel address (null).
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
622570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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.130358041328903.transcr...@bugs.debian.org
Re: building 2.6.26 kernel source fails on squeeze
On Sat, 23 Apr 2011, Faheem Mitha wrote: I've made some more changes - mostly additions - to your patch. [snippage] Oops, I accidentally included some redundant stuff. Resending corrected patch. Regards, Faheem diff -r 657cba972ce9 -r 4f9540ff7c84 chapter-common-tasks.sgml --- a/chapter-common-tasks.sgml Mon Apr 18 11:54:22 2011 +0530 +++ b/chapter-common-tasks.sgml Sat Apr 23 22:53:06 2011 +0530 @@ -45,7 +45,7 @@ The version ttemversion/em-emN/em/tt (like 2.6.18-8) of the ttlinux-patch-debian-emversion/em/tt - package contains all the individual patches applied to the + package contains all the individual patches applied to the source to achieve any patchlevel up to ttemN/em/tt. They are stored in the directory tt/usr/src/kernel-patches/all/emversion/em/debian//tt. @@ -90,7 +90,7 @@ /p /sect1 sect1 - headingApplying patches/heading + headingApplying patches or configuration changes/heading p It is possible to apply extra patches to the source before starting the build. First, you should apply the existing @@ -104,6 +104,60 @@ (featuresets added). You should apply the extra patches in the appropriate subdirectory. /p + p + To change the configuration before building, for example + for the 686-bigmem flavour on i386, run the commands: + example +$ fakeroot make -f debian/rules.gen setup_i386_none_686-bigmem +$ make -C debian/build/build_i386_none_686-bigmem menuconfig + /example + /p + p + Patches or configuration changes to the kernel may alter + the kernel Application Binary Interface (ABI). + /p + p +If an exported function is conditional on CONFIG_FOO, or +it uses a type whose definition depends on CONFIG_FOO, +then turning CONFIG_FOO on or off changes the ABI of that +function, and thus of the kernel as a whole. + /p + p + Enabling or changing the configuration of a single driver + usually doesn't change the ABI, because most drivers don't + export anything. + /p + p + The kernel build process generates a 'symbol version' for + each exported function or variable. This is a hash of the + definitions that it depends on, and should change whenever + the function's ABI changes. The kernel module loader + detects incompatible modules by comparing symbol versions. + The whole set of symbol versions represents the kernel + ABI. + /p + p + We collect the symbol versions for previously uploaded + packages under the directory debian/abi and then compare + the new kernel with those. If the ABI name is unchanged + but the ABI itself is changed - except for additions, or + changes that we have marked as acceptable - then the build + is aborted. + /p + p + If the kernel ABI has changed you must then change the ABI + name. This is the part after the upstream version in + package names and in the output of + ttuname -r/tt. For example, in the package name + ttlinux-image-2.6.38-2-686-bigmem/tt it is + the tt2/tt. It is defined by the ttabiname/tt + in ttdebian/config/defines/tt. For example, + ttabiname: custom1.0/tt. Then run the command + example +$ fakeroot debian/rules debian/control-real + /example + to regenerate the package definitions for this ABI name. + /p /sect1 sect1 headingBuilding many packages/heading @@ -125,17 +179,29 @@ sect1 headingBuilding packages for one flavour/heading p - For example, to build only the binary packages for 686 - flavour on i386 architecture, use the following commands: + For example, to build only the ttlinux-image-emversion/em/tt and + ttlinux-headers-emversion/em/tt binary packages + for 686 flavour on i386 architecture, use the following + commands: example $ fakeroot debian/rules source $ fakeroot make -f debian/rules.gen binary-arch_i386_none_686 /example - The target in this command has the general form of + The ttdebian/rules source/tt copies and patches the + upstream source. The target in this command has the + general form of ttemtarget/em_emarch/em_emfeatureset/em_emflavour/em/tt. Replace the ttemfeatureset/em/tt with ttnone/tt if you do not want any of the extra - featuresets. + featuresets. You will also need + the
Processing of linux-2.6_2.6.38-4_multi.changes
linux-2.6_2.6.38-4_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.38-4.dsc linux-2.6_2.6.38-4.diff.gz linux-patch-debian-2.6.38_2.6.38-4_all.deb linux-support-2.6.38-2_2.6.38-4_all.deb linux-source-2.6.38_2.6.38-4_all.deb linux-doc-2.6.38_2.6.38-4_all.deb linux-manual-2.6.38_2.6.38-4_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1qdgch-0001wh...@franck.debian.org
linux-2.6_2.6.38-4_multi.changes ACCEPTED into unstable
Accepted: linux-2.6_2.6.38-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.38-4.diff.gz linux-2.6_2.6.38-4.dsc to main/l/linux-2.6/linux-2.6_2.6.38-4.dsc linux-doc-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-doc-2.6.38_2.6.38-4_all.deb linux-manual-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-manual-2.6.38_2.6.38-4_all.deb linux-patch-debian-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.38_2.6.38-4_all.deb linux-source-2.6.38_2.6.38-4_all.deb to main/l/linux-2.6/linux-source-2.6.38_2.6.38-4_all.deb linux-support-2.6.38-2_2.6.38-4_all.deb to main/l/linux-2.6/linux-support-2.6.38-2_2.6.38-4_all.deb Override entries for your package: linux-2.6_2.6.38-4.dsc - source devel linux-doc-2.6.38_2.6.38-4_all.deb - optional doc linux-manual-2.6.38_2.6.38-4_all.deb - optional doc linux-patch-debian-2.6.38_2.6.38-4_all.deb - optional kernel linux-source-2.6.38_2.6.38-4_all.deb - optional kernel linux-support-2.6.38-2_2.6.38-4_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 617743 621072 622361 622570 Thank you for your contribution to Debian. -- 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/e1qdglq-000332...@franck.debian.org
Bug#622333: Debian Squeeze hangs with kernel 2.6.32-5-xen-686
On Fri, 2011-04-22 at 21:18 -0300, Daniel Bareiro wrote: On Friday, 22 April 2011 20:16:11 -0300, Daniel Bareiro wrote: Were you doing anything when it hung or was the system just running in a steady state? Well, 35 minutes ago I had another hang. Same symptoms: connecting directly a keyboard and monitor, there is no reaction when pressing any key (black screen); loss of connectivity to the dom0 and domUs. Additionally I can comment that this time the crash occurred when I was doing an aptitude update/upgrade in the dom0 and the domUs. I can also comment that the disk activity LED was constantly on (not flashing). After hard reset it seems that something was unconscious in one of the RAIDs, and is currently syncing. In /var/log/messages there is no evidence of any particular event from the previous boot. The same in kern.log and syslog. If the disk controller has gone funny it pretty likely that whatever log messages were generated never made it onto the disk. Here I found a thread [1] with a problem quite like this (although in my case the hardware is different: A8V-MX motherboard and AMD Athlon 64 Processor 3500+) in the xen-users mailing list. And another thread [2] which is derived from the above. I'll try using cpuidle=off or max_cstate=1 at xen cmdline in /boot/grub/grub.conf. It's probably worth trying cpuidle=off but it looks like the max_cstate=1 thing is Intel specific. It's not clear to me in either case if the root cause of the issue this fixes is a h/w or s/w issue. Do you have irqbalanced installed/running? Ian. -- Ian Campbell Questionable day. Ask somebody something. signature.asc Description: This is a digitally signed message part
Bug#593421: Bug not found in version 2.6.32-19
On Sun, Sep 26, 2010 at 11:12:09PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: On Dom 26 Sep 2010 22:52:19 Ben Hutchings escribió: On Tue, 2010-09-21 at 23:46 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: I just installed linux-image-2.6.32-5-amd64_2.6.32-19_amd64.deband I can't find the bug, so it has been introduced in 2.6.32-20. There have been some drm (kernel video driver) fixes since; can you try 2.6.32-23? Ben. I have already tried it on Friday without luck :-( The symptoms are the same: blank screen with backlight enabled. Once I plug an external monitor the LCD comes alive. Thanks for asking non the less :-) Does this bug still occur with the final version of the Linux kernel/Xorg ? Cheers, Moritz -- 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/20110423192233.GA4458@pisco.westfalen.local
Bug#596468: linux-image-2.6.32-5-openvz-amd64: Keyspan USA-49WG USB-Serial 4th Port Doesn't Work
On Wed, Dec 29, 2010 at 09:35:30PM +, Ben Hutchings wrote: On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote: On 12/29/2010 09:10 AM, Ben Hutchings wrote: On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote: On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote: Could you try to reproduce this with a current 2.6.37-rcX kernel from experimental? The kernel is available from packages.debian.org. If the error can still be reproduced, we should report it upstream. Unfortunately, 2.6.37-rc7-amd64 has an even greater problem, which prevents me from testing it. The error I am now encountering seems to be the one discussed here: https://bugzilla.kernel.org/show_bug.cgi?id=23012 [...] That was fixed in 2.6.37-rc5. ...then it has been re-introduced, or a new bug which causes the same behavior for at least my keyspan device has cropped up in -rc7. All access attempts to all of the 4 ports of my device with 2.6.37-rc7 failed with a Resource Temporarily Unavailable error. Please add that information on bugzilla.kernel.org. Steaphan, it seems you didn't followup in the kernel.org bugzilla. Is this fixed in current kernels from sid or testing? Cheers, Moritz -- 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/20110423194123.GA5687@pisco.westfalen.local
Bug#596468: linux-image-2.6.32-5-openvz-amd64: Keyspan USA-49WG USB-Serial 4th Port Doesn't Work
On 04/23/2011 03:41 PM, Moritz Mühlenhoff wrote: On Wed, Dec 29, 2010 at 09:35:30PM +, Ben Hutchings wrote: On Wed, 2010-12-29 at 14:05 -0500, Steaphan Greene wrote: On 12/29/2010 09:10 AM, Ben Hutchings wrote: On Wed, 2010-12-29 at 03:55 -0500, Steaphan Greene wrote: On 12/26/2010 06:46 AM, Moritz Muehlenhoff wrote: Could you try to reproduce this with a current 2.6.37-rcX kernel from experimental? The kernel is available from packages.debian.org. If the error can still be reproduced, we should report it upstream. Unfortunately, 2.6.37-rc7-amd64 has an even greater problem, which prevents me from testing it. The error I am now encountering seems to be the one discussed here: https://bugzilla.kernel.org/show_bug.cgi?id=23012 [...] That was fixed in 2.6.37-rc5. ...then it has been re-introduced, or a new bug which causes the same behavior for at least my keyspan device has cropped up in -rc7. All access attempts to all of the 4 ports of my device with 2.6.37-rc7 failed with a Resource Temporarily Unavailable error. Please add that information on bugzilla.kernel.org. Steaphan, it seems you didn't followup in the kernel.org bugzilla. Is this fixed in current kernels from sid or testing? No, I did not. By the time I got a chance to follow up on this, new kernel version were available, and I have not had time to test any of them (the machine using this hardware is constantly in use, including the serial device itself). I will see if I can follow up by connecting the device to a more expendable machine at some point when the serial ports won't be needed on my main machine for some time. I will e-mail again when I do finally manage to do that. -- Steaphan Greene sgre...@cs.binghamton.edu Lecturer, Computer Science, Binghamton University GPG public key: http://www.cs.binghamton.edu/~sgreene/gpg.key.txt -- 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/4db33011.1060...@cs.binghamton.edu
Bug#622333: Debian Squeeze hangs with kernel 2.6.32-5-xen-686
On Saturday, 2011-04-23 at 19:27:38 +0100, Ian Campbell wrote: Were you doing anything when it hung or was the system just running in a steady state? Well, 35 minutes ago I had another hang. Same symptoms: connecting directly a keyboard and monitor, there is no reaction when pressing any key (black screen); loss of connectivity to the dom0 and domUs. Additionally I can comment that this time the crash occurred when I was doing an aptitude update/upgrade in the dom0 and the domUs. I can also comment that the disk activity LED was constantly on (not flashing). After hard reset it seems that something was unconscious in one of the RAIDs, and is currently syncing. In /var/log/messages there is no evidence of any particular event from the previous boot. The same in kern.log and syslog. If the disk controller has gone funny it pretty likely that whatever log messages were generated never made it onto the disk. Here I found a thread [1] with a problem quite like this (although in my case the hardware is different: A8V-MX motherboard and AMD Athlon 64 Processor 3500+) in the xen-users mailing list. And another thread [2] which is derived from the above. I'll try using cpuidle=off or max_cstate=1 at xen cmdline in /boot/grub/grub.conf. It's probably worth trying cpuidle=off but it looks like the max_cstate=1 thing is Intel specific. It's not clear to me in either case if the root cause of the issue this fixes is a h/w or s/w issue. Using cpuidle=off and xen-hypervisor-4.0-amd64 package had no effect. After an uptime of 20:26:44, everything became frozen again. Now I'm trying with the max_cstate=1 option. This time there was no visual evidence in the disk activity LED when the problem occurred, but I do not see revealing information in system logs. Do you have irqbalanced installed/running? No, I'm not using irqbalance. This is a uniprocessor system (AMD Athlon(tm) 64 Processor 3500+ with A8V-MX motherdoard). Thanks for your reply. Regards, Daniel -- Daniel Bareiro - GNU/Linux registered user #188.598 Proudly running Debian GNU/Linux with uptime: 18:46:34 up 1 day, 4:43, 10 users, load average: 0.01, 0.05, 0.01 signature.asc Description: Digital signature
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
I've just tested this again, and the bug is still present as of the latest package incorporating 2.6.38.4: Linux jpc2 2.6.38-2-amd64 #1 SMP Sat Apr 23 18:47:49 UTC 2011 x86_64 GNU/Linux After completing the normal shutdown (unmounting file systems, etc.), the machine appears to stop very briefly and then it reboots. -- 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/20110424004910.ga17...@jdc.jasonjgw.net
Re: Debian/m68k kernel (preview)
On Sat, 2011-04-23 at 21:00 +, Thorsten Glaser wrote: Christian T. Steigies dixit: As Geert wrote, almost all patches will make it into the official kernel tree, only m68k usually needs them a little sooner. OK, I’ve tracked down the patches that were indeed submitted, added the SLUB workaround, and prepared another source package. It’s currently building (cross, for speed of testing), but if you like, you can review the patch I’d ask the Debian Kernel Team to include later (if this works). My patch is based on linux-2.6_2.6.38-3 since that’s what was in main when I began, but should work against the scheduled -4, too. I’ve reduced the number of patches to what I think is the minimum needed. You don't need to unset ECONET or X25 in debian/config/m68k/config; they are explicitly unset in the top-level config. Some of the changes to debian/config/m68k/* were already in sid/2.6.32 in Debian but not in what was trunk back then, so I’ve re-added them. I think they come from Stephen Marenka. I don’t know how the ABI files are generated, there’s none for m68k yet. Please tell me if I have to do something. [...] They are based on the Module.symvers files generated during a build and included in the linux-headers-* packages. They are added to the *next* version of the source package if we are intending to maintain the ABI, using debian/bin/abiupdate.py. If there has not been a successful build of kernel version '2.6.38-2' for m68k then there is no need to add them. 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
