Bug#334273: linux-image-2.6.13-1-686: /etc/init.d/dbus-1 causes kernel oops
Package: linux-image-2.6.13-1-686 Version: 2.6.13-1 Severity: normal As soon as /etc/init.d/dbus-1 is started in the boot process the following oops comes up: Oct 16 19:04:13 feivel kernel: lp0: using parport0 (interrupt-driven). Oct 16 19:04:15 feivel kernel: Unable to handle kernel paging request at virtual address 30303110 Oct 16 19:04:15 feivel kernel: printing eip: Oct 16 19:04:15 feivel kernel: c01a1beb Oct 16 19:04:15 feivel kernel: *pde = Oct 16 19:04:15 feivel kernel: Oops: 0002 [#1] Oct 16 19:04:15 feivel kernel: Modules linked in: lp autofs4 button af_packet quota_v2 aes_i586 dm_crypt dm_mod cpufreq_powersave cpufreq_userspace speedstep_centrino freq_table snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss thermal processor fan battery ac cryptoloop loop nvidia usbkbd pcmcia i810_audio ac97_codec eth1394 usbhid yenta_socket rsrc_nonstatic snd_intel8x0m ipw2100 firmware_class i2c_i801 e100 snd_intel8x0 i2c_core ieee80211 ieee80211_crypt mii snd_ac97_codec pcmcia_core ohci1394 ehci_hcd uhci_hcd snd_pcm snd_timer snd soundcore usbcore ieee1394 snd_page_alloc pci_hotplug parport_pc parport intel_agp agpgart psmouse serio_raw ide_cd cdrom evdev mousedev ext3 jbd mbcache ide_disk ide_generic via82cxxx trm290 triflex slc90e66 sis5513 siimage serverworks sc1200 rz1000 piix pdc202xx_old opti621 ns87415 it821x hpt366 hpt34x generic cy82c693 cs5530 cs5520 cmd64x atiixp amd74xx alim15x3 aec62xx pdc202xx_new ide_core unix Oct 16 19:04:15 feivel kernel: CPU:0 Oct 16 19:04:15 feivel kernel: EIP:0060:[sysfs_release+59/128]Tainted: PF VLI Oct 16 19:04:15 feivel kernel: EFLAGS: 00010206 (2.6.13-1-686) Oct 16 19:04:15 feivel kernel: EIP is at sysfs_release+0x3b/0x80 Oct 16 19:04:15 feivel kernel: eax: ebx: 30303030 ecx: c01cbaa0 edx: Oct 16 19:04:15 feivel kernel: esi: df3c3c00 edi: c15980a4 ebp: dcf4a90c esp: dcc0ff58 Oct 16 19:04:15 feivel kernel: ds: 007b es: 007b ss: 0068 Oct 16 19:04:15 feivel kernel: Process hald (pid: 5730, threadinfo=dcc0e000 task=de9f3aa0) Oct 16 19:04:15 feivel kernel: Stack: c15980a4 0010 dec12d40 c14d4100 c0160a81 dcf4a90c dec12d40 Oct 16 19:04:15 feivel kernel: dcf0f054 dec12d40 ded4cac0 dcc0e000 c015ef52 dec12d40 Oct 16 19:04:15 feivel kernel:ded4cac0 dec12d40 080d7ec8 080d66a0 c015efe8 dec12d40 ded4cac0 000e Oct 16 19:04:15 feivel kernel: Call Trace: Oct 16 19:04:15 feivel kernel: [__fput+161/384] __fput+0xa1/0x180 Oct 16 19:04:15 feivel kernel: [filp_close+82/144] filp_close+0x52/0x90 Oct 16 19:04:15 feivel kernel: [sys_close+88/96] sys_close+0x58/0x60 Oct 16 19:04:15 feivel kernel: [syscall_call+7/11] syscall_call+0x7/0xb Oct 16 19:04:15 feivel kernel: Code: 7c 24 0c 8b 51 08 8b 71 78 8b 42 0c 8b 40 48 8b 78 14 8b 42 48 85 ff 8b 40 14 8b 58 04 74 08 89 3c 24 e8 c9 9e 02 00 85 db 74 0b 8b e0 00 00 00 83 3b 02 74 2c 85 f6 74 16 8b 46 0c 85 c0 74 Just preventing the initscript from being run makes the kernel not oops anymore. Michael -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-1-686 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.13-1-686 depends on: ii initrd-tools 0.1.82 tools to create initrd image for p ii module-init-tools 3.2-pre9-2 tools for managing Linux kernel mo linux-image-2.6.13-1-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334275: linux-image-2.6.13-1-686: ide error messages come up
Package: linux-image-2.6.13-1-686
Version: 2.6.13-1
Severity: normal
With 2.6.13 I get the following IDE error messages during boot time:
Oct 14 15:55:24 feivel kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Oct 14 15:55:24 feivel kernel: hda: dma_intr: error=0x04 { DriveStatusError }
Oct 14 15:55:24 feivel kernel: ide: failed opcode was: unknown
Oct 14 15:55:24 feivel kernel: hda: set_drive_speed_status: status=0x51{
DriveReady SeekComplete Error }
Oct 14 15:55:24 feivel kernel: hda: set_drive_speed_status: error=0xd0 {
BadSector UncorrectableError SectorIdNotFound }, LBAsect=13684944, sector=24
921508
Oct 14 15:55:24 feivel kernel: ide: failed opcode was: unknown
I have never seen any of these with 2.6.12 or earlier kernels. The
unknown opcode and sector look strange. Any idea what I could do to get
more information?
Michael
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.13-1-686 depends on:
ii initrd-tools 0.1.82 tools to create initrd image for p
ii module-init-tools 3.2-pre9-2 tools for managing Linux kernel mo
linux-image-2.6.13-1-686 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334273: linux-image-2.6.13-1-686: /etc/init.d/dbus-1 causes kernel oops
On Sun, Oct 16, 2005 at 08:45:50PM +0200, Bastian Blank wrote: > On Sun, Oct 16, 2005 at 08:18:49PM +0200, Michael Meskes wrote: > > Oct 16 19:04:15 feivel kernel: EIP:0060:[sysfs_release+59/128] > > Tainted: PF VLI > > Proprietary module and forced module load. Fix that first. Sorry, my fault. I sent in the wrong oops. Actually the oops made me try nv again and since it works correctly with my card now I was finally able to get rid of nvidia. But the Oops didn't disappear. Just to be sure I tried again this morning. Here's the log entry: Oct 17 09:23:42 feivel kernel: Unable to handle kernel paging request at virtual address 30303110 Oct 17 09:23:42 feivel kernel: printing eip: Oct 17 09:23:42 feivel kernel: c01a1beb Oct 17 09:23:42 feivel kernel: *pde = Oct 17 09:23:42 feivel kernel: Oops: 0002 [#1] Oct 17 09:23:42 feivel kernel: Modules linked in: lp autofs4 button ipv6 af_packet quota_v2 aes_i586 dm_crypt dm_mod cpufreq_powersave cpufreq_userspace speedstep_centrino freq_table snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss thermal processor fan battery ac cryptoloop loop usbkbd eth1394 usbhid pcmcia ipw2100 i810_audio firmware_class ac97_codec ieee80211 ieee80211_crypt yenta_socket rsrc_nonstatic pcmcia_core e100 mii ohci1394 ieee1394 snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm snd_timer snd soundcore snd_page_alloc ehci_hcd i2c_i801 i2c_core uhci_hcd usbcore pci_hotplug parport_pc parport intel_agp agpgart ide_cd psmouse cdrom serio_raw evdev mousedev ext3 jbd mbcache ide_disk ide_generic via82cxxx trm290 triflex slc90e66 sis5513 siimage serverworks sc1200 rz1000 piix pdc202xx_old opti621 ns87415 it821x hpt366 hpt34x generic cy82c693 cs5530 cs5520 cmd64x atiixp amd74xx alim15x3 aec62xx pdc202xx_new ide_core unix Oct 17 09:23:42 feivel kernel: CPU:0 Oct 17 09:23:42 feivel kernel: EIP:0060:[sysfs_release+59/128]Tainted: GF VLI Oct 17 09:23:42 feivel kernel: EFLAGS: 00010206 (2.6.13-1-686) Oct 17 09:23:42 feivel kernel: EIP is at sysfs_release+0x3b/0x80 Oct 17 09:23:42 feivel kernel: eax: ebx: 30303030 ecx: c01cbaa0 edx: Oct 17 09:23:42 feivel kernel: esi: df82fdc0 edi: c15970a4 ebp: dd01dbd4 esp: dd4d9f58 Oct 17 09:23:42 feivel kernel: ds: 007b es: 007b ss: 0068 Oct 17 09:23:42 feivel kernel: Process hald (pid: 5696, threadinfo=dd4d8000 task=de223580) Oct 17 09:23:42 feivel kernel: Stack: c15970a4 0010 df1f6a40 c14d4100 c0160a81 dd01dbd4 df1f6a40 Oct 17 09:23:42 feivel kernel: dd7d540c df1f6a40 dde96200 dd4d8000 c015ef52 df1f6a40 Oct 17 09:23:42 feivel kernel:dde96200 df1f6a40 080d5c80 080d6028 c015efe8 df1f6a40 dde96200 000e Oct 17 09:23:42 feivel kernel: Call Trace: Oct 17 09:23:42 feivel kernel: [__fput+161/384] __fput+0xa1/0x180 Oct 17 09:23:42 feivel kernel: [filp_close+82/144] filp_close+0x52/0x90 Oct 17 09:23:42 feivel kernel: [sys_close+88/96] sys_close+0x58/0x60 Oct 17 09:23:42 feivel kernel: [syscall_call+7/11] syscall_call+0x7/0xb Oct 17 09:23:42 feivel kernel: Code: 7c 24 0c 8b 51 08 8b 71 78 8b 42 0c 8b 40 48 8b 78 14 8b 42 48 85 ff 8b 40 14 8b 58 04 74 08 89 3c 24 e8 c9 9e 02 00 85 db 74 0b 8b e0 00 00 00 83 3b 02 74 2c 85 f6 74 16 8b 46 0c 85 c0 74 Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334275: linux-image-2.6.13-1-686: ide error messages come up
On Sun, Oct 16, 2005 at 10:05:32PM +0200, Maximilian Attems wrote: > backup your data, aboves is a drive failure. Well, at first I thought the same, but when I went back to 2.6.12 for another reason the message disappeared. That's kind of strange. I do not get any ide error message with 2.6.12 and just this one during initilisation with 2.6.13. Is there a way to make sure it's really the hardware? Usually with hw problem the message comes up more often. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Still there
severity 479709 grave thanks Not sure whether the severity is correct, but this time the bug hit me with a dataloss and I suppose that others might/will experience the same. I doubt it's a good idea to have this kernel in Lenny, especially with the patch being that easy. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Still there
> On Wed, Jul 30, 2008 at 11:49:36AM +0200, Michael Meskes wrote: > > Not sure whether the severity is correct, > > No. There are many system which don't choke on this. Right, but there are also many systems choking. And they are all in the risk of losing data. > The patch is applied upstream for 2.6.26. Closing as it is in NEW now > and targeted for lenny. If 2.6.25 is not released with Lenny fine with me. Do you have an URL so I can go out and try the new kernel? I couldn't find it in NEW. Might be better to close the report once the new kernel is available, but this is kind of nitpicking. :-) Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Still there
On Wed, Jul 30, 2008 at 02:39:01PM +0200, Bastian Blank wrote: > > And they are all in the > > risk of losing data. > > Please explain. Data not reaching the disk is something which can't be > avoided in a crash situation. Data loss in the kernel context is usualy You're absolutely right, but this crash situation can be avoided and thus this bug is the very reason for my data loss which admittedly was not a significant one. > http://wiki.debian.org/DebianKernel describes how to get our snapshots. I know that one but thought the first "official" kernel would be available. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: reopened
I can confirm that a) the patch is applied and b) the system still freezes. Thus I reopen the bug. I ran 2.6.26 without a problem for quite some time until I discovered that my chrony still wasn't starting. After starting it again the system froze in a matter of seconds. Could anyone of you NOT experiencing the problem so far try running chrony to see whether this triggers it? Also for those of you having the same problem, does disabling chrony help? Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494144: Significant problem
severity 494144 serious thanks I think we have a very severe problem here that must be fixed before Lenny is released. There may be a solution around that I don't know or see that lies outside of the kernel and thus the bug should be reassigned, but still I think this needs a fix before the release. Now to my reasoning, : Jordi already pointed out there was a change in kernel behaviour with 2.6.26 in that the kernel default when not finding symbol version information. Up to kernel 2.6.25 the kernel called itself tainted and accepted the module. Since 2.6.26. the kernel throws an error. There is, however, a way to insmod modules without version information, namely by using "modprobe --force". But this is no longer possible because the kernel is compiled without setting CONFIG_MODULE_FORCE_LOAD. This has an effect for all out-of-tree modules, I stumbled upon it by looking at virtualbox-ose-guest-modules. There simply appears to be no way at all to include the vboxvfs module which depends on the vboxadd module. I might be wrong and like to hear what I missed, but if I didn't miss anything we are in must-fix situation. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Handling of linux-modules-*-2.6 during
> it was stupid to upload 1.6.6 to unstable, however, the the only sane Which of course is easy to say in hindsight. I do not remember seeing a similar statement before the upload. Besides I agree that virtualbox-ose 1.6.6 should move into Lenny because upstream considers this a bugfix release. This btw is also the reason why it was uploaded to sid. After all it fixes some bugs. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Handling of linux-modules-*-2.6 during
On Sat, Oct 04, 2008 at 08:33:01PM +0200, Daniel Baumann wrote: > how suprising is that when the upload was made by patrick without prior > discussion/announcement/communication/$whatever on the list. Right no discussion from noone. So we are all at fault somehow. > however, as indicated already, past is past. Agreed. > > This btw is also the reason why it > > was uploaded to sid. After all it fixes some bugs. > > for the records: the new upstream version only fixes two bugs: #495028 > which is a cosmetic thing and not worth the trouble, and #499623 which > is absolutely unimportant - 2.6.27 is post lenny anyway. Yes, in terms of Debian bugs. But it does close a lot of upstream bugs. Granted they weren't reported for Debian but they were available in Debian too. Therefore I think the release team's decision to unblock 1.6.6 is the best scenarion anyway. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437604: linux-headers-2.6.22-1: /usr/src/linux/net/mac80211/ieee80211_rate.h needed for iwlwifi compilation
Package: linux-headers-2.6.22-1 Version: 2.6.22-3 Severity: wishlist Please install [/usr/src/linux/]net/mac80211/ieee80211_rate.h. It is needed for compilation of Intel's new iwlwifi driver. Thanks. Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441146:
reopen 441146 thanks The bug is not fixed. I don't care which piece of the software broke, the fact in the matter is that the virtualbox-ose module is not build by linux-modules-extra. That means the bug is still present. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go VfL Borussia! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441146:
On Sat, Nov 10, 2007 at 06:08:44PM +0100, Daniel Baumann wrote: > > I don't care which piece of the software broke, > > thank you for letting me know. however, how about actually letting the > *maintainer* of the package decide that? Decide what? Which software is broken? Or whether this is a bug? > > the fact in the matter is that the virtualbox-ose module is not build by > > linux-modules-extra. > > wrong. what matters is the reason why it is not build. Of course the reason matters, but the bug simply was about a binary package not being available. IMO the only way to fix this is to deliver the package. > #441146 is about including it into the conglomeration package and thus a > bug in linux-modules-extra-2.6. > > the *new* issue is, unrelated to #441146, that virtualbox-ose modules do > no longer build since 1.5.2, and thus a bug in virtualbox-ose-source. > > it is the task of the module-source maintainer to ship a working > module-source package, not the conglomeration package maintainer; > therefore cloning, reassigned and closed the approriate bug. Fine with me. I don't mind having this bug reassigned. To be honest in my opinion we should have two open bugs, one against virtualbox-ose-source and one against linux-modules-extra-2.6 with the latter one being blocked by the former. I still disagree with you guys closing the bug though, though. Just for the record we should note that this bug had neither been reported against virtualbox-ose-source nor even communicated with the package maintainers. But then, given that you are part of the maintainer team for virtualbox-ose-source as well as the linux-modules-extra-2.6 team (or even its sole maintainer, too lazy to check) you might consier this enough information. > extremely sophisticated way to kill peoples time. No, just a try to keep our bug tracking system as open and informative as it can be. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go VfL Borussia! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441146:
On Sun, Nov 11, 2007 at 07:30:19PM +0100, Daniel Baumann wrote: > > Of course the reason matters, but the bug simply was about a binary > > package not being available. > > no, read again. #441146 is about including some definition files into > linux-modules-extra-2.6, not more, not less. as this was done, the bug > is fixed. Maybe we should agree upon disagreeing on this one. I try to view this from the user's point of view and the only way to help the user is to provide a package. But then Torsten might have meant the definition files only. > > IMO the only way to fix this is to deliver > > the package. > > are you really not getting it? the /new/ problem is a problem in > virtualbox-ose-source. it has absolutely nothing to do with > linux-modules-extra-2.6. it can not be fixed in linux-modulex-extra-2.6. > that is why it is not a bug in linux-modules-extra-2.6. You did read my message, didn't you? > > Fine with me. I don't mind having this bug reassigned. To be honest in > > my opinion we should have two open bugs, one against > > virtualbox-ose-source and one against linux-modules-extra-2.6 with the > > latter one being blocked by the former. I still disagree with you guys > > closing the bug though, though. > > no. the fact that virtualbox-ose-source does not comply with > linux-modulex-extra-2.6 is a bug in virtualbox-ose-source, not in > linux-modules-extra-2.6. No argument here. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go VfL Borussia! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451116: linux-modules-extra-2.6: Please add virtualbox-ose-guest-source and create virtualbox-ose-guest-modules
Package: linux-modules-extra-2.6 Version: 2.6.22-6 Severity: wishlist Subject says it all. The package in question virtualbox-ose-guest-source_1.5.2-dfsg2-1_all.deb is just being uploaded. Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451116: New virtualbox-ose upload
The problems mentioned in these two bug reports should be fixed in the lates virtualbox-ose upload that sits in incoming atm. Daniel, could you please build l-m-e again? Thanks. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go VfL Borussia! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451116: closed by Daniel Baumann <[EMAIL PROTECTED]>
reopen 451116 thanks > #451116: linux-modules-extra-2.6: Please add virtualbox-ose-guest-source and > create virtualbox-ose-guest-modules > > It has been closed by Daniel Baumann <[EMAIL PROTECTED]>. > ... > virtualbox-ose-modules-2.6-486_2.6.24-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6-486_2.6.24-1_i386.deb > virtualbox-ose-modules-2.6-686-bigmem_2.6.24-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6-686-bigmem_2.6.24-1_i386.deb > virtualbox-ose-modules-2.6-686_2.6.24-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6-686_2.6.24-1_i386.deb > virtualbox-ose-modules-2.6-xen-686_2.6.24-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6-xen-686_2.6.24-1_i386.deb > virtualbox-ose-modules-2.6.24-1-486_2.6.24+1.5.4-dfsg-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6.24-1-486_2.6.24+1.5.4-dfsg-1_i386.deb > virtualbox-ose-modules-2.6.24-1-686-bigmem_2.6.24+1.5.4-dfsg-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6.24-1-686-bigmem_2.6.24+1.5.4-dfsg-1_i386.deb > virtualbox-ose-modules-2.6.24-1-686_2.6.24+1.5.4-dfsg-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6.24-1-686_2.6.24+1.5.4-dfsg-1_i386.deb > virtualbox-ose-modules-2.6.24-1-xen-686_2.6.24+1.5.4-dfsg-1_i386.deb > to > pool/main/l/linux-modules-extra-2.6/virtualbox-ose-modules-2.6.24-1-xen-686_2.6.24+1.5.4-dfsg-1_i386.deb > ... > virtualbox-ose-modules-2.6-486 - PC virtualization solution modules for > Linux 2.6 on x86 > virtualbox-ose-modules-2.6-686 - PC virtualization solution modules for > Linux 2.6 on PPro/Celeron/ > virtualbox-ose-modules-2.6-686-bigmem - PC virtualization solution modules > for Linux 2.6 on PPro/Celeron/ > virtualbox-ose-modules-2.6-xen-686 - PC virtualization solution modules for > Linux 2.6 on i686 > virtualbox-ose-modules-2.6.24-1-486 - PC virtualization solution modules for > Linux 2.6.24 on x86 > virtualbox-ose-modules-2.6.24-1-686 - PC virtualization solution modules for > Linux 2.6.24 on PPro/Celer > virtualbox-ose-modules-2.6.24-1-686-bigmem - PC virtualization solution > modules for Linux 2.6.24 on PPro/Celer > virtualbox-ose-modules-2.6.24-1-xen-686 - PC virtualization solution modules > for Linux 2.6.24 on i686 > ... >* Adding virtualbox-ose-guest (Closes: #451116). Please correct me if I'm wrong but I fail to see the virtualbox-ose-guest packages on these lists. What am I missing? Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475131: Questions
> compilation failed when the last upload of lme happened, so most likely > no other attempt before 2.6.25. Where can we find this? Is Torsten correct with the assumption that only guest-sources fail? Judging from the build log on http://buildd.debian.org/fetch.cgi?pkg=linux-modules-extra-2.6;ver=2.6.24-7;arch=amd64;stamp=1207865393 it seems that virtualbox-ose sources are only build on i386: ... ** Using build dependencies supplied by package: Build-Depends: ... virtualbox-ose-guest-source [i386], virtualbox-ose-source [i386] Checking for already installed source dependencies... ... BTW the very same link shows that a different source package is failing amd64 build. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475131: Bug#475738: [Pkg-virtualbox-devel] Bug#475738: virtualbox-ose:
On Wed, Apr 16, 2008 at 11:27:34AM +0200, Daniel Baumann wrote:
> you need to build it yourself, however, it gives a lot of warnings and
> this is the last part where it breaks:
>
> {standard input}: Assembler messages:
> {standard input}:191: Error: suffix or operands invalid for `pushf'
> {standard input}:192: Error: suffix or operands invalid for `pop'
> ...
Yes, this looks like the well known problem of mixing i386 and amd64
builds. It appears to me that the culprit is lme setting ARCH to i386
when doing a amd64 build on i386, well at least it appears to set it to
this value, please correct me if I'm wrong. The virtualbox-ose Makefile,
however, uses ARCH to learn about the arch it is supposed to build for.
I haven't tried reproducing this in detail but assuming my assumption is
right, what do we do?
Is ARCH a reserved variable? Or is it just a design decision by lme? Or
in other words, can we change the name of this variable? According to
/usr/src/linux-headers-*/Makefile ARCH should be the target architecture:
When performing cross compilation for other architectures ARCH shall be set
# to the target architecture. (See arch/* for the possibilities).
Isn't this amd64 in this case?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Same here
I'm experiencing the same problem on my HP nx7400 laptop but do not get the lost interrupts. The system simply freezes after only a very short uptime, sometimes even during the boot process. No output given. I tried both, the amd64 and the 686 flavour and both fail. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Same here
Hi, On Sat, May 10, 2008 at 12:11:56AM +0200, maximilian attems wrote: > > I'm experiencing the same problem on my HP nx7400 laptop but do not get > > the lost interrupts. The system simply freezes after only a very short > > uptime, sometimes even during the boot process. No output given. > > > > I tried both, the amd64 and the 686 flavour and both fail. > > can you please file the bug upstream in bugzilla.kernel.org and > let us know the bug number. thanks I spend some time trying to figure out what's going on, using different boot option, compiling my own kernel, adding debug output, etc. which took some time because it sometimes took about a day before the system froze. At the moment I do run 2.6.25 with an uptime of ~ 26 hours (including suspend time in between) without a problem. It's too early to tell whether my last change was the reason, but you might want to try too. All I did was to disable the high precision timer by adding "hpet=disable" to my command line. Checking whether the right rtc module is included is probably the next step, but before I need to keep it running some more time to see whether the problem is really fixed. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Same here
On Fri, Jun 20, 2008 at 02:46:03PM +0200, maximilian attems wrote: > irc there were fixes for the hpet in 2.6.26, can you please checkout > those too, trunk apt lines -> http://wiki.debian.org/DebianKernel I tried the Ubuntu 2.6.26 package which was the kernel that ran for almost a day. Looking at the changes brought me to hpet=disable. :-) > (beware to blacklist snd-pcsp or you'll here a lot of noise) Yes, this one's ugly. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479709: Confirmation
I applied that patch given in this bugreport and recompiled the Debian packges. It seems that this successfully solved my problem as well as I'm using the kernel for about one day now without a problem. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#727041: kernel 3.11-1 freezes when via velocity interface comes up
Package: src:linux Version: 3.11.5-1 Severity: grave Tags: patch Subject kind of says it all. My system freezes solidly as soon as I ifup the network interface. Please see e.g. http://www.spinics.net/lists/netdev/msg251287.html for more details. Attached patch from mentioned URL fixes the problem for me. I haven't checked if kernel devs used the same patch, though. Michael Description: prevent freeze in velocity based networking Origin: http://www.spinics.net/lists/netdev/msg251312.html --- linux-3.11.5.orig/drivers/net/ethernet/via/via-velocity.c +++ linux-3.11.5/drivers/net/ethernet/via/via-velocity.c @@ -2172,14 +2172,12 @@ static int velocity_poll(struct napi_str unsigned int rx_done; unsigned long flags; - spin_lock_irqsave(&vptr->lock, flags); /* * Do rx and tx twice for performance (taken from the VIA * out-of-tree driver). */ - rx_done = velocity_rx_srv(vptr, budget / 2); - velocity_tx_srv(vptr); - rx_done += velocity_rx_srv(vptr, budget - rx_done); + rx_done = velocity_rx_srv(vptr, budget); + spin_lock_irqsave(&vptr->lock, flags); velocity_tx_srv(vptr); /* If budget not fully consumed, exit the polling mode */
virtualbox-ose modules
Hi, now that's Lenny is out I'd like to migrate virtualbox-ose-modules from experimental to sid. As agreed upon we have a new source package similar to lme that only builds virtualbox-soe modules. With the binary packages getting the same name I wonder what's the best way to migrate? Upload a lme version without those packages and as soon as this makes it into the archive upload the new package? Mcihael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: virtualbox-ose modules
On Mon, Feb 16, 2009 at 11:48:33AM +0100, Bastian Blank wrote: > On Mon, Feb 16, 2009 at 11:22:21AM +0100, Michael Meskes wrote: > > As agreed upon we have a new source package similar to > > lme > > that only builds virtualbox-soe modules. > > Agreed upon by whom? Well it was proposed by me to this very list and no one objected. So in the view of the good old Unix world I consider this agreed upon. However, I don't mind going for a different solution. You were the one not wanting to build virtualbox-ose module packages anymore. > > >Upload a lme version > > without > > those packages and as soon as this makes it into the archive upload the new > > package? > > I don't intend to remove that now. And I don't even intend to support > modules built not by this packages any longer. Sorry, I don't understand this. You don't want to remove virtualbox-ose from lme, okay, but what does the second sentence mean? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi
On Thu, Mar 26, 2009 at 12:44:32PM -0300, Henrique de Moraes Holschuh wrote: > never had to look back at, before writing something. The non-hotkey events > go over netlink, yes. But hotkeys go only over the input device, where they > belong, and there is no driver switch to mess with that. Could anyone enlighten me please, where these events are to be found? acpid does not just read the netlink inteface but also the input layer and thus is *supposed* to also get events coming over an input device. You can use kacpimon to try it out. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
virtualbox-ose modules, yet again
Hi, with a new vbox major version out people again start bugging us about the not-yet-existing modules package. As a vbox user/maintainer I have to rebuild the modules for a new vbox version as well as for a new kernel version so I wouldn't mind uploading it too, meaning we will get a lot bug reports less than with the current setup that rebuilds the vbox module package with lme. The last time I brought up this topic the discussion stopped somewhere in between, so I'd like to bring this up again and settle it for good. A test package is available in experimental albeit only having a 2.6.26 version as this was the actual kernel when vbox2 went from experimental to sid. What do you guys think? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Pkg-virtualbox-devel] Kernel module version requirements
On Tue, Oct 28, 2008 at 11:00:44PM +0100, Bastian Blank wrote: > Please describe the version requirements of the dependency vbox > application and kernel module. There was reports that a 1.6.2 module > does not work with a 1.6.6 application. The version has to be the same afaik. It appears that there is neither a backward nor a forward compatibility. I was under the impression that a 1.6.6 module works with a 1.6.2 application but a test showed that it doesn't. Therefore I wonder whether we should add a conflict into the module's control file. Comments anyone? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Kernel module version requirements
On Wed, Oct 29, 2008 at 01:52:20PM +0100, Bastian Blank wrote: > > Therefore I wonder whether we should add a conflict into the module's > > control > > file. Comments anyone? > > No. virtualbox have to make this a dependency. I have no problem in > producing a virtual package name which describes some sort of ABI. But it's just a recommendation then. There is no dependency on the module package in the vbox package. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Kernel module version requirements
On Wed, Oct 29, 2008 at 04:28:55PM +0100, Bastian Blank wrote: > Please read http://www.debian.org/MailingLists/. ??? > It is a hard dependency, or does virtualbox work without the module? It does work without a module, but you cannot start a VM. Now this reduces the functionality significantly but still there is functionality (like working with disk images) that works without it. Besides, people might install the module from source I think. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505440: initramfs-tools: leaks environment
Package: initramfs-tools Version: 0.92l Severity: important A lot of the environment is leaked into into creating problems in other init scripts. I'm not sure whether the severity is right, but some other init scripts do not work as expected because of some of the environment they inherit. Here's a list created by adding env >"$(mktemp -t foobar.env.)" to the boot process: CONSOLE=/dev/console SELINUX_INIT=YES break= TERM=linux rootmnt=/root INIT_VERSION=sysvinit-2.86 init=/sbin/init panic= PATH=/sbin:/usr/sbin:/bin:/usr/bin _=/usr/bin/env RUNLEVEL=S runlevel=S PWD=/ resume=/dev/hda5 ROOTFSTYPE= VERBOSE=no MODPROBE_OPTIONS=-qb resume_offset= PREVLEVEL=N previous=N ROOT=/dev/disk/by-uuid/cc016eb2-5e03-476c-936f-b2195a49b46f quiet=n ROOTFLAGS= SHLVL=2 ROOTDELAY= HOME=/ BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-686 DPKG_ARCH=i386 blacklist= readonly=y Michael -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=7f264e00-a4ae-45a5-88c4-aa077b575515 ro -- /proc/filesystems ext3 fuseblk iso9660 vfat -- lsmod Module Size Used by nls_utf86272 0 nls_cp437 11136 0 vfat 14976 0 fat51128 1 vfat isofs 35880 0 nls_base 12932 5 nls_utf8,nls_cp437,vfat,fat,isofs zlib_inflate 18944 1 isofs iwl394592916 0 mac80211 162864 1 iwl3945 nfs 251696 0 lockd 68560 1 nfs nfs_acl 7552 1 nfs sunrpc197480 5 nfs,lockd,nfs_acl i915 35072 1 drm91488 2 i915 rfcomm 38176 1 l2cap 23936 5 rfcomm bluetooth 57124 4 rfcomm,l2cap tun14084 1 vboxdrv 1658800 1 ppdev 11656 0 lp 14724 0 autofs424200 2 acpi_cpufreq 11792 0 cpufreq_powersave 6400 0 cpufreq_stats 9120 0 cpufreq_ondemand 11792 2 freq_table 9344 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand cpufreq_conservative11784 0 cpufreq_userspace 8452 0 ipv6 288328 14 bridge 53544 0 quota_v2 12800 2 fuse 53184 1 aes_x86_64 12416 1 aes_generic32552 1 aes_x86_64 cbc 7936 1 dm_crypt 17032 1 dm_mod 58864 3 dm_crypt loop 19468 0 arc46272 2 ecb 7296 2 crypto_blkcipher 21636 4 cbc,dm_crypt,ecb snd_hda_intel 434776 1 snd_pcm81672 1 snd_hda_intel snd_seq54304 0 parport_pc 31016 1 led_class 8968 1 iwl3945 yenta_socket 27916 1 snd_timer 25744 2 snd_pcm,snd_seq snd_seq_device 11668 1 snd_seq rng_core8968 0 rsrc_nonstatic 14080 1 yenta_socket snd63688 7 snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_device parport41776 3 ppdev,lp,parport_pc psmouse42268 0 pcspkr 7040 0 serio_raw 9860 0 iTCO_wdt 15696 0 cfg80211 30224 2 iwl3945,mac80211 container 8320 0 ac 9352 0 video 24084 0 output 7808 1 video wmi11712 0 battery16904 0 soundcore 12064 1 snd snd_page_alloc 13072 2 snd_hda_intel,snd_pcm intel_agp 31728 1 button 11680 0 evdev 14208 11 ext3 124944 5 jbd51240 1 ext3 mbcache12804 1 ext3 ide_cd_mod 36360 0 cdrom 37928 1 ide_cd_mod ata_generic10116 0 sd_mod 29376 7 usbhid 45792 0 hid41792 1 usbhid ff_memless 9224 1 usbhid b4429968 0 piix 12424 0 [permanent] ahci 32520 6 libata165472 2 ata_generic,ahci scsi_mod 160760 2 sd_mod,libata ssb43140 1 b44 pcmcia 38680 1 ssb pcmcia_core41508 4 yenta_socket,rsrc_nonstatic,ssb,pcmcia firmware_class 12544 2 iwl3945,pcmcia mii 9856 1 b44 dock 14112 1 libata ohci1394 32564 0 ide_pci_generic 9220 0 [permanent] ide_core 128284 3 ide_cd_mod,piix,ide_pci_generic ieee1394 93816 1 ohci1394 ehci_hcd 36108 0 uhci_hcd 25760 0 thermal22688 0 processor 42304 4 acpi_cpufreq,thermal fan
Bug#599054: [Pkg-virtualbox-devel] Bug#599054: After kernel upgrading vbox is no more usable
> I had to rebuild both -guest-kms and -ose modules, which implies that > there's not a safe upgrade path for vbox when ABI changes as it is > currently. Quite bad, because the näive user needs to manually recover > things more than expected. Well there is. If this really was an ABI change the kernel version number should have changed ttbomk which then would have easily told you to rebuild. After all there would have been no modules for that new kernel. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20101004130943.ga25...@hyperion.credativ.de
Bug#599054: [Pkg-virtualbox-devel] Bug#599054: After kernel upgrading vbox is no more usable
On Mon, Oct 04, 2010 at 01:18:42PM +0200, Francesco P. Lovergine wrote: > module-assistant fails as well: > ... > Starting VirtualBox kernel modulesmodprobe vboxdrv failed. Please use 'dmesg' > to find out why ... failed! > failed! > invoke-rc.d: initscript virtualbox-ose, action "restart" failed. Are you sure your headers are correct? I tried both, the dkms build and the m-a build and both worked for me. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20101004121226.ga16...@hyperion.credativ.de
Bug#599054: [Pkg-virtualbox-devel] Bug#599054: After kernel upgrading vbox is no more usable
> I'm not about to dig into the virtualbox source, so you tell me what's > going on. I guess he was talking about the bug report. The message is this: [11016.299837] supdrvGipCreate: failed to allocate the GIP page. rc=-8 Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20101004131027.gb25...@hyperion.credativ.de
Bug#564861: 2.6.32-trunk-amd64: oopses if quota enabled
Package: linux-2.6 Version: 2.6.32-5 Severity: normal Subject almost says it all. I have quota enabled on my /home partition but opening a file on / in vi and releasing it again makes the kernel oops: Jan 12 10:54:20 feivel kernel: [ 147.999029] kernel BUG at /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/quota/dquot.c:1398! Jan 12 10:54:20 feivel kernel: [ 147.999037] invalid opcode: [#1] SMP Jan 12 10:54:20 feivel kernel: [ 147.999042] last sysfs file: /sys/devices/pci:00/:00:1c.5/:0b:00.0/net/eth0/carrier Jan 12 10:54:20 feivel kernel: [ 147.999047] CPU 7 Jan 12 10:54:20 feivel kernel: [ 147.999050] Modules linked in: radeon ttm drm_kms_helper drm agpgart i2c_algo_bit sco bridge stp bnep rfcomm l2cap crc16 ppdev lp parport advantechwdt acpi_cpufreq cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_userspace kvm_intel kvm uinput quota_v2 quota_tree fuse loop firewire_sbp2 btusb snd_hda_codec_atihdmi joydev bluetooth snd_hda_codec_idt snd_hda_intel snd_hda_codec arc4 ecb snd_hwdep uvcvideo snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi iwlagn snd_rawmidi snd_seq_midi_event snd_seq iwlcore videodev v4l1_compat v4l2_compat_ioctl32 mac80211 snd_timer snd_seq_device i2c_i801 snd cfg80211 soundcore psmouse evdev dell_laptop serio_raw pcspkr snd_page_alloc wmi i2c_core dcdbas rfkill processor battery ac ext3 jbd mbcache sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod usbhid hid sg sr_mod sd_mod cdrom crc_t10dif sdhci_pci firewire_ohci sdhci ahci video mmc_core libata firewire_core output scsi_mod ehci_hcd crc_itu_t led_class r8169 mii usbcore Jan 12 10:54:20 feivel kernel: nls_base button thermal fan thermal_sys [last unloaded: scsi_wait_scan] Jan 12 10:54:20 feivel kernel: [ 147.999193] Pid: 2683, comm: vi Not tainted 2.6.32-trunk-amd64 #1 Studio 1557 Jan 12 10:54:20 feivel kernel: [ 147.999198] RIP: 0010:[] [] dquot_transfer+0x123/0x49d Jan 12 10:54:20 feivel kernel: [ 147.999213] RSP: 0018:880134ecdd98 EFLAGS: 00010246 Jan 12 10:54:20 feivel kernel: [ 147.999217] RAX: RBX: 88012cb61d50 RCX: 7fd1a3bb9000 Jan 12 10:54:20 feivel kernel: [ 147.999222] RDX: 0002 RSI: RDI: 88012cb61d50 Jan 12 10:54:20 feivel kernel: [ 147.999227] RBP: 88012cb61ca0 R08: R09: 880134ecdee8 Jan 12 10:54:20 feivel kernel: [ 147.999232] R10: 0051 R11: R12: 0001 Jan 12 10:54:20 feivel kernel: [ 147.999236] R13: R14: 1846 R15: Jan 12 10:54:20 feivel kernel: [ 147.999242] FS: 7fd1a3b9e790() GS:8800055c() knlGS: Jan 12 10:54:20 feivel kernel: [ 147.999248] CS: 0010 DS: ES: CR0: 80050033 Jan 12 10:54:20 feivel kernel: [ 147.999252] CR2: 0044aab0 CR3: 000133919000 CR4: 26e0 Jan 12 10:54:20 feivel kernel: [ 147.999257] DR0: DR1: DR2: Jan 12 10:54:20 feivel kernel: [ 147.999262] DR3: DR6: 0ff0 DR7: 0400 Jan 12 10:54:20 feivel kernel: [ 147.999268] Process vi (pid: 2683, threadinfo 880134ecc000, task 8801349ba350) Jan 12 10:54:20 feivel kernel: [ 147.999272] Stack: Jan 12 10:54:20 feivel kernel: [ 147.999274] 8801376ca000 8801360b8068 88012cb64000 Jan 12 10:54:20 feivel kernel: [ 147.999281] <0> 8801360bd800 8112a3ad Jan 12 10:54:20 feivel kernel: [ 147.999289] <0> 88012cb61ca0 8801360bd800 8112b8be Jan 12 10:54:20 feivel kernel: [ 147.999297] Call Trace: Jan 12 10:54:20 feivel kernel: [ 147.999304] [] ? dqput+0x89/0x21a Jan 12 10:54:20 feivel kernel: [ 147.999311] [] ? dquot_initialize+0x107/0x115 Jan 12 10:54:20 feivel kernel: [ 147.999318] [] ? vfs_dq_transfer+0x6a/0x86 Jan 12 10:54:20 feivel kernel: [ 147.999334] [] ? ext3_setattr+0x9e/0x1c9 [ext3] Jan 12 10:54:20 feivel kernel: [ 147.999343] [] ? notify_change+0x180/0x2c5 Jan 12 10:54:20 feivel kernel: [ 147.999351] [] ? chown_common+0x66/0x7c Jan 12 10:54:20 feivel kernel: [ 147.999357] [] ? sys_fchown+0x5c/0x86 Jan 12 10:54:20 feivel kernel: [ 147.999367] [] ? system_call_fastpath+0x16/0x1b Jan 12 10:54:20 feivel kernel: [ 147.999372] Code: 00 48 89 ef e8 ab 3b fc ff 48 89 df 49 89 c5 e8 45 b7 1b 00 48 8b 85 00 01 00 00 48 8b 40 40 48 8b 80 88 00 00 00 48 85 c0 75 04 <0f> 0b eb fe 48 89 ef ff d0 4c 8b 30 66 ff 85 b0 00 00 00 4b 8d Jan 12 10:54:20 feivel kernel: [ 147.999425] RIP [] dquot_transfer+0x123/0x49d Jan 12 10:54:20 feivel kernel: [ 147.999433] RSP Jan 12 10:54:20 feivel kernel: [ 147.999438] ---[ end trace e24f7f473235aecb ]--- Michael -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'u
Bug#564861: 2.6.32-trunk-amd64: oopses if quota enabled
On Tue, Jan 12, 2010 at 12:54:30PM +, Ben Hutchings wrote: > Please report this upstream at <http://bugzilla.kernel.org> (Product: > File System, Component: Other) and let us know the bug number. 15051 Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658980: general: The watchdog died unexpectedly.
reassign 658980 linux-image-3.1.0-1-686-pae severity 658980 normal thanks > Feb 7 02:04:47 djuro-desktop kernel: [100141.008163] Call Trace: > Feb 7 02:04:47 djuro-desktop kernel: [100141.008175] [] ? > warn_slowpath_common+0x68/0x79 > ... This is quite obviously a kernel backtrace. I have no idea why you reported this against a user level software package. Thus I reassign it to the kernel I *think* you might be running. Also I changed the severity although I don't really know what the right serity for a kernel problem like this is. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20120207223804.ga4...@feivel.credativ.lan
Bug#660265: please include patch to select rc6 modes via kernel parameter
Package: linux-2.6
Version: 3.2.6-1
Severity: wishlist
Eugeni Dodonov from Intel proposed a patch to make rc6 modes selectable via
kernel parameter. With these patch it is possible to enable rc6 but not deep or
deepest rc6, a setting that makes ultrabooks, well at least the ASUS Zenbook,
work very reliable but still get good battery time.
It would be nice of this patch could be added to the Debian kernel.
Michael
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.5-tunerc6v1-generic (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.2.0-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.41
ii initramfs-tools [linux-initramfs-tool] 0.100
ii linux-base 3.4
ii module-init-tools 3.16-1
Versions of packages linux-image-3.2.0-1-amd64 recommends:
ii firmware-linux-free 3
Versions of packages linux-image-3.2.0-1-amd64 suggests:
pn grub-pc1.99-14
pn linux-doc-3.2
Versions of packages linux-image-3.2.0-1-amd64 is related to:
pn firmware-atheros
pn firmware-bnx2
pn firmware-bnx2x
pn firmware-brcm80211
pn firmware-intelwimax
pn firmware-ipw2x00
pn firmware-ivtv
pn firmware-iwlwifi
pn firmware-libertas
pn firmware-linux
pn firmware-linux-nonfree
pn firmware-myricom
pn firmware-netxen
pn firmware-qlogic
pn firmware-ralink
pn firmware-realtek
pn xen-hypervisor
-- debconf information excluded
>From 1c9b22f81d12d0183d14689ef4667c778a202eab Mon Sep 17 00:00:00 2001
From: Eugeni Dodonov
Date: Tue, 3 Jan 2012 15:25:08 -0200
Subject: [PATCH] drm/i915: allow to select rc6 modes via kernel parameter
This allows to select which rc6 modes are to be used via kernel parameter,
via a bitmask parameter. E.g.:
- to enable rc6, i915_enable_rc6=1
- to enable rc6 and deep rc6, i915_enable_rc6=3
- to enable rc6 and deepest rc6, use i915_enable_rc6=5
- to enable rc6, deep and deepest rc6, use i915_enable_rc6=7
Note that this changes behavior - previously, value of 1 would enable both
RC6 and deep RC6. Now it should only enable RC6 and deep/deepest RC6
stages must be enabled manually.
Signed-off-by: Eugeni Dodonov
---
drivers/gpu/drm/i915/i915_drv.c |6 +-
drivers/gpu/drm/i915/i915_drv.h |5 +
drivers/gpu/drm/i915/intel_display.c | 24
3 files changed, 30 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index a1103fc..b7a91db 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -66,7 +66,11 @@ MODULE_PARM_DESC(semaphores,
int i915_enable_rc6 __read_mostly = -1;
module_param_named(i915_enable_rc6, i915_enable_rc6, int, 0600);
MODULE_PARM_DESC(i915_enable_rc6,
- "Enable power-saving render C-state 6 (default: -1 (use per-chip default)");
+ "Enable power-saving render C-state 6. "
+ "Different stages can be selected via bitmask values "
+ "(0 = disable; 1 = enable rc6; 2 = enable deep rc6; 4 = enable deepest rc6). "
+ "For example, 3 would enable rc6 and deep rc6, and 7 would enable everything. "
+ "default: -1 (use per-chip default)");
int i915_enable_fbc __read_mostly = -1;
module_param_named(i915_enable_fbc, i915_enable_fbc, int, 0600);
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 554bef7..51ee407 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -997,6 +997,11 @@ struct drm_i915_file_private {
#include "i915_trace.h"
+/* RC6 modes */
+#define INTEL_RC6_ENABLE (1<<0)
+#define INTEL_RC6p_ENABLE (1<<1)
+#define INTEL_RC6pp_ENABLE (1<<2)
+
extern struct drm_ioctl_desc i915_ioctls[];
extern int i915_max_ioctl;
extern unsigned int i915_fbpercrtc __always_unused;
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index daa5743..2bcb6a5 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -7907,7 +7907,7 @@ void intel_init_emon(struct drm_device *dev)
dev_priv->corr = (lcfuse & LCFUSE_HIV_MASK);
}
-static bool intel_enable_rc6(struct drm_device *dev)
+static int intel_enable_rc6(struct drm_device *dev)
{
/*
* Respect the kernel parameter if it is set
@@ -7938,6 +7938,7 @@ void gen6_enable_rps(struct drm_i915_private *dev_priv)
u32 gt_perf_status = I915_READ(GEN6_GT_PERF_STATUS);
u32 pcu_mbox, rc6_mask = 0;
int cur_freq, min_freq, max_freq;
+ int rc6_mode;
int i;
/* Here begins a magic sequence of register writes to enable
@@ -7968,9 +7969,24 @@ void gen6_enable_rps(struct drm_i915_private *dev_priv)
I915_
Bug#660265: please include patch to select rc6 modes via kernel parameter
On Fri, Feb 17, 2012 at 08:42:43PM +, Ben Hutchings wrote: > What is the upstream status of this? AFAIK included in 3.4. > Why is it important for the user to be able to configure this, i.e. > why can't the kernel just DTRT? Why can't it be changed at run-time > like CPU power-saving? It is already configurable in 3.2, but you can only switch it on. This include RC6 but also deep RC6 which makes (some) system stop quite frequently. That's why the default is to switch it off completely. However, that gives a much higher battery drain. > Does this result in a safe default if no kernel parameter is > specified? Yes, the same as in 3.2. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20120217222124.ga4...@feivel.credativ.lan
Bug#660265: please include patch to select rc6 modes via kernel parameter
On Sat, Feb 18, 2012 at 01:46:15AM -0600, Jonathan Nieder wrote: > Under discussion[1]. Not in drm-intel-next yet[2]. Sorry, I should have double checked my information. > I suspect a different, more targetted patch[3] would do a better job > of addressing the described use case: I'm currently testing this. And yes, this one seems to solve the problem I was trying to get addressed. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20120218133836.ga22...@feivel.credativ.lan
Bug#660265: Heads-Up
I've been running a kernel with the following two patches applied for a couple days now and haven't seen a sudden shutdown since: http://lists.freedesktop.org/archives/intel-gfx/2012-February/015131.html http://lists.freedesktop.org/archives/intel-gfx/2012-February/015319.html If these could be applied that would be great. Thanks. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20120226123507.ga15...@feivel.credativ.lan
Bug#660265: Heads-Up
On Sun, Feb 26, 2012 at 03:55:38PM +, Ben Hutchings wrote: > These will be in the next upload. I haven't added the patch to make use Great! Thanks a lot! > of the various modes configurable, but I think all you really wanted was > to be able to enable RC6 without RC6+ and that's what you will get. So > I'm considering these changes to close the bug. Yes, you're absolutely correct. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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/20120227093238.gb19...@feivel.credativ.lan
