| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20121021002424.GA16247@liondog.tnic>
Date: Sun, 21 Oct 2012 02:24:24 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Artem S. Tashkinov" <t.artem@...os.com>
Cc: pavel@....cz, linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
security@...nel.org, linux-media@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when
visiting a particular website
On Sat, Oct 20, 2012 at 11:15:17PM +0000, Artem S. Tashkinov wrote:
> You don't get me - I have *no* VirtualBox (or any proprietary) modules
> running
Ok, good. We got that out of the way - I wanted to make sure after you
replied with two other possibilities of the system freezing.
> - but I can reproduce this problem using *the same system running
> under* VirtualBox in Windows 7 64.
That's windoze as host and linux as a guest, correct?
If so, that's virtualbox's problem, I'd say.
> It's almost definitely either a USB driver bug or video4linux driver
> bug:
And you're assuming that because the freeze happens when using your usb
webcam, correct? And not otherwise?
Maybe you can describe in more detail what exactly you're doing so that
people could try to reproduce your issue.
> I'm CC'ing linux-media and linux-usb mailing lists, the problem is described here:
> https://lkml.org/lkml/2012/10/20/35
> https://lkml.org/lkml/2012/10/20/148
Yes, good idea. Maybe the folks there have some more ideas how to debug
this.
I'm leaving in the rest for reference.
What should be pointed out, though, is that you don't have any more
random corruptions causing oopses now that virtualbox is gone. The
freeze below is a whole another issue.
Thanks.
> Here are the last lines from my dmesg (with usbmon loaded):
>
> [ 292.164833] hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0002
> [ 292.168091] ehci_hcd 0000:00:1f.5: GetStatus port:1 status 00100a 0 ACK POWER sig=se0 PEC CSC
> [ 292.172063] hub 1-0:1.0: port 1, status 0100, change 0003, 12 Mb/s
> [ 292.174883] usb 1-1: USB disconnect, device number 2
> [ 292.178045] usb 1-1: unregistering device
> [ 292.183539] usb 1-1: unregistering interface 1-1:1.0
> [ 292.197034] usb 1-1: unregistering interface 1-1:1.1
> [ 292.204317] usb 1-1: unregistering interface 1-1:1.2
> [ 292.234519] usb 1-1: unregistering interface 1-1:1.3
> [ 292.236175] usb 1-1: usb_disable_device nuking all URBs
> [ 292.364429] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
> [ 294.364279] hub 1-0:1.0: hub_suspend
> [ 294.366045] usb usb1: bus auto-suspend, wakeup 1
> [ 294.367375] ehci_hcd 0000:00:1f.5: suspend root hub
> [ 296.501084] usb usb1: usb wakeup-resume
> [ 296.508311] usb usb1: usb auto-resume
> [ 296.509833] ehci_hcd 0000:00:1f.5: resume root hub
> [ 296.560149] hub 1-0:1.0: hub_resume
> [ 296.562240] ehci_hcd 0000:00:1f.5: GetStatus port:1 status 001003 0 ACK POWER sig=se0 CSC CONNECT
> [ 296.566141] hub 1-0:1.0: port 1: status 0501 change 0001
> [ 296.670413] hub 1-0:1.0: state 7 ports 8 chg 0002 evt 0000
> [ 296.673222] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
> [ 297.311720] usb 1-1: new high-speed USB device number 3 using ehci_hcd
> [ 300.547237] usb 1-1: skipped 1 descriptor after configuration
> [ 300.549443] usb 1-1: skipped 4 descriptors after interface
> [ 300.552273] usb 1-1: skipped 2 descriptors after interface
> [ 300.556499] usb 1-1: skipped 1 descriptor after endpoint
> [ 300.559392] usb 1-1: skipped 2 descriptors after interface
> [ 300.560960] usb 1-1: skipped 1 descriptor after endpoint
> [ 300.562169] usb 1-1: skipped 2 descriptors after interface
> [ 300.563440] usb 1-1: skipped 1 descriptor after endpoint
> [ 300.564639] usb 1-1: skipped 2 descriptors after interface
> [ 300.565828] usb 1-1: skipped 2 descriptors after endpoint
> [ 300.567084] usb 1-1: skipped 9 descriptors after interface
> [ 300.569205] usb 1-1: skipped 1 descriptor after endpoint
> [ 300.570484] usb 1-1: skipped 53 descriptors after interface
> [ 300.595843] usb 1-1: default language 0x0409
> [ 300.602503] usb 1-1: USB interface quirks for this device: 2
> [ 300.605700] usb 1-1: udev 3, busnum 1, minor = 2
> [ 300.606959] usb 1-1: New USB device found, idVendor=046d, idProduct=081d
> [ 300.610298] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=1
> [ 300.613742] usb 1-1: SerialNumber: 48C5D2B0
> [ 300.617703] usb 1-1: usb_probe_device
> [ 300.620594] usb 1-1: configuration #1 chosen from 1 choice
> [ 300.639218] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> [ 300.640736] snd-usb-audio 1-1:1.0: usb_probe_interface
> [ 300.642307] snd-usb-audio 1-1:1.0: usb_probe_interface - got id
> [ 301.050296] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
> [ 301.054897] usb 1-1: adding 1-1:1.2 (config #1, interface 2)
> [ 301.056934] uvcvideo 1-1:1.2: usb_probe_interface
> [ 301.058072] uvcvideo 1-1:1.2: usb_probe_interface - got id
> [ 301.059395] uvcvideo: Found UVC 1.00 device <unnamed> (046d:081d)
> [ 301.090173] input: UVC Camera (046d:081d) as /devices/pci0000:00/0000:00:1f.5/usb1/1-1/1-1:1.2/input/input7
> [ 301.111289] usb 1-1: adding 1-1:1.3 (config #1, interface 3)
> [ 301.131207] usb 1-1: link qh16-0001/f48d64c0 start 2 [1/0 us]
> [ 301.137066] usb 1-1: unlink qh16-0001/f48d64c0 start 2 [1/0 us]
> [ 301.156451] ehci_hcd 0000:00:1f.5: reused qh f48d64c0 schedule
> [ 301.158310] usb 1-1: link qh16-0001/f48d64c0 start 2 [1/0 us]
> [ 301.160238] usb 1-1: unlink qh16-0001/f48d64c0 start 2 [1/0 us]
> [ 301.196606] set resolution quirk: cval->res = 384
> [ 371.309569] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
> [ 390.729568] ehci_hcd 0000:00:1f.5: reused qh f48d64c0 schedule
> f5ade900 2296555[ 390.730023] usb 1-1: link qh16-0001/f48d64c0 start 2 [1/0 us]
> 437 S Ii:1:003:7[ 390.736394] usb 1-1: unlink qh16-0001/f48d64c0 start 2 [1/0 us]
> -115:128 16 <
> f5ade900 2296566256 C Ii:1:003:7 -2:128 0
> [ 391.100896] ehci_hcd 0000:00:1f.5: reused qh f48d64c0 schedule
> [ 391.103188] usb 1-1: link qh16-0001/f48d64c0 start 2 [1/0 us]
> f5ade900 2296926929 S Ii:1:003:7[ 391.104889] usb 1-1: unlink qh16-0001/f48d64c0 start 2 [1/0 us]
> -115:128 16 <
> f5ade900 2296937889 C Ii:1:003:7 -2:128 0
> f5272300 2310382508 S Co:1:003:0 s 01 0b 0004 0001 0000 0
> f5272300 2310407888 C Co:1:003:0 0 0
> f5272300 2310408051 S Co:1:003:0 s 22 01 0100 0086 0003 3 = 80bb00
> f5272300 2310412456 C Co:1:003:0 0 3 >
> f5272300 2310412521 S Ci:1:003:0 s a2 81 0100 0086 0003 3 <
> f5272300 2310415909 C Ci:1:003:0 0 0
> f5272300 2310418133 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f5272600 2310418219 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f52720c0 2310418239 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f5272a80 2310418247 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f5272480 2310418256 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f52723c0 2310418264 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f5272d80 2310418272 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
> f5272b40 2310418280 S Zi:1:003:6 -115:8:0 1 -18:0:100 100 <
>
> Hard freeze with 100% CPU usage at this point as if some driver got into an
> infinite loop or something.
>
> All debug options from https://lkml.org/lkml/2012/10/20/116 are enabled, but
> serial console is empty.
>
> Best wishes,
>
> Artem
>
>
> On Oct 21, 2012, Borislav Petkov wrote:
>
> > I don't think that's the problem - I rather suspect the fact that he's
> > using virtualbox which is causing random corruptions by writing to
> > arbitrary locations.
> >
> >
> >
> > please remove virtualbox completely from your system, rebuild the kernel
> > and make sure the virtualbox kernel modules don't get loaded - simply
> > delete them so that they are completely gone; *and* *then* retest again.
>
>
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists