Re: Bug#575833: BUG: scheduling while atomic oops on Alix 3D2 and 3D3
reassign 575833 linux-2.6 thanks On Montag, 29. März 2010, Marcel Langner wrote: Package: base Severity: important I upgraded from lenny to squeeze and noticed a lot of kernel errors. From time to time (probably on high system load?) the system is not accessible over the network anymore. Rebooting blind using a keyboard works though. dmesg gives a lot of theses messages for different processes: [448261.696505] Pid: 0, comm: swapper Not tainted (2.6.32-3-486 #1) [448261.696524] EIP: 0060:[c10146b4] EFLAGS: 0246 CPU: 0 [448261.696550] EIP is at native_safe_halt+0x2/0x3 [448261.696568] EAX: c131 EBX: 509d9736 ECX: c131baa4 EDX: 0001 [448261.696589] ESI: 0008d800 EDI: c1313000 EBP: 015d4003 ESP: c1311fd4 [448261.696610] DS: 007b ES: 007b FS: GS: 00e0 SS: 0068 [448261.696629] CR0: 8005003b CR2: b77bc000 CR3: 01bb2000 CR4: 0090 [448261.696649] DR0: DR1: DR2: DR3: [448261.69] DR6: 0ff0 DR7: 0400 [448261.696678] Call Trace: [448261.696703] [c1008054] ? default_idle+0x37/0x55 [448261.696728] [c1002363] ? cpu_idle+0x6a/0x83 [448261.696756] [c134c708] ? start_kernel+0x2de/0x2e3 [454721.120084] BUG: scheduling while atomic: get_em1010_data/13586/0x1100 [454721.124391] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables tun sco rfcomm bridge stp bnep l2cap crc16 dm_snapshot dm_mirror dm_region _hash dm_log dm_mod fuse hwmon_vid loop snd_cs5535audio snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss geode_rng snd_pcm rng_core ecb btusb snd_timer bluetooth rfkill cdc_acm aes_i586 snd soundcore aes_gen eric ac pcspkr processor evdev snd_page_alloc cs5535_gpio geode_aes sd_mod crc_t10dif usbhid hid usb_storage ext3 jbd mbcache ide_gd_mod ide_pci_generic ata_generic libata ohci_hcd scsi_mod amd74xx ehci_hcd c s5536 via_rhine usbcore ide_core mii nls_base button thermal fan thermal_sys nbd [last unloaded: scsi_wait_scan] [454721.124698] I am using an AMD Geode based ALIX3D3 (with graphics card) but noticed the same errors on an ALIX3D2 (without graphics adapter). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.32-3-486 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem
On Tue, Mar 30, 2010 at 04:21:14PM +0200, Mathias Brodala wrote: Package: linux-2.6 Version: 2.6.33-1~experimental.4 Severity: grave Tags: experimental Justification: renders package unusable not at most important, as only local breakage, works fine for thousand others and we need more info. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All 2.6.33-based kernels in Experimental failed to boot here since they were available. The last boot message I see is the infamous Waiting for root filesystem. No specific errors or the like are printed before that. I have to Ctrl+Alt+Del my way out and boot with 2.6.32 again. how are you booting? post your grub2 /boot/grub/grub.cfg pn grub | lilo none (no description available) that seems fishy for i686. -- 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/2010033015.gd32...@baikonur.stro.at
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
maximilian attems, 30.03.2010 17:11:
On Tue, Mar 30, 2010 at 04:21:14PM +0200, Mathias Brodala wrote:
Package: linux-2.6
Version: 2.6.33-1~experimental.4
Severity: grave
Tags: experimental
Justification: renders package unusable
not at most important, as only local breakage, works fine for thousand
others and we need more info.
I never really liked the description of severities since there?s no way
for me to know if others are also affected by my specific issue. But
yeah, downgrade the severity as seems fit.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All 2.6.33-based kernels in Experimental failed to boot here since they
were available. The last boot message I see is the infamous Waiting for
root filesystem. No specific errors or the like are printed before that.
I have to Ctrl+Alt+Del my way out and boot with 2.6.32 again.
how are you booting?
Not sure what kind of answer you expect from me here.
post your grub2 /boot/grub/grub.cfg
Attached to this mail.
pn grub | lilo none (no description available)
that seems fishy for i686.
Why? The grub package is only a dummy transitional package, thus I
don?t need it. If you mean something else, please let me know.
Regards, Mathias
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuyF3oACgkQYfUFJ3ewsJhT1QCeLrVVTNdY/YAw1UET4HsgIOUY
S2cAoJj7iSo49z5wlvhtlxlRnv/rrvIR
=8/zW
-END PGP SIGNATURE-
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1920x1080
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
set locale_dir=($root)/boot/grub/locale
set lang=de
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, with Linux 2.6.33-2-amd64 --class debian --class
gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echoLoading Linux 2.6.33-2-amd64 ...
linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro
vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,85,255,255,255,255
vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,255,85,85,255,255
vt.default_red=250,170,0,170,0,170,0,51,85,255,85,255,85,255,85,255
echoLoading initial ramdisk ...
initrd /boot/initrd.img-2.6.33-2-amd64
}
menuentry Debian GNU/Linux, with Linux 2.6.33-2-amd64 (recovery mode) --class
debian --class gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echoLoading Linux 2.6.33-2-amd64 ...
linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro single
vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,85,255,255,255,255
vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,255,85,85,255,255
vt.default_red=250,170,0,170,0,170,0,51,85,255,85,255,85,255,85,255
echoLoading initial ramdisk ...
initrd /boot/initrd.img-2.6.33-2-amd64
}
menuentry Debian GNU/Linux, with Linux 2.6.32-2-amd64 --class debian --class
gnu-linux --class gnu --class os {
set gfxpayload=keep
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set b9203278-8db6-47cb-9074-e6781dada314
echoLoading Linux 2.6.32-2-amd64 ...
linux /boot/vmlinuz-2.6.32-2-amd64 root=/dev/hda6 ro
vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,85,255,255,255,255
vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,255,85,85,255,255
vt.default_red=250,170,0,170,0,170,0,51,85,255,85,255,85,255,85,255
echoLoading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-2-amd64
}
menuentry Debian GNU/Linux, with
Processed: tagging 575919
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 575919 unreproducible Bug #575919 [linux-2.6] linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem Added tag(s) unreproducible. 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 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.12699641106517.transcr...@bugs.debian.org
Processed: severity of 575919 is important
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 575919 important Bug #575919 [linux-2.6] linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem Severity set to 'important' from 'grave' 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 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.12699641026407.transcr...@bugs.debian.org
Processed: tagging 575919
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 575919 moreinfo Bug #575919 [linux-2.6] linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem Added tag(s) moreinfo. 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 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.12699641186591.transcr...@bugs.debian.org
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem
On Tue, Mar 30, 2010 at 05:23:38PM +0200, Mathias Brodala wrote: [...] linux /boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,85,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,255,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85,255,85,255,85,255 [...] This says '/dev/hda6' but root has probably changed to /dev/sda6. How did you answer the upgrade questions? 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/20100330161134.go16...@decadent.org.uk
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Ben Hutchings, 30.03.2010 18:11: On Tue, Mar 30, 2010 at 05:23:38PM +0200, Mathias Brodala wrote: [...] linux/boot/vmlinuz-2.6.33-2-amd64 root=/dev/hda6 ro vt.default_blu=250,0,0,0,170,170,170,51,85,85,85,85,255,255,255,255 vt.default_grn=250,0,170,85,0,0,170,51,85,85,255,255,85,85,255,255 vt.default_red=250,170,0,170,0,170,0,51,85,255,85,255,85,255,85,255 [...] This says '/dev/hda6' but root has probably changed to /dev/sda6. How did you answer the upgrade questions? I told it to leave it as it is. I guess it won’t be a big issue to rename this to sda and move my existing sd? devices down. Or how can I make that question re-appear? I tried with dpkg-reconfigure once but it didn’t appear again. (Maybe it should be noted that answering with No to that question will result in an unbootable state if one tries to boot with such a kernel.) Regards, Mathias -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuyJX8ACgkQYfUFJ3ewsJi7qwCdEBRKEWkNte+d+oyPFACnqD1F beMAn15OzBenvSt8Ir5IIP+ufLddQ0vC =XCrz -END PGP SIGNATURE- -- 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/4bb2257f.6000...@noctus.net
Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem
On Tue, Mar 30, 2010 at 05:23:38PM +0200, Mathias Brodala wrote: Not sure what kind of answer you expect from me here. post your grub2 /boot/grub/grub.cfg Attached to this mail. that one :) anyway grub2 looks fine, so we need more info can you please check http://wiki.debian.org/InitramfsDebug thanks -- 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/20100330163618.ge32...@baikonur.stro.at
Processed: reassign 575893 to linux-2.6, tagging 575893
Processing commands for cont...@bugs.debian.org: reassign 575893 linux-2.6 2.6.32-10 Bug #575893 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: Occasional flickering Bug reassigned from package 'xserver-xorg-video-radeon' to 'linux-2.6'. Bug No longer marked as found in versions xserver-xorg-video-ati/1:6.12.192-2. Bug #575893 [linux-2.6] xserver-xorg-video-radeon: Occasional flickering There is no source info for the package 'linux-2.6' at version '2.6.32-10' with architecture '' Unable to make a source version for version '2.6.32-10' Bug Marked as found in versions 2.6.32-10. tags 575893 + fixed-upstream Bug #575893 [linux-2.6] xserver-xorg-video-radeon: Occasional flickering Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.126997015715630.transcr...@bugs.debian.org
Bug#575919: marked as done (linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem)
Your message dated Tue, 30 Mar 2010 19:05:44 +0100 with message-id 20100330180544.gp16...@decadent.org.uk and subject line Re: Bug#575919: linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem has caused the Debian Bug report #575919, regarding linux-image-2.6.33-2-amd64: Fails to boot Waiting for root filesystem 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.) -- 575919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.33-1~experimental.4 Severity: grave Tags: experimental Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All 2.6.33-based kernels in Experimental failed to boot here since they were available. The last boot message I see is the infamous Waiting for root filesystem. No specific errors or the like are printed before that. I have to Ctrl+Alt+Del my way out and boot with 2.6.32 again. - -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: To Be Filled By O.E.M. product_name: To Be Filled By O.E.M. product_version: To Be Filled By O.E.M. chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: P2.10 board_vendor: board_name: AM2NF3-VSTA board_version: ** PCI devices: 00:00.0 Host bridge [0600]: nVidia Corporation nForce3 250Gb Host Bridge [10de:00e1] (rev a1) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:00e1] 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 Region 0: Memory at ignored (32-bit, prefetchable) Capabilities: access denied Kernel driver in use: agpgart-amd64 00:01.0 ISA bridge [0601]: nVidia Corporation nForce3 250Gb LPC Bridge [10de:00e0] (rev a2) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:00e0] 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 00:01.1 SMBus [0c05]: nVidia Corporation nForce 250Gb PCI System Management [10de:00e4] (rev a1) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:00e4] 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- Interrupt: pin A routed to IRQ 0 Region 0: I/O ports at 5080 [size=32] Region 4: I/O ports at 5000 [size=64] Region 5: I/O ports at 5040 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus 00:02.0 USB Controller [0c03]: nVidia Corporation CK8S USB Controller [10de:00e7] (rev a1) (prog-if 10 [OHCI]) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:00e7] 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 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 20 Region 0: Memory at febff000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:02.1 USB Controller [0c03]: nVidia Corporation CK8S USB Controller [10de:00e7] (rev a1) (prog-if 10 [OHCI]) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:00e7] 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 (750ns min, 250ns max) Interrupt: pin B routed to IRQ 22 Region 0: Memory at febfe000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:02.2 USB Controller [0c03]: nVidia Corporation nForce3 EHCI USB 2.0 Controller [10de:00e8] (rev a2) (prog-if 20 [EHCI]) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:00e8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
Re: drbd in linux-2.6
On 2010-03-30, dann frazier da...@debian.org wrote: drbd maintainers, As you no doubt know, linux-modules-extra has been dropped for squeeze. The recommended[1] direction for building out-of-tree module is to either: a) get merged into linux-2.6 b) use the dkms framework DRBD is now merged upstream, so it seems like a good candidate for option a. Do the drbd8 maintainers know of any issue with that (userspace tool compatability, etc)? Are you ok with dropping the drbd8-source binary package if we include this in linux-2.6? I've backported the latest upstream DRBD bits into our kernel targeted at squeeze: http://people.debian.org/~dannf/drbd/ I'd appreciate it if an existing drbd user could test it. [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html I've done the same 3-4 weeks ago and likewise send them the patch for testing, unfortunately they we unable to test it yet. 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/slrnhr4s8i.2es@inutil.org
Re: drbd in linux-2.6
On Tue, Mar 30, 2010 at 11:45:54PM +0200, Moritz Muehlenhoff wrote: On 2010-03-30, dann frazier da...@debian.org wrote: drbd maintainers, As you no doubt know, linux-modules-extra has been dropped for squeeze. The recommended[1] direction for building out-of-tree module is to either: a) get merged into linux-2.6 b) use the dkms framework DRBD is now merged upstream, so it seems like a good candidate for option a. Do the drbd8 maintainers know of any issue with that (userspace tool compatability, etc)? Are you ok with dropping the drbd8-source binary package if we include this in linux-2.6? I've backported the latest upstream DRBD bits into our kernel targeted at squeeze: http://people.debian.org/~dannf/drbd/ I'd appreciate it if an existing drbd user could test it. [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html I've done the same 3-4 weeks ago and likewise send them the patch for testing, unfortunately they we unable to test it yet. Oh, sorry - I must've missed that. Did you get a response or just silence? I was thinking that if we didn't get a response in a couple of days, I could contact some of the drbd8 bug reporters and see if we can recruit them to test :) -- dann frazier -- 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/20100330220222.ga...@lackof.org
Bug#575893: xserver-xorg-video-radeon: Occasional flickering
Alex Deucher wrote: should be fixed with this patch: http://marc.info/?l=dri-develm=126996657723896w=2 Alex Yes, applying that (manually because some chunks fail to apply) to the kernel's source package seems to fix the issue. Thanks you! So it seems the problem is in the kernel and not the xorg video driver. Regards, Rubidium -- 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/4bb26c5e.30...@rbijker.net
Bug#575726: [088/116] rt2860sta: Fix argument to linux_pci_unmap_single()
2.6.32-stable review patch. If anyone has any objections, please let us know.
--
From: Ben Hutchings b...@decadent.org.uk
John Halton wrote in http://bugs.debian.org/575726:
Whenever wpa_supplicant is deactivated (whether by killing the process or
during a normal shutdown) I am getting a kerneloops that prevents the
computer from completing shutdown. Here is the relevant syslog output:
The backtrace points to an incorrect call from RTMPFreeTxRxRingMemory()
into linux_pci_unmap_single(). This appears to have been fixed in Linux
2.6.33 by this change:
commit ca97b8388838ee9ea4b4bad04948f8f7f8a607a3
Author: Bartlomiej Zolnierkiewicz bzoln...@gmail.com
Date: Tue Sep 22 20:44:07 2009 +0200
Staging: rt28x0: updates from vendor's V2.1.0.0 drivers
For stable-2.6.32, just fix this one function call.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Signed-off-by: Greg Kroah-Hartman gre...@suse.de
---
drivers/staging/rt2860/common/2860_rtmp_init.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/rt2860/common/2860_rtmp_init.c
+++ b/drivers/staging/rt2860/common/2860_rtmp_init.c
@@ -716,7 +716,7 @@ VOID RTMPFreeTxRxRingMemory(
{
if ((pAd-RxRing.Cell[index].DmaBuf.AllocVa)
(pAd-RxRing.Cell[index].pNdisPacket))
{
- PCI_UNMAP_SINGLE(pObj-pci_dev,
pAd-RxRing.Cell[index].DmaBuf.AllocPa,
pAd-RxRing.Cell[index].DmaBuf.AllocSize, PCI_DMA_FROMDEVICE);
+ PCI_UNMAP_SINGLE(pAd,
pAd-RxRing.Cell[index].DmaBuf.AllocPa,
pAd-RxRing.Cell[index].DmaBuf.AllocSize, PCI_DMA_FROMDEVICE);
RELEASE_NDIS_PACKET(pAd,
pAd-RxRing.Cell[index].pNdisPacket, NDIS_STATUS_SUCCESS);
}
}
--
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/20100330225657.012198...@linux.site
