Re: BUG: unable to handle kernel paging request at virtual address

2008-01-22 Thread Alexander Shaduri
On Sun, 6 Jan 2008 00:20:50 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > On Sun, Jan 06, 2008 at 12:30:34AM +0400, Alexander Shaduri wrote: > > > Get a serial console? Take another box, plug e.g. pl2303-based > > > usb-to-serial (several bucks these days

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-22 Thread Alexander Shaduri
On Sun, 6 Jan 2008 00:20:50 +0300 Alexey Dobriyan [EMAIL PROTECTED] wrote: On Sun, Jan 06, 2008 at 12:30:34AM +0400, Alexander Shaduri wrote: Get a serial console? Take another box, plug e.g. pl2303-based usb-to-serial (several bucks these days) into it, stick null-modem convertor

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
On Sun, 6 Jan 2008 00:20:50 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > netconsole should be more quick: Thanks a lot for the tip, I'll try that. Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
> Get a serial console? Take another box, plug e.g. pl2303-based > usb-to-serial (several bucks these days) into it, stick null-modem > convertor (ditto) on its serial end and attach to ttyS0 on the > victim. console=ttyS0 on victim, something like minicom on watcher > and tell it to capture

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
On Sat, 5 Jan 2008 15:34:25 +0100 Mikael Pettersson <[EMAIL PROTECTED]> wrote: > This kernel is tainted by the nvidia module... I know that, but as I wrote in the original message, the hangs occur without it too. I just tested it today. Had to leave it running (in vesa framebuffer mode), without

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
On Sat, 5 Jan 2008 09:10:12 + Al Viro <[EMAIL PROTECTED]> wrote: > and we have q->page == 0x48464443. Seeing how we assign that sucker, that > smells like we've got a page on quicklist with {0x43, 0x44, 0x46, 0x48} > in its first 4 bytes. Instead of having address of the next page stored >

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
On Sat, 5 Jan 2008 09:10:12 + Al Viro [EMAIL PROTECTED] wrote: and we have q-page == 0x48464443. Seeing how we assign that sucker, that smells like we've got a page on quicklist with {0x43, 0x44, 0x46, 0x48} in its first 4 bytes. Instead of having address of the next page stored in

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
On Sat, 5 Jan 2008 15:34:25 +0100 Mikael Pettersson [EMAIL PROTECTED] wrote: This kernel is tainted by the nvidia module... I know that, but as I wrote in the original message, the hangs occur without it too. I just tested it today. Had to leave it running (in vesa framebuffer mode), without

Re: BUG: unable to handle kernel paging request at virtual address

2008-01-05 Thread Alexander Shaduri
On Sun, 6 Jan 2008 00:20:50 +0300 Alexey Dobriyan [EMAIL PROTECTED] wrote: netconsole should be more quick: Thanks a lot for the tip, I'll try that. Alexander -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo

BUG: unable to handle kernel paging request at virtual address

2008-01-04 Thread Alexander Shaduri
I got the following message, shortly followed by a system hang. BUG: unable to handle kernel paging request at virtual address 48464443 (see the oops below). I've been getting kernel oopses for quite some time now, ever since I got a new computer (several months now). The problem manifests

BUG: unable to handle kernel paging request at virtual address

2008-01-04 Thread Alexander Shaduri
I got the following message, shortly followed by a system hang. BUG: unable to handle kernel paging request at virtual address 48464443 (see the oops below). I've been getting kernel oopses for quite some time now, ever since I got a new computer (several months now). The problem manifests