On Friday 30 June 2006 10:21, Daniel O'Connor wrote: > I have an odd problem with 6.1 where it panics, and then when it reboots > the system hangs solid just after printing how much memory is in the > system, the only way out is the reset switch. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xb6 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0512564 > stack pointer = 0x28:0xdea06b1c > frame pointer = 0x28:0xdea06b4c
I got another one in 'rtorrent' (BitTorrent client) with exactly the same
stack & frame pointer and stack trace.
#7 0xc0512564 in soo_poll (fp=0x54, events=-557274220, active_cred=0xdec8ab84,
td=0x122) at /data/src/sys/kern/sys_socket.c:232
232 {
Current language: auto; currently c
(kgdb) list
227 soo_poll(fp, events, active_cred, td)
228 struct file *fp;
229 int events;
230 struct ucred *active_cred;
231 struct thread *td;
232 {
233 struct socket *so = fp->f_data;
234 int error;
235
236 NET_LOCK_GIANT();
(kgdb) print so
$1 = (struct socket *) 0xc48f8300
(kgdb) print fp
$2 = (struct file *) 0x54
(kgdb) print fp->f_data
Cannot access memory at address 0x60
(kgdb) up
#8 0xc050cff1 in kern_select (td=0xc48f8300, nd=290, fd_in=0x8122000,
fd_ou=0x8122400, fd_ex=0x8122800, tvp=0xdec8acd0)
at /data/src/sys/kern/sys_generic.c:763
763 error = selscan(td, ibits, obits, nd);
(kgdb) print td
$3 = (struct thread *) 0xc48f8300
(kgdb) print ibits
$4 = {0xdec8ac1c, 0xdec8ac44, 0xdec8ac6c}
(kgdb) print obits
$5 = {0xdec8aba4, 0xdec8abcc, 0xdec8abf4}
(kgdb) print nd
$6 = 290
...
I don't know where the stack frame for selscan went..
Does anyone else see this? It is fairly frequent and is getting a bit
frustrating :)
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pgp8i2R6eUidm.pgp
Description: PGP signature
