Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
On Tue, 2011-01-04 at 23:14 +, Ben Hutchings wrote: On Tue, Jan 04, 2011 at 10:08:32PM +, Ian Campbell wrote: On Tue, 2011-01-04 at 21:44 +0100, Stephan Austermühle wrote: So the problem was already present in -23 and it just seems to have the same symptoms like #596802. OK, thanks for testing that. I wonder if you could play with ethtool to enable/disable various features on the physical NIC. In particular I think it might be worth fiddling with the LRO and GRO settings, via the -k/-K options. I don't think this has anything to do with the physical NIC. LRO is automatically turned off for interfaces that are connected to a bridge, and GRO is safe with bridging. OK, thanks for confirming, I've always been a bit confused by the relationships between [GL]RO and bridging etc. Furthermore I failed to notice that the warning in question is during a send via the physical NIC in any case. netback needs to fix up the checksum information for packets that the guest sent with TSO and no checksum: 1. Calculate the IPv4 header checksum and write it to the packet buffer (not for IPv6, obviously). The Xen PV network protocol only supports v4 segmentation offload at the moment anyway. 2. Calculate the TCP/UDP pseudo-header checksum and store it in skb-csum. 3. Set skb-csum_start and skb-csum_offset per kernel-doc. 4. Set skb-ip_summed = CHECKSUM_PARTIAL. For a GSO frame 1 and 2 must already be set correctly by the frontend as part of the PV protocol. netback does 3 (in skb_checksum_setup()) and 4 (based on the csum_blank and data_validated flags received from the frontend). There was a bug in older versions of the Citrix drivers where it failed to set the correct metadata flags for GSO frames (csum_blank must be 1 for a GSO frame, the drivers were setting it to zero, even though the partial checksum was correct, which is invalid) which caused netback to set the wrong ip_summed. I thought this was fixed long enough ago that this wouldn't be an issue today but perhaps I'm wrong. Stephan, which Citrix WHQL drivers are you using? Some XCP version or something else? Where did you download them from? I presume that if you dig around in the Windows properties pages that there is a version or build number or something. XenServer carries a temporary netback workaround for this issue, which is below, in order to support smoother upgrades. The intention was that it would be dropped in some future release and I don't really want to propagate it further (since it could also paper over a guest which hasn't obeyed #2 above) unless there is no other choice. GRO is a generalisation of LRO, I'm not sure if it is supposed to fix this forwarding issue or not. GRO is a specific software implementation of LRO that preserves enough information that it is safe to bridge/forward the resulting skb. The original packets can be reconstructed on transmit (usually through TSO, otherwise through GSO). Thanks I'd been wondering if that was the case. Out of interest, does it reconstruct the exact original packets or just one of the possible valid segmentations of the LRO SKB? Ian. That patch: diff -r 52e594b04f24 drivers/xen/netback/netback.c --- a/drivers/xen/netback/netback.c Fri Aug 07 11:44:54 2009 +0100 +++ b/drivers/xen/netback/netback.c Fri Aug 07 11:46:57 2009 +0100 @@ -1413,6 +1413,13 @@ else if (txp-flags NETTXF_data_validated) skb-ip_summed = CHECKSUM_UNNECESSARY; + /* + * Workaround Windows frontends which do not set + * NETTXF_csum_blank for GSO packets. (CA-31409) + */ + if (skb_shinfo(skb)-gso_type) + skb-ip_summed = CHECKSUM_PARTIAL; + netbk_fill_frags(netbk, skb); skb-dev = netif-dev; diff -r 52e594b04f24 drivers/xen/netfront/netfront.c --- a/drivers/xen/netfront/netfront.c Fri Aug 07 11:44:54 2009 +0100 +++ b/drivers/xen/netfront/netfront.c Fri Aug 07 11:46:57 2009 +0100 @@ -1436,6 +1436,13 @@ else if (rx-flags NETRXF_data_validated) skb-ip_summed = CHECKSUM_UNNECESSARY; + /* + * Workaround Windows frontends which do not set + * NETTXF_csum_blank for GSO packets. (CA-31409) + */ + if (skb_shinfo(skb)-gso_type) + skb-ip_summed = CHECKSUM_PARTIAL; + np-stats.rx_packets++; np-stats.rx_bytes += skb-len; -- Ian Campbell Current Noise: Turbonegro - Babylon Forever Conversation enriches the understanding, but solitude is the school of genius. -- 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/1294220042.3831.2644.ca...@zakaz.uk.xensource.com
Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
package linux-2.6 retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 thanks Gregg gkn...@tampabay.rr.com writes: [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 1229, block = 40271874 [1393760.788779] [ cut here ] [1393760.788835] kernel BUG at /build/buildd-linux-2.6_2.6.32-28~bpo50+1-i386-VgAojN/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Sounds like an ext3 bug. Either ext3 corrupted its data structures or something else (HDD, RAM) did and ext3 didn't cope with it. Googling for BUG jbd/transaction.c:1156 finds other cases: I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors. The most interesting line from dmesg is: [15174.549931] kernel BUG at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/jbd/transaction.c:1156! Here is the full output from dmesg: -- http://forums.debian.net/viewtopic.php?f=5t=56527 1) Are you using aacraid on this dm-5 device too? 2) Can you make the bug occur again? 3) If yes, can you temporarily try it without raid at all? (Just make backups before test) -- 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/8462u5jfpm@sauna.l.org
Processed: Re: Bug#608858: linux-image-2.6.32-bpo.5-amd64: smbd kernel bug copying large file
Processing commands for cont...@bugs.debian.org: package linux-2.6 Limiting to bugs with field 'package' containing at least one of 'linux-2.6' Limit currently set to 'package':'linux-2.6' retitle 608858 copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 Bug #608858 [linux-2.6] copying large file with smbd on raid causes BUG at fs/jbd/transaction.c:1156 Ignoring request to change the title of bug#608858 to the same title thanks Stopping processing here. Please contact me if you need assistance. -- 608858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608858 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.129422069928810.transcr...@bugs.debian.org
Re: Bug#607368: Please decide how kernel ABI should be managed
Don Armstrong d...@debian.org wrote: Hi, Ok. My main concern here is what exactly would happen if we were to ignore the ABI change for this particular issue, and then put in place some kind of a process where the kernel team could be informed of downstream users of the ABI. The harm is done now, reverting or bumping the ABI at this point only makes things worse. Full deployment involves over a thousand workstations. But presumably they're not running a testing version affected by this. At this time I have no assurance that this issue or a similar issue with another symbol won't happen again during the Squeeze lifetime, so they are potentially affected until proven otherwise as far as I'm concerned. To the thousand machines given above, you can add several hundred machines part of several HPC clusters; the nodes use external InfiniBand drivers from ofa-kernel 1.5.2 in the pkg-ofed repository. Having the cluster fail to come online after a kernel upgrade would be interesting. We also have servers using the Brocade FC HBA/CNA drivers from Brocade, due to the 2.6.32 drivers being way out of date (2.6.32-2.6.37 is ca. 100 commits and needs new firmware files with new names, if anyone is interested). package is upgraded, we'd still have issues with on-disk modules not matching the running kernel ABI until the machine is rebooted. This can sometimes take two or three weeks if a long-running computation is running on the machine. Presumably this wouldn't be much of an issue, unless users are going to be newly loading these modules. [Which I would hope wouldn't be the case if you were running a long-running computation.] Modules get loaded automatically pretty much all the time on a workstation: filesystem modules for a USB key or when upgrading grub, drivers for USB devices, you name it. And I'll ask again: what's the point of the kernel ABI number if we have to use strict dependencies? Some modules may need strict dependencies if they are using symbols not covered by the ABI; this is one possible way that we can resolve this issue. The issue I have with that, other than the fact that it is just plain wrong, is that all the module packaging tools were built on the premise that changes to the kernel ABI are reflected by the ABI number. None of the tools work if that premise doesn't hold true. JB. -- Julien BLACHE jbla...@debian.org | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- 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/871v4rwpv1@sonic.technologeek.org
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
On Wed, 2011-01-05 at 09:34 +, Ian Campbell wrote: (csum_blank must be 1 for a GSO frame, the drivers were setting it to zero, even though the partial checksum was correct, which is invalid) Netback is supposed to drop such invalid packets, however I've just found a patch in my .git/patches, dated August 2009, to do this which I forgot to send upstream. I'll do that now! This will fix the warning but at the expense of dropping traffic from guests with the buggy drivers so it is still worth making sure those are up to date. Ian. -- Ian Campbell Current Noise: Skid Row - Livin' On A Chain Gang If you are a police dog, where's your badge? -- Question James Thurber used to drive his German Shepherd crazy. -- 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/1294233100.3831.3436.ca...@zakaz.uk.xensource.com
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
Hi Ian, Am 05.01.2011 14:11, schrieb Ian Campbell: Netback is supposed to drop such invalid packets, however I've just found a patch in my .git/patches, dated August 2009, to do this which I forgot to send upstream. I'll do that now! Shall I still test something or just wait for the fix? I do not understand all of Ben's and your explanations. I have especially now clue what SKB, GRO, and LRO are. Stephan smime.p7s Description: S/MIME Cryptographic Signature
Bug#608865: initramfs-tools: requested additional information
Package: initramfs-tools Version: 0.98.7 Severity: normal that was just about the full output: r...@buildserver-1:~# dpkg-reconfigure initramfs-tools update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/init-top/all_generic_ide: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/init-top/blacklist: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/init-top/keymap: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/init-top/udev: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/init-bottom/udev: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/local-premount/resume: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/local-bottom/cryptopensc: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/local-top/cryptopensc: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/local-top/cryptroot: Permission denied /usr/sbin/mkinitramfs: 296: /tmp/mkinitramfs_THw6p9/scripts/local-top/lvm2: Permission denied r...@buildserver-1:~# export TMPDIR=/root/tmp r...@buildserver-1:~# dpkg-reconfigure initramfs-tools update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 r...@buildserver-1:~# mount /dev/mapper/buildServer--1-root on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sda1 on /boot type ext2 (rw,nosuid,nodev) /dev/mapper/buildServer--1-home on /home type ext3 (rw,nosuid,nodev) /dev/mapper/buildServer--1-tmp on /tmp type ext3 (rw,noexec,nosuid,nodev) /dev/mapper/buildServer--1-usr on /usr type ext3 (rw,nodev) /dev/mapper/buildServer--1-var on /var type ext3 (rw,nosuid,nodev) /dev/mapper/buildServer--1-log on /var/log type ext3 (rw,noexec,nosuid,nodev) The output of the command sh -x /usr/sbin/mkinitramfs -o /tmp/foo is too much to paste here: it outputs 435kB! -- Package-specific info: -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/buildServer--1-root ro quiet -- /proc/filesystems ext3 ext2 ext4 reiserfs xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs btrfs -- lsmod Module Size Used by nls_utf81208 1 cifs 258800 2 btrfs 375622 0 zlib_deflate 17746 1 btrfs crc32c 2560 1 libcrc32c 1074 1 btrfs ufs56474 0 qnx46194 0 hfsplus65270 0 hfs37455 0 minix 21197 0 ntfs 162796 0 vfat7884 0 msdos 6202 0 fat40038 2 vfat,msdos jfs 140089 0 xfs 436925 0 exportfs3170 1 xfs reiserfs 194156 0 ext4 289033 0 jbd2 67015 1 ext4 crc16 1319 1 ext4 xt_limit1782 2 xt_multiport2267 1 xt_tcpudp 2319 12 xt_state1303 25 nf_conntrack_ftp5537 0 nf_conntrack_ipv4 9833 25 nf_conntrack 46535 3 xt_state,nf_conntrack_ftp,nf_conntrack_ipv4 nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 dm_snapshot18481 0 iptable_filter 2258 1 ip_tables 13899 1 iptable_filter sha256_generic 8692 6 aes_x86_64 7340 6 aes_generic25714 1 aes_x86_64 cbc 2539 3 ipt_ULOG7129 3 x_tables 12845 6 xt_limit,xt_multiport,xt_tcpudp,xt_state,ip_tables,ipt_ULOG ext2 52969 1 loop 11799 0 dm_crypt 10664 3 snd_pcm60503 0 snd_timer 15582 1 snd_pcm snd46446 2 snd_pcm,snd_timer soundcore 4598 1 snd dcdbas 5048 0 snd_page_alloc 6249 1 snd_pcm psmouse49777 0 serio_raw 3752 0 evdev 7352 1 pcspkr 1699 0 processor 29935 8 power_meter 8302 0 button 4650 0 ext3 106518 12 jbd37085 1 ext3 mbcache 5050 3 ext4,ext2,ext3 dm_mod 53770 49 dm_snapshot,dm_crypt sg 18744 0 sr_mod 12602 0 cdrom 29415 1
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
On Wed, 2011-01-05 at 14:23 +0100, Stephan Austermühle wrote: Hi Ian, Am 05.01.2011 14:11, schrieb Ian Campbell: Netback is supposed to drop such invalid packets, however I've just found a patch in my .git/patches, dated August 2009, to do this which I forgot to send upstream. I'll do that now! Shall I still test something or just wait for the fix? Per my previous mail please can you let me know the details of the Windows driver versions you are using, where you got them from etc. I guess you could experiment with disabling the offload settings on the Windows side. (I think you can do this by right clicking the NIC in device manager and disabling Large Send Offload in the advanced tab.) Other than that there is nothing to test just yet. I do not understand all of Ben's and your explanations. I have especially now clue what SKB, GRO, and LRO are. No problem. Ian. -- Ian Campbell Current Noise: Annihilator - Romeo Delight Many people are desperately looking for some wise advice which will recommend that they do what they want to do. -- 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/1294235871.3831.3491.ca...@zakaz.uk.xensource.com
Bug#608865: initramfs-tools: requested additional information
On Wed, Jan 05, 2011 at 02:44:47PM +0100, martin.ger...@dser.de wrote:
/dev/mapper/buildServer--1-tmp on /tmp type ext3 (rw,noexec,nosuid,nodev)
wondering why this snippet does not trigger:
DESTDIR=$(mktemp -d ${TMPDIR:-/tmp}/mkinitramfs_XX) || exit 1
chmod 755 ${DESTDIR}
# do not execute cache_run_scripts() if mounted with noexec
NOEXEC=
fs=$(df $DESTDIR | tail -1 | awk '{print $6}')
if [ -n $fs ] mount | grep -q on $fs .*noexec ; then
NOEXEC=1
fi
thanks for the followup, please post also
df /tmp
--
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/20110105142119.gv20...@vostochny.stro.at
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
On Wed, Jan 05, 2011 at 09:34:02AM +, Ian Campbell wrote: [...] GRO is a specific software implementation of LRO that preserves enough information that it is safe to bridge/forward the resulting skb. The original packets can be reconstructed on transmit (usually through TSO, otherwise through GSO). Thanks I'd been wondering if that was the case. Out of interest, does it reconstruct the exact original packets or just one of the possible valid segmentations of the LRO SKB? [...] It reconstructs the exact same packets, modulo header fields that are supposed to be modified on forwarding. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20110105151410.gj3...@decadent.org.uk
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
On Wed, Jan 05, 2011 at 02:23:35PM +0100, Stephan Austermühle wrote: Hi Ian, Am 05.01.2011 14:11, schrieb Ian Campbell: Netback is supposed to drop such invalid packets, however I've just found a patch in my .git/patches, dated August 2009, to do this which I forgot to send upstream. I'll do that now! Shall I still test something or just wait for the fix? I do not understand all of Ben's and your explanations. I have especially now clue what SKB, GRO, and LRO are. That was for Ian's benefit. You are not expected to follow all of that. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20110105151500.gk3...@decadent.org.uk
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
Hi, Am 05.01.2011 14:57, schrieb Ian Campbell: Per my previous mail please can you let me know the details of the Windows driver versions you are using, where you got them from etc. PV drivers are Citrix WHQL server for XenServer 5.5, don't know download source anymore (looked for it in xen-users mailing list). The driver reports Citrix XenServer PV Ethernet Adapter Driver date: 11/9/2009 Driver version: 5.5.0.23143 I guess you could experiment with disabling the offload settings on the Windows side. (I think you can do this by right clicking the NIC in device manager and disabling Large Send Offload in the advanced tab.) There is no advanced tab and no possibility to change any options for this driver. Stephan smime.p7s Description: S/MIME Cryptographic Signature
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
On Wed, 2011-01-05 at 16:29 +0100, Stephan Austermühle wrote: Hi, Am 05.01.2011 14:57, schrieb Ian Campbell: Per my previous mail please can you let me know the details of the Windows driver versions you are using, where you got them from etc. PV drivers are Citrix WHQL server for XenServer 5.5, don't know download source anymore (looked for it in xen-users mailing list). The driver reports Citrix XenServer PV Ethernet Adapter Driver date: 11/9/2009 Driver version: 5.5.0.23143 That is old enough to suffer from the issue I described. I'd strongly recommend upgrading to something newer, such as the drivers supplied with the XCP 1.0 beta. The beta designation does not apply to the Windows driver component of this release, they are a GA version of the drivers. http://www.xen.org/files/XenCloud/Software/xcp-1.0-beta/ The drivers are in XCP-1.0-base-38754.iso as /client_install/windows-pvdrivers-xensetup.exe If you want a Free alternative then there are GPL Windows PV drivers available also: http://wiki.xen.org/xenwiki/XenWindowsGplPv As far as the Debian bug goes I will apply my fix to correctly drop the invalid SKBs so that they do not cause the warning in dom0. Ian. -- Ian Campbell We don't really understand it, so we'll give it to the programmers. -- 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/1294244541.3831.3547.ca...@zakaz.uk.xensource.com
Processed: tagging 608144
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 608144 + pending Bug #608144 [linux-2.6] linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared) Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 608144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608144 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.12942451453478.transcr...@bugs.debian.org
Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)
Hi, Am 05.01.2011 17:22, schrieb Ian Campbell: I'd strongly recommend upgrading to something newer, such as the drivers supplied with the XCP 1.0 beta. The beta designation does not apply to the Windows driver component of this release, they are a GA version of the drivers. http://www.xen.org/files/XenCloud/Software/xcp-1.0-beta/ Thanks for your hint. Unfortunately, the drivers included in XCP 1.0 beta don't work with W2k8 R2. I'm using the GPLPV drivers on another system but they have the big disadvantage of not being WHQL signed (enabling test signing in Windows isn't alway an option). As far as the Debian bug goes I will apply my fix to correctly drop the invalid SKBs so that they do not cause the warning in dom0. Thanks. Stephan smime.p7s Description: S/MIME Cryptographic Signature
Bug#609046: linux-image-2.6-686: pata_via module boot fail with vt6415
Package: linux-image-2.6-686 Version: 2.6.32-5 Severity: important pata_via module and ATAPI device cause panic with VIA vt6415 PATA IDE Host Controller. I tried boot from ATAPI CD drive with squeeze beta2 iso image. but normal boot fail. Then put boot command libata.dma=1 or nolapic, successfully booted. --- DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101127 X_INSTALLATION_MEDIUM=cdrom --- uname -a: Linux (none) 2.6.32-5-486 #1 Sat Oct 30 22:14:18 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 18) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:840b] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 06) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 06) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a6) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 5 Series Chipset LPC Interface Controller [8086:3b06] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: 00:1f.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3b20] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: 00:1f.5 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller [8086:3b26] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8383] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8432] lspci -knn: 02:00.0 IDE interface [0101]: VIA Technologies, Inc. PATA IDE Host Controller [1106:0415] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:838f] lspci -knn: Kernel driver in use: pata_via -- 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/aanlkti=6et0m=d5qkep48mc=b+cd2vm_rrmekx5uf...@mail.gmail.com
Re: Processed: tagging 571035
Hello distinguished bug owner, :)
Is there a replacement bug I can subscribe too regarding the
below? If I can help kill this squeeze bug I'm willing. Not
everybody has this old hardware.
Thanks,
Mark Lila
On Fri, 31 Dec 2010 05:31 -0700, Mark Lila m...@lilas.net
wrote:
Hello,
I have an old Toshiba Satellite 225CDS with 144MB of RAM and it
does the exact same thing as the 32MB laptop in 571035. I used
the Dec 29th, 2010 daily netinst cd. Before that I used the beta
2 squeeze cd.
Is this bug going anywhere? If it's dead maybe I just need to
eBay the old laptop after Lenny ends support.
Is there an easy way to work around this issue. Holger booted
from:
debian-testing daily build from
23. Aug 2010.
That kernel boots fine!!!
That's a rough work-around (where were those daily snap-shots
again?). I'll probably stay with Lenny if that's where we are
going to stay.
Thanks,
Mark Lila
PS. I'd be happy to join/use the official bug system if this
goes anywhere.
~~~
[[1]Date Prev][[2]Date Next] [[3]Thread Prev][[4]Thread Next]
[[5]Date Index] [[6]Thread Index]
Processed: tagging 571035
* To: Ben Hutchings [7]...@decadent.org.uk
* Cc: Debian Kernel Team [8]debian-ker...@lists.debian.org
(linux-2.6 for {571035})
* Subject: Processed: tagging 571035
* From: [9]ow...@bugs.debian.org (Debian Bug Tracking System)
* Date: Sun, 12 Sep 2010 02:36:05 +
* Message-id:
[10]handler.s.c.1284258810888.transcr...@bugs.debian.org
* In-reply-to: [11]1284258802-4175-bts-...@decadent.org.uk
* References: [12]1284258802-4175-bts-...@decadent.org.uk
Processing commands for cont...@bugs.debian.org:
tags 571035 - moreinfo
Bug #571035 [linux-2.6] Kernel freezes at boot
Removed tag(s) moreinfo.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
571035: [13]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Reply to:
* [14]debian-ker...@lists.debian.org
* [15]Debian Bug Tracking System (on-list)
* [16]Debian Bug Tracking System (off-list)
* Prev by Date: [17]Bug#571035: [squeeze alpha1]
installationsreport: grub2: machine doesn't boot
* Next by Date: [18]Bug#596419: Acknowledgement
(xen-linux-system-2.6.32-5-xen-amd64: causes a system hangup
by the shutdown of the system, aacraid (sw raid) involved in
hangup)
* Previous by thread: [19]Bug#596478: [PATCH] ALSA: emux: Add
trivial compat ioctl handler
* Next by thread: [20]Bug#595511: (no subject)
* Index(es):
+ [21]Date
+ [22]Thread
References
1. http://lists.debian.org/debian-kernel/2010/09/msg00261.html
2. http://lists.debian.org/debian-kernel/2010/09/msg00263.html
3. http://lists.debian.org/debian-kernel/2010/09/msg00353.html
4. http://lists.debian.org/debian-kernel/2010/09/msg00265.html
5. http://lists.debian.org/debian-kernel/2010/09/maillist.html#00262
6. http://lists.debian.org/debian-kernel/2010/09/threads.html#00262
7. mailto:ben%40decadent.org.uk
8. mailto:debian-kernel%40lists.debian.org
9. mailto:owner%40bugs.debian.org
10. http://lists.debian.org/debian-kernel/2010/09/msg00262.html
11.
http://lists.debian.org/msgid-search/1284258802-4175-bts-ben%40decadent.org.uk
12.
http://lists.debian.org/msgid-search/1284258802-4175-bts-ben%40decadent.org.uk
13. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571035
14.
mailto:debian-ker...@lists.debian.org?in-reply-to=%3chandler.s.c.1284258810888.transcript@bugs.debian.org%3ESubject=Re:%20Processed:%20tagging%20571035
15.
mailto:ow...@bugs.debian.org?in-reply-to=%3chandler.s.c.1284258810888.transcript@bugs.debian.org%3ESubject=Re:%20Processed:%20tagging%20571035cc=debian-ker...@lists.debian.org
16.
mailto:ow...@bugs.debian.org?in-reply-to=%3chandler.s.c.1284258810888.transcript@bugs.debian.org%3ESubject=Re:%20Processed:%20tagging%20571035
17. http://lists.debian.org/debian-kernel/2010/09/msg00261.html
18. http://lists.debian.org/debian-kernel/2010/09/msg00263.html
19. http://lists.debian.org/debian-kernel/2010/09/msg00353.html
20. http://lists.debian.org/debian-kernel/2010/09/msg00265.html
21. http://lists.debian.org/debian-kernel/2010/09/maillist.html#00262
22. http://lists.debian.org/debian-kernel/2010/09/threads.html#00262
Bug#609046: linux-image-2.6-686: pata_via module boot fail with vt6415
On Thu, Jan 06, 2011 at 03:40:58AM +0900, Aki wrote: Package: linux-image-2.6-686 Version: 2.6.32-5 Severity: important pata_via module and ATAPI device cause panic with VIA vt6415 PATA IDE Host Controller. Then send the panic message. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20110105202115.gl3...@decadent.org.uk
Processed: tagging 609046
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 609046 moreinfo Bug #609046 [linux-image-2.6-686] linux-image-2.6-686: pata_via module boot fail with vt6415 Added tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 609046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609046 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.129425888925334.transcr...@bugs.debian.org
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-2.6_2.6.37-1~experimental.1.diff.gz linux-2.6_2.6.37-1~experimental.1.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:28:52, the files will be deleted. If you didn't upload those files, please just ignore this message. 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/e1padkz-0005pk...@franck.debian.org
Bug#599368: [124/152] watchdog: Improve initialisation error message and documentation
2.6.36-stable review patch. If anyone has any objections, please let us know. -- From: Ben Hutchings b...@decadent.org.uk commit 551423748a4eba55f2eb0fc250d757986471f187 upstream. The error message 'NMI watchdog failed to create perf event...' does not make it clear that this is a fatal error for the watchdog. It also currently prints the error value as a pointer, rather than extracting the error code with PTR_ERR(). Fix that. Add a note to the description of the 'nowatchdog' kernel parameter to associate it with this message. Reported-by: Cesare Leonardi celeo...@gmail.com Signed-off-by: Ben Hutchings b...@decadent.org.uk Cc: 599...@bugs.debian.org Cc: 608...@bugs.debian.org Cc: Don Zickus dzic...@redhat.com Cc: Frederic Weisbecker fweis...@gmail.com LKML-Reference: 1294009362.3167.126.ca...@localhost Signed-off-by: Ingo Molnar mi...@elte.hu Signed-off-by: Greg Kroah-Hartman gre...@suse.de --- Documentation/kernel-parameters.txt |2 +- kernel/watchdog.c |3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1745,7 +1745,7 @@ and is between 256 and 4096 characters. nousb [USB] Disable the USB subsystem - nowatchdog [KNL] Disable the lockup detector. + nowatchdog [KNL] Disable the lockup detector (NMI watchdog). nowb[ARM] --- a/kernel/watchdog.c +++ b/kernel/watchdog.c @@ -377,7 +377,8 @@ static int watchdog_nmi_enable(int cpu) goto out_save; } - printk(KERN_ERR NMI watchdog failed to create perf event on cpu%i: %p\n, cpu, event); + printk(KERN_ERR NMI watchdog disabled for cpu%i: unable to create perf event: %ld\n, + cpu, PTR_ERR(event)); return -1; /* success path */ -- 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/20110106002308.434740...@clark.site
Processing of linux-2.6_2.6.37-1~experimental.1_multi.changes
linux-2.6_2.6.37.orig.tar.gz has incorrect size; deleting it Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. 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/e1padsu-s2...@franck.debian.org
Security review of 2.6.32.28
These are the patches that looked security-relevant, from a fairly quick review: [03/49] fuse: verify ioctl retries Kernel buffer overflow, but only CUSE servers could exploit it and /dev/cuse is normally restricted to root. [16/49] IB/uverbs: Handle large number of entries in poll CQ Fixes integer overflow and information leak which I assume can be triggered by unprivileged local users. [20/49] orinoco: fix TKIP countermeasure behaviour Fixes cryptographic weakness potentially leaking information to remote (but physically nearby) users. [24/49] tracing: Fix panic when lseek() called on trace opened for writing File is normally only writable by root, so not a security issue. [33/49] [SCSI] bfa: fix system crash when reading sysfs fc_host statistics Local denial-of-service. CVE-2010-4343 [36/49] install_special_mapping skips security_file_mmap check. May enable privilege escalation through null pointer bugs that would otherwise only cause denial-of-service. CVE-2010-4346 [42/49] sound: Prevent buffer overflow in OSS load_mixer_volumes Not relevant to Debian kernel images since we don't build OSS. CVE-2010-4257 [44/49] ima: fix add LSM rule bug Allows subversion of IMA. Not relevant to Debian kernel images since we don't build IMA. [48/49] sctp: Fix a race between ICMP protocol unreachable and connect() Remote denial-of-service. CVE-2010-4526 Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#576274: Possible Bug Fix?
Good Morning, I've been working on this bug for the last 3 days and think I've isolated and corrected the problem. Intel provides special (open source) linux drivers for their video cards at this url: http://intellinuxgraphics.org/index.html After looking over the site for awhile and attempting to install them I found that most were just updates to what we had already (pending upstream). So I went back into XOrg.conf to look through and try to see if perhaps the system was misconfigured. This is what I saw: --- Section Device IdentifierConfigured Video Device OptionUseFBDevtrue EndSection Section Monitor IdentifierConfigured Monitor EndSection --- I personally find it uneasy when all it tells me is that its configured so I went through the repositories to confirm I had the right driver packages and autoconfigs to attempt to refresh the conf file so to speak. I installed/reinstalled the following packages: mesa-utils (7.0.3-7), xdebconfigurator (1.35), xserver-xorg (1:7.3+20), xserver-xorg-core (2:1.4.2-10.lenny3), xserver-xorg-video-dummy (1:0.3.0-1), xserver-xorg-video-intel (2:2.3.2-2+lenny8) Then I ran 'xdebconfigurator', after it completed I got curious as to the changes it made so I went back to XOrg.conf to see, the following was changed: Section Device IdentifierConfigured Video Device Driveri810 EndSection Section Monitor IdentifierConfigured Monitor EndSection Its evidently using the i810 Intel drivers now. Though I have a 945GM card I dont know if there is a driver for that card specifically, or if it would make a difference. I've been runing my system for 3 days now without interruption. Can someone else replicate these steps on an affected system to see if it fixes it? I might have just had a different problem... -- 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/4d251b81.6070...@eastlink.ca
Processing of linux-2.6_2.6.37-1~experimental.1_multi.changes
linux-2.6_2.6.37-1~experimental.1_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.37-1~experimental.1.dsc linux-2.6_2.6.37.orig.tar.gz linux-2.6_2.6.37-1~experimental.1.diff.gz linux-support-2.6.37-trunk_2.6.37-1~experimental.1_all.deb linux-patch-debian-2.6.37_2.6.37-1~experimental.1_all.deb linux-base_2.6.37-1~experimental.1_all.deb firmware-linux-free_2.6.37-1~experimental.1_all.deb linux-source-2.6.37_2.6.37-1~experimental.1_all.deb linux-doc-2.6.37_2.6.37-1~experimental.1_all.deb linux-manual-2.6.37_2.6.37-1~experimental.1_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/e1paetx-00068t...@franck.debian.org
linux-2.6_2.6.37-1~experimental.1_multi.changes is NEW
firmware-linux-free_2.6.37-1~experimental.1_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.37-1~experimental.1_all.deb linux-2.6_2.6.37-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.37-1~experimental.1.diff.gz linux-2.6_2.6.37-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.37-1~experimental.1.dsc linux-2.6_2.6.37.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.37.orig.tar.gz linux-base_2.6.37-1~experimental.1_all.deb to main/l/linux-2.6/linux-base_2.6.37-1~experimental.1_all.deb linux-doc-2.6.37_2.6.37-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.37_2.6.37-1~experimental.1_all.deb linux-manual-2.6.37_2.6.37-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.37_2.6.37-1~experimental.1_all.deb linux-patch-debian-2.6.37_2.6.37-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.37_2.6.37-1~experimental.1_all.deb linux-source-2.6.37_2.6.37-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.37_2.6.37-1~experimental.1_all.deb (new) linux-support-2.6.37-trunk_2.6.37-1~experimental.1_all.deb optional devel Support files for Linux 2.6.37 This package provides support files for the Linux kernel build, e.g. scripts to handle ABI information and for generation of build system meta data. Changes: linux-2.6 (2.6.37-1~experimental.1) experimental; urgency=low . * New upstream release: http://kernelnewbies.org/Linux_2_6_37 - starfire: Fix dma_addr_t size test for MIPS (fixes FTBFS) - watchdog: Improve failure message and documentation (Closes: #608138) . [ Ben Hutchings ] * i2c-i801: Include linux/slab.h (fixes FTBFS on alpha) * [x86] Staging: Enable R8712U as module (r8712u, replacing r8192s_usb) - Enable loading external firmware, thanks to Stefan Lippers-Hollmann * linux-base: Look for GRUB 1 configuration in both /boot/grub and /boot/boot/grub (Closes: #607863) * btrfs: Require CAP_SYS_ADMIN for filesystem rebalance (Closes: #608185) * r8169: Change RTL8111D/RTL8168D initialisation and firmware loading to match upstream version (Closes: #596390 with firmware-realtek 0.28) Override entries for your package: firmware-linux-free_2.6.37-1~experimental.1_all.deb - optional kernel linux-2.6_2.6.37-1~experimental.1.dsc - source devel linux-base_2.6.37-1~experimental.1_all.deb - optional kernel linux-doc-2.6.37_2.6.37-1~experimental.1_all.deb - optional doc linux-manual-2.6.37_2.6.37-1~experimental.1_all.deb - optional doc linux-patch-debian-2.6.37_2.6.37-1~experimental.1_all.deb - optional kernel linux-source-2.6.37_2.6.37-1~experimental.1_all.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 596390 607863 608138 608185 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- 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/e1paexs-0006rn...@franck.debian.org
Bug#576274: Possible Bug Fix?
On Wed, 2011-01-05 at 21:31 -0400, Brian Michalski wrote: [...] So I went back into XOrg.conf to look through and try to see if perhaps the system was misconfigured. This is what I saw: --- Section Device IdentifierConfigured Video Device OptionUseFBDevtrue EndSection Section Monitor IdentifierConfigured Monitor EndSection --- I personally find it uneasy when all it tells me is that its configured It's just an arbitrary name. so I went through the repositories to confirm I had the right driver packages and autoconfigs to attempt to refresh the conf file so to speak. You probably don't even need this configuration file. I installed/reinstalled the following packages: mesa-utils (7.0.3-7), xdebconfigurator (1.35), xserver-xorg (1:7.3+20), xserver-xorg-core (2:1.4.2-10.lenny3), xserver-xorg-video-dummy (1:0.3.0-1), xserver-xorg-video-intel (2:2.3.2-2+lenny8) Then I ran 'xdebconfigurator', after it completed I got curious as to the changes it made so I went back to XOrg.conf to see, the following was changed: Section Device IdentifierConfigured Video Device Driveri810 EndSection Section Monitor IdentifierConfigured Monitor EndSection Its evidently using the i810 Intel drivers now. The correct driver is 'intel' I don't how why you ended up with 'i810', but in any case that would be a bug in xdebconfigurator, not the kernel. Possibly 'i810' just works as an alias for 'intel'. Though I have a 945GM card I dont know if there is a driver for that card specifically, or if it would make a difference. [...] If you have problems with the 945GM, open a separate bug report. This bug report concerns the 915GM chip. 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
Processed: tagging 555835
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 555835 + pending Bug #555835 [linux-2.6] linux-image-2.6.30-2-686: Unusual usb storage Samsung YP-CP3 not working Bug #555836 [linux-2.6] linux-image-2.6.30-2-686: Unusual usb_storage device Samsung YP-CP3 not working Ignoring request to alter tags of bug #555835 to the same tags previously set Ignoring request to alter tags of bug #555836 to the same tags previously set End of message, stopping processing here. Please contact me if you need assistance. -- 555835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555835 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.12942900934990.transcr...@bugs.debian.org
