Bug#802764: virtualbox-source: fucks up my kernel's modules

[Gianfranco Costamagna]

Hi,

>Well I had no modules for framebuffer, so Xorg would not run because of "no 
>video card" and no modules for network interfaces.
we don't provide any graphical kernel module AFAIK, so I don't think we can mess
with framebuffer.


TBH we have a guest module that might have some graphical interaction, but 
nothing
on host.

cheers,

G.

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Salvo Tomaselli]

> Creating a kernel module has nothing in common with not booting a system, 
unless you get a kernel panic or similar.

Well I had no modules for framebuffer, so Xorg would not run because of "no 
video card" and no modules for network interfaces.

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Gianfranco Costamagna]

Creating a kernel module has nothing in common with not booting a system, 
unless you get a kernel panic or similar.

I tried to reproduce and I have been able to do so.

I also talked with upstream, they will make some changes in making the dkms 
more robust, but nothing should have changed in this
particular release.

cheers,

G.




Il Sabato 24 Ottobre 2015 13:33, Salvo Tomaselli  ha 
scritto:



It is the only recent package that touched kernel modules.
Il 24/ott/2015 12:09, "Ritesh Raj Sarraf"  ha scritto:

Control: tag -1 +moreinfo
>Control: severity -1 normal
>
>
>For a bug with severity "critical", you should provide appropriate
>information. Otherwise it does not justify the severity.
>
>
>Your logs have nothing mentioned about vbox. So I don't understand how
>you'd point this as a vbox problem.
>
>
>On Fri, 2015-10-23 at 11:14 +0200, Salvo Tomaselli wrote:
>> Dear Maintainer,
>>
>> apparently upgrading virtualbox messed with my custom built kernel's
>> modules,
>> and so if I boot with that kernel I no longer have a video card and I
>> am not
>> able to start Xorg.
>>
>> Also, the text on my console is unusually huge.
>--
>Ritesh Raj Sarraf
>RESEARCHUT - http://www.researchut.com
>"Necessity is the mother of invention."
>
>

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Ritesh Raj Sarraf]

Control: tag -1 +moreinfo
Control: severity -1 normal


For a bug with severity "critical", you should provide appropriate
information. Otherwise it does not justify the severity.


Your logs have nothing mentioned about vbox. So I don't understand how
you'd point this as a vbox problem.


On Fri, 2015-10-23 at 11:14 +0200, Salvo Tomaselli wrote:
> Dear Maintainer,
> 
> apparently upgrading virtualbox messed with my custom built kernel's
> modules,
> and so if I boot with that kernel I no longer have a video card and I
> am not
> able to start Xorg.
> 
> Also, the text on my console is unusually huge.
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



signature.asc
Description: This is a digitally signed message part

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Salvo Tomaselli]

It is the only recent package that touched kernel modules.
Il 24/ott/2015 12:09, "Ritesh Raj Sarraf"  ha scritto:

> Control: tag -1 +moreinfo
> Control: severity -1 normal
>
>
> For a bug with severity "critical", you should provide appropriate
> information. Otherwise it does not justify the severity.
>
>
> Your logs have nothing mentioned about vbox. So I don't understand how
> you'd point this as a vbox problem.
>
>
> On Fri, 2015-10-23 at 11:14 +0200, Salvo Tomaselli wrote:
> > Dear Maintainer,
> >
> > apparently upgrading virtualbox messed with my custom built kernel's
> > modules,
> > and so if I boot with that kernel I no longer have a video card and I
> > am not
> > able to start Xorg.
> >
> > Also, the text on my console is unusually huge.
> --
> Ritesh Raj Sarraf
> RESEARCHUT - http://www.researchut.com
> "Necessity is the mother of invention."
>
>

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Salvo Tomaselli]

Package: virtualbox-source
Version: 5.0.8-dfsg-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

apparently upgrading virtualbox messed with my custom built kernel's modules,
and so if I boot with that kernel I no longer have a video card and I am not
able to start Xorg.

Also, the text on my console is unusually huge.

Attaching my dmesg.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.6a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virtualbox-source depends on:
ii  build-essential   12.1
ii  bzip2 1.0.6-8
ii  debhelper 9.20151005
ii  kbuild1:0.1.9998svn2786+dfsg-1
ii  module-assistant  0.11.8

Versions of packages virtualbox-source recommends:
ii  virtualbox  5.0.8-dfsg-1

virtualbox-source suggests no packages.

-- no debconf information
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.2.1a (root@hal9000) (gcc version 5.2.1 20150911 
(Debian 5.2.1-17) ) #1 SMP PREEMPT Mon Sep 28 13:40:48 CEST 2015
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.1a root=/dev/sda2 ro 
pcie_aspm=force i915.enable_rc6=4
[0.00] Disabled fast string operations
[0.00] x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100
[0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 0x340 
bytes, using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable
[0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xba99efff] usable
[0.00] BIOS-e820: [mem 0xba99f000-0xbae9efff] reserved
[0.00] BIOS-e820: [mem 0xbae9f000-0xbaf9efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbaf9f000-0xbaffefff] ACPI data
[0.00] BIOS-e820: [mem 0xbafff000-0xbaff] usable
[0.00] BIOS-e820: [mem 0xbb00-0xbf9f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfe80-0xfe80] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed08000-0xfed08fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xffd8-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00013fdf] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.6 present.
[0.00] DMI: LENOVO 11433LG/11433LG, BIOS 8HET41WW(1.23) 01/13/2012
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x13fe00 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0FFC0 mask FFFC0 write-protect
[0.00]   1 base 0 mask F8000 write-back
[0.00]   2 base 08000 mask FC000 write-back
[0.00]   3 base 0BC00 mask FFC00 uncachable
[0.00]   4 base 0BB00 mask FFF00 uncachable
[0.00]   5 base 1 mask FC000 write-back
[0.00]   6 base 13FE0 mask FFFE0 uncachable
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0xbb000 max_arch_pfn = 0x4
[0.00] Base memory trampoline at [88097000] 97000 size 24576
[0.00] reserving inaccessible SNB gfx pages
[0.00] init_memory_mapping: [mem 0x-0x000f]
[