Hi again

Looks like everything is fine, i will deploy at few NAS today night and will 
see if there any issues. Both oops what i gave, is it related to this bug?
No need to dig anything else?

On Tue, 27 Mar 2007 17:10:36 +0200, Patrick McHardy wrote

Denys wrote:

quoted

Mar 26 21:20:04 ROUTER-75 [  551.481081] BUG: unable to handle kernel 

NULL 

quoted

pointer dereference
Mar 26 21:20:04 ROUTER-75 at virtual address 00000074
Mar 26 21:20:04 ROUTER-75 [  551.481187]  printing eip:
Mar 26 21:20:04 ROUTER-75 [  551.481236] f8a11df1
Mar 26 21:20:04 ROUTER-75 [  551.481289] *pde = 00000000
Mar 26 21:20:04 ROUTER-75 [  551.481340] Oops: 0000 [#1]
Mar 26 21:20:04 ROUTER-75 [  551.481384]
Mar 26 21:20:04 ROUTER-75 SMP
Mar 26 21:20:04 ROUTER-75
Mar 26 21:20:04 ROUTER-75 [  551.481549] Modules linked in:
.... long module list
ar 26 21:20:04 ROUTER-75 [  551.485237] CPU:    0
Mar 26 21:20:04 ROUTER-75 [  551.485238] EIP:    0060:[<f8a11df1>]    Not 
tainted VLI
Mar 26 21:20:04 ROUTER-75 [  551.485239] EFLAGS: 00010282   (2.6.20.3-

build-

quoted

0001 #4)
Mar 26 21:20:04 ROUTER-75 [  551.485438] EIP is at htb_qlen_notify+0x9/

0x79 

quoted

[sch_htb]

Oops, that seems to be my fault. Can you please try the attached patch?
To reproduce the problem you need to have packets queued while the
device is going down, so please make sure that is true by flooding
the device or something like that.

--
Virtual ISP S.A.L.