Re: Re: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Sun, 21 Oct 2012, Artem S. Tashkinov wrote:
dmesg messages up to a crash can be seen here:
https://bugzilla.kernel.org/attachment.cgi?id=84221
The first problem in the log is endpoint list corruption. Here's a
debugging patch which should provide a little more information.
Alan Stern
drivers/usb/core/hcd.c | 36
1 file changed, 36 insertions(+)
Index: usb-3.6/drivers/usb/core/hcd.c
===
--- usb-3.6.orig/drivers/usb/core/hcd.c
+++ usb-3.6/drivers/usb/core/hcd.c
@@ -1083,6 +1083,8 @@ EXPORT_SYMBOL_GPL(usb_calc_bus_time);
/*-*/
+static bool list_error;
+
/**
* usb_hcd_link_urb_to_ep - add an URB to its endpoint queue
* @hcd: host controller to which @urb was submitted
@@ -1126,6 +1128,20 @@ int usb_hcd_link_urb_to_ep(struct usb_hc
*/
if (HCD_RH_RUNNING(hcd)) {
urb-unlinked = 0;
+
+ {
+ struct list_head *cur = urb-ep-urb_list;
+ struct list_head *prev = cur-prev;
+
+ if (prev-next != cur !list_error) {
+ list_error = true;
+ dev_err(urb-dev-dev,
+ ep %x list add corruption: %p %p %p\n,
+ urb-ep-desc.bEndpointAddress,
+ cur, prev, prev-next);
+ }
+ }
+
list_add_tail(urb-urb_list, urb-ep-urb_list);
} else {
rc = -ESHUTDOWN;
@@ -1193,6 +1209,26 @@ void usb_hcd_unlink_urb_from_ep(struct u
{
/* clear all state linking urb to this dev (and hcd) */
spin_lock(hcd_urb_list_lock);
+ {
+ struct list_head *cur = urb-urb_list;
+ struct list_head *prev = cur-prev;
+ struct list_head *next = cur-next;
+
+ if (prev-next != cur !list_error) {
+ list_error = true;
+ dev_err(urb-dev-dev,
+ ep %x list del corruption prev: %p %p %p\n,
+ urb-ep-desc.bEndpointAddress,
+ cur, prev, prev-next);
+ }
+ if (next-prev != cur !list_error) {
+ list_error = true;
+ dev_err(urb-dev-dev,
+ ep %x list del corruption next: %p %p %p\n,
+ urb-ep-desc.bEndpointAddress,
+ cur, next, next-prev);
+ }
+ }
list_del_init(urb-urb_list);
spin_unlock(hcd_urb_list_lock);
}
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Sun, Oct 21, 2012 at 01:57:21AM +, Artem S. Tashkinov wrote: The freeze happens on my *host* Linux PC. For an experiment I decided to check if I could reproduce the freeze under a virtual machine - it turns out the Linux kernel running under it also freezes. I know that - but a freeze != oops - at least not necessarily. Which means it could very well be a different issue now that vbox is gone. Or, it could be the same issue with different incarnations: with vbox you get the corruptions and without it, you get the freezes. I'm assuming you do the same flash player thing in both cases? Here's a crazy idea: can you try to reproduce it in KVM? Thanks. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Oct 21, 2012, Borislav Petkov wrote: On Sun, Oct 21, 2012 at 01:57:21AM +, Artem S. Tashkinov wrote: The freeze happens on my *host* Linux PC. For an experiment I decided to check if I could reproduce the freeze under a virtual machine - it turns out the Linux kernel running under it also freezes. I know that - but a freeze != oops - at least not necessarily. Which means it could very well be a different issue now that vbox is gone. Or, it could be the same issue with different incarnations: with vbox you get the corruptions and without it, you get the freezes. I'm assuming you do the same flash player thing in both cases? Here's a crazy idea: can you try to reproduce it in KVM? OK, dismiss VBox altogether - it has a very buggy USB implementation, thus it just hangs when trying to access my webcam. What I've found out is that my system crashes *only* when I try to enable usb-audio (from the same webcam) - I still have no idea how to capture a panic message, but I ran while :; do dmesg -c; done in xterm, then I got like thousands of messages and I photographed my monitor: http://imageshack.us/a/img685/9452/panicz.jpg list_del corruption. prev-next should be ... but was ... I cannot show you more as I have no serial console to use :( and the kernel doesn't have enough time to push error messages to rsyslog and fsync /var/log/messages -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Sun, 21 Oct 2012, Artem S. Tashkinov wrote: What I've found out is that my system crashes *only* when I try to enable usb-audio (from the same webcam) - I still have no idea how to capture a panic message, but I ran while :; do dmesg -c; done in xterm, then I got like thousands of messages and I photographed my monitor: http://imageshack.us/a/img685/9452/panicz.jpg list_del corruption. prev-next should be ... but was ... I cannot show you more as I have no serial console to use :( and the kernel doesn't have enough time to push error messages to rsyslog and fsync /var/log/messages Is it possible to use netconsole? The screenshot above appears to be the end of a long series of error messages, which isn't too useful. The most important information is in the first error. Alan Stern -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Sun, Oct 21, 2012 at 11:59:36AM +, Artem S. Tashkinov wrote: http://imageshack.us/a/img685/9452/panicz.jpg list_del corruption. prev-next should be ... but was ... Btw, this is one of the debug options I told you to enable. I cannot show you more as I have no serial console to use :( and the kernel doesn't have enough time to push error messages to rsyslog and fsync /var/log/messages I already told you how to catch that oops: boot with pause_on_oops=600 on the kernel command line and photograph the screen when the first oops happens. This'll show us where the problem begins. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Oct 21, 2012, Borislav Petkov b...@alien8.de wrote:
On Sun, Oct 21, 2012 at 11:59:36AM +, Artem S. Tashkinov wrote:
http://imageshack.us/a/img685/9452/panicz.jpg
list_del corruption. prev-next should be ... but was ...
Btw, this is one of the debug options I told you to enable.
I cannot show you more as I have no serial console to use :( and the kernel
doesn't have enough time to push error messages to rsyslog and fsync
/var/log/messages
I already told you how to catch that oops: boot with pause_on_oops=600
on the kernel command line and photograph the screen when the first oops
happens. This'll show us where the problem begins.
This option didn't have any effect, or maybe it's because it's such a serious
crash
the kernel has no time to actually print an ooops/panic message.
dmesg messages up to a crash can be seen here:
https://bugzilla.kernel.org/attachment.cgi?id=84221
I dumped them using this application:
$ cat scat.c
#include stdio.h
#include stdlib.h
#include unistd.h
#include string.h
#include sys/types.h
#include sys/stat.h
#include fcntl.h
#define O_LARGEFILE 010
#define BUFFER 4096
#define __USE_FILE_OFFSET64 1
#define __USE_LARGEFILE64 1
int main(int argc, char *argv[])
{
int fd_out;
int64_t bytes_read;
void *buffer;
if (argc!=2) {
printf(Usage is: scat destination\n);
return 1;
}
buffer = malloc(BUFFER * sizeof(char));
if (buffer == NULL) {
printf(Error: can't allocate buffers\n);
return 2;
}
memset(buffer, 0, BUFFER);
printf(Dumping to \%s\ ... , argv[1]);
fflush(NULL);
if ((fd_out = open64(argv[1], O_WRONLY | O_LARGEFILE | O_SYNC |
O_NOFOLLOW, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH)) == -1) {
printf(Error: destination file can't be created\n);
perror(open() );
return 2;
}
bytes_read = 1;
while (bytes_read) {
bytes_read = fread(buffer, sizeof(char), BUFFER, stdin);
if (write(fd_out, (void *) buffer, bytes_read) != bytes_read)
{
printf(Error: can't write data to the destination
file! Possibly a target disk is full\n);
return 3;
}
}
close(fd_out);
printf( OK\n);
return 0;
}
I ran it this way: while :; do dmesg -c; done | scat /dev/sda11 (yes, straight
to a hdd partition to eliminate a FS cache)
Don't judge me harshly - I'm not a programmer.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Sun, Oct 21, 2012 at 07:49:01PM +, Artem S. Tashkinov wrote: I ran it this way: while :; do dmesg -c; done | scat /dev/sda11 (yes, straight to a hdd partition to eliminate a FS cache) Well, I'm no fs guy but this should still go through the buffer cache. I think the O_SYNC flag makes sure it all lands on the partition in time. Oh well, it doesn't matter. Don't judge me harshly - I'm not a programmer. If you wrote that and you're not a programmer, it certainly looks cool, good job!. [ Btw, don't forget to free(buffer) at the end. ] Also, there was a patchset recently which added a blockconsole method to the kernel with which you can do something like that in a generic way. Back to the issue at hand: it looks like ehci_hcd is causing some list corruptions, maybe coming from the uvcvideo or whatever. I think the usb people will have a better idea. Btw, is there any particular reason you're running a 32-bit kernel? Thanks. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
You don't get me - I have *no* VirtualBox (or any proprietary) modules running - but I can reproduce this problem using *the same system running under* VirtualBox in Windows 7 64. It's almost definitely either a USB driver bug or video4linux driver bug: 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 Here are the last lines from my dmesg (with usbmon loaded): [ 292.164833] hub 1-0:1.0: state 7 ports 8 chg evt 0002 [ 292.168091] ehci_hcd :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 :00:1f.5: suspend root hub [ 296.501084] usb usb1: usb wakeup-resume [ 296.508311] usb usb1: usb auto-resume [ 296.509833] ehci_hcd :00:1f.5: resume root hub [ 296.560149] hub 1-0:1.0: hub_resume [ 296.562240] ehci_hcd :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 [ 296.673222] hub 1-0:1.0: port 1, status 0501, change , 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/pci:00/: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 :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 :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 :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 0 f5272300 2310407888 C Co:1:003:0 0 0 f5272300 2310408051 S Co:1:003:0 s 22 01 0100
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 +, 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 evt 0002 [ 292.168091] ehci_hcd :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 :00:1f.5: suspend root hub [ 296.501084] usb usb1: usb wakeup-resume [ 296.508311] usb usb1: usb auto-resume [ 296.509833] ehci_hcd :00:1f.5: resume root hub [ 296.560149] hub 1-0:1.0: hub_resume [ 296.562240] ehci_hcd :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 [ 296.673222] hub 1-0:1.0: port 1, status 0501, change , 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/pci:00/: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 :00:1f.5: reused qh f48d64c0 schedule [ 301.158310] usb 1-1: link qh16-0001/f48d64c0 start 2 [1/0 us] [
Re: Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Oct 21, 2012, Borislav Petkov wrote: On Sat, Oct 20, 2012 at 11:15:17PM +, 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? Exactly. If so, that's virtualbox's problem, I'd say. I can reproduce it on my host *alone* as I said in the very first message - never before I tried to run my Linux in a virtual machine. Please, just forget about VirtualBox - it has nothing to do with this problem. 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? Yes, like I said earlier - only when I try to access its settings using Adobe Flash the system crashes/freezes. Maybe you can describe in more detail what exactly you're doing so that people could try to reproduce your issue. I don't think many people have the same webcam so it's going to be a problem. It can be reproduced easily - just open Flash Settings in Google Chrome 22. The crash will occur immediately. 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. The freeze happens on my *host* Linux PC. For an experiment I decided to check if I could reproduce the freeze under a virtual machine - it turns out the Linux kernel running under it also freezes. Artem -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Re: A reliable kernel panic (3.6.2) and system crash when visiting a particular website
On Sat, 20 Oct 2012, Artem S. Tashkinov wrote: You don't get me - I have *no* VirtualBox (or any proprietary) modules running - but I can reproduce this problem using *the same system running under* VirtualBox in Windows 7 64. It's almost definitely either a USB driver bug or video4linux driver bug: Does the same thing happen with earlier kernel versions? What about if you unload snd-usb-audio or ehci-hcd? Alan Stern -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
