[Suspend2-devel] oops during compile after resume
devsku at gmail.com
Sat Jul 22 21:17:54 UTC 2006
but you at least saw problems while running it. I didn't even see anything
wrong, let alone it trying to repair it.
Could IRQ sharing be a problem because right now libata shares IRQ with
nvidia card and eth0. I have no idea why the IRQs are shared anyway.
$ cat /proc/interrupts
217: 1979676 6 IO-APIC-level libata, eth0
225: 197114 10 IO-APIC-level libata, NVidia CK804
On 7/22/06, Johannes Berg <johannes at sipsolutions.net> wrote:
> On Sat, 2006-07-22 at 11:44 -0700, Sunil Kumar wrote:
> > This is with 2.2.7 with kernel 22.214.171.124.
> > I forced a full fsck on the next boot and no problems were found with
> > the filesystem.
> Don't count on that too much. I had a weird problem recently:
> EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory
> #283460: rec_len % 4 != 0 - offset=0, inode=1969317987, rec_len=25646,
> Aborting journal on device sda1.
> ext3_abort called.
> EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted
> Remounting filesystem read-only
> EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has
> EXT3-fs error (device sda1) in start_transaction: Journal has aborted
> e2fsck did *NOT* repair this, I had it 4 hours later exactly the same.
> The second time around, e2fsck did detect and repair it though. I know,
> very strange, but I actually have the whole session saved in a log file
> so I know :)
> -----BEGIN PGP SIGNATURE-----
> Comment: Johannes Berg (powerbook)
> -----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the TuxOnIce-devel