Bug#401035: Fixed upstream
tags 401035 patch fixed-upstream etch stop http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b0244a00451c1ad64bf0a51f50679f7146786780 Would be so nice to have this come to etch kernels at some point. This issue on drivers/ide side repeats also with drivers/ata code, but the patches have not settled yet: http://marc.info/?l=linux-idem=118657911029543w=2 -Mikko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#401035: Fixed upstream
Processing commands for [EMAIL PROTECTED]: tags 401035 patch fixed-upstream etch Bug#401035: linux-image-2.6-686: errors with hard disk ST340823A There were no tags set. Tags added: patch, fixed-upstream, etch stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439892: linux-image-2.6.21-2-amd64: random crashes/hangs on dual-core AMD64 under heavy disk write load (local and NFS)
Package: linux-image-2.6.21-2-amd64 Version: 2.6.21-6 Severity: important My AMD64 dual core system hosts a backup disk (SATA) and every night it takes a local backup and is also accessed over NFS by another system which writes a backup. Every few days, the system has hung or crashed when I go to use it in the morning. This only seems to occur when both systems are doing heavy backups. For a while the remote system's ethernet was broken and I was using a low speed, USB attached ethernet -- the crashes stopped. Now I have replaced the broken ethernet and both systems have working gigabit ethernet devices and the crashes have returned. The crashing system writes nothing in its logs but it does remote syslog and the remote logs show the problem. Here are the last two crashes: Aug 19 01:33:13 black kernel: PGD f97f067 PUD 60935067 PMD 0 Aug 19 01:33:13 black kernel: CPU 0 Aug 19 01:33:13 black kernel: Modules linked in: nfsd exportfs ppdev lp button ac battery ipv6 nfs lockd nfs_acl sunrpc vfat fat dm_snapshot dm_mirror dm_mod it87 hwmon_vid eeprom i2c_isa sr_mod sbp2 ide_generic ide_disk snd_mpu401 snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_intel8x0 snd_seq_midi snd_seq_midi_event snd_ac97_codec snd_ac97_bus snd_seq snd_pcm_oss snd_mixer_oss analog snd_rawmidi snd_seq_device gameport snd_pcm snd_timer parport_pc parport pcspkr psmouse serio_raw snd soundcore snd_page_alloc joydev evdev tsdev i2c_nforce2 i2c_core eth1394 ext3 jbd mbcache usbhid sd_mod ide_cd cdrom sata_nv libata scsi_mod skge floppy ohci1394 ieee1394 ehci_hcd forcedeth amd74xx generic ide_core ohci_hcd thermal processor fan Aug 19 01:33:13 black kernel: Pid: 209, comm: kswapd0 Not tainted 2.6.18-4-amd64 #1 Aug 19 01:33:13 black kernel: RIP: 0010:[88181931] [88181931] :ext3:ext3_discard_reservation+0x28/0x67 Aug 19 01:33:13 black kernel: RSP: 0018:810037c01d20 EFLAGS: 00010202 Aug 19 01:33:13 black kernel: RAX: 810076a95000 RBX: 00d0 RCX: Aug 19 01:33:13 black kernel: RDX: 8100208a0d60 RSI: 81002dbdac88 RDI: 8100208a0a40 Aug 19 01:33:13 black kernel: RBP: 8100208a0a40 R08: 0041 R09: 0007e019 Aug 19 01:33:13 black kernel: R10: R11: 8818c15b R12: 00f0 Aug 19 01:33:13 black kernel: R13: 81007b9d8000 R14: 0080 R15: 0080 Aug 19 01:33:13 black kernel: FS: 2af51eba5dc0() GS:80521000() knlGS: Aug 19 01:33:13 black kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Aug 19 01:33:13 black kernel: CR2: 00f8 CR3: 2305f000 CR4: 06e0 Aug 19 01:33:13 black kernel: Process kswapd0 (pid: 209, threadinfo 810037c0, task 81007d76c040) Aug 19 01:33:13 black kernel: Stack: 810006c96c88 8100208a0a40 8100208a0978 00d0 Aug 19 01:33:13 black kernel: 810037c01db0 8818c1da 8100208a0a40 8100208a0a40 Aug 19 01:33:13 black kernel: 0042 80220e2c 8100208a0a50 802327d9 Aug 19 01:33:13 black kernel: Call Trace: Aug 19 01:33:13 black kernel: [8818c1da] :ext3:ext3_clear_inode+0x6c/0x8a Aug 19 01:33:13 black kernel: [80220e2c] clear_inode+0xc5/0xf6 Aug 19 01:33:13 black kernel: [802327d9] dispose_list+0x56/0xf6 Aug 19 01:33:13 black kernel: [8022b954] shrink_icache_memory+0x1d4/0x204 Aug 19 01:33:13 black kernel: [8023d2d4] shrink_slab+0xe2/0x15a Aug 19 01:33:13 black kernel: [80253956] kswapd+0x31c/0x41b Aug 19 01:33:13 black kernel: [80290381] autoremove_wake_function+0x0/0x2e Aug 19 01:33:13 black kernel: [802901be] keventd_create_kthread+0x0/0x61 Aug 19 01:33:13 black kernel: [8025363a] kswapd+0x0/0x41b Aug 19 01:33:13 black kernel: [802901be] keventd_create_kthread+0x0/0x61 Aug 19 01:33:13 black kernel: [8023055a] kthread+0xd4/0x107 Aug 19 01:33:13 black kernel: [80259360] child_rip+0xa/0x12 Aug 19 01:33:13 black kernel: [802901be] keventd_create_kthread+0x0/0x61 Aug 19 01:33:13 black kernel: [8026f34e] physflat_send_IPI_mask+0x0/0x6a Aug 19 01:33:13 black kernel: [80230486] kthread+0x0/0x107 Aug 19 01:33:13 black kernel: [80259356] child_rip+0x0/0x12 Aug 19 01:33:13 black kernel: Aug 19 01:33:13 black kernel: Aug 19 01:33:13 black kernel: Code: 49 83 7c 24 08 00 74 2e 49 8d bd 00 41 00 00 e8 38 ce 0d f8 Aug 19 01:33:13 black kernel: RSP 810037c01d20 Aug 28 01:36:35 black kernel: PGD 8063 PUD 0 Aug 28 01:36:35 black kernel: CPU 0 Aug 28 01:36:35 black kernel: Modules linked in: nfsd exportfs ppdev lp button ac battery ipv6 nfs lockd nfs_acl sunrpc vfat fat dm_snapshot dm_mirror dm_mod it87 hwmon_vid eeprom i2c_isa sr_mod sbp2 ide_generic ide_disk snd_mpu401 snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi
Bug#439892: linux-image-2.6.21-2-amd64: random crashes/hangs on dual-core AMD64 under heavy disk write load (local and NFS)
On Tue, Aug 28, 2007 at 10:12:57AM +0100, Graham Cobb wrote: Package: linux-image-2.6.21-2-amd64 Version: 2.6.21-6 Severity: important why are your reporting against that old image, fetch 2.6.22 from unstble. 2.6.21 is no longer supported. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401482: Possible patch for broken GDB
tag 401482 +patch thanks On Fri, 2007-08-24 at 11:11 +0100, Sam Morris wrote: See the attachment from https://bugzilla.novell.com/show_bug.cgi?id=258433#c49. I've tested the patch out and it works. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
update-initramfs, chroots ro /boot, and debian-live (Re: d-l and /boot ro)
On Tue, Aug 28, 2007 at 09:13:00PM +0200, Daniel Baumann wrote: Justin Pryzby wrote: Check update-initramfs, which reads from proc/mounts, which makes the scripts not completely hostfs agnostic. ummm.. bad one that, thanks for pointing it out. someone has a good idea about that? actually, at the time where update-initramfs is run, we should not mount /proc, but that's going to be a bit nasty to mount/unmount it just before and after lh_chroot_hacks. Should u-i check if it's in a chroot before testing for ro root (I don't know). I tried briefly bind mounting dev/null over proc/mounts but made some kind of process specific proc/PID/mounts instead.. initramfs people, see thread starting at: http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-August/002075.html Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439072: snd-intel8x0 line-in not working in later 2.6.x kernels
On Wed, Aug 22, 2007 at 04:13:19AM +0200, Josip Rodin wrote: On Wed, Aug 22, 2007 at 02:52:59AM +0200, Josip Rodin wrote: I'm reporting this bug that I have been seeing for a while and which is a regression from a few months/years ago - the line-in input simply doesn't work right. arecord(1) just doesn't record anything with it, it doesn't show any errors, it records silence. The recording from the same external source works just fine with the microphone input. This works just fine with the same hardware in MS Windows (ugh), and it also worked fine with an earlier 2.6.x kernel version that I had been using when I was still running sarge on this machine. But, I removed it in the meantime so I don't know which one it was. I think it was 2.6.16 or so, but I'm not sure. It's definitely not working with = 2.6.18 (I still have one of those and it behaves the same as 2.6.21). Oh, I might have been too vague there. I can't exactly reproduce the old state because I changed much of my other hardware in this machine since and my old kernel images won't boot; and then I also noticed that there was once an old OSS driver and then I switched to alsa, but I don't have backups of my ancient /etc/modules file so I don't know when that was. I re-selected the old-style i810_audio driver in 2.6.21 and compiled it, unloaded the ALSA driver, loaded the old driver, and voila, everything went back to normal, I can hear the TV sound just fine. So, it might be that this is an OSS-ALSA regression that slipped through the cracks? After an upstream developer helped debug it, it seems that it works if I use alsamixer to change the mixer from the 4 channel mode to the 2 channel mode. The 2ch mode is supposed to be the default; I have no idea why my alsamixer setup used the 4ch mode, at least I certainly don't remember ever fiddling with that setting (because I have no idea what it really means :). Can someone tell me the proper steps to test the default value to see if the bug was really just some local mishap? Move away /var/lib/alsa/asound.state and reload the modules? -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 429064 in 2.6.21-4
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.7 found 429064 2.6.21-4 Bug#429064: linux-libc-dev: linux/types.h conflicts with sys/ustat.h Bug marked as found in version 2.6.21-4. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
